What this covers
Custom software for one process that spreadsheets can’t handle, built in small releases with clear goals.
Tools
TypeScript, React, Node.js, PostgreSQL. The exact stack depends on what you already use.
Where it helps
- Approval queues where every item has an owner
- Customer portals where people only see their own data
- Dashboards connected to the systems you already use
We agree what “done” means before work starts.
What you get
- A map of the current process and who does what
- A first working release of the custom app
- Source code, setup notes and an agreed definition of done
The final list depends on the agreed scope. The estimate and schedule follow from it.
Data and security
We agree who owns each record, how long it’s kept, what needs an audit trail, and who can access what, before designing the database.
How I work on it
Map how the process works today, agree on a small first release, build and review it, check permissions and edge cases, then hand it over.
What helps me get started
- A short description of the process and who uses it.
- Sample data, any API documents, and what access is available.
- How much it will be used, who reviews the work, and your release priorities.
A short outline is enough for a first call. Please send sample data, not real records or passwords.
Related services
Read the planning guideQuestions
Why build instead of buying a tool?
Check what’s available first. Custom software makes sense when your process or integrations are unusual enough to justify maintaining it.
How do you price the work?
I look at the workflow, the systems involved, the access needed and what “done” means, then send an estimate. If there are big unknowns, we start with a short discovery or a prototype.