Ops runs on a spreadsheet nobody trusts anymore.
The spreadsheet, replaced by an internal tool: a real data model, permissions, an audit trail, and the views each team actually uses. Your operations team keeps working through the transition.
The published price applies when discovery confirms the work fits the scope and requirements below. Materially different or additional work is quoted separately.
Delivery timeline and milestones
Data model and permissions agreed, with historical data migrated to staging
Core tool live in staging, with the operations team testing real workflows
In production alongside the spreadsheet, with both running in parallel
Spreadsheet retired, with audit trail and reporting live
Handover, documentation, and administrator training
What we need from you
- The current spreadsheet
- 90 minutes with the person who maintains it
- One operations user available for testing in weeks 2 and 3
Payment and scope
€8,850 to start after the €150 discovery credit. The final invoice is €9,000.
Work outside this published package, third-party subscription and usage fees, and ongoing support are excluded unless separately agreed.
Common questions
The spreadsheet, replaced by an internal tool: a real data model, permissions, an audit trail, and the views each team actually uses. Your operations team keeps working through the transition. It is delivered against dated milestones, ending with handover, documentation, and administrator training.
It is delivered in 4 weeks for a fixed €18,000, excluding VAT. Payment splits in two: €8,850 to start after the €150 discovery credit, and €9,000 on delivery. The milestones above show what ships and when.
To keep the 4 weeks timeline, we need The current spreadsheet, 90 minutes with the person who maintains it, and one operations user available for testing in weeks 2 and 3. Access and a decision-maker are what keep the build moving; without them, delivery dates slip.
That is what the €150 discovery session confirms. We check the systems, data, and integrations this build touches before committing. If it fits the published scope, the price holds. If your setup needs materially different work, we scope and price that separately rather than absorb it mid-build.
Anything outside the scope above, plus third-party subscription and usage fees and ongoing support, unless separately agreed. If discovery shows the work is materially different from this published build, it is quoted separately. You will know before we start, not halfway through.