Build Internal Tools for Your Business With AI (The Spreadsheet Graveyard)

Every business — including one-person ones — runs on a shadow IT layer of spreadsheets and group-chat habits: the inventory sheet that's wrong by Thursday, the 'who has the van' text thread, the pricing formula only one person understands. Internal tools were never built because no business would pay developer rates for a sign-out sheet. That economics just flipped: an afternoon of describing gets a tool shaped exactly like the job. This is, quietly, the highest-ROI category on this site — boring software for problems you have every single day.

Step 1 — Find your candidate (the audit)

List every spreadsheet and chat-thread 'system' your operation touches in a week. Score each: how often it's wrong, how often it's the bottleneck, how often someone asks 'wait, where's the…'. The winner is usually obvious — and it's usually the one where MULTIPLE people update the same data, because that's exactly what spreadsheets do worst and shared little apps do best. Start with one. The graveyard gets cleared one grave at a time.

Step 2 — Specify like an operator, not a developer

Notice what the prompt is made of: who, on what device, which actions must be near-zero friction, and which mistakes the tool must make impossible. That third list — the rules — is what makes a tool better than the spreadsheet it replaces; the sheet relied on discipline, the tool relies on buttons.

Step 3 — Pilot it on a Tuesday

Run tool and spreadsheet in parallel for a few days. Real use finds what specs miss: the tutor with fat fingers needs bigger presets, sessions get logged at night in batches so 'backdate' matters, someone immediately asks for a weekly-totals view. Each is a sentence to Claude. Then the cutover ritual matters: announce the sheet is frozen, link the tool from everyone's home screen, and import the old data (Claude converts the CSV). A tool that runs 'alongside' a spreadsheet forever just became spreadsheet #2.

Step 4 — The proven gallery (steal these)

Patterns that map across trades: inventory/stock counter with low-stock flags (retail, kitchens, workshops); equipment sign-out (who has it, since when — vans, cameras, tools); job/order status board the whole team can read at a glance (the CRM tutorial's kanban, simplified); a quote calculator encoding YOUR pricing rules so anyone can quote consistently (the invoice tutorial's form-to-document skeleton); shift/availability collection (the booking tutorial's machinery pointed inward); a daily checklist with timestamps for compliance-ish routines (opening/closing, cleaning logs). Every one is the same anatomy: a table, three screens, five rules.

Step 5 — Know when you've outgrown cute

Honest boundaries: staff-shared-everything RLS is fine for a trusted small team, wrong past ~10 users or wherever permissions start mattering ('drivers shouldn't see payroll') — that's the auth tutorial's per-role patterns, a real step up. Audit trails ('who changed this number') are one ask and worth it for anything money-adjacent. And anything customer-facing graduates out of this tutorial entirely — internal tools earn their simplicity by trusting their users, which is exactly the assumption public apps can't make.

The compounding part

Tool #1 takes an afternoon; tool #4 takes an hour, because they're all the same parts and you've stopped re-deciding them. Within a season you have an operations stack molded to your business that competitors are still paying per-seat for — or doing in their heads. That stack is also, told plainly on a sales call or a portfolio page, the most convincing 'I build things that work' story you own.