How We Work

Talk, agree, deliver

Every partnership we run follows the same three steps. The steps are simple on purpose; their value is in doing each one properly.

Step 1 — Talk

We begin with a conversation, not a proposal. We want to understand what you sell, who you sell to, how you deliver today and where extra capacity or expertise would help most. We also ask about the things that went wrong in past partnerships, because those tell us what to protect against. We will be candid about whether we are a good fit. Sometimes the honest answer is that a different kind of firm would serve you better.

Step 2 — Agree

Once we have decided to proceed, we write down how the partnership will work. The document is short and readable. It covers:
- Roles and responsibilities: for each workstream or task.
- Communication: who speaks to the customer, who attends which meetings and how often we report.
- Standards: the templates, tools and quality checks we will follow.
- Change and escalation: how changes are handled and how disagreements are resolved.
- Commercial terms: kept clear and proportionate.
We ask both sides to read it and challenge it before signing. A document that nobody argued with has usually not been read.

Step 3 — Deliver

During delivery, we follow the agreement. We hold regular check-ins, report status honestly and raise risks early. We keep a decision log so that agreements are easy to find. At agreed points, we review how the partnership itself is working: are roles still right, is communication useful, is anything creating friction?

Regular reviews

Partnerships change as projects change. We schedule periodic reviews, typically at natural project milestones, to look at what is working, what is not and what should be adjusted. Small corrections early are far easier than repairs later.

Ending well

If a partnership ends, whether at the close of a project or for other reasons, we hand over documentation, close out open items and make sure the customer experiences no disruption. How a partnership ends says a great deal about how it was run.