Process
You should never have to ask how the project is going.
Five phases, each with named deliverables. The structure is the same whether the engagement is a two-week audit or a six-month build.
Phase 01 · Week 0
Discovery call
Forty-five minutes on your systems, constraints, and what 'done' looks like. We ask about the business before the technology — most software problems turn out to be workflow problems wearing a costume.
- A shared write-up of the problem
- An honest fit assessment
Phase 02 · Within a week
Scope & proposal
A written scope: deliverables, timeline, engagement shape, and what we need from you. For existing systems, this is where the paid audit week happens — we read before we promise.
- Written scope with a fixed timeline
- Audit report (for existing systems)
- One price, no surprise line items
Phase 03 · The build
Weekly increments
Working software on a staging link every Friday, with a changelog in plain language. You have a direct channel to the engineer building it — not an account manager relaying messages.
- Staging link, always current
- Friday changelog, every week
- Direct channel to the engineer
Phase 04 · Launch
Launch & handover
Deployment to your infrastructure, under your accounts. Handover is a deliverable with its own checklist: repository, credentials, runbook, and a walkthrough with whoever inherits it.
- Your repo, your cloud, your credentials
- Runbook and documentation
- Team walkthrough session
Phase 05 · After
Ongoing care — or a clean exit
Either your team takes it from here, or we stay on: monitoring, patching, backups with restore drills, and incident response with stated response times under an Infrastructure Care plan.
- Care plan with response-time commitments
- Monthly report: uptime, incidents, spend
- Or: nothing. A clean exit is a valid outcome.
Every single week
Three things arrive every Friday, no matter what.
A staging link
The current state of the build, running, clickable, always up to date. Not a slide deck about it.
A written changelog
What shipped, what's next, what's blocked — in plain language, every Friday, without being asked.
A direct line
Questions go to the person writing the code. Answers come back the same day, in writing.
See the process from the inside.
The discovery call is phase one, and it costs nothing. If we're not the right fit, you'll leave with a clearer problem statement anyway.