Packages and Process
I help SaaS teams structure their knowledge so onboarding is faster, support load decreases, and work stops depending on who's available.
Each package below is scoped to solve a specific problem. Not sure where to start? Most teams begin with an audit.
Packages at a Glance
Scope and deliverables confirmed before work starts.
1. Knowledge Audit
Best for: Teams whose support, onboarding, or handover processes break down because no one owns the knowledge.
Starting at: €1000 excl. tax
Timeline: 2–3 working days
What this solves
- Repetitive support questions
- Knowledge trapped in people's heads or scattered across tools
- Inconsistent structure slowing onboarding
- No clear ownership, so nothing ever gets fixed
What you get
- Structured review of existing documentation, help centre articles, internal wikis, and process guides
- Gap analysis based on onboarding flows, feature usage, and support patterns
- Clear information architecture recommendations
- Prioritised action plan based on operational impact
- 1 alignment call to agree on next steps
Outcome: You leave with a prioritised plan your team can act on immediately and a clear answer to why things keep breaking.
2. Feature & Onboarding Documentation
Best for: Startups shipping a feature or MVP without documentation ready to scale.
Starting at: €1800 excl. tax
Timeline: 7–9 working days
What this solves
- User confusion after new releases
- Support tickets that spike per release
- Slow onboarding requiring repeated team explanations
- Low feature adoption
What you get
- Structured user guide built around real user tasks and decision points
- Supporting knowledge base articles or FAQs
- Consistent terminology and structure your team can maintain
- 1 revision round aligned with product and support
Outcome: Users find answers without asking your team. Support pressure drops from the first release.
3. API & Developer Documentation
Best for: SaaS teams where integration friction costs developer time and slows deals.
Starting at: €3500 excl. tax
Timeline: 10–12 working days
What this solves
- Integration delays stalling revenue
- Repetitive developer support requests
- Poorly structured API references
- Technical onboarding reliant on engineers
What you get
- Structured API reference, integration guides, or developer tutorials
- Clear setup and first-success paths to reduce time to integration
- Logical information architecture your team can extend
- 1–2 revision rounds depending on scope
- Post-launch support is not included. See Ongoing Knowledge Support for updates
Outcome: Developers integrate without needing your engineers in the loop. Your team stops being the bottleneck.
4. Ongoing Knowledge Support
Best for: Teams that ship fast and can't afford documentation debt to accumulate.
What this solves
- Knowledge drifting out of date
- Features shipped without documentation
- Help centre inconsistencies eroding user trust
- No accountability for keeping the system coherent
Scope is fixed per tier
If your needs grow, we'll review together at the next monthly check-in.
| Tier | Days/month | Monthly rate |
|---|---|---|
| Essentials | 2 days | €650 excl. tax |
| Standard | 3 days | €950 excl. tax |
| Growth | 5 days | €1500 excl. tax |
What you get
- Dedicated monthly capacity for updates and improvements
- Work aligned directly with product releases
- Ongoing structure and consistency improvements
- Light governance support: templates, standards, ownership frameworks
- Regular prioritisation based on product and support needs
Outcome: Your knowledge system stays current without you managing it.
Need something more comprehensive?
Most engagements start with an audit or a specific deliverable.
The Knowledge System Sprint is for teams that have tried patching individual problems and need to address the structure itself.
Knowledge System Sprint
Best for: Scaleups that have outgrown their knowledge setup and need structure before they can grow into it.
Starting at: €5500 excl. tax
Timeline: 15–20 working days, delivered in four phases
Phases
- Strategy & Audit (Days 1–5) - Knowledge audit, stakeholder interviews, and current state analysis
- Information Architecture (Days 6–10) - Clear IA for public and internal docs, templates, and standards
- Core Documentation Build (Days 11–15) - Initial onboarding, feature guides, and knowledge base content
- Governance & Handover (Days 16–20) - Ownership frameworks, ongoing processes, and team training
What this solves
- Knowledge silos slowing onboarding and cross-team collaboration
- No single source of truth: every team maintains their own version
- Support and onboarding dependent on specific people being available
- Structural chaos that more content alone won't fix
What you get
- Knowledge strategy aligned with product, support, and onboarding workflows
- Core documentation built to a scalable structure
- Template and standards system your team can own going forward
- Governance framework with clear ownership recommendations
Outcome: Your team onboards, hands over, and ships without losing knowledge every time something changes.
Scope confirmed after a 30-minute discovery call. Book yours here.
My Process
Every engagement follows the same structure:
- 01Discovery Call
Understand your situation and confirm the right starting point before anything is scoped or agreed.
- 02Scope & Agreement
Clear deliverables, timeline, and pricing agreed in writing before work starts.
- 03Research & Planning
Review existing content, interview your team, and map the gaps that matter most.
- 04Drafting & Review
Structured drafts with consolidated feedback addressed in one revision pass per round.
- 05Delivery & Handover
Final content delivered in your preferred format, ready to use.
Timelines include a buffer for feedback and stakeholder availability. If you have a hard deadline, mention it at the start of the project.
Not sure where to start?
Start with a discovery call. Thirty minutes to understand your situation and agree on the next step.