Company · How we implement

Six waypoints, then the next leg. Three gates you sign.

Six waypoints and an optional next leg, three gates where you sign, three threads that run the whole way, and a governance rhythm you can watch.

The six waypoints

Survey · 2 weeks
Chart · 2 to 4 weeks
Build · 4 to 12 weeks by tier
Rehearse · 3 to 5 weeks
Cross over · 1 to 2 weeks, plus the parallel run
Settle · 30 days

YOU SIGN ATBlueprint sign-offGo-live readiness reviewHandover sign-off

Survey

2 weeks

Understand how the business runs today and what must change

Deliverables: As-is and to-be process maps; module list; risk list; project charter naming sponsor, champion and key users
Exit: Charter signed
You provide: Function heads in workshops, 2 sessions of 3 hours per module

Chart

2 to 4 weeks

Write the map of the system before building

Deliverables: A BRD per module: current process, expected process, how the system handles it, each line marked standard, configuration or custom; the scope of each phase; the migration templates
Exit: Gate 1: Blueprint sign-off by function heads, then the CXO, then Bizmap’s implementation lead. Nothing is built before it
You provide: Reviews within 3 working days; one decision-maker per open point

Build

4 to 12 weeks by tier

Configure the standard, build the custom app

Deliverables: A configured site on staging; a custom Frappe app in your repository; a demo every two weeks on your data; the change-request log
Exit: Sprint demos accepted; scope frozen except through written change requests
You provide: Champion at ~6 hours a week; key users at demos

Rehearse

3 to 5 weeks

Prove the data, the users and the plan before anyone depends on it

Deliverables: Two migration dry runs reconciled (trial balance, stock, open AR and AP, bank); two UAT cycles on scripted scenarios with a pass rate; role-based training with a competency sign-off per role; cutover plan
Exit: Gate 2: Go-live readiness review, a written go or no-go
You provide: Clean masters in the templates by the agreed date; UAT team for two cycles of about two days; every user at training

Cross over

1 to 2 weeks, plus the parallel run

Go live without stopping the business

Deliverables: Cutover on a date you choose; a parallel run or pilot site where risk warrants it (manufacturing, hospitals); legacy system kept read-only; daily check-ins
Exit: First month-end closed in the new system
You provide: Sponsor visible on go-live day; champion on the floor

Settle

30 days

Make it stick, then hand over

Deliverables: 30 days of hypercare with agreed response times; adoption tracked as users transacting; the four-pillar governance (access control, knowledge base, health monitoring, change governance); open-items list
Exit: Gate 3: Handover sign-off to the AMC or to your own team
You provide: A quarterly review slot

Optional add-on after waypoint 6

→

Next leg

As scoped

The second deployment: phase-2 modules, integrations, AI workflows

Deliverables: A new BRD and a new plan
Exit: Same gates
You provide: Same roles

Three threads

PEOPLE

A named sponsor who attends steering; a champion and key users per function; a readiness check before each go-live wave; sponsor communication at kick-off and go-live; adoption measured as transactions per user in the first 30 days.

DATA

Cutover-date principle: migrate what you need to operate and report from day one, not history; templates issued in week 1; client owns cleansing with Bizmap’s validators; two dry runs; three reconciliations before cutover; legacy read-only after.

TRAINING

Role-based; train-the-trainer plus end-user sessions inside the two weeks before go-live; recorded; a competency sign-off per role; later waves get the same hours, never compressed.