3,000 leads were in a CRM that no one trusted.
Jannik joined a B2B consultancy as an inside sales representative. The pipeline was there — at least on paper. Around 3,000 contacts were in HubSpot, accumulated over time, hardly touched, not neatly sorted, not clearly measurable. No clear scripts. No clear system. No picture of what works and what doesn't. Calls took place every day, but without structure and without a clear goal.
From an operator perspective, this is exactly what an unstructured pipeline feels like: chaos, pressure, self-doubt. “I felt absolutely terrible in that setup,” Jannik later wrote on Trustpilot. It was chaotic. There was no clear structure, no clear goal and no measurable results.
CRM changed. Scripts disassembled. Rebuilt from real calls.
Domenic started with the tool first: a new CRM with the structure that sales really needed, not with the structure that happened to already be there. Then came the scripts. Existing call recordings were listened to, the old scripts dismantled and rebuilt from what worked in real conversations. Not from theory. From Jannik's actual calls.
The process is typical for MSA: first the structure, then the script, both made of real material. A nice framework doesn't automatically survive the fifth call. Patterns from real conversations do.
Three weeks. Every 3,000 leads. The funnel leak was visible.
The entire 3,000-lead backlog was worked through, sorted and qualified within three weeks. Good leads were separated from dead leads. Patterns became visible. The funnel leak was no longer a guess, but a concrete, pinpointable problem.
From this point on, sales no longer feels improvised, but rather a process. Volume becomes measurable. Work doesn't become less serious, but it does gain direction.
At Dietrichs Consulting, the system was built from day one.
Jannik's next role was at Dietrichs Consulting GmbH, the company from the e-commerce consulting testimonial, which grew from $38,000 to over $100,000 in monthly sales in a parallel MSA collaboration with the founder. For Jannik this meant that he didn't end up in a mess that had to be repaired later. He came into a setup where the structure was built from the start.
According to Jannik, the difference was like night and day. Clear structure from the start. A script that works. A power dialer that stands. Bringing performance to the road was no longer a future goal, but the daily mode.
300-400 calls per day. Sometimes 500. Never less than 150.
Once the system was up and running, volume was no longer just a matter of will. It became a consequence of the structure. 300 to 400 qualified calls a day, sometimes 500. Not because Jannik suddenly became a different person, but because the system took the friction out of the way: lead routing clear, script clear, power dialer active. The attention was on the conversation, not on the chaos around it.
Jannik puts it himself this way: “If I did X, Y, Z, I got a predictable result.” This phrase is the core of Revenue Architecture. Predictability does not replace work. It ensures that work goes in the right direction.
When the script worked, the system was already there.
Jannik describes a specific moment: The script worked, and at the same time the system behind it was already built. From then on it was no longer a search. It was execution. Volume no longer depended solely on hardness, but on a process that knew what would happen next.
MSA is working towards this moment. Not on motivation. Not on perseverance slogans. To the moment when an operator no longer has to think about the system, but only about the people in the conversation. Then daily volume becomes controllable again, not just a burden.
From an operator's perspective, in his own words.
From Operator to Enterprise BDR. With a system in mind.
Jannik now works as an Enterprise Business Development Representative in a B2B SaaS company. CRM discipline, script clarity, predictable volume and the idea of “system over willpower” continue to accompany him. This is exactly how you can tell whether the work has really been carried out: it stays with the operator, even if the company changes.
Sales structure transfers. It is not tied to one company.
The same architecture has sustained two successive companies and continues to operate in a third. She has survived a CRM transition, script work, high call volumes and a career change. MSA doesn't just build a special solution for an individual case. MSA builds forms that people can understand, execute and carry forward.
That's why the unity of our work is architecture, not consulting hours. Consultation time ends. A good system lasts — in the company that uses it and in the people who have learned to run it.
