Step 1 · Scope
What it does, and what it will not.
What we do, in detail
Four services, each ending with you holding the keys.
Program 01 · Documented as built
Custom software development
Documentation written at the end of a project is documentation written badly, from memory, under time pressure, by someone already thinking about the next thing. So it is delivered as the work proceeds and it forms part of each milestone. The test is simple and we apply it honestly: could a competent developer who has never met us pick this up?
Step 2 · Build
In increments you can see running.
Step 3 · Document
Delivered with each milestone.
Step 4 · Hand over
Code, accounts and instructions.
Step 1 · Map it
What actually happens now.
Step 2 · Question it
Which steps should go away.
Step 3 · Connect
As simply as the job allows.
Step 4 · Monitor
Alerts that mean something.
Program 02 · Fewer moving parts
Systems integration and automation
Before automating a process we ask whether it should exist, because automating an unnecessary step makes it permanent and harder to question later. We also prefer the smaller integration that can be understood to the elegant one that cannot: every connection between two systems is something that will break at some point, usually when nobody remembers how it worked.
Program 03 · Before you commit
Technical second opinions
A short review before signing is the cheapest technical work a business ever buys. We read the codebase or the proposal and report plainly: what is solid, what is risky, what is missing, and whether the price bears any relation to the work. If the answer is that the existing supplier is doing a decent job, that is the report you get.
Step 1 · Material
Code, proposal or quotation.
Step 2 · Review
Against what it claims to do.
Step 3 · Report
Risks and gaps, in writing.
Step 4 · Questions
What to ask before signing.
Step 1 · Inventory
Every account, domain and service.
Step 2 · Your name
Ownership and admin access to you.
Step 3 · Escrow
Code deposited, if you want it.
Step 4 · Substitute
Named, for longer engagements.
Program 04 · Written for your sake
Continuity and handover
This is the service that argues against our own indispensability, which is exactly why it is here. Accounts and domains in your name, administrative access held by you, source code deposited with a third party if you want it, and a named substitute contractor for longer engagements. A supplier who has not done this is relying on your inability to leave.
Got something to build, or a supplier to check?
A free first conversation, with no obligation, to work out whether we are the right fit.