Blog

Process landscape of a small business: core, management and support processes, with an example

You mostly know the process landscape from quality management: a picture with arrows and boxes, management at the top, core processes in the middle, support at the bottom. For a business with 3 to 15 people, it can be something simple and useful: one page that shows you how your business makes money, who steers it and what has to keep running in the background. And it shows you where everything depends on you. In this article, we explain the three layers in plain owner language, give you a template to fill in and show the process landscape of Kevin's own business.

What a process landscape shows

A process landscape is an overview of the major process areas in a business, sorted into three layers. It shows how the parts fit together. Individual tasks and steps belong somewhere else. The technical terms for the three layers are core processes, management processes and support processes. We translate them into three questions that every owner can answer.

Core processes: what brings in money

Core processes are everything that has to do with your customers directly: how customers find you, how an inquiry turns into an order, how you deliver and how you invoice. When a core process stalls, the customer notices. In a trade business, these are the inquiry, the quote, the job itself and the invoice. In a consultancy, they are the first conversation, the engagement and the actual expert work.

The test question is: Does the customer notice right away when it stalls? If yes, it's a core process.

Management processes: what steers

Management processes decide where the business is going. Setting goals, setting prices, hiring people, looking at the numbers, shifting priorities. For you, this probably happens between two appointments, inside your own head. That's exactly why it's worth writing them down. What isn't written down anywhere, nobody else can take over.

The test question is: Is something decided here that applies to other processes? If yes, it's a management process.

Support processes: what carries the load

Support processes keep the business running without the customer seeing them: preparing the bookkeeping, handling mail and email, filing, coordinating appointments, looking after IT. They don't bring in money, but if they're left lying around, the core processes stall sooner or later.

The test question is: Does the customer only notice when something goes wrong? If yes, it's a support process.

For our work, this layer is often the most interesting one. Support processes repeat often, follow rules and, at the end, mainly need a report saying that they're done. That's exactly the kind of work an AI employee can take over. But there's also plenty in the core that can simply be done, as the example below shows. Whatever needs judgment, ideas and concepts, stays in conversation with you.

The process house: the same landscape as a picture

Some people draw the process landscape as a house. The roof is the management processes, below it the core processes stand as rooms or pillars, and the support processes form the foundation. That's where the name process house comes from. In substance, it's the same thing, just in a different shape.

The picture has one advantage: everyone on the team gets it right away. Whoever works in the foundation sees that the house doesn't stand without them. Whoever sits in the roof sees that they don't have to work in the rooms themselves. If the house helps you in the conversation with your team, use the house. If a table is enough, use the table. The shape is secondary. What matters is that you agree once on what goes where.

How to show a single process, as a list, as a process profile (our word for a process description) or as a flowchart, is described in Process visualization: three formats your team understands.

Template: your process landscape on one page

You don't need a drawing program. A table with three rows is enough. In each layer, enter the process areas that exist in your business, and add who does them today. The areas in the second column are the same ones we use in our template for the process map.

LayerAreas to choose fromYour process areasWho does it today?Does it depend on you?
Management: what steersLeadership and steering, HR……yes / no
Core: what brings in moneyMarketing, sales, fulfillment (delivering the service), customer service……yes / no
Support: what carries the loadBookkeeping and finance, administration and back office, HR……yes / no

HR appears in two rows on purpose. Whom you hire is a management decision. Payroll and the vacation schedule are support. Overlaps like this are normal. Decide once where they go and stick with it.

The last column is the most important one. It shows you at a glance where your business depends on you. If there's a yes in more than one layer, you can see the places where your business depends on you today.

How to build the process landscape with your team

You can fill in the table on your own. It gets better with your team. We do it in three steps.

  1. Core processes first. Start with the customer and walk the path once: How do they find you, how do they make an inquiry, how do they get a quote, how is the work delivered, how is it invoiced? Every stop on that path is a core process.
  2. Then support. At every stop, ask: What has to happen in the background for this to work? This is where the people on your team help you most, because they do this work and you often don't even see it.
  3. Management last. Write down what you decide and how often. For every item, ask yourself: Is this a real decision, or am I signing off here out of habit?

Keep the landscape rough. It should fit on one page. Once you start entering individual tasks, you're already working on the process map.

