Six phases. Each one has a duration, a price and a written output, so you always know which phase you are in and what it is producing.
01DISCOVER
1 – 2 weeks
We learn the process before proposing a system. Sessions with the people who do the work, a read of the systems already in place, and an honest map of what is fixed and what is negotiable.
What happens
What you get
02ARCHITECT
1 – 2 weeks
A written technical plan you can challenge: boundaries, data model, integration contracts, hosting, and the failure modes we design against. The estimate is built from this, not from a hunch.
What happens
What you get
03BUILD
2-week cycles
Delivery in fortnightly slices, each ending in something running on a real environment. You see progress in the product rather than in a status report.
What happens
What you get
04HARDEN
1 – 2 weeks
Before launch, our security team tests what our developers built, and we load-test against the traffic you expect on your worst day rather than your average one.
What happens
What you get
05LAUNCH
1 week
A rehearsed cutover with a rollback path, then a genuine handover: documentation, walkthroughs and credentials transferred into your accounts.
What happens
What you get
06OPERATE
Ongoing, optional
Support with response times in writing, dependency and security patching, and a quarterly review that decides what to build next from usage data rather than opinion.
What happens
What you get
Reporting arrives on a schedule whether the news is good or not. Silence is not a delivery strategy.
Weekly
Written progress note
What shipped, what is next, what is blocked.
Fortnightly
Demo of working software
On a real environment, not slides.
Monthly
Invoice with burn-up
Spend against estimate, variance explained.
Quarterly
Roadmap review
What usage data says to build next.
Projects rarely fail on engineering. They fail on decisions that take four weeks to make. This is the short list that keeps a build moving.
If any of these are difficult in your organisation, tell us during discovery. We can design the engagement around it — we just cannot design around finding out in month three.
You end it with a written scope, an architecture and an estimate accurate to about 15% — whether or not you build it with us.
