Internal tools worth building first
Not every internal pain deserves software. Build tools where manual work is repeated, error-prone and clearly slowing revenue or delivery.
Every ops team has a spreadsheet that became a system by accident. It works until it does not. Someone copies the wrong tab, a formula breaks quietly and suddenly client reporting is a fire drill.
The internal tools worth building first share a pattern. The task happens often. The steps are known. Mistakes are expensive. Existing software forces awkward workarounds. And the people doing the work can describe the desired outcome in one sentence.
Good candidates look boring in the best way. Client onboarding checklists with status tracking. Dashboards that pull live metrics instead of weekly exports. Admin panels for content or inventory that your CMS was never meant to handle. Approval flows that currently live in email threads.
Bad candidates are vague wish lists. Build us something like Notion but for our exact vibe. Replace the whole ERP. Automate a process nobody has documented yet. Those projects stall because the problem is organisational, not technical.
Internal tools should earn their keep quickly. If a focused build saves ten hours a week, prevents costly mistakes or lets you take on clients you would otherwise turn away, the ROI is obvious. If it is mainly interesting to engineers, wait.