Senior in the room, always
The person who sold the engagement is the person doing the engagement. No handover from partners to juniors, no layered account teams. If the engagement warrants a partner, a partner is present at every meeting.
We exist to do considered work with a small number of organisations at a time. Founder-led, present in the room at every layer, from the boardroom conversation through to the architecture and the code itself.
An AI initiative is stalled because the data plumbing beneath it has three owners and no plan. A cloud bill is rising, and the person reading it can see the number but not what it really represents: a service that was quietly deprecated and migrated to a more expensive tier, a default that changed at a version upgrade, a licence model that shifted from committed to on-demand, an instance family that no longer matches the workload. A product team has quietly built the same platform capability twice because the shared version was too painful to adopt. Each piece looks reasonable in isolation. The system does not.
We started Equiti Ventures to work these problems the way we always wanted them worked. Slowly at the start. Honestly on the page. Present at the layer where decisions actually get made, and again at the layer where the work actually gets done.
The person who sold the engagement is the person doing the engagement. No handover from partners to juniors, no layered account teams. If the engagement warrants a partner, a partner is present at every meeting.
We produce short, considered documents in plain English. What we think is really going on. What to do about it. What we are less sure about. If we get something wrong later, we say so, in writing, and adjust.
Strategy, architecture, the code itself. We work at the layer where the answer actually lives, not the one that is easiest to slide-ware. That often means we are in a boardroom in the morning and reading a pull request in the afternoon.
We take on a limited number of engagements each year. It keeps the quality of attention high, keeps the senior partner genuinely available, and keeps us honest about which problems we can actually help with.
The instinct to reach for a solution before understanding the problem is the source of most bad technology decisions we see.
Complexity accretes on its own. Removing it is the harder and more valuable move. Almost every good architecture is a subtraction.
Recommendations that no one is accountable to deliver tend not to land. Where it helps, we stay past the strategy and into the execution.
If the roadmap is unrealistic, if the vendor choice is wrong, if the shape of the team is not set up for what the business now needs, we say so early, plainly and once. Then we recommend the change, and where invited, help make it.
Runaway cloud spend, licence sprawl and AI token drift are almost never really about money. They are architectural and organisational signals dressed up as bills.
The people closest to the problem usually know something the leadership deck does not. Most of our best moves come from that conversation.
A conversation first. Then, if it makes sense, a short written read. No proposal, no deck.