Custom Software
Software Engineering
You have a job that runs on spreadsheets and email, two systems that never pass anything between them, or work somebody redoes by hand every week. The software that does it instead gets built here.
What It Covers
What you get.
Everything below is part of the work. Nothing here is an upgrade.
The First Read
A call, then a walk through the job as it runs now: the spreadsheet, the email thread, and the steps nobody wrote down. What gets built comes from that.
Built Around the Job
The screens follow the steps the work already takes, in the order it takes them. Everything the job needs is in it and nothing else is.
Systems Wired Together
Two tools that hold the same information and never exchange it, connected through their APIs. A record entered once shows up in both without anybody retyping it.
Run on a Schedule
The report somebody rebuilds every Monday runs on a schedule instead. When it fails it says so, rather than stopping quietly.
Screens for Your Staff
A screen with the records they need, the buttons they press, and none of the rest. Access is set per person, so each one sees their own work.
Yours to Keep
React, Node, Postgres, and functions on Vercel and Supabase. The repository and the accounts are in your name, so another engineer can pick it up after us.
Time and Cost
How long it takes, and what it costs.
How Long It Takes
A small integration or automation takes a week or two, and a full application six to twelve weeks. The date is agreed in writing before any work starts.
What It Costs
Priced per project, because no two are the same. You get the number in writing after the first call and agree to it before anything starts. There is nothing monthly behind it: the project ends when it is done.
The Rest of It
Everything else on offer.
Let’s Talk
Start with a call.
Tell us what the work is and what it has to do when it is done. We read it and answer it ourselves, usually within the hour, and you get the scope and the price in writing before anything is charged.