Why do you charge for discovery?

Discovery is real work. We spend 1–2 weeks mapping your business processes, interviewing the people who actually use the systems, auditing your current stack, and documenting requirements. If we gave it away free, we’d either skip it (which is how projects fail) or absorb the cost in a bloated fixed price. Charging for it keeps discovery rigorous and keeps the delivery price honest.

When do I get a fixed price?

At the end of discovery, not before. We can give you a rough order-of-magnitude estimate based on a 30-minute call, but the fixed price comes with the design proposal at the end of discovery — because that’s the first point we genuinely know what we’re building.

What if the scope changes after the fixed price is locked?

Change requests are priced separately and transparently. Each one has its own scope note and fixed price. The original project price holds for the original scope; anything new is quoted and approved before we start it. No retroactive hourly invoices.

How do you guarantee zero data loss during migration?

Triple-backup methodology plus a dual-validation migration runbook. Every record is backed up three times, test-migrated into a staging environment, validated record-by-record against source, then re-migrated into production with final validation before cutover. We rehearse the migration at least twice before go-live.

What does "unlimited support" actually cover?

Everything operational: troubleshooting, user questions, training refreshers, configuration tweaks, minor integrations, upgrade compatibility work. It does not cover new feature development or major scope extensions — those are scoped and fixed-priced separately. In practice, unlimited means our engineers answer your calls until the issue is resolved, not a capped ticket allowance.

How long before we see value?

Most clients see the first measurable improvement within 2–4 weeks of go-live, once early automations and data consolidation kick in. Full ROI depends on the project scope but is typically in the 6–12 month window for ERP and CRM engagements.

Who do we actually work with at AMBR IT?

The same engineers from first call through to years of ongoing support. No account managers between you and the team building the thing. No offshore tier-one handoff. No hiding behind a ticket queue.

How We Work | Our Process-First Methodology

Discovery

1–2 weeks•Paid

We sit with the people who actually use the systems. We map every process end-to-end, audit your current stack, document pain points, and identify integration requirements. No platform recommendation comes out of discovery — the output is a clean understanding of the problem.

What you get out of discovery

Process maps across every in-scope workflow
Current-state systems audit
Compliance requirements register (IRAP / Essential Eight / PSPF where relevant)
Integration and data-flow diagram
Requirements document signed off by both sides

Design

1–2 weeks•Paid

Now we pick the platform. Based on the requirements — not our certifications, not a vendor’s quarterly push — we recommend the best-fit technology and architect the solution. You get a detailed design document and, critically, a fixed-price proposal for build.

What you get out of design

Platform recommendation with rationale
Solution architecture document
Data migration plan with triple-backup methodology
Detailed timeline with milestone dates
Fixed-price build proposal with scope locked

Build

6–24 weeks•Fixed price

Configuration, customisation, and integration. We work in fortnightly sprints with live demos so you see progress weekly, not quarterly. Change requests are scoped and priced transparently; the base project price holds for the base scope.

What you get out of build

Configured platform to the agreed design
Built integrations with acceptance tests
User acceptance testing environment
Training materials and runbooks
Migration rehearsal completed at least twice

Deploy

1–2 weeks•Included

The migration happens under triple backup with verification at every step. We stage the cutover, run in parallel where possible, and stay on-site or on-call for the first week after go-live. Zero data loss across 500+ projects isn’t an accident — it’s this phase done properly.

What you get out of deploy

Production data migrated and verified record-by-record
Cutover plan executed with rollback ready
Staff trained before go-live
First-week hypercare with the build team on standby
Sign-off on success criteria

Support

Ongoing•Unlimited

The same engineers who built your system answer your calls. Unlimited operational support — troubleshooting, user questions, training refreshers, configuration tweaks, integration adjustments. New feature work is scoped and fixed-priced separately.

What you get out of support

Direct access to the build team — no tier-one handoff
Quarterly system health reviews
Proactive monitoring and patch management
Annual roadmap and upgrade planning
Named technical lead for your account

How we work.Five phases, done properly.

Most systems projects fail at the start, not the end.

Every phase has a gate, every gate has deliverables.