How we work

Eight phases, each with a written exit gate.

Software projects fail on communication far more often than on code. This is the whole process, including what we need from you. A good build often goes wrong when both sides are waiting on each other.

45 minutes, free

Discovery Call

We work out whether this project makes sense and whether we are the right team for it. You do most of the talking. If we are not a fit, we say so on this call and point you somewhere better.

You receive

An honest read on feasibility and rough cost band
A recommendation on what to build first
A written summary of what we discussed

We need from you

The problem in your own words, not a feature list
Who will use the system and how they work today
Your real budget range and deadline

Phase ends whenBoth sides agree there is a project worth scoping, or we part ways cleanly.

1–2 weeks

Discovery & Scoping

We map your current process properly, decide the architecture, and turn a conversation into a costed plan. This is paid work because it is the phase that determines whether everything after it succeeds.

You receive

Process map of how the work happens today, including the failure points
System architecture and data model
Clickable prototype of the core workflow
Phased delivery plan with fixed cost per phase

We need from you

Access to the people who do the work daily, not only management
Samples of your real data, forms and reports
Decisions on the priority order of features

Phase ends whenYou approve the scope, architecture and phase plan in writing.

2–4 days

Proposal & Agreement

You get one document containing the scope, the phases, the fixed price, the payment schedule and what is explicitly not included. Nothing after this point should surprise you.

You receive

Written proposal with fixed price per phase
Service agreement covering IP, confidentiality and termination
Payment schedule tied to milestones
A clear out-of-scope list

We need from you

Questions on anything ambiguous. Ask them now, not in week six
Signature and the deposit invoice settled

Phase ends whenAgreement signed and deposit received.

1–3 weeks

Design & Architecture

Interfaces get designed and the technical foundation gets built: data model, environments, deployment pipeline. Boring, and the reason the later phases run predictably.

You receive

Interface designs for every core screen
Design tokens shared across web and mobile
Repository, staging environment and deployment pipeline
Database schema you can review

We need from you

Brand assets: logo, colors, fonts and photography
Design feedback consolidated into one round, not drip-fed

Phase ends whenDesigns signed off and the staging environment is live.

4–16 weeks, in phases

Development

We build in phases, and each phase ends with something working on staging that you can use. You see progress weekly. No four-week silence followed by a reveal.

You receive

Working software on staging at the end of every phase
A weekly written update: shipped, in progress, blocked
Direct access to the person building it
Change requests costed in writing before any work starts

We need from you

Review of each phase within a week of delivery
One named decision-maker for approvals
Third-party credentials and accounts when a phase needs them

Phase ends whenEvery agreed phase is accepted on staging and the change log is settled.

1–3 weeks

Testing & Hardening

We test the system against real workflows and real data, fix what surfaces, and review security and performance before anything touches production.

You receive

Test coverage across the critical paths
Security review: access control, data handling, dependencies
Performance check under realistic load
User acceptance testing with your actual staff

We need from you

Two or three staff available for acceptance testing
Production data for migration rehearsal
Sign-off on the defects that will and will not block launch

Phase ends whenAll blocking defects closed and you approve go-live.

1 week

Launch & Handover

We deploy to production, migrate your data, train your team, and hand over the keys. You own everything: code, accounts, documentation.

You receive

Production deployment with monitoring and backups configured
Data migrated and reconciled against your records
Staff training session, recorded for future hires
Written documentation and runbook
Repository and infrastructure access transferred to you

We need from you

Staff available for the training session
Confirmation that migrated data reconciles
Final invoice settled

Phase ends whenSystem live, team trained, ownership transferred to you.

30–60 days, then optional

Warranty & Support

Defects found after launch are fixed free during the warranty window. After that, you can take it in-house, hire anyone you like, or keep us on a retainer.

You receive

Free fixes for any defect in delivered scope during the warranty window
Response within one business day
An optional retainer with agreed monthly capacity
No obligation. You own the code and can walk

We need from you

Defect reports with steps to reproduce
A decision on support arrangements before the warranty ends

Phase ends whenWarranty period closes with all reported defects resolved.

The paperwork

Three documents, and that is all.

The proposal

Scope, phases, fixed price per phase, payment schedule, assumptions and an explicit out-of-scope list. If it is not in here, it is not in the project.

The service agreement

IP transfer, confidentiality, change requests, warranty, termination and governing law. Signed once, covers the engagement.

Milestone invoices

Issued as phases complete, referencing the milestone they cover, payable within 14 days. No hidden line items.

Phase one is a conversation.

No commitment, no proposal attached. Forty-five minutes to work out whether there is a project here worth scoping.

Book a discovery call Message on WhatsApp