Process landscape and process map: the frame and the working state

This is the difference that matters in practice. The process landscape is the frame. It shows the major areas and rarely changes. The process map is the working state. It lists every recurring process individually: who does it, how often, how long it takes, what starts it, and whether it takes thinking or just doing.

An example: in the process landscape, "Incoming mail" sits under support. On the process map, there are several individual processes below it, such as scanning letters, sorting emails with attachments, and passing invoices on to bookkeeping. Only at this level can you say which process is worth handing to an AI employee first.

That's why, in Owner Autonomy, the process map is the worksheet. The first month starts with us creating it together with your team and choosing your process from it.

The process landscape is still a good place to start: it makes sure you don't forget an area while you collect processes. How the process map comes together and how to choose the first process from it is covered in Creating a process map: an example and choosing process no. 1.

How this differs from the process landscape in quality management

In quality management, the process landscape is a widely used tool, for example in businesses that work according to ISO 9001. There, it serves to steer and improve processes and to show them to third parties.

We use the same three layers for a different question: Which work can someone else take over, a person or an AI employee, and where does the business depend on its owner today? Both purposes have their place. For documentation according to standards, we're not the provider, and what a standard requires is not the topic of this article.

If you already have a process landscape from quality management in a drawer, you can use it directly as the frame. Below it, you then write the individual processes into the process map.

What this looks like for us

Kevin runs his own business with 14 AI employees: content, SEO, video editing, bookkeeping prep, leads and email. Each one has a personnel file, a fixed role and clear limits. An AI manager reviews their work; that role is still on trial.

If you lay that out in the three layers, the process landscape looks like this. It stays at the level of areas. The assignment to layers is our own reading; the details come from our home page.

LayerAreasWhat belongs to it
Management: what steersLeadership and steeringKevin decides; an AI manager reviews the AI employees' work, and that role is still on trial
Core: what brings in moneyMarketing, sales, fulfillmentContent, video editing, SEO and leads with AI employees; the 1:1 with Kevin and the communities Claude Practitioners (German) and AI Employee Framework (English)
Support: what carries the loadBookkeeping and finance, administration and back officeBookkeeping prep and email with AI employees

That's all a process landscape contains. Which individual processes sit below these areas, who does them and whether they take thinking or just doing is shown on the process map. A filled-in example from the same business is in Creating a process map: an example and choosing process no. 1.

Even these three rows show something: in the core and in support, AI employees work alongside the people, while management stays with Kevin. The next autonomy level starts with management. Kevin tries new levels in his own business first, before they come to a client's business.

At a tax advisory firm, the landscape looks different, but the pattern is similar. The core is the professional work for the firm's clients. The professional work and the final check stay with people there. The first two processes an AI employee took over there are in support: filing digital tax assessment notices and the notices that arrive on paper. Both are at Autonomy Level 2, Autopilot (as of September 2026).

Frequently asked questions

What's the difference between a process landscape and a process map?

The words are often used interchangeably, and some people call it a business process map. We keep them apart: the process landscape shows the major areas in three layers. The process map lists every recurring process individually, with how often it runs, how long it takes and who does it. The landscape is the frame, the process map is the working state.

Does a business with ten people even need a process landscape?

Not necessarily as a picture on the wall. As a page on which you agree once what counts as core, management and support, it's worth it. It helps you collect the processes and shows where everything depends on you. Whether you turn it into a whole manual is a different question. We answer that one in Creating a process manual: does a business with ten people need one, and what is enough instead.

Where does marketing go?

We put it in the core, because that's how customers come in. If you see it differently, you're not wrong. What matters is that you decide once.

How often do I have to change the process landscape?

Rarely. It changes when your business changes, for example through a new offer. The process map below it changes much more often, because that's where every process stands with its current state.

Read more

What comes after the process landscape is the actual documentation: the process map, process profiles and rules in one place. We describe that in Business process documentation in a small business: as little as possible, enough for someone else to run it. Kevin's own page for businesses with a team is called Process Optimization for SMEs.

Your next step

With three rows on one page, you can see where your business depends on you. On a call, we go one level deeper from there and look for the process that can be the first to go to an AI employee.