Service
Internal tools that replace the spreadsheet running your business
Most small businesses run something important inside a spreadsheet only one person really understands. An internal tool replaces it with something that has proper permissions, a record of who changed what, checks on what people type in, and a screen you can teach a new starter in ten minutes. Without paying for a full software product.
Sound familiar?
The signs this is your problem
If two or more of these are true, there is almost certainly a worthwhile automation hiding in it.
- One spreadsheet holds something the business genuinely cannot lose
- Only one person knows how the process actually works
- There is no record of who changed what, or when
- Everyone has full edit access because permissions were never possible
- Onboarding someone into the process takes weeks of shadowing
What gets built
What an internal tool build includes
Four things, in roughly this order. The proportions shift by project — the shape does not.
What you get
Handed over, documented, yours.
- A working internal tool deployed to infrastructure you own
- Role-based access control and a change audit log
- Data migrated from the spreadsheet it replaces
- A training walkthrough recorded for your team
- Source code and documentation handed over in full
Typically built with
Chosen per project, not by habit. Everything runs in accounts registered to you — you hold the keys and see the bills directly.
When this is not the right service
How we'd work
From audit to autopilot in weeks.
Fixed scope. One fixed price. Working software every week. You always know what ships next and what it saves.
- Week 0 · Free
Audit
Thirty minutes on where your hours actually go. I map the repetitive workflows, time them, and score each one by what automating it would return. You keep that map either way — including the honest note on which processes to leave alone.
- Week 1
Blueprint
A written proposal: what gets built, which systems it touches, what it costs to run each month, the timeline, and one fixed price for the whole engagement. Nothing starts until you approve it. The price does not move unless you change the scope.
- Weeks 2–4
Build
I design, build and test inside your own accounts, with evaluations and guardrails on anything using a language model. You see working software every week rather than a status update — which means you can redirect early, while redirecting is still cheap.
- Ongoing
Run & improve
Launch, monitor, iterate. Thirty days of support included with every build. After that: take a care plan, hand it to your own team using the documentation, or run it yourself. All three are genuinely fine.
Questions
Internal tools & dashboards — the usual questions
Completely. On final payment, ownership of the custom code and configuration transfers to you in writing, it runs in infrastructure and accounts registered to you, and you receive the source and documentation. There is no proprietary platform you have to keep subscribing to in order to keep using what you paid for.
Very often, yes — and I will say so. If an off-the-shelf product covers eighty percent of what you need, buying it is usually the better decision and I would rather tell you that than sell you a build. Custom makes sense when the process is genuinely specific to how you operate, or when the off-the-shelf options each solve a third of the problem.
Typically a small hosting cost plus whatever the underlying services charge — often under fifty dollars a month for a team-sized tool. You get the running-cost estimate in writing before the build, and the tool runs on your own accounts so you can see the bills directly rather than through me.
Related
Often paired with
Ready to get the hours back?
A free 30-minute audit call. You leave with a written map of your automatable workflows and what each one is worth — whether we end up working together or not.
Replies within 24 hours · No sales team — you talk to the builder