What we produce.
A working prototype
Something you can click through, built to answer the riskiest question first.
A written plan
The scope, the stages and the deliverables for the full build, in plain language.
A quote
A price for the build, specific to the plan we agreed, not a round number.
A technical assessment
What is feasible, what the risks are, and what to decide before you start.
The stages for this work.
Step 01: Frame the question
What decision this discovery has to make, and what would make it a yes or a no.
Step 02: Prototype the risk
We build the smallest thing that tests the riskiest assumption.
Step 03: Plan the build
We write the scope, stages and deliverables, and quote the build.
Step 04: Decide together
You decide whether to build, with the prototype and the plan in front of you.
Yours to keep, from day one.
Your source code
All of it, in a repository in your name, with its history.
Automated tests
The tests that prove the behaviour, run on every change.
Documentation and a runbook
How it works and how to run it, written in plain language.
A change log
A record of what was added, changed and fixed, stage by stage.
Checked on every change.
OWASP ASVS 4.0.3 Level 1 as the baseline, Level 2 on request. We follow NCSC secure development guidance.
Type checks
Every change is type-checked before it is merged.
Automated tests
The behaviour is covered by tests that run on every change.
Secret scan
Every change is scanned so no credential reaches the repository.
Dependency scan
Dependencies are scanned for known vulnerabilities on every change.
When this is the right work, and when it isn't.
A good fit
You are about to invest in a build and want to reduce the risk first, or you need to show stakeholders something real before a decision.
Not the right call
The scope is already clear, small and well understood. Then discovery is overhead; we would start the build and save you the step.
Common questions.
Do I own the prototype?
Yes. The prototype, the plan and the assessment are yours, in your name, whether or not you go on to build.
Is discovery paid?
Yes. It is a short, focused piece of paid work with its own written scope and deliverables.
What if discovery says do not build?
Then it did its job. A clear "no, not like this" before a build is a good outcome, not a wasted one.
Related work and guides.
How we work
Tell us what you need built.
A few lines is enough. We reply within 2 business days.