How we work
We are not trying to do everything. We are trying to see everything — and bring in exactly the right capability for exactly the right thread.
The principle
We read the business. We find the gaps. Then we bring in whoever is genuinely best for that gap — not whoever we can upsell.
Most consultants who position themselves as strategic advisors are selling something. The strategy is the entry point for the implementation, the platform, the retainer, the team. The advice is shaped — consciously or not — by what they can deliver.
We made a deliberate choice not to work that way. Our value is in reading the fabric of a business — seeing where it's strong, where it's fraying, where the gaps live, and what kind of capability is needed to close them. Some of that capability is ours. Much of it belongs to people who specialise in exactly what the gap requires.
Technology tools are no different. We work with platforms and tools we trust — not because we resell them, but because we've seen what they do well and where they break down. We are the abstraction layer: we decide when a tool applies, how it should be introduced, and what it should be measured against. The tool doesn't drive the recommendation. The fabric does.
What we bring to every engagement
Technology
AI and automation tools are not interchangeable. Each has a specific design philosophy, a specific kind of task it handles well, and a specific failure mode when misapplied. We know these tools because we've worked with them — and we know when not to use them.
We don't recommend a tool because it's popular. We recommend it because it fits the specific gap we've identified in the specific business we're reading. That's the abstraction layer: we sit between the tool and the business so the business doesn't have to.
AI is only as good as the data it operates on and the systems it integrates with. Before any AI implementation, we look at the information architecture: where data lives, how it flows, where it breaks down. Gaps here create failures downstream that are expensive and hard to trace back to their origin.
We work with tools and partners who specialise in data infrastructure — not because every engagement needs them, but because some do, and introducing AI into a broken data environment is one of the most common and costly mistakes a business can make.
Specialist partners
Engineering organisations have some of the most complex information environments in any industry — CAD systems, document management platforms, asset databases, specification workflows. When the fabric reading identifies gaps in these threads, we bring in partners with genuine deep expertise in these environments.
This is not a referral network. These are people we have worked with, whose judgment we trust, and who work the same way we do: starting with the problem rather than the solution.
The principle at the heart of the Fabric methodology came from accessibility work: reducing cognitive load is a form of respect. Making complex systems legible to everyone who needs to use them — not just the people who built them — is both a design value and a business advantage.
We work with inclusive design specialists who share this philosophy. When an engagement surfaces gaps in how an organisation communicates, documents, or designs its systems, these partners bring the depth we don't.
Sometimes the fabric reading reveals a gap that isn't about clarity or strategy — it's about execution capacity. The business knows what to do. It doesn't have the operational horsepower to do it. In those cases, what's needed is delivery expertise, not more diagnosis.
We have relationships with operations specialists, project delivery partners, and workflow designers who can take a specific thread and build the structure it needs. We don't stay involved to justify our retainer. We hand off when the handoff is what serves the client.
For potential partners
We're always looking for specialists who start with the problem, not the solution. If that's how you work, we'd like to know you exist.