Foreword

Who this handbook is for, what it proves, and why the window to act is still open in 2026.

About This Edition

Edition: May 2026
Last reviewed: April 22, 2026
Update cadence: monthly scheduled review, with fast patches for major ecosystem changes
Companion volume: The Agentic Handbook (Builder Edition) — architecture, skills, memory, governance internals for teams building their own agentic platform

What This Book Is

This is a handbook for business leaders who already run on SaaS and want to understand what it means to operate it with an autonomous agent instead of a team of clickers.

It is not a pitch. It is a report. Every finding in these chapters is logged, timestamped, and verifiable in a production session file. Every claim about what agents can and cannot do is either tagged validated against live evidence, partial where only part of the behavior has been observed, or hypothesis where the thesis is directional and waiting for data.

The experiment it reports is simple: take a stock OpenClaw instance, give it no internal privileges, connect it to a production B2B SaaS via the same public API surface any integration would use, and let it operate the business. Two things built the experiment: FlowWink (the business — a self-hosted business operating system: CRM, ERP, and CMS in one) and Clawable (the external OpenClaw operator running above it). Chapter three introduces both. None of it is a fork, none of it is a back channel. What you read is what happens when the protocol the industry agreed on in 2026 is actually pointed at a working business.

A Note on the Scenarios

The cases and scenarios in this handbook run on FlowWink — a next-generation business operating system built natively for the agent era. FlowWink combines CRM, ERP, and CMS in a single self-hosted platform: deal pipeline and lead management, quote-to-cash and accounting, content and contract publishing — all on one data model, all exposed via MCP. 200+ skills across CRM, finance, orders, contracts, content, HR, analytics, and accounting. It is self-hosted, open source, and built on Lovable — a production-grade stack that previously required months of engineering, now accessible to any team. If you want to know what an agent-ready business operating system looks like from the inside, FlowWink is the reference implementation.

The significant fact for anyone reading this handbook in 2026: FlowWink is available today. Free. Open source. Self-hosted in minutes. While every major SaaS vendor — Salesforce, HubSpot, SAP, ServiceNow — is in the process of retrofitting agent support onto platforms built for a different era, FlowWink was built for this era from line one. Any team running an autonomous agent — OpenClaw, Hermes, Claude Code, Paperclip, Cofounder — can connect to FlowWink and run the same experiments documented here. Not in a sandbox. Against a production-grade, fully operational MCP surface, today. No vendor negotiation. No integration sprint. No waitlist.

That is what makes the proof in this handbook reproducible — and what makes FlowWink the fastest path from “we want to understand autonomous agents” to “we are running one.”

The data used in these scenarios is representative: structured to reflect the operational reality of a mid-market B2B company, not sourced from a client under NDA.

What is not constructed is Clawable’s behaviour. The agent operates on standing objectives configured in its HEARTBEAT.md — a file that defines what it checks on each scheduled cycle. The April 19 sweep that surfaced over €1 million in exposure was not triggered by a human prompt. Clawable woke up on its own schedule, read its objectives, and went through the business. No one was watching.

Some SIM tests in chapter three used a single open prompt to probe specific reasoning capabilities. Even those prompts contained no targets, no categories of risk to investigate, and no guidance on what to find.

The SIM frameworks and objectives are documented in the sources appendix. The experiment is reproducible by anyone running FlowWink.

The proof is in the reasoning, not in whose name was on the contract.

The Thesis

A business running on SaaS does not need a human to operate it continuously. It needs an autonomous operator — an external agent that reads the live state of the business, reasons about what it sees, and acts on what matters. The human role shifts from discovery and execution to direction and approval.

Business runs itself. Employees assist.

This is a logged production claim, not a vision statement. Every chapter that follows is proof, context, or instruction.

Who This Book Is For

Business leaders and operators — if you run a company on SaaS and want to understand what autonomous operation looks like in practice, start here.
Agent Managers — if you have been given responsibility for agent deployments and need an operating model rather than a product manual, chapters 6 through 10 are the core.
Board members and advisors — if you need a defensible read on what is real in agentic AI versus what is still narrative, the evidence structure in chapters 2, 3, and 9 is designed for your fact-check.

If you build the platforms themselves — if your job is to make a SaaS agent-ready from the source code level — this is the wrong book. Read the builder edition instead.

How to Read This Handbook

Chapters 2–5 make the business case — the automation ceiling, the live proof, the architecture choice, and the skill audit that tells you what your stack can already do. Read these if you need to understand why before you understand how.

Chapters 6–10 cover deployment — choosing an operator, connecting MCP, configuring the heartbeat, and the enterprise view including governance and cost. Read these if you are ready to move.

Chapters 11–15 go deeper — the enterprise-scale picture and business case, what to demand from your vendors, where the world is heading, how to design the governance boundary that makes autonomy trustworthy, and what your role looks like in practice. Read these if you want the full picture.

— The Clawable Project, April 2026

With genuine and deep thanks to Peter Steinberger — for choosing to build in the open, share generously, and show that one person with the right idea can still change the direction of an entire industry.

With equal thanks to Anton Osika and the Lovable team — for building the platform that made FlowWink possible. FlowWink exists because Lovable made it buildable in weeks. This handbook’s proof exists because FlowWink does. The combination of Lovable for building SaaS and OpenClaw for operating it is, we believe, the fastest path from idea to running business that has ever existed.

FlowWink is self-hosted, open source, and available at github.com/magnusfroste/flowwink.

The claw is the law.