Practical Lessons from Deploying OpenClaw for Five Businesses

A developer with five OpenClaw instances running in production on Hetzner VPS shares concrete lessons from real business deployments.

Infrastructure Decisions

The developer tried local deployment (easiest but not scalable) and AWS (expensive), then landed on Hetzner CPX22 at €13/month (3 vCPU, 4GB RAM) for being cheap, fast, and stable. A key discovery: WhatsApp is dead on datacenter IPs because Meta blocks them, leading to two lost days chasing Meta Developer App approval. Telegram became the default because its API is more forgiving than WhatsApp's.

Every client gets their own VPS. Multi-tenancy was tried early but abandoned because one client's runaway process shouldn't kill another client's agent. Isolation is considered worth €13/month and non-negotiable.

Onboarding and Personalization

Early agents were generic but not effective. The developer created a 26-question intake form that feeds into an n8n workflow that auto-generates a SOUL.md and USER.md for each deployment. The form covers business type, tone preferences, what the agent should handle vs escalate, tools used, daily schedule, and communication style. One user reported the agent was "so useful and specific right out the gate."

The developer notes: "A generic agent is a product. A personalized one is a team member. Even more so — the more they use it, the more embedded it becomes."

Billing Approach

What doesn't work: charging for setup and hoping they stick. What does work: 7-day free trial on the developer's Anthropic API key (costing $5-15), then clients get their own key. The developer walks them through setup live on Zoom in about 10 minutes. Clients see the transparency and own their costs. One client switched from Claude to OpenAI in 3 minutes because they already had a subscription.

Model Tiering Strategy

The default stack per deployment:

• Haiku: Heartbeats, simple responses, routine checks (90% of volume)
• Sonnet: Complex tasks, multi-step workflows, anything needing judgment (9%)
• Opus: Strategic thinking, high-stakes decisions (1%)

The developer compares this to a typical small business structure: "The visionary/founder at the top, then people come on board to execute the vision."

Important tip: pin models on every cron job. Forgetting to pin one resulted in running heartbeats on Sonnet for a week with a $40 bill.

Technical Optimization

Use the OS, not the LLM, for mechanical tasks like rotating logs, restarting services, or backing up files. The LLM gets invoked for decisions while the OS handles mechanics. This cut token usage by about 30% across all deployments.

Actual Use Cases

• Care agency: CQC compliance reminders, staff scheduling conflicts, policy lookup (saves ~5 hours/week)
• Events business: Lead capture, follow-up sequences, quote generation integrated with CRM
• SEN consultant: EHCP deadline tracking, parent communication templates, school liaison scheduling
• Auto detailer (Florida): Appointment booking, review follow-ups, photo organization
• Developer's own agent: Strategic planning, content drafting, memory across 4,000+ workspace files

The developer notes: "None of them wanted a chatbot. They wanted a business operating system that happens to use AI."