Focused discovery
Discovery
Make the problem visible before committing to the build.
A focused piece of work for situations where the symptoms are clear but the real constraint is not.
When the problem is still fuzzy
A CRM problem can turn out to be an ownership problem. A campaign problem can start with audience data. A website can be stuck because sales, product, and marketing are telling three slightly different stories.
Discovery is how I get close enough to tell the difference.
I follow the work across the people, systems, data, and decisions involved. We look at what is happening now, where the handovers break, and which assumptions still hold when we check them against the actual work.
This is not a general marketing audit. It is scoped around the situation you bring.
What happens during the work
I speak with the people closest to the problem and get into the relevant systems and existing material. I map the current state as we learn, so the team can challenge it before it becomes the basis for a decision.
I use agents where they are useful: comparing material, checking data, tracing patterns, and keeping the working documentation current. They help me cover more ground. The judgment stays with the people who understand the business.
By the end, the vague collection of symptoms should have become a problem the team can actually act on.
What you leave with
You get the map, the diagnosis, the important trade-offs, and a practical route forward. Sometimes that is a plan. Sometimes it is a prototype, a repaired part of the setup, or a small tool that proves what the next phase needs.
The output is meant to be used by the team, whether I stay involved or not.
Cost and next step
Discovery starts at 35.000 kr ex. VAT. The proposal sets the scope, timing, access, and output around the problem.
Sometimes discovery is enough. When the work needs someone close to the team to build, run, and adjust what comes next, I can stay embedded.
Send me the situation. A clean brief is not required.
Practical questions