Blueprint first. Then the system that carries it.
A CRM is a record of decisions somebody made about how a business operates. When those decisions have not been made, configuring software just moves the confusion into a new place. So we design the revenue and lifecycle architecture on paper first, agree it with the people who have to live with it, and only then build.
Five stages, and you can stop after any of them.
Some clients want the whole thing. Some want the assessment and nothing else. Some take the blueprint and build it with their own team, or hand it to an implementation partner they already use. All three are fine, and we would rather say so upfront than discover it at the end. If you need a quick win before the bigger work, say so at the start and we will sequence for it.
Current state assessment
We look at what exists rather than at what the documentation says exists: the CRM configuration, the marketing platform, the integrations, the reports people actually use, the spreadsheets they use instead, and the data underneath all of it. We talk to the people doing the work as well as the people who commissioned the project, because those two accounts are rarely identical.
You get a written assessment of what is working, what is broken, what it is costing and what we would change first. If that is all you want, the engagement can end here.
You keep: written assessment · prioritised findings · remediation roadmap
Revenue and lifecycle blueprint
This is the design document: journey and lifecycle mapping, process design, lifecycle stage definitions with entry and exit criteria, automation and trigger design, the data model, the reporting and KPI framework, and the CRM architecture that carries them.
It is written to be built from. Detailed enough that a competent team who has never met us could implement it, which is deliberate. It is your document either way.
You keep: blueprint document · process and journey maps · data model · KPI definitions · implementation roadmap
Platform decision and architecture
If the platform is already settled, this is the system design: objects, records, fields, permissions, integration points and the technical decisions behind them. If it is not settled, this is where selection happens, scored against the requirements the blueprint just made explicit rather than against a generic feature matrix.
We take no commission from any vendor, so the recommendation costs us nothing either way. Occasionally it is to stay on the platform you already have and fix the way it is set up.
You keep: architecture specification · platform recommendation with trade-offs · integration design
Implementation
Configuration, data migration and cleansing, integrations, automation, testing, and enablement for each role that has to use the system. We phase it so the first useful piece lands early rather than everything arriving at once on go live day.
Rollout is planned from the start rather than added at the end. Ninety per cent of CRM implementations fall short in some way, and the reason is almost never the software. It is that nobody planned for the people.
You keep: configured system · migrated and validated data · documentation · role-based training
Measurement and optimisation
The first real quarter of data always exposes something the design got slightly wrong. A stage that everything sits in, a routing rule that sends too much to one team, a field nobody fills in. We measure against the KPIs agreed at the start and adjust.
Some clients keep a fixed number of days a month with us after that. Others take it in house, which is the outcome we design for. There is no retainer requirement on any engagement.
You keep: reporting against agreed KPIs · post-launch adjustments · optional ongoing support
A few things worth knowing before you get in touch.
The two of us
Sandy and Niels run every engagement. There is no bench of juniors, no account manager between you and the work, and no handover to a delivery team after the sales conversation. It also means we take on a limited number of engagements at a time.
Scoped, not open ended
Fixed scope and fixed price for assessments and blueprints, so you know the cost before you commit. Implementation is scoped after the blueprint, when there is enough detail to estimate honestly. We would rather tell you a number is unknown than invent one.
NDAs on request
We sign NDAs whenever a client needs one, and treat systems, data and commercial strategy as confidential regardless. Client names are not published and client work is not used as a case study without written permission.
The answer is sometimes no. A fair number of the conversations we have end with us saying the problem is not one we should be paid to solve: the process needs deciding internally before any consultant can help, the existing system is fine and the reporting is the only issue, or the budget would be better spent on a person than on a project. Saying that costs us nothing, which is rather the point of not taking commissions.
Start with a conversation.
Tell us where you are, where you would like to be and what is in the way. You get back a call, a written take, or an honest redirect.