A stack a small firm can actually run

Small firms accumulate software the way desks accumulate cables. A new problem, a new login, a card that nobody cancels. Two tools overlap. The overlap has no owner. Reporting means exporting three spreadsheets and hoping.

Draw the work, not the vendor landscape. How does a stranger become a client, a client become a project, a project become an invoice, an invoice become cash? For each handoff, one system of record. Not a favourite. A record.

A website sits at the front of that path. It should brief a serious buyer: who you serve, what the work is, what it is not, and how to start a conversation. It does not need a tour of your values before it says what you do.

Then cancel what the map does not require. Assign each remaining system to a person, with a quarterly hour to review access, cost and whether it is still the record. A stack you can explain on one page is a stack you can run when someone is on leave.

Every tool needs a name next to it. If the name is “everyone”, the name is no one.

HI