Built by consultants for consultants
We’re Fractal Force, a consulting firm working with life-sciences companies on complex commercial, customer engagement and transformation challenges.
Like most boutique consultancies, we work across several clients at once. Different projects. Different stakeholders. Different histories, commitments, politics and ways of working.
And too much of that context was living in our heads, inboxes, meeting transcripts and folders.
So we built a better way to run the firm.
Pieter Vanderbeeken
Mark Watson
It started with a problem we had ourselves
We wanted Claude to know what we knew.
Not just read a few uploaded documents, but understand our clients, remember what had happened, know how we work and use that context when preparing a meeting, writing a proposal or producing client work.
What started as a few instructions became a connected system.
Over months of daily use, we kept adding to it, testing it, breaking it and improving it.
Today it includes 30+ interconnected skills, a structured knowledge layer and the routines that keep everything current.
It runs on real client work inside Fractal Force every day.
Built by consultants, for consulting work
This matters because consulting has its own way of working.
A proposal needs to reflect what was actually said in discovery. A client brief needs to distinguish between the official decision-maker and the person who really influences the outcome. A deliverable needs to follow the client’s standards, not yours. A handover needs the history behind the project, not just the latest file.
Those details are difficult to design from the outside.
We built Tessentra while doing the work ourselves.
Every skill started with a real consulting job we wanted to do better.
Months of improvements are what you’re buying
Could you build something similar yourself? Absolutely.
The underlying tools are available to everyone.
But getting from a few useful prompts to a system you can trust across live consulting work takes time.
You have to decide how the knowledge should be structured. What context each skill should load. What should stay private. How client information stays separated. How to prevent unsupported claims. How to keep the system useful as the knowledge base grows. What happens when Claude or Notion changes.
We have spent months working through those problems. And we still use it ourselves.
Tessentra is not something we built, packaged and moved on from. It is how we run Fractal Force. We use it for client meetings, proposals, deliverables, market monitoring, content and the day-to-day management of the firm.
That means we encounter the problems first.
When Claude changes, when Notion changes, when a workflow stops behaving as expected or when we find a better way to do something, we improve the system we use ourselves — and those improvements become part of the product.
You’re not buying the idea. You’re buying the iterations, and a working set-up built by a team that uses it every day.