Build · Service
Custom Software
We design and build web applications, internal tools and integrations around how your team actually works. Delivered in increments you can use, on a stack your next hire can maintain.
- ✓tests passed
- ✓migration applied on staging
- ✓preview deployed
- …production: waiting for your approval
IllustrationEvery change runs through tests and staging. Production waits for a person.
Who is Custom Software for?
For operations running on spreadsheets, inboxes and tools that don't talk to each other.
Manual processes
Work moves only when someone pushes it: copy, paste, chase, repeat. When that person is out, it stops.
Operational chaos
Escalations, workarounds and “ask the one person who knows”. The real system lives in people's memory.
What do you get?
- Working software in your repository, deployed to your cloud account
- Automated tests and a CI/CD pipeline from the first release
- Roles, permissions and audit logging where the workflow needs them
- Documentation and a handover session with your team
How do you know it's done?
- Your team runs the workflow in the software, not around it
- Every environment can be rebuilt from the repository
- An engineer who isn't us can ship a change after handover
How does an engagement run?
- 01
Brief. A few minutes with our intake. Your context arrives before the call does.
- 02
Intro call. Thirty minutes. We ask the hard questions and tell you honestly whether we're the right fit.
- 03
Written scope. Scope, exclusions, milestones and a fixed price per phase, in writing, before any invoice.
- 04
Architecture. Diagrams and decision records you review and approve before the build starts.
- 05
Build. Working software on staging, demoed on a fixed cadence. You see progress, not status reports.
- 06
Handover. Code, infrastructure, docs and runbooks in your accounts. Ongoing support only if you want it.
How is it priced?
By scope. After the call you get a written scope with exclusions, milestones and a fixed price per phase. Payment follows accepted milestones. The budget range you pick in the brief isn't a quote; it helps us suggest a first phase that fits.
Which technologies do you use?
Our usual stack for Custom Software. We work with yours when you have one.
- TypeScript
- NestJS
- Next.js
- React
- PostgreSQL
- Prisma
- Redis
- Docker
- AWS
Custom Software: questions and answers
What kind of software do you build?
Web applications, internal tools and integrations, built around how your team actually works and delivered in increments you can use. The usual stack is TypeScript with NestJS, Next.js and React on PostgreSQL, deployed to your own cloud account.
Who owns the code?
You do. It lives in your repository from the first commit, and the contract assigns the IP to you.
Can another team maintain it after handover?
That's the standard we build to: every environment can be rebuilt from the repository, and an engineer who isn't us can ship a change after handover. You get documentation and a handover session with your team.
Start a brief for Custom Software.
A few questions, about three minutes. Nothing is sent until you review it and press Send, and the first call is thirty minutes to check fit, both ways.