Build WhatsApp bots for clients — keep 100% of what you charge

Most bot platforms take a monthly cut of every client you onboard — your margin funds their subscription. FlowBot is a free builder, so a client bot costs you nothing to build and nothing per month: design it as a flowchart, demo it with a live link, launch it on the client's own WhatsApp number, and deliver the source code as the hand-off. Whatever you charge is yours.

The freelancer workflow, end to end

1. Draft in minutes. Start from a template close to the client's business — restaurant, store, clinic, hotel — or describe the brief to the AI Builder and edit the flowchart it draws.
2. Demo without a meeting. Every bot gets a public share page: the client opens one link, sees the flowchart, and chats with the bot live in their browser. No account, no screen-share, no "imagine it works".
3. Launch on the client's number. Connect their Meta Cloud API, Twilio, Green API or Whapi account in the activation panel — message costs bill straight to the client, never through you.
4. Hand over (or host). Deliverable option A: export the bot as a Node.js project and hand the client code they fully own — a deliverable platforms can't match. Option B: keep it running yourself and charge a monthly care retainer.

Why clients say yes faster

• No platform fee to explain. Your quote covers your work — not a third-party subscription the client resents in month three.
• The bot is theirs. "You'll own the full source code" wins deals against agencies pitching locked platforms. There's a comparison hub you can send skeptical clients.
• Website widget included. The same flow embeds on the client's site with one script tag — two deliverables from one build.
• Numbers to report. The funnel overlay shows how many conversations reached each block, and the analytics panel gives 30-day totals — screenshot-ready for your monthly client report.

Scaling past the first client

Flows are independent — build each client's bot in its own flow, reuse your best blocks via Block Lab (your custom blocks work in every project), and keep a private library of template flows you clone per niche. When a client outgrows the setup, the code export means the upgrade path is a migration, not a rebuild.