Case study
Signature is halftime.
A global enterprise deal I closed taught me that the signature is halftime, not the finish. This is how the deal was won, where it slowed down afterward, and what I do differently now.
The deal
The buyer was a European industrial group headquartered in the DACH region. It runs dozens of legal entities across several continents, and each entity pays its own invoices.
The contract covered the whole group. The rollout was planned in phases, country by country, starting with one pilot entity at headquarters.
Names, numbers and contract terms are left out on purpose. The pattern is what matters, and it repeats in almost every DACH enterprise deal.
What got it signed
The deal was signed because every function with a veto was won before the contract reached the board.
- 01
Start with the user, not the title.
The first demo went to an operational user. She became an internal fan and brought in the decision-maker.
- 02
Run a veto round early.
The champion invited finance and tax. The goal of that meeting was a single outcome: no veto. Tax questions are often the biggest blocker.
- 03
Stay between the two legal teams.
Contract, liability, data protection and exclusivity went back and forth between the two legal teams. I stayed in every exchange and explained each change to both sides, so nothing was lost or misread on the way.
- 04
Start implementation before signature.
Pilot scope, data templates and a weekly call were running while legal was still working.
- 05
Show up in person.
A visit on site built the relationship in a way calls alone had not.
- 06
Let the champion sell internally.
The board approval was her pitch. My job was to hand her short, visual material she could use.
Where it slowed down after signature
After signature the pilot slipped by months, and none of the causes were about the product.
The entities were mapped, but the plan was not approved.
Every legal entity had a phase and a platform. No one at headquarters had signed off a group-wide rollout plan. In the end the customer asked for exactly that: a redefined plan with org charts per country and plant.
The master data had gaps.
The pilot user list had no approver filled in for a single user. Without approvers there is no approval workflow, and without the workflow there is no go-live.
The board’s calendar beat the project.
The decision-maker sat in the executive office. A training was canceled at short notice for a board meeting, and the go-live moved with it.
Only headquarters had a data owner.
There was no global HR system. Outside headquarters nobody was named to keep joiners, leavers and cost centers current.
The contract ran on a date, the rollout did not.
The exclusivity clause switched on at a fixed date. Plants that were not live by then would have been bound to a tool they could not use yet.
The calendar was underestimated.
July, August and December are quiet in DACH, and the budget season in autumn ties up finance.
What changed
The answer was one rollout master plan with fixed gates, put in front of headquarters for sign-off before the next entities start. The rollout is still running, so this section describes the plan, not a finished result.
One standard, approved once.
Usage policy, approval model, invoicing standard and the data owner per country are decided at headquarters a single time.
Every phase is a new discovery.
Each entity runs through the same checklist: legal data, org chart, approvers, local finance, IT and existing local contracts.
Gates before go-live.
Data complete, setup accepted by local accounting, trainings done. A phase starts only when the one before has passed its review.
A fixed rhythm.
A weekly project call, a monthly steering meeting, and sign-off per gate. An operational deputy can decide when the executive office is tied up.
Go-lives in quiet windows.
Dates avoid the customer’s busiest months, the summer and the budget season.
Contract terms follow the rollout.
The proposal is to tie exclusivity to the go-live of each entity instead of a calendar date.
Why this deal needed German
The strongest champion in this deal would probably not have become one in English.
The champion was built in her language.
She sold the project to finance, tax, legal and the board. She could do that because every detail had been worked through with her in German first.
Complex contracts are discussed in German.
Tax models, liability, data protection and exclusivity are hard enough in a first language. In my experience many decision-makers in traditional DACH companies will not negotiate them in a second one. They go quiet, or they hand the topic to someone else.
Every function with a veto spoke German.
Finance, tax, legal and data protection each had to say yes. A seller who needs a translator in those rooms is a messenger, not a partner.
English came later.
Trainings and rollout material for other countries can run in English. The decision at headquarters did not.
What this means for your DACH entry
If you sell into DACH enterprises, the work between signature and full rollout can take longer than the sales cycle itself. Plan it inside the sales process.
Map the account before the contract.
Entities, countries, approvers, invoicing, IT and local contracts belong in discovery, not in onboarding.
Get the rollout plan approved by headquarters before signature.
A plan that only the project team knows is not a plan.
Multi-thread from the first week.
User, champion, finance, tax, legal, data protection, IT and the board each hold a veto.
Write the contract around the rollout.
Exclusivity, credit terms and pricing should move with each phase.
Name a data owner per country early.
Master data is the hidden blocker.
This is one example of a deal architecture Stark GTM builds and runs for companies entering Germany, Austria and Switzerland, and then hands over as a playbook.
Book a call