Finish the small thing

Most of the software I've shipped on my own is small. A script that renames invoices. A page that turns a messy spreadsheet into a clean one. A bot that posts one reminder to one channel. None of them would impress anyone at a demo day, and every one of them still runs.

The ones that didn't survive weren't worse ideas. They were small ideas I let grow until they were too big to finish. Here's the process I use now to keep a tool small enough to actually ship.

Write the job in one sentence

Before I open an editor, I write down what the tool does in a single sentence, with a real person in it: "Maya exports her bank CSV and gets a file her accountant will accept." If I can't write that sentence, I don't understand the problem yet. If the sentence needs an "and," I probably have two tools.

Decide what done looks like before you start

Scope creep rarely arrives as a big feature. It shows up as "while I'm in here." A settings page. A second export format. Dark mode. Each one is reasonable, and together they're the reason a two-evening project is still open three months later.

So I write a short list of what "done" means, usually three to five items, and anything not on it goes into a file called later.txt. Most of later.txt never gets built, and nobody misses it.

Ship to one person

The first user is not "the market." It's one specific person who has the problem this week. Shipping to them is fast, because you can skip onboarding, pricing, and a landing page. You find out immediately whether the sentence you wrote is true. Often the answer is "almost," and the correction is small, because the tool is small.

Finished is a feature

An unfinished tool has a cost that doesn't show up anywhere: it sits in the back of your head. Every half-built project is a small tax on attention, and for a solo founder, attention is the whole budget.

A finished tool that does one narrow thing well pays that tax off. You can stop thinking about it, and if the one-sentence job was real, it keeps paying you back every time someone uses it.

There's a version of this job where you only ever build big things. I've found it more useful, and a lot more fun, to build small things and finish them.