Relationships
Growth is built on relationships.
Your next round rests on relationships.
Every lane runs on relationships.
Retainers grow out of trust.
Your order book runs on relationships.
Finance, strategy and implementation only work if the people behind them trust one another. This is the cornerstone on which everything else rests.
Your board, your lead investor, your first fifty customers and your sales team: numbers and plans only land when those people trust you.
Margin per lane, fleet planning and your credit line only work when shipper, subcontractors, drivers and bank build on your word. That carries the rest.
Your margin depends on the product owner who signs off on time, the senior developer who stays and the client who signs a retainer after the project.
Your German buyer, the bank funding your work in progress, the supplier of your control cabinets: every machine you ship rests on their trust.
A relationship is an agreement about the truth.
Trust isn’t built on a sales pitch, but on what you consistently demonstrate: accurate figures, commitments you honour, and a consistent approach. That is the foundation on which a relationship is built.
Your board does not trust you for a polished deck. That trust grows when the NRR on slide four matches your CRM, when last quarter's forecast held and when you can trace every variance back to one source.
A shipper does not trust you for your quote. He trusts what he sees every week: a fuel surcharge that visibly tracks the index, a CMR scanned within a day, an invoice that matches the agreed rate line by line.
A client does not trust you for your demo. They trust you when the timesheet matches the invoice, when every change request carries a price before any code exists and when you put the sprint cost-to-complete on the table unasked.
A German buyer does not trust you because of your presentation. He trusts you when the second milestone invoice matches exactly what he saw on your shop floor, and when every drawing change can be traced. That is what the relationship stands on.
A relationship is built on a thousand small choices, not on a single contract.
What looks like a single picture from a distance turns out, up close, to be made up of separate pieces: a question answered, a correct figure, a deadline met. Each piece on its own is small. Together, they determine whether someone trusts you.
What a customer calls a good vendor turns out, up close, to be small moments: a P1 ticket picked up within the hour, an invoice that matched the quote, a feature that shipped in the promised release. Together they decide the renewal.
What your customer sees as one carrier is made of small moments: the planner who rings at quarter past six to say the trailer is stuck near Oberhausen, a pallet count that matched at unloading, a missed slot you rebooked yourself. Each is minor. Together they decide your next tender.
A P1 ticket from Friday evening that is fixed by Monday morning. An estimate of forty hours that lands at forty-two. A status email that arrives before the client asks for it. On its own each moment is small. Together they decide whether your framework contract gets renewed.
From outside, your company is one name on a rating plate. Up close it is small moments: the service engineer who calls back the same day when a line stands still, the seal shipped the next morning, the extra-work price agreed before assembly. Together they build trust.
That is why we do not build a pitch, but rather build up a series of small pieces of evidence — until trust is no longer a risk, but a given.
Without a relationship, there can be no implementation.
Without trust, everyone waits for a signature before taking any action. With trust, a decision immediately becomes action, and that action remains measurable and traceable for everyone around the table.
Without trust, your account executive waits for your sign-off on every discount above ten per cent, and the deal slips into next quarter. With trust, he applies an agreed discount policy himself, and everyone in the pipeline review sees what it cost.
Without trust, the bank waits for the annual accounts before approving the lease on new warehouse reach trucks, and your shipper won't renew until your rate is in. With trust, everyone signs on the same trip data, and every kilometre stays traceable.
Without trust, the client has their IT manager sign off every sprint, and every release waits a week for a signature. With trust, a change goes into the backlog after one call, priced and visible to both sides.
Without trust, your engineers wait for the down payment and your customer waits for your bank guarantee. You lose three weeks of lead time before one drawing exists. With trust, the order starts at the handshake and every step stays traceable.
A breach of trust leaves scars, even after it has been repaired.
A relationship that has once been broken will always bear the scars of that break. You can piece the fragments back together, but the cracks remain visible — in the way someone asks questions, in what they no longer take for granted.
A customer who first saw your price increase on his invoice may still renew. The crack stays: from now on he questions every quote line by line, and he signs a multi-year contract only with a termination clause.
Bill one toll surcharge that doesn't match the kilometres driven, and your shipper checks every line from then on. You issue a credit note. The seam still shows: in payment terms that slide from 30 to 60 days, in the questions at every new tender.
Send one extra-work invoice the client never saw coming, and it sticks. The project carries on, but from then on their procurement lead asks for an hour-by-hour breakdown on every quote and checks each line of your invoice against the plan.
One extra-work invoice that arrived after the fact, and the relationship carries a crack. Orders keep coming, but the buyer now wants every engineering hour itemised and asks for a penalty clause in the next quote. That seam shows in every meeting.
That is not a weakness. It is the reason why we choose never to work on repairs after the event, but on preventative maintenance.
We’ll continue to stand by your side.
Not just a one-off assignment that ends upon completion, but a partnership that grows alongside your next step. We’ll stay involved, even after the first project has been completed.
Our work does not stop at a finished pricing model. We stay at the table when, after your Series B, you go live with your first German enterprise customer and your board asks what DACH costs before it pays back.
We stay at the table when your next step comes: a second warehousing client beside your own haulage, or your own cross-dock on the German side. The first project is where that starts.
We stay at the table after the first review. Also when you move from one-off projects to managed services at a fixed monthly fee, and your largest client needs to become a smaller share of revenue.
After the first project the harder step often follows: growing service and spare parts into steady margin, or preparing the handover to your successor. We stay at the table for that step too.
A good working relationship never involves just one point of contact.
Finance, strategy and implementation are not separate disciplines that only come together at the end of the process. They involve people who need to be able to liaise with one another throughout the process, without everything having to go through a single point of contact.
Your CFO, VP Sales, Head of Customer Success and product lead need to talk to each other directly between board meetings. If everything runs through you as founder, you learn at the churn review that a key account had doubts for weeks.
Your planner sees the empty kilometres, your controller sees DSO creeping up and your sales lead agrees the annual rate. If everything runs through the owner, he signs a contract the lane never earns back. Let them speak to each other directly, before the signature.
Your account manager, the lead developer and your controller need to reach each other mid-project. If everything runs through that one account manager, finance hears about the scope creep at month-end close. And if he leaves, your biggest client may leave too.
Your project manager, your head of engineering and your controller must be able to talk to each other halfway through an order. If everything runs through the salesperson who won it, you see the overrun hours only in the post-calculation. By then the margin is gone.
We therefore build relationships on several levels at once — so that the collaboration remains strong, even if one person leaves.
Build a relationship that pays off.
A brief closing line that leads into the conversation.
Which relationship slows your ARR? 30 minutes to find out.
Spend 30 minutes on the relationships behind your lanes.
Bring your three biggest accounts: 30 minutes, one table.
In 30 minutes, see which relationship carries your orders.
30 mins · senior consultant · no slide deck