Hourly team: review effort and forecast
Each cycle you see the completed scenarios, the time recorded and the forecast for the next stage, then approve the next work. Roles, rates, limits and the billing cycle are set in the proposal.
An example distributor shows how assessment, development, support and infrastructure contribute to the budget, with the assumptions and exclusions stated for each stage.
Example distributor: 20 staff, 100 customer accounts, one warehouse, 10,000 historical records and one accounting interface. The first workflow connects a customer order, stock reservation, portal status and exception reporting. Accounting stays in place.
| Build work | Example budget (USD) | What it covers |
|---|---|---|
| Paid assessment | $3,600–$5,400 | Workflow, source review, first-release boundary and decision brief; counted once here. |
| Detailed design | $5,400–$8,100 | Journeys, data contracts and acceptance specification beyond the assessment. |
| Modules and shared foundation | $63,900–$102,600 | Users, customers, orders, stock, portal and reports; foundation and module-level checks counted once. |
| Historical data transfer | $3,600–$6,300 | One customer/product/order import, trial runs and reconciliation; no ongoing source synchronisation. |
| Accounting interface | $4,500–$8,100 | One agreed export with acknowledgements and safe retries; accounting remains in the existing system. |
| Release validation | $3,600–$5,400 | Cross-module acceptance, permissions and recovery checks; excludes module checks already above. |
| Training and cutover | $1,800–$2,700 | Pilot walkthrough, operator guide and one launch window. |
| Delivery coordination | $3,600–$5,400 | Cross-team planning, reviews and decisions; excludes analysis and engineering above. |
| One-off subtotal | $90,000–$144,000 | Counted once; no second assessment or foundation charge in this example. |
| Operating cost | USD / month | Assumption |
|---|---|---|
| Paid support | $720–$1,440 | 16–32 hours a month of scheduled coverage, not 24/7. Coverage and commitments are set in the support plan. |
| Hosting, backups and monitoring | $250–$500 | Client-paid allowance for a small deployment; provider prices vary. |
| Licences and paid APIs | $50–$150 | Usage allowance; confirm vendor plans and volumes. |
| Monthly subtotal | $1,020–$2,090 | For twelve months: $12,240–$25,080 |
Before taxes, contingency, pre-launch hosting and later feature changes. This spans the delivery period plus twelve operating months, not cash spending in the first twelve months after signing. Billing milestones and any reserve are agreed separately.
Warranty fixes follow the agreed defect coverage and period. Paid support covers its agreed operating work. Multi-warehouse operations, autonomous AI, an accounting replacement, data remediation beyond the sample allowance and 24/7 coverage are outside this example.
Each cycle you see the completed scenarios, the time recorded and the forecast for the next stage, then approve the next work. Roles, rates, limits and the billing cycle are set in the proposal.
For the accounting interface, the fields, acknowledgement, retry behaviour and acceptance checks are agreed with the module price. A second accounting system is a change: its cost and timing are documented, approved or deferred, then the scope is updated.
Example budget, not a quote. Your proposal will include the cost of your agreed scope, integrations, data work and support.
Share your processes, the systems you use today, and what you want to improve first. Our CEO normally leads the first discussion of possible approaches and what needs investigation before an estimate.
Europe, USA, Canada & Australia