Start a knowledge base writing service for SaaS teams

You do not write the knowledge base yourself. Actionist does. Here is how it works on any business idea, applied to a documentation service: you sign the client, the agent reads the product and the tickets, plans every article, drafts them all and publishes the finished help centre.

1. 01

   You pick the clients and set your terms

   You choose which kinds of SaaS or e-commerce teams to target, what you charge per project, and how many clients you can carry at once. That is the only strategic decision you make at the start. Everything after this, Actionist plans and runs around your schedule.

   →A clear brief Actionist can pitch and plan against.
2. 02

   Actionist plans every article and subtask

   Actionist breaks the full engagement into stages: the outreach and proposal, the audit of the product and support inbox, the article structure, the drafting and revision cycle, and the final publish. You see the full scope in one place before any work begins.

   →A complete task plan for the engagement.
3. 03

   It reads the product and mines the tickets

   Actionist reads the product documentation, explores the features and mines the support inbox for the most repeated questions. It builds a picture of what users struggle with and which articles are missing, without you doing any of that reading yourself.

   
   →A ranked list of gaps the knowledge base needs to close.
4. 04

   It drafts every article and assigns you the human bits

   Actionist works through the article list, drafting each one from the product context and ticket data. The few tasks only a person can do, like taking the discovery call with the client team, get assigned to you with everything you need, then Actionist carries on with the plan once they are done.

   →A full draft of every article, ready for your review.
5. 05

   It asks before anything goes to the client or goes live

   Before Actionist sends a content plan, shares a draft batch with the client or publishes articles to the live help centre, it stops and asks you to approve. You set how hands-on you want to be per stage, from seeing every draft to just approving the final publish.

   →You stay in control of quality and your client relationship.
6. 06

   You keep your day job and check in

   You run this service around your existing schedule. Check the board when it suits you, approve what is waiting and message Actionist over Telegram or Slack to adjust anything. The project moves forward between your check-ins.

   →A service that delivers while you are at work.

This is the plan Actionist builds to deliver a knowledge base: every stage from winning the client to publishing the finished help centre. The work is split across your agents. Only the discovery call and a handful of approvals are left to you.

An example plan for a SaaS knowledge base project. Your plan adapts to the client's product, their ticket volume and your agreed scope.

Here is what a week actually looks like once the service is running. Your agents handle the research, drafting and client comms every day. You step in for a handful of moments, the ones that take your judgment, and the rest of your week stays yours.

This is your service and your clients. Actionist asks before it sends anything to a client or publishes anything live, and it keeps a full record of every action so you can see exactly what happened.