From discovery call to running on its own.
We don't sell open-ended retainers, and we don't bill hourly. Every project runs on a fixed-fee SOW with a defined timeline, defined deliverables, and a defined go-live date — so you know exactly what you're paying for and what you're getting.
Five steps, every project.
The cadence below applies whether you're hiring us for a full Odoo migration, an Elastic rollout, or a single custom integration. The shape of the work changes; the rhythm doesn't.
Discovery
Two-week paid engagement. We map your current operations end-to-end, run a gap analysis against the target system, and produce a fixed-fee SOW that itemizes scope and hours by phase. You leave Discovery with the deliverables in hand whether or not you choose to continue.
- Process map (current state)
- Gap analysis (current → target)
- Fixed-fee SOW with phased hour estimate
- Decision document for any open scope questions
Plan
Fixed-fee SOW signed. Integration architecture mapped, data migration plan documented, project schedule built around your business calendar (no go-live the week of your trade show). Named owners on both sides. Weekly demo cadence locked.
- Signed SOW
- Integration architecture diagram
- Data migration plan + cutover runbook draft
- Project schedule with named owners
Build
Configuration, data migration, and integration work running in parallel sprints. Weekly status, weekly demos, weekly decisions. The rhythm stays predictable all the way through, with no quiet periods and no surprises right before go-live, and every demo shows working software.
- Working configuration in your staging instance
- Live integrations in test mode
- Migration scripts run against staging data
- Weekly demo recordings + decision log
Validate
UAT with your team on your data, against the scenarios that actually run your business. Order-to-cash, procure-to-pay, EDI flows, month-end close, manufacturing routings — whatever your team needs to be confident on Monday. Sign-off per scenario before any cutover happens.
- Scenario library (signed off)
- Issues triage log
- Training materials and SOPs in your docs system
- Go / no-go checkpoint document
Cutover
Go-live with hands-on support. Daily standups for the first week, transitioning to scheduled checkpoints over four weeks of hypercare. Every issue triaged and resolved by us, not handed off. Hypercare wraps with a clean handoff and a written post-mortem of what we'd refine next time.
- Live system with team running on it
- Hypercare ticket log
- Post-mortem document
- Optional ongoing portal subscription
Predictability is the deliverable.
In our experience, ERP projects rarely fail on the technology. They fail when the project loses its rhythm, and a weekly demo discipline is the cheapest insurance against that because it forces small course-corrections before they turn into large surprises.
Fixed-fee SOWs make the same point structurally. There's no incentive on either side to let scope drift quietly — we both want the same thing, which is a clean delivery on the date we agreed to.
And the four-week hypercare window is what makes the difference between “the project is over” and “the team is confident.” That's the only definition of done that actually matters.