TOPOS

enter TOPOS
← All patterns
Pattern · Small Business
Self-serve
a team the apps they already use one node the business’s the owner what moved the team the weekly nobody installs anything
What’s in the box
Nodes
OneThe business’s, on a machine you choose
Connectors
Two, to startWhere the team talks, where the work is tracked
Agreed first
A short listWhich systems it reads. It holds work, not lives
From the team
NothingThey keep their tools. Zero adoption
Running in
A weekMaking the two reads good takes longer
The hypothesis

That the business already knows what is happening and simply cannot assemble it without interrupting four people. If that is right, the status meeting stops being the mechanism — and you will see it in the first month.

BenefitsSetupHow it worksThe caseIngredients

Stop finding out on Thursday what broke on Monday.

The apps your team already works in feed one node. It tells you what actually moved, and sends the team a weekly read they will open. Nobody changes tools and nobody installs anything.

Benefits Illustrative

Two reads off one node, plus the same thing posted where the team already is.

Every morning · to you
What actually moved
  • The Fairfield job shipped Tuesday. Invoice not raised.
  • No reply from Northgate in eleven days. Was weekly before that.
  • Two people are both on the rebuild. Nobody is on the audit.
Three lines you would otherwise get by interrupting four people.
Friday · to the team
This week
  • Shipped: Fairfield, and the export fix.
  • Next: the rebuild, and the audit nobody has picked up.
  • Stuck: Northgate, waiting on them, not on us.
One page. The meeting this replaces was forty minutes.
Monday 9:02 · in the team chat

Same summary, posted where they already are.

Nobody opens a new tool to read it. The connector that brought the week in is the one that puts the summary back.

PostedEdit first
Setup — what the team does

Nothing.

They keep working in the tools they already have open. The connectors read those. Adoption is what kills software like this, so this shape asks for none of it — there is nothing on anyone’s machine, no new login, and no habit to build.

You point it at two things first

Wherever the team talks, and wherever the work is tracked. Those two carry most of it. Everything else gets added the first time someone misses something.

It holds work, not lives

Which systems it reads is a short list agreed when it goes in, and personal accounts are not on it. Worth writing down before anyone connects anything — we write it down with you.

How it works

Many people in, one node, two reads out. Still no layer between nodes, because there is still only one node.

1 · THE TEAM they keep working exactly as they do now 4 · CONNECTORS the team chat the project board the CRM shared drive calendar work email the apps they already open every day 3 · ONE NODE, THE BUSINESS’S what actually shipped this week which client has gone quiet what got promised on Tuesday who is carrying too much of it WHERE IT RUNS in the office or hosted 5 · COMMUNITY INTELLIGENCE NONE IN THIS SHAPE one node. Nothing runs between nodes, because there is only one. your business data never joins anyone else’s 6 · THE FEEDBACK LOOP — two reads, from one node The owner’s read what changed, what slipped, what is waiting on a decision only they can make daily, or whenever they ask The team’s weekly one page, Friday: what we did, what is next, what is stuck and on whom by email · nothing to install Back inside the apps they use the same summary posted into the team chat, or onto the board — where they already are the connector runs both ways This node holds work, not lives. Which systems it reads is set when it is installed, and it is a short list.

Drag sideways to read the whole diagram →

The team is the input and the audience, and never the operator. They keep their tools; the connectors do the funnelling. One node means nothing has to work between nodes, which is why this shape needs nothing built either — and why the boundary that matters here is which systems it reads, not which people can see it.
The full case
Who it’s worth something to six layers, and the arithmetic you do yourself
The value stack
Beneficiarythe employee They can see what everyone else is doing without asking, and their own work shows up in what the business says about itself.
Userwhat they actually do Nothing new. They keep working in the tools they already have open.
Operatorwhoever runs the week The status meeting stops being the only way anyone finds out. The chasing stops being a job.
Buyerthe owner A read of the business that does not depend on interrupting four people, and a team that is informed without another meeting on the calendar.
Championspends the capital Usually the owner, or the first ops hire who is tired of being the company’s memory. This is the argument they have been making.
Economicwhat actually moves Hours in status meetings. Work redone because nobody knew. Clients who went quiet before anyone noticed. Time-to-productive for the next hire.
The number, honestly

We will not print a return on investment here. Every figure in it would be invented, and the first person to check would be right. So the worksheet does the half we can do.

What that costs you a year — computed in your browser. Nothing is sent anywhere.
What it becomes once this runs you measure it the first month tells you, and the number is yours.
Ingredients, and getting it running what it needs on day one, and the three things worth deciding together
What it takes

Who needs a node

The business. One node, one owner of it. Employees are contributors and readers, and never operators — there is nothing on their machines.

Where it runs

A machine in the office is the strongest version and the one most businesses pick, because the answer to where is our data is a room. Hosted works too, at roughly $20 per seat per month.

What runs, and what we’d shape with you
All of this, today
  • One node holding the business’s work, on a machine you choose.
  • Connectors reading the tools the team already uses.
  • Routines on a schedule, and on demand.
  • Delivery by email, and back into the team’s own tools.
  • Aggregate answers that count without naming anyone.
Worth deciding together
  • What counts as needs you. That threshold is specific to a business, and getting it wrong turns the whole thing into noise.
  • The weekly, so people open it. One page, in the register your team actually speaks. More a writing problem than a software one.
  • Which two connectors first. The order matters more than the count.
The other two patterns
Individualsthe same shape, for one person Organizationmany nodes, and a layer between them