Internal tools
The tool your business needs does not exist as a product.
Not every problem has a market. Sometimes the thing you need is specific to how your business works, which means no vendor has built it, because there is no category to sell it into.
That is the normal case for an internal tool. A pricing calculator only your business uses. A dispatch board that matches your logic. A portal that shows your clients exactly the four things they keep ringing about.
The shape of these projects
Small, specific, and worth more than they cost.
Internal tools are usually the highest-return thing we build, because the scope is tight and the pain is precise. Somebody in the business does a task repeatedly, badly supported, and everyone knows exactly what it costs.
These are the ones that pay for themselves quickly: a two-week build that saves one person a day a week has cleared its cost inside a year without touching a single subscription.
Where the no-code tools stop
Airtable, Glide and their peers are genuinely good for the first version of a tool like this, and we say so on the spreadsheet-to-app page. They stop at three points: per-seat pricing once everyone needs access, logic complex enough to fight the builder, and the moment you need it to integrate properly with something else.
The client portal case
Four screens that stop the phone ringing.
The most requested internal tool is not internal at all. It is a client-facing portal showing the four things clients ring to ask: where is my job, what did I approve, what do I owe, and what happens next.
It is a small build and it changes a business’s day, because those four questions are most of the inbound phone calls in most service businesses.
The scope
What gets built, and what we leave alone.
Things we have been asked for
- Pricing and quoting calculators with logic no product sells
- Dispatch and allocation boards that match how you actually decide
- Client portals covering job status, approvals and invoices
- Approval workflows that route by amount, by client or by risk
- Data entry tools that replace a shared spreadsheet with a real form and a real audit trail
- Dashboards that pull from the systems you already run
- Import and reconciliation tools for the file a supplier sends every week
- Internal request systems: equipment, leave, purchasing, whatever is currently email
What we will not build
- A tool that duplicates something you already pay for and are happy with
- Something one person wants and nobody else will use. We will ask who else uses it before we quote
- Anything regulated or certified, which stays with the specialist product
We will tell you when it is not worth it. If the job is genuinely a spreadsheet job, keep the spreadsheet. Internal tools earn their money when the task is frequent, done by several people, and currently painful. Two of three is usually not enough.
The other sum
The one where the cost is hours rather than licences.
Do it on your own number
For an internal tool, the honest number is often not a subscription. Take the hours a week the task costs, multiply by a fair hourly rate, and put that in the dial instead.
Common questions
Answered plainly.
How much does an internal tool cost to build?
From $5,000, and many are at the lower end of that because the scope is tight. Two to six weeks is the usual range. We quote fixed before starting.
Is it worth building instead of using Airtable?
Not always, and Airtable is a genuinely good first version. It stops being the right answer when everyone needs a seat, when the logic starts fighting the builder, or when it needs to integrate properly with your other systems.
Can it connect to our existing systems?
Usually yes, and that is often the point of the tool. Where a system has an API we integrate directly; where it does not, we work with exports and are upfront about the limits of that.
What is the most common internal tool you build?
A client-facing portal answering the four questions clients ring about: where is my job, what did I approve, what do I owe, and what happens next. It is a small build that changes how a service business's day feels.
Do we need a big system first?
No. Internal tools are frequently the first thing we build for a business, precisely because they are small, cheap and prove whether working together is any good before anyone commits to something larger.
Where to next
Bring the task everyone complains about.
The repetitive one nobody has fixed because no product does it. Twenty minutes is usually enough to tell you whether it is a two-week build or a spreadsheet you should keep.