Build
Nothing you own holds the whole job.
- Spreadsheets bridge your systems
- The same data entered twice
- No field for owner or exception
- People need one focused screen
Custom software
Your business runs on a spreadsheet nobody owns.
That spreadsheet is the job your CRM, calendar and accounting cannot hold. We build the one screen that does — or we tell you not to build.
30 minutes. One workflow mapped. Scope and price come after discovery, never before it.
When existing software stops fitting
Build only when
building is justified.
Custom software is the most expensive answer, and often the wrong one. Two lists, and a straight answer about which one you are in.
Do not build
We will say so on the call.
- An existing tool already works
- The workflow isn’t understood
- The process changes weekly
- Nobody will own the result
Saying “don’t build this” costs us a project and saves you one.
- Off-the-shelf fitsWe help you use what you already pay for.
- Workflow still movingWe map it first. Building waits.
- No named ownerWe stop. Orphan tools help nobody.
Keep, connect, or build
The decision comes
before the code.
Three outcomes, and two are cheaper than building. Discovery decides which, not a sales preference.
Keep
Duplicating a tool that already works adds cost and a second source of truth.
Cost Nothing. Our most common answer about at least one tool you already pay for.
Connect
Your systems work, but they do not share one record or one next action.
Cost A fraction of a build. Everything you already run keeps doing its job.
Build
No tool you own can hold the job, so we build the one screen that does.
Cost The largest of the three. Which is why discovery comes first and prices are scoped, not published.
What we can build
Focused tools,
not platforms.
One application, one job, one workflow. Nothing here is a product we resell.
- Client portals
- Workflow applications
- Operations dashboards
- Exception queues
- Document generators
- Knowledge assistants
- Approval tools
- Purpose-built integrations
01
Customer document portal
Stop chasing files through email — every package shows its own status.
Acceptance and review stay human.
See the working demonstration02
Internal exception dashboard
Problems stop hiding in spreadsheets, because every one of them gets an owner.
Thresholds and corrective action stay human.
See the working demonstration03
Template & document generator
Nobody rebuilds the same document by hand again; it comes off live data.
Final review and sending stay human.
See the capability04
Knowledge & approval assistant
The answers stuck in one person’s head become sourced answers anyone can check.
Uncertain answers route to an expert.
See the working demonstrationEvery record in the demonstrations above is synthetic — the workflow is real, the data is invented so you can click it.
Product process
Mapped, phased,
and handed over.
Seven phases, each ending in something you can hold, test or reject. Stopping at any of them is a normal outcome.
-
Mapping call
Thirty minutes on one workflow, and where ownership gets lost.
You leave with
A map of your current state with the breakpoint named. Yours either way.
Your decision
-
Discovery & specification
Paid, fixed in scope: records, users, rules, exceptions, integrations.
You leave with
A written spec you own and could hand to any competent builder.
Your decision
-
Focused prototype
We build the path the workflow actually turns on — before the rest.
You leave with
A working prototype, and proof it survives the people who use it.
Your decision
-
Build in working phases
Every milestone opens in your hands. Nothing ships unseen.
You leave with
Approvals on record, and a system corrected while correction is cheap.
-
Test with realistic scenarios
Wrong data, missing fields, duplicates — the cases that actually break things.
You leave with
Proof it stops and routes an exception to a named person instead of guessing.
-
Launch, document, transfer ownership
Training, a written runbook, logging, a fallback path and an off switch.
You leave with
Source and documentation handed off. Access stays in your accounts.
-
Stabilisation
A defined window for what only real use surfaces.
You leave with
Maintenance scope that is defined, not unlimited.
What it costs
Scoped after discovery.
Pricing is defined per scope, not published. We do not quote package prices for work that has not been defined yet — the definition is what determines the price.
- Discovery & specification
- Focused prototype
- Phased custom build
Ownership and maintainability
“You own everything”
is not a precise answer.
A custom system is five kinds of material, and they do not transfer the same way. Every line below is in the agreement before we start.
Yours
Your data, records and accounts
Hosting, domains and services live in your name, with your billing.
Yours
The agreed custom deliverables
Source, configuration and documentation, named explicitly in the agreement.
Vendor terms
Third-party software and services
Your CRM, mail, model APIs and hosting stay on their vendors’ own terms.
Open-source licence
Open-source components
Permissive by default, listed, with any obligation flagged up front.
Licensed to you
Our pre-existing reusable material
Licensed to you perpetually and irrevocably — named, not reverse-engineered later.
Maintainability, in practice
- Ordinary technology, no private framework
- A runbook any developer can follow
- Logging you can read yourself
- A fallback path and an off switch
Start with the missing piece
Bring the spreadsheet.
Get a straight answer.
Thirty minutes, one workflow, and a straight answer: keep, connect, or build. You keep the map either way.