Approach
A clear process, from first conversation to everyday use.
Understand
Review the business, existing workflow, users, and constraints.
You receive
Agreed problem statement and priorities.
Scope & Design
Define deliverables, approach, responsibilities, and costs.
You receive
Written scope, milestones, and proposed running costs.
Build & Review
Develop in manageable stages with your feedback.
You receive
Working demonstrations and agreed refinements.
Launch & Enable
Deploy, document, and enable the team.
You receive
Handover, hands-on enablement, and agreed support arrangements.
Built to keep working after handover.
Every proposal defines these explicitly, before work starts:
- Ownership and licensing of custom work built for you
- Access to relevant accounts and infrastructure
- Documentation and administrator guidance
- Team enablement
- Backup and recovery responsibilities
- Third-party subscriptions and usage charges — hosting, APIs, messaging platforms
- Warranty, maintenance, and support scope
Change requests
Changes beyond the agreed scope are quoted separately once the impact is clear — they don't silently expand the original cost or timeline.
Partner responsibilities
Timely feedback, access to relevant accounts or data, and a named point of contact — agreed at scoping, so the build stage doesn't stall waiting on either side.
Support & maintenance
Ongoing support is available as an option beyond initial handover, with its scope and cost agreed separately — it's never assumed to be included indefinitely.
Running costs
Hosting, APIs, messaging platform fees, and similar third-party charges are estimated upfront and billed separately from the build — self-hosted options are used where they genuinely reduce cost.