— How we work
How we work together
No sales call, no upsell, no surprise invoice. You send a short brief; we reply within one business day with a plan, a timeline, and a clear next step.
The process
-
01
Brief
Words on a page before code. Always.
You write us a 200–400 word brief. We send a written response — “fit” or “no fit” — within one business day. If it’s a fit, we draft a one-page engagement memo that defines what success looks like. The memo is the artefact. Everything later is judged against it.
Artefact — Engagement memo (PDF, 1 page)
-
02
Architect
Decisions before estimates. Estimates before invoices.
For longer engagements, the architecture is documented before the scope is fixed. Cloudflare bindings, data flow, AI surface area, security posture, observability — all written, all linked to the brief. You can show this artefact to your CTO. We pre-empt the “why this stack” conversation by writing the answer down.
Artefact — Architecture document (Markdown, 4–8 pages)
-
03
Sprint
Two-week rhythms. Demo at every cycle.
Work happens in two-week sprints with a demo and written changelog at the close of each. You don’t chase status — the changelog is the status. Slack is open during business hours; everything important also lands in writing so the engagement has a paper trail.
Artefact — Sprint changelog + demo recording
-
04
Ship
Production cutover with a runbook, not a hope.
Cutover happens behind a feature flag where possible. We write the runbook before the cutover, including rollback. After ship, we monitor for 14 days at our cost — the engagement isn’t done at deploy; it’s done when the product is stable in production.
Artefact — Runbook + 14-day stabilisation report
-
05
Operate
A clean hand-off, or a continuing operating relationship.
Either we hand off — with documentation written for your team specifically, not generic — or we continue under a longer-term operating arrangement. Hand-off includes a working demo of every operational task: deploy, rotate secrets, run migrations, restore from backup. Knowledge transfer that survives the meeting.
Artefact — Operations handbook + walkthrough recording
— 04 — After you submit
Here’s what happens next.
-
You write the brief
Two paragraphs in your own words. The problem, the constraint, what done looks like.
-
We reply in writing within one business day
A direct “fit” or “no fit” answer. No discovery call required.
-
If it’s a fit, we draft a one-page engagement memo
Scope, outcome, timeline, price. The memo is the artefact everything is judged against.
-
You decide
Sign the memo and we begin, or decline and the conversation closes cleanly.
No phone call. No upsell. Written brief, written response.
When the engagement doesn’t end
Most of our work continues past Ship. Ongoing relationships take one of three shapes — described here so you can name what you are asking for. None of them has a rate card: we scope each one in writing, to the environment it covers.
- Care
- For a website or a small system we built or adopted: updates, security patches, backups, monitoring, and small content changes — kept healthy month over month, with search and AI readiness maintained as the standards move.
- Managed IT
- For a business that runs on its technology: helpdesk with agreed response expectations, device and Microsoft 365 management, patching, backups that get restore-tested, and monthly reporting. The day-to-day, owned.
- Technology partner
- For a business without a technical team that does not want one yet: everything above, plus a roadmap. We sit on your side of the table for vendor decisions, budgets, and build-versus-buy calls — an outsourced technology department, accountable on one rope.
What we don’t do
Said openly so you don’t have to ask:
- × Hourly contracts. Fixed prices, agreed in writing.
- × Discovery calls without a written brief from you first.
- × Competitive RFPs and agency bake-offs.
- × Theme-only WordPress / Wix / Shopify builds with no engineering underneath.
- × One-off break-fix IT for businesses we don’t manage.
- × Engagements where success requires evading the truth.
Common questions
How much does it cost?
It depends on what you need, so we quote per project after we understand the work. Finding out costs nothing — send a brief and we’ll tell you.
How do we start?
You send a short written brief. We reply within one business day with a plan and a clear next step.
Do you take small projects?
Yes. Tell us what you need and we’ll be honest about whether we’re the right fit.
Tell us what you’re trying to build.
Two paragraphs is enough — what you’re trying to build, what’s in the way, and what done looks like. We reply within one business day.