Company of one, built like fifty.

A fifty-person shop is a shape most people recognise from the outside, and a company of one is a shape most people have never looked at properly.

Most people running a one-person business have had the pitch put to them, probably more than once. Look like a fifty-person shop, so a bigger client will take you seriously. Branded invoices, a sign-off process on a one-page proposal, a status report that reads like a quarterly review. It is backwards for a one-person business. The bigger firm looks the way it does because the standard needs more scaffolding when fifty people share it; one person with the same standard underneath looks almost nothing like it.

The question is not what fifty people's output looks like. It is what the standard underneath looks like when one person is holding it.

Three to copy

A written statement of what done means, agreed before you start. At the bigger firm this is a scoping document with sign-offs on it. On the one-person desk it is three lines in the email thread, agreed by the customer and pasted into a note under the deal. The point is the same in both places: whoever will say "this is done" sees the shape of done before any work is done. A one-line reply, "yes, that is what I meant", is the agreement. Without it, the ending drifts, and everyone involved, including the version of you who reads the invoice next quarter, has to re-litigate the finish line.

A trail you could hand to someone else, saying why each line of the invoice is there. At fifty people this is time entries, tickets and a reviewer sitting between the two. At one it is a two-column note per piece of work: what was asked for, and what was done. The invoice line reads from column two; the dispute, if there is one, is settled in column one. It takes less than a minute per entry, and it means a dispute about any one line is a document reading rather than two people trying to remember weeks later what they had agreed.

One pattern I've noticed over the years is this. A customer queries one line on an invoice a few weeks after it went out, saying it was not what they asked for. The two-column note goes up on screen. Column one carries the request in the customer's own words from the thread; column two carries what was shipped against it. The customer reads column one, agrees it was theirs, and the invoice gets paid the same afternoon. Without the note, that call takes a week to settle, and the one-person business usually eats the time. On the one-person desk there is no reviewer in the room; column one is the reviewer, and it is written by the customer themselves.

A weekly line you refuse to cross on new promises. Fifty people run capacity planning. One person runs a short note at the end of the week that says what next week will not take on, and names the one promise already in motion that would break if it did. A practice I keep for myself is one line a week on that question, written before I open the inbox on Monday. Without it the inbox decides the week, and the previous week's promises are the ones that slip.

Two to leave behind

Status reporting that reads like translation. The bigger firm writes status reports for seats that are not in the room: a product owner, a steering committee, a department that needs to know next quarter's demand. That is a real win when fifty people share the delivery; the coordination is the point. The one-person business has none of those seats. A short end-of-week note to yourself, with the two or three promises still open and the one new fire, does the same job in two minutes. The reader is you; the register is plain.

I have watched this one more than once. A monthly report, several pages long, written for a client's steering committee that does not include the person it was sent to. It takes the better part of a day to produce. Nobody reads it; a few months later the client asks for a catch-up call because they cannot find it. The reader was never the person on the invoice, and the ceremony has been running on its own. When one of these reports finally stops going out, in my experience nobody writes back to ask where it went.

Governance surfaces whose job is to tell a chain of command what you could tell yourself on a walk. The bigger firm has architecture review boards and change advisory boards because every decision above a certain cost needs cover from someone who is not the person making it. The one-person business keeps a decision log of two lines per decision, in the same note as everything else. Two lines are enough: what was decided, and what was rejected and why. The point is to find the decision again in six months, not to persuade a committee the call was reasonable at the time. Those two surfaces, if you ask me, exist to translate between seats you do not have; keeping them for a reader of one is the paperwork without the point of it.

The yardstick is three artefacts

The three practices land on three things the reader already has in their week: the inbox, the invoice and the calendar. The inbox holds the promises in writing. The invoice holds the reason each line is there. The calendar holds what next week will not take on. The test is not that any of them looks professional. The test is that a stranger could pick up any one of the three and read the standard off it. If they cannot, there is a step missing that no amount of fifty-person styling will fill in for you.

The bigger firm has a name for the first of those: acceptance criteria as contract, the written statement that whatever gets built is answerable to. It is a bigger artefact when fifty people share it; it is the same idea, written in three lines in an email thread, when one person is holding it.

The fifty-person shop and the one-person business can share a standard without sharing a shape. The reader of this piece does not need to look like a fifty-person shop. They need to pass the one test the shop passes, which is that the written record holds. Building like fifty is not about looking busier. It is about leaving the trail a fifty-person shop would leave.