Enterprise
Built to pass your procurement process.
Named contacts, documented handover, and a security questionnaire we will actually fill in.
Teams we have worked with
- Dumpty
- Auto Flow
- Lazy Meet
- The Ruff Agency
Why procurement signs off
- 01
Named delivery contacts
The people in the pitch are the people on the project, named in the statement of work.
- 02
Documented handover
Architecture notes, runbooks and access inventory delivered as part of the engagement, not on request.
- 03
Accessibility commitment
WCAG 2.1 AA as a build gate, verified in CI rather than audited annually.
- 04
Security review support
We complete your vendor questionnaires and will sit the technical review call.
Governance and quality
- 01
Change control
Scope changes are written, priced and signed before work starts on them.
- 02
Code ownership
You own the repository from day one. No escrow arrangement is needed because nothing is held back.
- 03
Dependency policy
New third-party dependencies are flagged and justified, not added silently.
Support priorities
Response times are agreed per engagement and written into the contract. We do not publish a single figure because it depends on what you need covered.
| Priority | Definition | Response target |
|---|---|---|
| P1 | Site down, or a critical path unavailable to all visitors. | TODO — not yet agreed |
| P2 | Major function degraded, with a workaround available. | TODO — not yet agreed |
| P3 | Minor defect or cosmetic issue with no functional impact. | TODO — not yet agreed |
Response targets are deliberately unfilled — see docs/PROGRESS.md. Do not publish invented SLA figures.
Procurement questions
Do you sign a mutual NDA before commercial discussions?
Yes. We will sign yours, or provide a standard mutual NDA if you prefer to start from ours.
Who owns the code you write?
You do, from the first commit. Work is delivered into a repository you control, so there is nothing to escrow and nothing to hand over at the end.
Can you work inside our cloud account?
Yes. We default to Vercel because preview deployments make review faster, but we deploy into a client-owned AWS, Azure or Google Cloud account where policy requires it.
What accessibility standard do you build to?
WCAG 2.1 AA, checked automatically in the build pipeline and reviewed manually before launch.
Need us in your vendor process?
Tell us where it hurts and we will tell you what we would do about it.