Revenue went up. So why did the job get harder?
A method for drawing one map of your company — how customer pain turns into promises, processes, people, and only then into structure — so the same problems stop coming back.
Why am I still in every decision?
Why do the same problems keep coming back?
We hired strong people — why are they stuck in the same routine, producing less change than everyone expected?
We bought expensive software — why is there just as much chaos as before?
If I had to hand this company to someone else tomorrow — could I explain how it actually works?
If you recognize these questions, this book is for you.
Your company doesn't have a map. Not an org chart — a map: a single picture showing how the pain your customer feels turns into the promises you make, the processes behind those promises, the people and systems that execute them, and the structure that holds it all together.
The 7 Horizons Framework is a method for drawing that map. Not for the whole company at once — for one core customer segment, enough to start making better decisions this quarter.
Each layer generates the next. That is why the map is a graph and not a list: change one node and you can see what moves downstream before it moves.
Org structure is a conclusion, not a starting point.
I wrote this for owners and CEOs of companies doing roughly $10M to $500M with 50 to 500 people.
You have outgrown gut-feel management. You can no longer keep the whole system in your head. "Just hire good people" stopped being a strategy — you hired good people, and they got stuck in the same mud. The company isn't broken. Revenue may even be growing. But decisions take too long, problems return in new forms, and when a strong person leaves, a surprising amount of knowledge about how things actually work leaves with them.
The CEO will buy this book. The COO will use it every week.
If you're a startup before product-market fit: don't draw the full map yet. Read Chapter 2 — locate yourself honestly on three scales — and Chapter 18, for what investors will expect at later rounds.
The point isn't to wear a big company's structure while you're four people. It's to know where the seams are, so you don't spend two years optimizing into a shape you'll have to demolish. Some transitions can't be tuned through. They have to be rebuilt.
If you're a large enterprise with a transformation office, you have different problems and different budgets.
My name is Serhii. I've spent twenty-five years building IT businesses — three companies of my own in telecom and contact centers. Two became leaders in their niches, 29% and 49% of their markets according to industry publications. One of those two I lost to a hostile takeover. I personally led more than 150 B2B contact center implementations, and served two terms as president of the Kyiv Entrepreneurs Club. Kyiv, then Los Angeles.
Why do contact centers give me standing to write about business design in general? Because a contact center is a laboratory where the entire map is visible to the naked eye, every single day. Customer pain — they can't get through. Touchpoint — call, chat, email. What you promised — answer in 30 seconds. The process that delivers it. The supporting process nobody notices until it breaks. Who does it: your person, an outsourcer, a bot, or a service you bought. And the structure holding it together.
The mistakes in those five questions above — buying tools, hiring people, copying practices without understanding why they work — I made every one of them first.
It's a 500-page book. You probably shouldn't read all of it.
"I have a specific problem."
Revenue is leaking, a key person is about to leave, a process keeps failing the same way. Don't start at Chapter 1. Start at Chapter 11 — find your symptom in structural terms, trace the damage, then jump to the layer where it started.
"I want a system that doesn't depend on me being in every decision."
Chapters 1 through 10, in order. Foundation plus all seven horizons. The sequence matters because each layer constrains the next. Then Chapter 14 for a 90-day plan.
"I'm evaluating a business — for investment, acquisition, or succession."
Start at Chapter 18 — what kind of map to reasonably expect at this stage. Then Chapter 11, for structural risk and hidden concentration a financial model won't show you.
The worksheets
The templates from Appendix A as spreadsheets: dropdowns, conditional formatting, linked sheets, ready to fill. English, Russian and Ukrainian. Free.
DownloadThe First Map
I work with your team on one customer segment and we draw the first map together. You keep the map, and the three things it exposes.
Get in touch