process
Client Engagement & Delivery Process
Good software starts with understanding, not code. Before we build anything, we make sure we have understood the client's goals, validated the right approach for their situation, and agreed exactly what success looks like. This document explains how we work with every client, so that at every stage they know what we are doing, what they will receive, and what it costs.
lifecycle
The Engagement Lifecycle
Our full process runs through the phases below. The table sets out what each phase produces, whether the client receives it, and what it costs.
| Phase | Focus | Deliverable | Cost |
|---|---|---|---|
| Discover | |||
| 01 Discovery | Understand goals, constraints, budget, timeline | Shared understanding; go / no-go | Free |
| 02 Requirements & Approach (Level 1) | Study needs, validate the best approach | Assessment document | Free |
| 03 Solution Blueprint (Level 2, optional) | Deep technical design and roadmap | Blueprint (owned by the client) | Paid |
| 04 Proposal & Agreement | Fix scope, pricing, acceptance criteria, terms | Signed scope agreement | Free |
| Design | |||
| 05 Onboarding & Kickoff | Access, accounts, comms setup, kickoff | Agreed project plan | Within build |
| 06 Design | Branding, UX, wireframes, final architecture | Approved designs | Within build |
| Build | |||
| 07 Development | Iterative Agile sprints with regular demos | Working build, sprint by sprint | Within build |
| 08 Testing & QA | Functional, integration, mobile, browser, performance, regression, UAT | Tested, accepted build | Within build |
| Launch | |||
| 09 Deployment & Handover | Go-live, training, runbook, deployment checklist, rollback | Live platform + documentation | Within build |
| 10 Support & Maintenance | Warranty, response times, support channels, escalation | Support and SLAs | Warranty, then optional |
analysis
Our Two Levels of Analysis
Every engagement begins with analysis. We deliberately separate it into two levels, so a client only pays for depth when it is actually needed.
| Level 1: Requirements & Approach Assessment | Level 2: Solution Blueprint & Technical Roadmap | |
|---|---|---|
| Depth | What you need and the best approach; no full implementation detail | Full technical design and implementation plan, end to end |
| Contents | Goals, scope, recommended path, trade-offs, indicative timeline and cost | Architecture, integrations, data flow, security, failure handling, testing strategy, risk register, deployment plan, detailed TCO and ROI, phased build plan |
| Purpose | Align both sides before commitment | A production-ready plan to build from |
| Shared with the client | Yes, at no charge | Yes, once commissioned |
| Cost | Free | Paid |
| Ownership | Shared understanding | The client's to keep and reuse with any vendor |
Every prospective client receives the Level 1 assessment free of charge. A Level 2 Solution Blueprint is always produced when a project is engineered; the only difference is whether it is commissioned as a shared deliverable, or kept for our internal team.
how we work
Why We Work This Way
How We Communicate
A single point of contact throughout; a regular cadence of brief updates and demos during the build, with a review at each phase gate; the client's preferred mix of WhatsApp, email and scheduled calls; transparent reporting, so they always know what is done, what is next, and any risks; and clear change handling, where any change in scope is discussed, quoted and agreed before work begins, so there are no surprises on the invoice.
Ownership, IP & Confidentiality
All platform accounts and assets are created under the client's ownership. Any paid deliverable, including the Solution Blueprint, is theirs to keep and reuse with any vendor. Client information and materials are treated as confidential throughout.
Ethics review
Our Professional Ethics & Engagement Standards describe the kind of work we will and will not take. This section is only about when that review happens in the engagement, and what follows if we cannot agree.
Why We Work This Way
This model protects the client as much as it protects us. Trust is built before either side commits; a client pays for depth only when it adds real value; and they always own what they have paid for. It is how we make sure the right thing gets built, at the right time, for the right reason.
get in touch
Discuss your next project.
Tell us what you're making. We'll tell you honestly how we'd approach it - and whether we're the right team for it.