My approach isn’t fancy. I don’t do copy or UX fixes. I work with software taxonomy.
How you organize, group & nest software capabilities shapes messaging across teams, assets, and stages.
For example, if you ...
– overlap features, copy gets redundant
– mix up capabilities, value gets buried
– flatten hierarchy, nothing is important
– split platform for optics, story breaks
– list features out of order, people get lost
– use vague labels, nobody gets it
Taxonomy is the root of messaging clarity or confusion. Yet no one owns it or gives it too much thought, until it’s too late.
My process
I don’t have a “playbook.” Every B2B SaaS & taxonomy requirements are different.
But I’ve developed a process. Once the work starts, here’s what I do:
I. Map your reality
– how you organize the product internally
– public taxonomies across teams, assets
– invisible work when creating messaging
– messaging dependencies you don’t see
– the reality of your prospects & users
– how teams communicate internally
Duration: (approx.) 1 – 2 months
let’s talk > book intro callII. Build your public taxonomy
– create modules based on user logic
– define the nesting relationships
– nest features under the right modules
– use MECE to avoid overlaps
– establish consistent name convention
– document rules for grouping & naming
Duration: (approx.) 1 – 2 months
let’s talk > book intro callIII. Implement it everywhere
– redesign website navigation menu
– restructure pages around new logic
– realign marketing materials & docs
– work on sales materials to fit new logic
– design KB flows to match taxonomy
– align every team on the new map
Duration: (approx.) 1 – 2 months
let’s talk > book intro callPlus, ongoing support:
– create lightweight docs & guides
– coach teams to take over & make it stick
Who I work with
Companies:
– established B2B SaaS
– remote / distributed teams
– different verticals & niches
Leaders:
People who know that chasing trends & quick fixes is expensive & unsustainable. Leaders who value rigor and depth.
let’s talk > book intro callMy principles
– participatory work with your teams
– context-aware of your reality
– lightweight, no heavy bureaucracy
– messaging docs as living artefacts
What happens after?
I build in ways your team can operate just fine without me. My goal is to exit once the work is done. But I do offer ongoing support if wanted.
let’s talk > book intro callHow much does it cost?
Pricing: €5,800 per month, 3 to 6 months depending on the complexity of your SaaS. Check the FAQ for more info.
