Small on purpose. Specific on purpose.
We build a narrow set of things properly rather than a wide set adequately, and we say no to the rest in writing. That is the whole strategy, and it is why the timelines are weeks.
The person who runs your discovery writes the code and is still the person replying in month six. Nothing is handed to a delivery team you have never met.
Five things we can be held to
We quote in writing
Scope and price after a discovery workshop — itemised beside the work, not invented on a call. See the service portfolio for what we build.
Discovery produces a document you own
A half-day workshop with the person who does the work. You get a gap map you keep — not a proposal we own — and it changes who turns up to the meeting.
We tell people not to buy
Roughly one discovery in three ends with "do not build this". Those are the conversations that produce the referrals.
We hand over the code
On final payment the repository is yours. By default the system runs in your own cloud account, where you can revoke our access entirely.
We read, we do not write
Read-only credentials into your existing systems, every call logged. The one exception is a system of record we built, which is ours to write to.
And one thing we cannot
We cannot staff a 24-hour desk. If an hour of downtime stops your production line, we are the wrong shop and will say so first, not third.
What we will not build
Naming precisely what you will not do is the fastest way to be believed about what you will.
- Accounting, GST and statutory filing. Regulated, high-consequence, and served by vendors with a decade of runway.
- Payroll. Same reason, and it goes wrong in a way people remember.
- Inventory with stock valuation. An accounting problem wearing a logistics costume.
- Replacing your ERP, CRM or ticket system. We read from systems of record. We do not become one, except for data that has no home at all.
- Anything sold as headcount reduction. Not a moral position — those projects get quietly sabotaged by the people who have to make them work.
An ERP is where a whole business runs. This is one register, done properly. Only one of those is a promise we can keep.
Who this is for
Businesses with real operational data and a reporting or follow-up burden carried by senior people — typically 150 to 5,000 staff, with an in-house tool or two that no vendor supports.
If you are pre-data, pre-process, or shopping for the cheapest possible website widget, we are the wrong shop and will say so in the first call rather than the third.
The fastest way to find out if we are useful is four hours.
You keep the written verdict either way — including the version that says do not build this.