The 7 Roles in a Small Business (And Why Yours Are Probably Unnamed)

What roles does every small business run?

Every small business runs seven roles: attention, conversation, decision, delivery, quality, money and maintenance. They exist whether or not anyone has been given them, because the work they cover has to happen for the business to function.

In a small company those seven are rarely written down. They get absorbed by whoever notices them first, which is usually the founder, which is why the roles in a small business tend to be invisible until something breaks.

Naming them is the step that comes before hiring, buying software or automating anything.

Who is this for?

This is for a founder whose offer already sells. Clients arrive, the work gets delivered, money comes in. You are past the stage of wondering whether the business works.

What you have now is a different problem. Nobody can describe who owns what. You have a designer, or an assistant, or two freelancers, and their job titles describe where they came from rather than what they hold.

So the work moves, and every few days it stops and waits for you. Not because anyone is failing. Because the piece that stalled was never anybody's.

Key takeaways

• A small business runs seven roles whether anyone has named them or not: attention, conversation, decision, delivery, quality, money and maintenance.
• A role is defined by the outcome it owns, not by the list of tasks it performs.
• An unnamed role defaults to the founder, silently, and shows up later as interruptions.
• Gallup measured 46% of US employees in 2024 who strongly agree they know what is expected of them at work, down from 56% in March 2020. It is a self-reported survey across organisations of all sizes.
• Two different people can hold two roles each. Seven roles do not mean seven hires.
• You cannot delegate, automate or buy software for a role you have not named.
• The fastest way to see your map is to sort last week's interruptions into the seven.

Table of contents

• Why unnamed roles are the ones that break
• The seven roles in a small business
• What the evidence says about role clarity
• Name a role by its outcome, not its task list
• The role nobody held in a two person team
• A ten minute check you can run today
• Frequently asked questions
• Recommended tools and resources
• Where to explore next
• Final summary

Why unnamed roles are the ones that break

A role is a promise the business makes to itself. Someone will make sure enquiries get answered. Someone will make sure invoices go out. Someone will decide whether the deliverable is ready.

In a company of three, nobody writes those promises down. The founder holds all of them and is always in the room.

Then the business grows and the promises get split. The visible ones get handed over, because they look like work. Send the proposal. Post the content.

The invisible ones stay. Noticing that a supplier has gone quiet. Deciding that a piece is good enough. Knowing that the calendar link broke last Tuesday. None of those look like a task, so none of them get assigned.

The business keeps running until the unnamed promise goes unkept. Then it looks like carelessness, when it was a gap in the design.

The roles in a small business are worth naming for one practical reason. Once a role has a name and an owner, the question stops being "did anyone do this" and becomes "who holds this", which has an answer.

The seven roles in a small business

This is a working map rather than an org chart. Read each one as an outcome somebody owns.

1. Attention. The business is findable by the people it wants. Content, search, referrals, partnerships, whatever the channel. The outcome is that strangers who should know you, do.

2. Conversation. Interest gets a reply, and the reply moves it forward. Enquiries, DMs, follow-ups, the call that gets booked. The outcome is that nobody who raised a hand is left standing there.

3. Decision. Who you say yes to, at what price, on what terms. This is the role that almost always stays with the owner, and it is the one most often mistaken for admin.

4. Delivery. The client gets what they bought. The outcome is the work itself, finished, on the agreed terms.

5. Quality. Somebody says this is good enough to leave the building. In most small companies this sits silently inside delivery, which is why it disappears when delivery gets busy.

6. Money. Invoices go out, payments come in, late ones get chased, and someone looks at the numbers often enough to notice a change. The outcome is that the business knows where it stands.

7. Maintenance. The machinery keeps working. Access, files, tools, the booking link, the automation that stopped firing in July. The outcome is that the things you already built still do their job.

Seven roles does not mean seven people. One person can hold attention and conversation comfortably. Delivery and quality together is common and workable, as long as everyone knows quality is a separate promise and not a mood.

What matters is that each of the seven has a name against it. Including yours.

What the evidence says about role clarity

There is a measurement worth knowing here. In 2024 Gallup reported that 46% of US employees strongly agree they know what is expected of them at work, down from a high of 56% in March 2020.

Read that carefully before using it. It is a self-reported survey, run across organisations of every size, most of them far larger than yours. It measures whether people feel clear, and it does not prove that naming roles causes a business to perform better.

What it does tell you is that clarity of expectations has been getting worse in the years when tooling got dramatically easier. More software did not produce more clarity about who holds what.

If more than half of employees inside structured companies with HR departments cannot say what is expected of them, the odds that your three freelancers can are not high, and it has nothing to do with how good they are.

Name a role by its outcome, not its task list

Here is where most role descriptions go wrong. They get written as a list of actions, which reads like a job spec and behaves like a to-do list.

Flavie said this to a client during a working session, about prompts rather than people, and it applies exactly the same way here: describe the result, not the task. Say what you want to be true when it is done.

The difference shows up immediately.

Task version. Post three times a week. Reply to comments. Update the newsletter.

Outcome version. The right people keep finding us, and there is always a next thing for them to read.

With the first, someone posts three times a week into an empty room and reports that the task is complete. Nothing was wrong with their work. The task was the whole brief.

