Taking on new projects
Software that survives handover.
Most studios ship code and disappear. We ship requirement-traced code, role-based manuals and full documentation as standard — so your software still makes sense a year after we leave.
- TypeScript
- Next.js
- React
- Flutter
- Python
- PostgreSQL
- Prisma
- Docker
What we do
Three things, done properly
We keep the list short on purpose. A narrow studio ships better work than a broad one.
Web development
Web applications, dashboards, and marketing sites that stay fast and stay maintainable after we hand them over.
Applied AI
AI that does one specific job well: searching your documents, extracting structure, triaging requests. Shipped with evaluations and a cost model.
Learning platforms
Course delivery, admissions, student and instructor portals — built for institutions that need documentation as much as software.
Selected work
How we build
A learning platform built to a formal specification, and documented to match
Web and mobile clients on a single API, built against a written requirements specification with every requirement traced into the code that satisfies it.
- TypeScript
- Node.js
- PostgreSQL
- Prisma
- Flutter
An offline-first mobile app for children who cannot rely on a connection
A Flutter support tool for autistic children and their caregivers — communication, emotion learning, predictable routines, and explainable progress tracking.
ReadEducation operationsCutting an automation brief down until it was worth building
A Python service that files class recordings into the correct batch folder automatically — after we removed most of what was originally requested.
Read- 3
- Production systems shippedWeb, mobile and automation
- 4
- Role-based manuals per buildAdmin, teacher, student, super-admin
- 100%
- Requirements traced to codeEvery FR-ID cited where it is satisfied
- 4 hrs
- Response time commitmentOn any working day
How it runs
You always know what happens next
The same four steps on every project. No account managers, no status meetings that produce nothing.
- 01
A call
Thirty minutes. We ask about the problem, the deadline, the budget range, and who signs. If we are not the right fit, we say so on the call.
- 02
A written scope
Within 24 hours: deliverables, explicit exclusions, assumptions, timeline, price. Three options — reduced, recommended, extended.
- 03
Weekly demos
A staging URL from week one and a demo in the same slot every week. You watch it being built. Changes get priced before they are built.
- 04
Handover
Documentation, environment notes, a recorded walkthrough, and 30 days of bug cover. The code is yours outright.
Why we are different
We document like a much larger company
On our last learning platform, every requirement in the specification has an identifier, and that identifier is cited in the code that satisfies it. If the code and the specification disagree, one of them is a defect — and it is obvious which.
That platform shipped with four separate role-based manuals and a QA test pack the client's own team can re-run. Most studios our size cannot do this. It is why institutions hire us.
Requirement traceability
Every requirement ID cited where it is satisfied in code.
Role-based manuals
Separate written guides for each type of user, not one generic PDF.
A re-runnable QA pack
Test cases your team can run after any change we did not make.
Written handover
Deployment notes, environment config, and a recorded walkthrough.
Priced change orders
Nothing outside scope gets built before you know what it costs.
Code you own
Full IP transfer on final payment, written into the contract.
Pricing
Fixed scope, fixed price, published
Most studios hide their prices. Showing ours saves everybody a wasted call.
Launch Site
A company that needs a credible site quickly.
$2,400
2 weeks
- 5–7 pages, designed and built
- CMS for the blog
- Contact form and calendar booking
- Analytics and SEO foundation
- Lighthouse 95+ verified
Product MVP
A founder who needs something real in front of users.
$9,000
6 weeks
- Authentication and data model
- Core feature set, scoped in writing
- Admin panel
- Payments integration
- Deployed, monitored, documented
AI Feature Sprint
A product team adding its first AI capability.
$6,500
3 weeks
- One shipped feature inside your product
- Evaluation set and measured accuracy
- Cost model at your projected volume
- Fallback behaviour for outages
- A written note on what it cannot do
What does success look like for your project?
Tell us the problem and the deadline. We will tell you honestly whether we are the right people to solve it.