When does custom software make sense?
Most businesses should not start with custom software. A good sheet, an existing SaaS tool and a few automations go a long way. Custom software starts to make sense when one of these is true:
- Your process is the thing that makes you different, and every tool forces you to work like everyone else.
- Your team copies data between three tools every day because none of them does the whole job.
- A shared sheet has become the system: many people edit it, rows get broken, and nobody trusts the totals.
- Clients or partners need to log in and see their own data, and only theirs.
- You pay for many seats of a large tool to use one small part of it.
Build or buy?
| Question | Points to buying a tool | Points to building |
|---|---|---|
| Is the process standard? | Yes, like invoicing or payroll | No, it is how you win work |
| How many people use it? | Few, and they can adapt | Many, and adapting costs time every day |
| Does it need your own data rules? | Not really | Yes, with checks a tool cannot do |
| Who maintains it? | The vendor | You, or a partner, for its whole life |
The last row matters most. Software needs updates, security fixes and small changes as your business moves. Our build or buy guide goes through the full decision.
What we build
- Internal tools: an order desk, an approval queue, a stock planner, a quality check screen such as the label artwork checker.
- Client portals: reports, files and status for each client behind a login.
- Data products: an API or a dashboard on top of data you collect, like the data API explorer.
- Glue: the small web app that holds your automations together, with a review screen for the cases a workflow sends to a person.
How a build runs
- A written scope: the screens, the data, who uses it, and what is out of scope. You sign off before any build starts.
- A clickable first version within the first weeks, on test data, so you can react to something real.
- Short cycles. Each cycle ends with something you can use, not a status report.
- Your real data moved in carefully, with a check that nothing was lost.
- Launch, then a support plan for fixes, updates and small changes.
The stack, in plain words
We build web apps with Next.js and TypeScript, store data in Postgres, and run automations next to them in n8n. These are widely used, well documented tools, so another developer can pick the work up later. You own the code and the data.
When we will tell you not to build
If a ready-made tool covers most of what you need, we will say so and help you set it up and connect it instead. If the process is still changing every week, we suggest running it in a sheet with a few automations for a while first. Building software for a process nobody has settled is the most expensive way to find out what you need.
Questions people ask about custom web software
Who owns the code?
You do. The code is in a repository you can access, the data is in a database in your account or ours with an export at any time, and the stack uses common tools so another team can take over.
How much does custom software cost?
It depends on the number of screens, users, roles, integrations and data rules. A small internal tool is a small project; a client portal with logins, permissions and billing is a larger one. After the first call you get a written scope and a fixed price for the first version.
Can it connect to the tools we already use?
Yes, if those tools have an API, a webhook or an export. Most of what we build sits next to existing tools rather than replacing all of them.
What happens after launch?
You choose a support plan for hosting, monitoring, security updates and small changes. Larger additions are scoped and priced like the first version.