With the second, the same person notices that nobody is reading, and changes something, because the promise they were given was the result and not the activity.

That is also the test. If the description could be finished without the outcome happening, it is a task list wearing a role's name.

The role nobody held in a two person team

A client of mine runs a supplements company with two people on the team. In a session in April, we went through what was actually breaking.

Purchase orders were being missed. Suppliers were going unanswered for days. Invoices were getting lost in the middle of an inbox that both people were half watching.

Neither of them was working badly. Both were working hard, and both assumed the other had seen the message.

There was no maintenance role and no money role. There was an inbox, which belonged to everyone, which is the same thing as belonging to nobody. Every item in it was somebody's job in theory and nobody's promise in practice.

The fix started with naming, before any tool came into it. Once the two roles had owners, it became obvious which parts could be handled by a system and which parts needed a human decision. That order matters. Software dropped on top of an unnamed role automates the confusion.

A ten minute check you can run today

Open your calendar and your messages, and look at the last seven days. Not the whole month. Last week only, because last week is still honest.

Write down every moment where the work stopped and came to you. The question about a price. The "is this okay to send". The supplier who had gone quiet.

Now put each one next to one of the seven roles: attention, conversation, decision, delivery, quality, money, maintenance.

Two things usually appear. One role is generating most of the interruptions, and it is rarely the one you would have guessed. And at least one of the seven has no name against it at all, which has been costing you hours a week for months.

Decision is allowed to sit with you. That one is yours by design. Any of the other six landing on your desk repeatedly is a naming problem, and naming is free.

Do it on paper. A document you have to maintain is one more maintenance task.

Frequently asked questions

How many roles does a small business actually need?

Seven roles need to exist. The number of people is a separate question. A solo founder holds all seven, and naming them shows which ones are quietly eating the week.

Is this the same thing as an org chart?

No. An org chart shows reporting lines between people. This map shows promises the business makes, independent of who currently holds them. You can build it with a team of one.

What if one person holds three roles?

That is normal and often fine. What causes trouble is one person holding three roles without knowing it, because then the two that are least visible get dropped when the week gets busy.

Which role should I hand over first?

Usually the one producing the most interruptions that are not decisions. Run the ten minute check and it will tell you. Handing over the loudest role first buys back the most attention.

Can I automate a role instead of hiring for one?

Parts of a role, yes. A whole role, rarely, because every role contains at least one judgement. Automate the repeatable pieces underneath a named owner, and keep the judgement with a person.

Does naming roles mean writing job descriptions?

It means one sentence per role saying what is true when that role is doing its job. A long document is a different project, and usually a stalled one.

What if I cannot afford to hire for any of these?

Naming still pays. Much of the cost of an unnamed role is the switching, the re-deciding and the forgetting. You get some of that back before anyone new is paid.

How is this different from documenting processes?

A process describes how something is done. A role says who owns the outcome. Process without ownership produces a document nobody opens, which is why roles come first.

My team is freelancers rather than employees. Does this still apply?

Yes, and the gaps are usually wider. A freelancer is scoped to a deliverable, so the promises around the deliverable are the ones nobody picked up.

What happens if I skip this and buy software instead?

The software runs the part somebody already understood, and the unnamed part stays unnamed. You end up with a tool nobody owns, which becomes a maintenance item.

How often should I revisit the map?

When something changes in the business rather than on a schedule. A new offer, a new hire, a channel you stopped using. Each of those moves at least one of the seven.

Recommended tools and resources

• A single sheet of paper. Seven lines, one per role, one name against each. This is the whole method, and starting anywhere more sophisticated is how it stops.
• Your last seven days of calendar and messages. The only honest source for where the roles in a small business actually sit today. Memory will tell you a flattering version.
• Gallup's Q12 research on clarity of expectations, for the measurement quoted above and its methodology. Read it as context on a broad employee population.
• A shared document for the seven sentences, once the paper version has survived two weeks.

Where to explore next

• How to Delegate Without Losing Control: what to do once a role has a name and needs an owner who is not you.
• The 5 Decisions You Should Never Delegate in Your Business: the decision role in detail, and where its boundary sits.
• Hire vs Automate: How to Tell Which One Your Business Actually Needs: the question that comes immediately after naming a role.
• How to Know What to Fix First in Your Business: sequencing, when the map shows more than one gap.
• Where AI Doesn't Belong in Your Business: what to settle about a role before any tool takes it over.
• 7 Signs Your Business Has Outgrown Its Systems: what it looks like from the outside when the roles have drifted.

Final summary

The roles in a small business exist before anyone names them. Attention, conversation, decision, delivery, quality, money and maintenance all have to happen, and the ones nobody has claimed default to the founder without any announcement.

The cost arrives as interruptions, as things remembered at eleven at night, as a supplier who went quiet three weeks ago.

Naming the seven takes an afternoon and costs nothing. It also changes every later decision, because hiring, automating and buying software become answerable once you know which role you are talking about. Skip it, and each one gets made in the dark.

Start with last week's interruptions. Sort them into the seven. The map you get is the real one.

Want a second pair of eyes on how your business is designed?

If you have run the check and the map is telling you something you do not like, bring what you found. We will look at the whole picture, including the parts you have stopped noticing.

Book a call