What you actually get.
An illustration, built on a company that does not exist
One full week of signals, the monthly review with the numbers, what is handed over at each step, and the assumptions behind the first year. Every name and every number on this page is invented. The shape and the level of detail are real.
Back to Relationship OS
Monday, 8:00. Five signals, and why each one is on the list.
Three of them come from outside your company. Two come from inside it, and those are the difference between a news feed and a system that also watches your own discipline.
Promoted on Tuesday, after four years as Head of Controlling. Trusted connection: Anna. They worked together from 2016 to 2019, last exchange in March.
Action: Anna congratulates her and reopens the pilot that stalled on budget. As CFO, the budget is now hers. Message template attached.
Gamma is on your target list. Trusted connection: Gábor. They worked on a joint supplier project in 2021.
Action: Gábor congratulates him now, and asks for the introduction in two weeks, once Novák has settled in. Timer set.
K. Tanaka became Head of Ops in the spring reorg. Trusted connection: Petra. Three years on the same team, they still meet at industry events.
Action: Petra asks for the introduction while the Munich vendor list is open. Deadline in two weeks.
He is your only strong route into MedTech, which makes it a concentration risk. Nothing went wrong. The relationship is simply going cold.
Action: a step back that gives something, not a sales one. Last week’s industry report with one personal sentence. Draft attached.
The quote promised in the meeting summary is 12 days late. Deals are won in the follow up, and this one is slipping.
Action: today. Draft of the covering email attached.
If a week does not produce five signals worth acting on, three go out instead of five. Fewer, but certain. A list nobody trusts is worse than a short one.
One page, two minutes, measured against your own starting point.
The top line is the outcome. The middle is the funnel, every weekly card followed to where it ended. The bottom line is what happened to the network itself.
- Signals sent21
- Acted on14 · 67%
- Replied9 · 64%
- Became a meeting4 · 44%
- Became an opportunity2
Next month: close the Munich thread, and build a second person into the MedTech route.
Every number here comes out of the signal log. The review is generated, not written up, which is why it arrives on the same day every month.
What is handed over, step by step.
| Step | What you get | Built from |
|---|---|---|
| 1 · Snapshot EUR 1,000 · 1 week |
The merged, deduplicated contact map as a spreadsheet you keep. The companies in your target market you can already reach, with strong, medium or weak paths and the name that opens each door. A surprise list: companies and markets nobody in the room had thought of. A half page summary and a 30 minute readout. | The LinkedIn export of 2 or 3 leaders, plus a short questionnaire. No system access. |
| 2 · Network mapping + setup 4 to 6 weeks |
The full relationship inventory for up to 10 people: contact, who owns it, last touch, strength. The reach map with routes: target company, trusted connection, suggested way in. Your baseline numbers, which everything later is measured against. A prioritized 90 day action plan. The practice set up around your stack, the team trained, an internal owner in place. And the first live signals. | The above, plus email and calendar metadata, CRM data and client lists, at the connection level you choose. |
| 3 · Signals weekly · 12 month term |
The weekly signal package: 3 to 5 cards, each with what happened, who the trusted connection is, the suggested action and a message template. The one page monthly review above. A consultation every two weeks, and support before an important negotiation. A quarterly report on what is going cold and what is worth reinforcing. | Continuous feeds from the sources you connected, plus outside signal sources that sit on our side, not yours. |
What has to happen for the first year to pay for itself.
These are not promises. They are the assumptions written out, so you can put your own numbers in. After three months of real data, your numbers replace these. The monthly review above shows a month running at five signals a week; the table below deliberately uses three, the conservative floor.
| Step | Assumption | Over a year | Why that number |
|---|---|---|---|
| Signals sent | 3 per week | 144 | the floor of the weekly package, not the target |
| Acted on | 40% | 58 approaches | realistic with a ready template and a trained team; without them it is 10 to 20% |
| Replied | 30% | 17 conversations | a warm route with a reason to write; the cold email benchmark is 1 to 5% |
| Became a meeting | 40% | 7 meetings | conversion once someone already knows the person introducing you |
| Became an opportunity | 30% | 2 opportunities | B2B average |
| Closed | 25% | about 1 deal | segment average close rate |
Where the line is
If one closed deal in your segment is worth what the first year costs, the conservative case above already pays for it with a single one. Everything past that is the return, and it does not count the admin time your team should get back.
For comparison: a cold outbound agency costs EUR 2,000 to 3,000 a month and works at a 1 to 5% reply rate with no trust behind it. A mid-level BD hire costs about the same as this first year, ramps for six to nine months, and leaves with their network. Here the arithmetic starts warm, and everything it builds stays with you.
The real version is built on your own network.
The Snapshot is where it starts: one week, no system access, and you see how far your company already reaches before you commit to anything.
Back to Relationship OS