Chatbot vs. co-worker
Why most people get 10% out of AI. What makes a digital co-worker different from a prompt window.
Not a chatbot that starts from scratch every session. A digital co-worker that knows your work, with identity, memory, tools and clear boundaries. Copy-paste templates you can put to use tomorrow morning.
A guide, not a guru. This playbook is built from months of working with an autonomous agent every day, including the mistakes and hard lessons you will not find in blog posts.
This is not an e-book full of meta statements about AI. It is the configurations, templates and boundaries we use ourselves every day, packaged so you can adopt them.
Complete IDENTITY.md, SOUL.md, MEMORY.md and TOOLS.md templates. Plus the configuration of an agent we use ourselves, which you translate to your own work in thirty minutes.
For founders, knowledge workers and operators who are technical enough to edit a config file, or willing to learn. Not for anyone looking for a no-code button.
Every template comes from an agent that picked up tasks daily for months. Including what went wrong: memory that was too complex on day 1, the cold start, the approval queues that overload themselves.
Identity, memory, tools, boundaries: those four blocks work for any function. You learn the method; which role you give it is up to you.
Calendar, mail triage, summaries and follow-ups. Always up to date, always available.
Analyse campaigns, segment audiences, propose A/B tests and build out reports.
Blog posts, newsletters and presentations, in your tone, with knowledge of your brand and audience.
Schedule posts, monitor trends, manage the community and track engagement, consistently across every channel.
Qualify leads, automate follow-ups, update the CRM and prepare quotes. No lead slips through.
Track progress, status reports, flag risks, update stakeholders. A grip on every project.
The playbook teaches you the method. Which role you choose is up to you, or build several side by side.
Each chapter ends with a template or configuration you copy-paste straight away. No filler, no "why AI matters", only what works.
Why most people get 10% out of AI. What makes a digital co-worker different from a prompt window.
OpenClaw, Claude Desktop, or a custom build? Pros and cons, honest, no affiliate talk.
SOUL.md and IDENTITY.md: voice, behaviour, boundaries and role. Includes a copy-paste base.
Three-layer system: MEMORY.md, journals, knowledge graph. With nightly extraction and memory decay.
What is essential (mail, files, web, shell) and what is optional (GitHub, browser automation, sub-agents).
Trust Ladder, approval queues, mail boundaries and defence against prompt injection, as configuration.
Communication, planning and autonomy: how you work day to day with a co-worker that knows your working style.
From mail to reports. Parallel workflows, automatic restart when something stalls.
From reactive to proactive: the agent detects, triages and resolves, before you even see it.
From one co-worker to a team. Role division, cost optimisation, shared memories.
Honest lessons: memory too complex on day 1, cold start, approval overload, surprises about personality.
Seven steps, from a 30-minute install to a working agent in week 4, with checklists.
Start this afternoon with thirty minutes of setup. By the end of week four you have an agent that knows your work.
Choose a platform, set up the repo, create your first IDENTITY.md. Start with one role, one task.
→ "Hi, I'm here"Fill SOUL.md with your voice and boundaries. Activate three-layer memory, hot/warm/cold.
→ knows your contextConnect mail, files, web. Configure the Trust Ladder: what is autonomous, what needs review, what is forbidden.
→ does first tasksAdd a second task, first sub-agents, a ralph loop for long-running work. Only scale once layer 1 is stable.
→ a working co-workerThese are the building blocks that make the difference between a chatbot and a co-worker. In the playbook you work through them step by step.
Four levels of AI autonomy: from read-only to acting independently. You start restrictive and build trust on proof, not on hope.
No long sessions that stall. Short sprints, automatic restart on a stall, parallel agents in isolated worktrees. Work that carries on while you sleep.
Not everything matters equally. Recent work stays prominent, old work fades on its own. MEMORY.md for patterns, daily notes for the timeline, a knowledge graph for entities.
The playbook is practical and technical, not a pretty e-book you cannot do anything with. Read below whether your situation fits.
This playbook was not written from theory. It is the result of months of working with an autonomous agent every day, including the mistakes and surprises you read nothing about in neatly styled threads.
Every template, configuration and safety rule in this playbook runs in practice. You do not get a philosophical story about "what AI could become", but the exact files, prompts and checklists we work with every day.
The mistakes are in there too. Because it is not fair to sell only the highlights.
"No theory, the actual systems, configurations and lessons from building a working relationship between human and AI." — FlowBaas, from the playbook's introduction
Complete, copy-paste, in markdown.
From zero to an agent that knows your work.
One off, no subscription, no upsell.
This playbook is secondary to our done-for-you track. For anyone with the time and the appetite for detail, building it yourself is fine. For anyone who wants it outsourced, there is the autonomous agent.
One task, integrated into your existing tools, with logging and KPIs from the very first run. Four working days to live, no annual contract, scale up only once the numbers add up.
See the done-for-you agent →The playbook is out soon. Reserve at the early-bird price of €19.95 and get an email the moment it is available. No subscription, no upsell, no sales funnel.