Start small, fixed and reversible
Four ways to work together. Each one is scoped in writing before it starts, and each one leaves you with something you own.
Assessment
2–3 weeks, fixed fee
Anyone starting out with us, or anyone who needs an outside view before committing budget.
- Interviews and floor walks
- System, data and integration map
- Written findings report
- Prioritized roadmap with effort ranges
Build
6–16 weeks per phase
A defined problem with an owner and a budget, often straight out of an assessment.
- Fixed scope or phased delivery
- Working software every week
- Side-by-side cutover
- Code, docs and runbooks in your accounts
Run
Monthly retainer
Systems we built, or inherited systems, that need monitoring, fixes and steady improvement.
- Monitoring and on-call for agreed hours
- Bug fixes and small changes
- Monthly improvement backlog
- Model and cost reviews for AI features
Advisory
Monthly
Owners and executives who need senior technology judgment without a full-time hire.
- Roadmaps and budget planning
- Vendor selection and contract review
- Build versus buy decisions
- Hiring and team setup
We recommend starting with an assessment. It is the cheapest way to find out whether we are the right fit.
About pricing and contracts
Why don’t you publish prices?
Because the honest answer depends on scope, and a number without scope is misleading. The assessment is a fixed fee agreed before we start, and every build phase is quoted in writing against a defined scope before any work begins.
Do we have to start with an assessment?
No, but we recommend it. If you already have a clear, well-scoped problem and good documentation, we can quote a build directly. If not, the assessment usually saves more than it costs by stopping the wrong project early.
Who owns the code and the data?
You do, from the first commit. We work in your repositories and your cloud accounts wherever possible, and anything we set up on your behalf is transferred to you.
Can we stop after one phase?
Yes. Every phase ends with something that works on its own and with documentation good enough for another team to pick it up. Nothing we build depends on us staying.