Software Engineering
Software built to be maintained.
Custom software rarely fails in month two. It fails in year two, when whoever built it has gone and nobody can safely change anything. We build for that year.
What it covers
What it covers.
- Custom web applications
- APIs and integrations
- SaaS feature sprints
- Legacy modernization
- Maintenance and support
Built with
Next.js · TypeScript · Node · Postgres · Supabase · Vercel
How we work
How a project runs.
Scope
Week 0
A free 30-minute call, no deck. We ask what's not working and what you've already tried. You get back a written summary of the problem as we understand it, which is also the first test of whether we understood it.
Architect
3–5 days
We map the system, name the constraints and the risks, and decide what sits outside the scope. Then you get a fixed quote with milestones, so you know the price and the shape of the thing before anything is built.
Build
2–6 weeks typical
Weekly sprints, each ending in something you can click. You watch it come together, which means scope problems surface in week one instead of week five.
Operate
Ongoing
A written architecture summary, a runbook, and an access inventory, handed over with the keys. Launch is the middle of the project rather than the end, so from there either you run it or we do.
Related work
Where this shows up.
Questions
Before you ask.
Do we own the code?
Yes. Your repository, your hosting, your accounts - from day one, not on final payment. You get a written architecture summary, a runbook, and an access inventory at handover.
How is it priced?
Fixed price, quoted after the Architect stage. You approve a number and a milestone schedule before anything is built.
What if requirements change mid-build?
We re-quote the delta rather than absorbing it silently or pretending it was always in scope. Weekly demos exist so this surfaces in week one, not week five.
Have something that needs building?
Tell us what's not working. If we can help, we'll say how.