A formal delivery method, on every project
Most failed ERP projects fail on process, not software. Ciranta runs every engagement through the same six stages, with named deliverables and a sign off before moving on.
Discover
Sign off on BRD
Design
Sign off on FRD and plan
Build
Sprint demos accepted
Test
UAT sign off
Go live
Go live approval
Hypercare
Transition to support
What you receive at each stage
| Stage | What happens | Deliverables | Gate |
|---|---|---|---|
| 1. Discover | Workshops with each department, review of current systems and data, and a Business Requirements Document (BRD). | BRD, process maps, data inventory | Sign off on BRD |
| 2. Design | Gap analysis against standard Odoo, a Functional Requirements Document (FRD), impact analysis and a baseline estimate and plan. | Gap analysis, FRD, impact analysis, project plan | Sign off on FRD and plan |
| 3. Build | Configuration, custom development and data migration, delivered in sprints with regular demos. | Configured database, custom modules, migration scripts | Sprint demos accepted |
| 4. Test | Internal QA and regression testing, then User Acceptance Testing (UAT) with your key users against agreed test scripts. | Test scripts, QA report, UAT log | UAT sign off |
| 5. Go live | Cutover plan, final data load, role based training and go live support. | Cutover plan, training material, go live checklist | Go live approval |
| 6. Hypercare | Stabilization support after go live, then handover to managed support. | Issue log, handover document | Transition to support |
Named roles on every project
Every engagement has the same four accountable roles, so there is never a question about who owns a decision.
Engagement lead
Owns the relationship, commercials and escalations. Based in the US for North American clients.
Project manager
Runs the plan, sprints, status reports, risks and change control.
Solution architect
Designs the solution, leads workshops and reviews every custom change.
QA lead
Owns test scripts, regression testing and the UAT process.
Change control
New requests are logged, estimated and approved before they are built, so scope and price stay predictable.
Transparent reporting
Weekly status reports with progress, risks, open decisions and next steps, plus a shared project workspace.
Upgrade safe build
Custom code follows Odoo standards and is peer reviewed, so the database can be upgraded later without a rewrite.
Tell us where your systems are breaking
A 30 minute call with a senior consultant. You leave with a clear scope, a recommended approach and a fixed price range.