Knowledge Systems Consultant

I help tech companies turn scattered knowledge into systems people actually use.

Book a 20-min discovery call See how it works

Symptoms

Sounds familiar?

Clients come to me with concrete pain that feels like a documentation problem. But it almost never is.

  1. 01

    Engineering doesn't know what sales promised.

    Deals close on commitments nobody wrote down — engineering finds out at the sprint review, the customer at delivery.

  2. 02

    Onboarding takes three months because nothing is written down.

    New hires ask the same questions seniors answered last quarter — and the quarter before that. Critical knowledge lives in heads, not in your base.

  3. 03

    Support runs a parallel knowledge base.

    The official docs are written for engineering. Support built their own to actually answer customers. Now there are two versions of reality, and they disagree.

  4. 04

    Your Confluence has 4,000 pages. Nobody trusts any of them.

    Half are outdated, a quarter are duplicates, and the search returns 2019 drafts before current process docs.

  5. 05

    You want to launch an internal AI assistant.

    But feeding your current knowledge base to an LLM would teach it to hallucinate confidently.

You point at the symptom — I point at where the system actually breaks and what your team can change to fix it.

Services

What I do

Knowledge Systems Diagnostic

Core service

I audit where knowledge falls apart in your company and design what to do about it.

You get a clear answer to three questions: what's actually wrong, what to fix first, and what your team needs to do.

The plan takes the shape that fits the diagnosis: a taxonomy and information architecture, a process design with owners and rhythm, or both — depending on what's actually broken.

You walk away with a plan your team can act on.

I work with the stack you already have — Notion, Confluence, Google Drive, any combination. No migration, no new tools.

2–4 weeks · From €4,500

Implementation Support

After the Diagnostic

The diagnostic gives you a plan. Execution is where most plans quietly die — questions pile up, edge cases appear, the team gets stuck on "how should we actually do this."

The first two months of execution shape everything that follows — get the early architectural decisions right, and the team carries the plan from there. That's what Implementation Support is for.

I work as a technical advisor, not a project manager. Your team or your implementer runs the work. I answer the hard questions — how new things fit into the system, whether an edge case breaks the architecture, what to do when reality diverges from the plan — and keep the system coherent while you execute.

What's included

  • A monthly written check-in: progress, drift from the plan, open questions, architectural recommendations, and a health signal on the system.
  • Async answers as your team hits hard questions (typically 5–10 per month).
  • A 45-min monthly call — a working session on what's hard right now, not a status meeting.
  • Review of artifacts your team produces, on request.

From €1,500/month

Quarterly Guard

After implementation

For teams that have finished executing the roadmap and want to make sure the system stays healthy. Knowledge systems drift quietly — new content gets filed the wrong way, ownership changes don't propagate, edge cases pile up. Within 6–12 months without check-ins, coherence starts to break.

Quarterly Guard is a focused quarterly mini-diagnostic. I run the same framework as the full diagnostic on a representative sample — random documents, hot zones from the quarter, and weak zones from last time. You get a written state-of-the-system report: what's holding, what's starting to drift, what needs attention now, and how things have changed since last quarter. No calls, no scheduling — two short touchpoints from you per quarter.

€750/quarter

Process

How it works

  1. 01

    Discovery call (20 min)

    We talk about the problem. By the end of the call, we both know if I can help.

  2. 02

    Proposal, NDA, contract

    Concrete scope, timeline, exact price. NDA is signed before any access to documents.

  3. 03

    Knowledge Flow Mapping

    I start with people, not documents. Three to five short interviews with the people who create, search for, or hold the knowledge.

  4. 04

    Audit and synthesis

    I work through your knowledge base solo, guided by the flow map. I build a taxonomy hypothesis and validate it against real documents.

  5. 05

    Validation and delivery

    We review the findings and the plan with your team — discussion, adjustments, sign-off. Then a written report and a 60-minute walkthrough call. From there, your team or your implementer takes the plan forward.

Security & confidentiality

How your data is handled

This isn't a footnote. Your knowledge base may contain internal processes, customer information, and product details. The handling rules are explicit and built into the contract.

NDA before access — always.

NDA is signed after the discovery call and before any document is shared with me. No exceptions.

Local, encrypted, isolated.

Client material is stored on a local encrypted device, in a folder dedicated to your project. No automatic cloud sync. Nothing gets uploaded anywhere by default.

Explicit consent for any AI tool.

If I want to use an AI assistant on actual content from your base, I ask for written consent in the contract. Without consent, AI is used only on structure and abstract problem descriptions — never on your real content.

Deletion after 90 days.

Ninety days after the project closes, your data is deleted. I send written confirmation.

About

Who I am

I'm Daria Savina — Knowledge Systems Consultant, based in Limassol, working remotely with teams worldwide.

I was a technical writer for many years. I sat at the end of the broken process — trying to reconstruct reality from three contradicting specs and a Slack thread. That's where I learned that documentation is just an artifact, a symptom — the cause is always upstream, in the processes and architecture behind it. That's the level I work at now.

Before going independent, I spent six years as Head of Technical Writers at a fintech company, building documentation infrastructure from scratch across 10+ SaaS products. Earlier, I worked on government-contract documentation and ran the full release cycle of technical materials in 50+ languages.

LinkedIn — linkedin.com/in/savignon

Contact

Let's talk

A 20-minute discovery call. Bring the problem you're trying to solve. We'll figure out together whether I'm the right person to help.

Book a call

Or write to daria@savina.tech