letsbe/LetsBeBiz-Redesign
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Initial commit: LetsBe Biz project with openclaw source

Browse Source 
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
Matt
2026-02-27 16:24:23 +01:00
commit 14ff8fd54c
93 changed files with 31651 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

439
docs/strategy/LetsBe_Biz_Competitive_Landscape.md Normal file
View File

@@ -0,0 +1,439 @@
# LetsBe Biz — Competitive Landscape
**Version:** 1.0
**Date:** February 26, 2026
**Authors:** Matt (Founder), Claude (Strategy)
**Status:** Living Document
**Companion docs:** Foundation Document v1.0, Product Vision v1.0, GTM Strategy v1.0, Website Copy v1.0
---
## 1. Market Position
LetsBe occupies an empty quadrant at the intersection of two growing trends: self-hosted business infrastructure and autonomous AI agents. No existing product combines privacy-first infrastructure, pre-deployed business tools, and AI agents that operate those tools autonomously.
| | **SaaS (cloud-hosted)** | **Self-hosted (customer-controlled)** |
|---|---|---|
| **Workflow automation** (user builds flows) | n8n Cloud, Make, Zapier | n8n† (self-hosted), Activepieces, Dify |
*† n8n is a competitor only — NOT in the LetsBe stack. Its Sustainable Use License prohibits managed service deployment.*
| **AI workforce** (AI operates tools) | OpenAI Frontier, Lindy, Sintra AI | **LetsBe Biz (alone here)** |
The quadrant LetsBe occupies is empty because it requires solving three hard problems simultaneously: deploying and managing 25+ open-source business tools on isolated infrastructure, building an AI agent runtime that can operate those tools through APIs and browser automation, and wrapping everything in a secrets firewall that keeps credentials out of LLM providers. Each piece exists in isolation elsewhere. The combination is the product.
---
## 2. Competitor Categories
Competitors fall into five categories. No single competitor competes on all dimensions — LetsBe faces different players depending on which angle the customer approaches from.
### Category 1: AI Agent Platforms (Cloud)
These platforms offer AI agents that can perform business tasks, but run entirely in the cloud with no self-hosting option.
#### OpenAI Frontier
**What it is:** Enterprise AI agent platform launched February 2026. Builds, deploys, and manages AI agents that connect to enterprise systems (Salesforce, ServiceNow, Jira). Partnered with McKinsey, BCG, Accenture, and Capgemini for enterprise rollout.
**Target market:** Enterprise (Uber, State Farm, Intuit, Thermo Fisher). Not SMB.
**Pricing:** Enterprise contracts — not publicly disclosed. Requires existing Microsoft/enterprise stack.
**Strengths:** Massive distribution via consulting partners. Deep enterprise integrations. OpenAI's model capabilities. "Shared business context" that connects siloed internal systems.
**Weaknesses from LetsBe's perspective:**
- Enterprise-only — no SMB play, no self-service signup
- Cloud-hosted — customer data lives on OpenAI infrastructure
- Requires existing enterprise stack (Salesforce, ServiceNow, etc.)
- Not privacy-first — data processed on OpenAI's infrastructure
- Pricing will be enterprise-level (likely $50-100+/user/month based on Copilot comparisons)
**LetsBe differentiator:** "OpenAI Frontier is built for Fortune 500 companies with existing enterprise software. LetsBe is built for the 5-person company that doesn't have enterprise software yet — we give you the tools AND the AI team to run them, on your own server."
#### Lindy AI
**What it is:** AI agent platform with 5,000+ integrations. Users create agents via natural language that automate tasks across existing SaaS tools (Gmail, HubSpot, Slack, etc.). Includes AI phone agents (Gaia) and computer-use capabilities.
**Target market:** SMBs and individual professionals. Closest direct competitor to LetsBe's AI agent story.
**Pricing:** Free tier (400 credits), Starter $49/mo (5,000 credits), Pro $99/mo, Business $299/mo. Credit-based — costs vary by task complexity and model choice.
**Strengths:** Large integration catalog. Natural language agent creation. No coding required. Phone agent capability. Active development.
**Weaknesses from LetsBe's perspective:**
- Cloud-only — customer data flows through Lindy's servers
- Connects to existing SaaS tools — doesn't provide the tools themselves
- Credit-based pricing creates unpredictable costs ("you won't know exact consumption until tasks run")
- No privacy controls — no secrets firewall, no credential redaction
- Customer still pays for all the underlying SaaS subscriptions (HubSpot, Gmail, etc.)
**LetsBe differentiator:** "Lindy connects AI to your existing SaaS tools — you still pay for all those subscriptions. LetsBe replaces them. You get the CRM, email, files, invoicing, AND the AI to run them, for one monthly price, on your own server."
#### Sintra AI
**What it is:** Team of 12 specialized "AI helpers" covering marketing, support, sales, e-commerce, recruiting, and data analysis. Central "Brain AI" maintains brand context and preferences.
**Target market:** Non-technical small business owners, solo entrepreneurs, side hustlers. Revenue ceiling of $100K/month in their onboarding tells the story.
**Pricing:** $39/mo for one helper, $97/mo for full Sintra X (all 12 helpers). Unlimited usage within chat workspace.
**Strengths:** Very accessible for non-technical users. Proactive task suggestions. Flat pricing (no credit anxiety). The "AI team" metaphor is well-executed.
**Weaknesses from LetsBe's perspective:**
- Advice-only — "great at coming up with ideas/suggestions for tasks, the actual execution was underwhelming"
- No tool integrations — Sintra doesn't actually do things in your CRM or send emails
- No custom agents, no shared task context, no cross-tool automation
- Cloud-only, no privacy story
- Very basic — targets absolute beginners, not growing businesses
**LetsBe differentiator:** "Sintra gives you AI that suggests what to do. LetsBe gives you AI that actually does it — across real tools on your own server. Our AI doesn't just draft an email, it sends it through your actual email server."
### Category 2: Workflow Automation Platforms
These platforms let users build automated workflows between tools. They require manual setup and don't have autonomous AI agents.
#### n8n
**What it is:** Fair-code workflow automation platform with 400+ integrations and native AI capabilities. Self-hostable. Achieved unicorn status (£2B valuation) in October 2025.
**Target market:** Technical operations teams, developers, automation-savvy businesses.
**Pricing:** Self-hosted community edition is free (unlimited). Cloud: Starter €24/mo (2,500 executions), Pro €60/mo, Business €800/mo.
**Strengths:** Self-hostable (strong GDPR story). 400+ integrations. AI agent workflow capabilities. Large community. Active development. Free self-hosted tier.
**Weaknesses from LetsBe's perspective:**
- Users must build every workflow manually — no autonomous agents
- Technical setup required — not for non-technical business owners
- Doesn't provide business tools — only connects them
- AI capabilities are workflow nodes, not autonomous agents
- No pre-deployed tool stack — customer must source and manage their own tools
**LetsBe differentiator:** "n8n is a powerful automation builder — if you're a developer. LetsBe gives non-technical business owners an AI team that figures out the workflows on its own. You don't build automations. You describe what you want and the AI does it."
#### Make.com (formerly Integromat)
**What it is:** Visual automation platform for connecting apps and designing workflows. Cloud-only.
**Target market:** Marketing teams, operations managers, small businesses comfortable with visual builders.
**Pricing:** Free tier (1,000 ops), Core $10.59/mo (10,000 ops), Pro $18.82/mo, Teams $34.12/mo, Enterprise custom.
**Strengths:** Beautiful visual builder. Thousands of integrations. More accessible than n8n for non-developers.
**Weaknesses from LetsBe's perspective:**
- Cloud-only — all data processed on Make's servers (US-based AWS, no self-hosting)
- Still requires manual workflow building
- No AI agent capabilities — purely rule-based automation
- No business tools provided — only connects existing SaaS
- GDPR concern: "Zapier processes all data on US-based AWS servers" — same concern applies to Make
**LetsBe differentiator:** "Make helps you connect your existing tools with IF-THEN rules. LetsBe gives you the tools AND an AI team that connects them intelligently — no rules to build, no workflows to maintain."
#### Zapier
**What it is:** The dominant workflow automation platform. 7,000+ app integrations. Recently added AI features ("Zapier Central").
**Target market:** Everyone from solo founders to mid-market companies. The automation default.
**Pricing:** Free (5 zaps), Starter $29.99/mo (750 tasks), Professional $73.50/mo, Team $103.50/mo, Enterprise custom.
**Strengths:** Massive integration library. Brand recognition. Zapier Central adds conversational AI layer. Easy to start.
**Weaknesses from LetsBe's perspective:**
- Cloud-only, US-hosted — no self-hosting, GDPR complexity
- Users still build automations (even with Zapier Central's AI assistance)
- Expensive at scale — task-based pricing adds up quickly
- Doesn't provide tools — only connects them
- No privacy story — all data flows through Zapier's cloud
**LetsBe differentiator:** "Zapier connects your 10 different SaaS subscriptions. LetsBe replaces them with one server and an AI team that runs everything. Fewer subscriptions, lower cost, better privacy."
### Category 3: Self-Hosted App Management Platforms
These platforms help you deploy and manage self-hosted applications. They solve the infrastructure problem but have no AI capabilities.
#### Cloudron
**What it is:** Platform for deploying, managing, and securing web applications on your own server. One-click app installs, automatic updates, backups, SSL, and user management.
**Target market:** Tech-savvy individuals and small businesses who want self-hosted apps without sysadmin complexity.
**Pricing:** Free (2 apps), Pro $15/mo (unlimited apps). VPS costs extra ($5-40/mo depending on provider).
**Strengths:** Excellent app management UX. 100+ available apps. Automatic updates and backups. Good documentation. Affordable.
**Weaknesses from LetsBe's perspective:**
- No AI — tools are installed but nobody operates them
- No cross-tool workflows — apps are silos
- Technical knowledge still required (DNS, SSH, basic server concepts)
- No business-specific curation — generic app store
- Customer must still learn and operate each tool manually
**LetsBe differentiator:** "Cloudron installs the tools. LetsBe installs the tools AND gives you an AI team to run them. The difference between having a kitchen and having a chef."
#### YunoHost
**What it is:** Free, open-source Debian-based OS for self-hosting web services. App catalog, user management, SSL, backups.
**Target market:** Privacy enthusiasts, hobbyists, technically inclined individuals. Community-driven.
**Pricing:** Free (open source). VPS costs only.
**Strengths:** Completely free. Active community. Good app selection. Privacy-focused ethos.
**Weaknesses from LetsBe's perspective:**
- Requires significant technical knowledge
- No AI capabilities
- No cross-tool integration
- Community support only — no commercial backing
- Not business-focused — general self-hosting OS
**LetsBe differentiator:** "YunoHost is great if you're a developer who wants to self-host for fun. LetsBe is for the business owner who wants their tools managed by AI so they can focus on their business."
### Category 4: All-in-One Business Suites
These provide integrated business tools in one platform, but without AI autonomy and typically cloud-hosted.
#### Odoo
**What it is:** Modular ERP/CRM/business suite with 30+ apps covering sales, marketing, HR, accounting, manufacturing, and more. Available as cloud, self-hosted, or Odoo.sh (managed).
**Target market:** SMBs to mid-market. The most direct alternative for "all my business tools in one place."
**Pricing:** One app free (unlimited users). Standard ~$31/user/mo (all apps, cloud). Custom ~$47/user/mo (self-hosted or Odoo.sh). Community Edition free but limited.
**Strengths:** Comprehensive module catalog. Self-hosted option. Mature product (15+ years). Large partner ecosystem. One unified platform. Implementation support available.
**Weaknesses from LetsBe's perspective:**
- No autonomous AI agents — automation is rule-based (Odoo Studio, server actions)
- Per-user pricing scales badly for growing teams
- Implementation complexity — typical implementation costs $1,500-$10,000+
- Monolithic — all tools are Odoo's, not best-of-breed open source
- Self-hosted requires significant technical knowledge
- No secrets firewall or AI privacy controls
**LetsBe differentiator:** "Odoo gives you one company's version of every business tool. LetsBe gives you best-in-class open-source tools — the ones the community picks — PLUS an AI team that runs them. And it costs the same whether you have 1 user or 10."
#### Microsoft 365 + Copilot
**What it is:** The incumbent business productivity suite with AI capabilities via Copilot. Copilot Studio enables building autonomous agents that connect to enterprise systems.
**Target market:** Everyone from small businesses to enterprises. The default choice for businesses already in the Microsoft ecosystem.
**Pricing:** Microsoft 365 Business Basic $6/user/mo + Copilot $18-21/user/mo (adjusting to $21 after March 2026). Copilot Studio: $200/mo per 25,000 credit pack for custom agents.
**Strengths:** Ubiquitous — most businesses already use Microsoft tools. Deep Office integration. Copilot is getting genuinely useful. Massive distribution. Trust and brand recognition.
**Weaknesses from LetsBe's perspective:**
- Cloud-only — all data on Microsoft's infrastructure
- Per-user pricing (a 5-person team pays $100-140/mo just for Microsoft 365 + Copilot — before any other tools)
- Copilot agents require significant setup (Copilot Studio)
- Not privacy-first — Microsoft's data practices are complex
- Doesn't provide CRM, invoicing, project management, etc. — only productivity tools
- AI is assistant-level, not workforce-level (helps you write emails, doesn't run your business)
**LetsBe differentiator:** "Microsoft gives you Word, Excel, and an AI that helps you write in them. LetsBe gives you a CRM, email server, project manager, invoicing, website, AND an AI team that runs all of it. Microsoft helps you work. LetsBe works for you."
### Category 5: Virtual Assistants (Human)
Not software competitors, but the incumbent solution for the problem LetsBe solves.
#### Human Virtual Assistants (Belay, Time Etc, Fancy Hands, etc.)
**What it is:** Remote human assistants who manage email, scheduling, data entry, social media, and administrative tasks.
**Target market:** Solo founders, executives, small business owners who need operational help.
**Pricing:** $25-75/hour depending on expertise and region. Typical packages: 10-40 hours/month ($250-3,000/mo). Belay starts at ~$1,700/mo for a dedicated VA.
**Strengths:** Human judgment. Can handle truly ambiguous tasks. Personal relationship. No technical setup.
**Weaknesses from LetsBe's perspective:**
- Expensive — even budget VAs cost $500+/mo for meaningful hours
- Limited availability (not 24/7 unless you pay for multiple)
- Inconsistent quality — depends on the individual
- Doesn't scale — more work requires more hours/more people
- Security risk — a human with your passwords is a bigger trust issue than a firewalled AI
- No audit trail of actions
**LetsBe differentiator:** "A virtual assistant costs $1,000-3,000/month for 20-40 hours of work. LetsBe costs €29-109/month and works 24/7. It's not as creative as a human — but for 95% of routine business operations, it doesn't need to be."
---
## 3. Competitive Comparison Matrix
| Capability | LetsBe | OpenAI Frontier | Lindy | Sintra | n8n | Cloudron | Odoo | M365+Copilot | Human VA |
|-----------|--------|-----------------|-------|--------|-----|----------|------|-------------|----------|
| **AI agents that operate tools** | ✅ | ✅ | ✅ | ❌ (advice only) | ❌ | ❌ | ❌ | Partial | ✅ |
| **Pre-deployed business tools** | ✅ (25+) | ❌ | ❌ | ❌ | ❌ | ✅ (100+) | ✅ (30+) | Partial | ❌ |
| **Self-hosted / customer-controlled** | ✅ | ❌ | ❌ | ❌ | ✅ | ✅ | ✅ | ❌ | N/A |
| **Secrets firewall** | ✅ | ❌ | ❌ | ❌ | N/A | N/A | N/A | ❌ | ❌ |
| **Cross-tool AI workflows** | ✅ | ✅ | ✅ | ❌ | Manual | ❌ | Rule-based | Partial | ✅ |
| **Non-technical setup** | ✅ | ❌ | ✅ | ✅ | ❌ | ❌ | ❌ | ✅ | ✅ |
| **Flat pricing (no per-user)** | ✅ | ❌ | ❌ | ✅ | ✅ (self-hosted) | ✅ | ❌ | ❌ | ❌ |
| **Regional data residency (EU or NA)** | ✅ (EU or US) | ❌ | ❌ | ❌ | ✅ (if self-hosted) | ✅ (if EU VPS) | ✅ (if self-hosted) | ❌ | N/A |
| **24/7 availability** | ✅ | ✅ | ✅ | ✅ | ✅ | N/A | N/A | ✅ | ❌ |
| **SMB pricing (<€150/mo)** | ✅ (€29-109) | ❌ | Depends on usage | ✅ ($39-97) | ✅ (free self-hosted) | ✅ ($15) | ❌ (per-user) | ❌ (per-user) | ❌ |
---
## 4. Positioning by Customer Persona
Different customers evaluate LetsBe against different competitors. The pitch changes depending on where the customer is coming from.
### 4.1 The Solo Founder / Freelancer (Maria)
**Coming from:** Google Workspace + scattered SaaS tools + manual everything
**Evaluating against:** Lindy, Sintra, Zapier, or just doing it themselves
**Key message:** "Stop paying for 5 different subscriptions and spending your evenings on admin. LetsBe gives you every tool you need and an AI team to run them — for less than what you're paying for HubSpot alone."
**Objection to handle:** "I can just use ChatGPT/Claude for free"
**Response:** "ChatGPT can draft an email. It can't send it through your server, update your CRM, schedule the follow-up, and log the interaction — all from one instruction. LetsBe's AI has access to your actual tools."
### 4.2 The Small Agency Owner (Tom)
**Coming from:** Mix of SaaS tools, maybe a VA, growing team
**Evaluating against:** Odoo, n8n + SaaS stack, hiring another person
**Key message:** "Your next hire doesn't need to be a person. LetsBe gives you an AI operations team for the cost of a single SaaS subscription. It handles the admin so your humans can do the creative work."
**Objection to handle:** "We already have Odoo / our tools work fine"
**Response:** "Your tools work — but who's operating them? Someone on your team spends hours every week on data entry, scheduling, email follow-ups. LetsBe automates that across all your tools simultaneously."
### 4.3 The Privacy-Conscious Professional (Dr. Weber)
**Coming from:** Reluctantly using cloud tools, or avoiding digital tools entirely
**Evaluating against:** Cloudron/YunoHost, on-premise solutions, paper
**Key message:** "Finally, AI that respects your data. Everything runs on your own server — in Germany for EU customers, in Virginia for North American customers. Your credentials never leave the machine. Your AI never sees your passwords. Privacy-compliant by architecture, not by policy."
**Objection to handle:** "How can I trust AI with sensitive data?"
**Response:** "Our secrets firewall strips all credentials before anything reaches an AI provider. The AI manages your tools without ever seeing your passwords — it's enforced at the transport layer, not by hoping the AI behaves."
---
## 5. Competitive Moat Analysis
LetsBe's competitive advantages build in layers over time:
**Layer 1 — Technical complexity (immediate).** Combining 25+ containerized tools with an AI agent runtime and a secrets firewall is genuinely hard to replicate. The Safety Wrapper extension alone — with typed hooks for interception, credential management, token metering, and audit logging — represents months of engineering. A competitor starting from zero faces 6-12 months of infrastructure work before they have a usable product.
**Layer 2 — Speed to market (months 1-6).** Being first with a working product means real user feedback, real bug fixes, real tool cheat sheets refined by actual usage. Every week in market generates knowledge that improves the product in ways a competitor can't shortcut.
**Layer 3 — Tool ecosystem depth (months 6-18).** Each tool integration (cheat sheet, API patterns, edge case handling) takes 30-60 minutes to write but represents hard-won knowledge about that tool's quirks. At 25+ tools, this library becomes a significant asset. A competitor would need to replicate each one.
**Layer 4 — Customer lock-in through data gravity (year 1+).** Once a customer's CRM, email, files, calendar, and invoices all live on their LetsBe server, switching costs are real. Not because we trap them — every tool is open-source with standard exports — but because migrating 6-10 tools simultaneously is painful enough that they won't do it casually.
**Layer 5 — Network effects (year 2+).** As the customer base grows: shared skill improvements benefit everyone, community-contributed tool integrations expand the catalog, and LetsBe's operational knowledge (which tools work best together, which AI models handle which tasks most efficiently) becomes a compounding advantage.
### What Could Kill Us
Honesty about threats matters more than optimism:
| Threat | Severity | Likelihood | Mitigation |
|--------|----------|-----------|------------|
| **Microsoft adds Copilot agents for self-hosted tools** | High | Low (Microsoft is doubling down on cloud) | Speed — ship before they notice the niche |
| **n8n adds autonomous AI agents** | High | Medium (they're already building AI workflow nodes) | Differentiate on "tools included" — n8n will never deploy CRMs and email servers |
| **OpenAI Frontier launches SMB tier** | High | Medium (they're focused on enterprise for 2026) | Privacy angle — Frontier will always be cloud-hosted |
| **A YC startup copies the concept** | Medium | High | Execution speed + 30-tool integration depth as moat |
| **Open-source replication** | Medium | Medium | The secret sauce is the combination + operational knowledge, not any single component |
| **AI agents become commoditized** | Low-Medium | High (inevitable long-term) | Value shifts to tool integration quality and customer trust — LetsBe becomes the "trusted managed business infrastructure" brand |
---
## 6. Pricing Comparison
Total cost of ownership for a typical 3-person small business needing CRM, email, files, project management, calendar, and AI assistance:
| Solution | Monthly Cost | What's Included | What's Missing |
|----------|-------------|----------------|----------------|
| **LetsBe Biz (Business tier)** | **€75/mo** | All 25+ tools + AI team + server + privacy | — |
| Lindy Pro + HubSpot Starter + Google Workspace + Asana | ~$200/mo | AI agents + CRM + email + projects | No privacy, 4 separate platforms, no self-hosting |
| Odoo Standard (3 users) | ~$93/mo | All business tools | No AI agents, no privacy (cloud), per-user scaling |
| n8n Cloud + SaaS stack (HubSpot + Google + Asana) | ~$170/mo | Automation + CRM + email + projects | No AI agents, manual workflow building, no privacy |
| Microsoft 365 + Copilot (3 users) | ~$80/mo | Productivity suite + AI assistant | No CRM, no invoicing, no project management, cloud-only |
| Cloudron + manual SaaS stack | ~$60/mo | Self-hosted tools | No AI, manual operation, technical knowledge required |
| Human VA (10 hrs/mo) | ~$500/mo | Human judgment | Limited hours, expensive, security risk |
LetsBe is price-competitive with DIY stacks while including AI capabilities that no DIY stack offers. It's dramatically cheaper than human VAs while being available 24/7.
---
## 7. Battlecard Quick Reference
For sales conversations. One card per likely competitor mention.
### vs. "I'll just use ChatGPT/Claude directly"
**Their pitch:** "AI is free/cheap, why pay for LetsBe?"
**Our response:** ChatGPT is a conversation. LetsBe is a workforce. ChatGPT can draft an email — LetsBe sends it, updates the CRM, schedules the follow-up, and logs the interaction. You're comparing a notepad to an office.
### vs. Lindy
**Their pitch:** "5,000+ integrations, natural language agents"
**Our response:** Lindy connects to your existing SaaS tools — you still pay for all those subscriptions. LetsBe replaces them. One price, all tools, AI included, on your own server.
### vs. n8n
**Their pitch:** "Self-hosted, free, 400+ integrations"
**Our response:** n8n is powerful — for developers who want to build automations. LetsBe is for business owners who want things done. You don't build workflows. You tell the AI what you need.
### vs. Odoo
**Their pitch:** "All-in-one business suite, 30+ apps"
**Our response:** Odoo gives you the tools. LetsBe gives you the tools AND the team to run them. Plus: flat pricing regardless of team size, not $30+ per user per month.
### vs. "We already use [SaaS tool]"
**Their pitch:** "Our current tools work fine"
**Our response:** Your tools work — but who's operating them? How many hours does your team spend on data entry, scheduling, follow-ups? LetsBe automates the operational work across all your tools. Your team does the human stuff.
### vs. Microsoft 365 + Copilot
**Their pitch:** "We're already in Microsoft, Copilot is included"
**Our response:** Copilot helps you write in Word and Excel. LetsBe runs your CRM, sends your invoices, manages your calendar, and handles your customer communications. Microsoft helps you work. LetsBe works for you.
### vs. "I can hire a VA for that"
**Their pitch:** "I'd rather have a human"
**Our response:** A VA costs $500-3,000/month for 10-40 hours. LetsBe costs €29-109/month and works 24/7. For the 95% of business operations that are routine — scheduling, data entry, follow-ups, reporting — AI is faster, cheaper, and more consistent. Save your human budget for the 5% that actually needs human judgment.
---
## 8. Market Timing
The competitive landscape is moving fast. Key trends working in LetsBe's favor:
**The "Great SaaS Exodus"** — Companies are moving from SaaS subscriptions to self-hosted alternatives. The self-hosting market is projected to hit $85.2 billion by 2034, growing at 18.5% annually. LetsBe rides this trend while adding the AI layer that pure self-hosting solutions lack.
**AI agent adoption is accelerating** — Over 90% of SMBs are predicted to have at least one agentic AI system in production by end of 2026. The market is growing from ~$7.8B (2025) to a projected $52.6B by 2030 (46.3% CAGR). LetsBe enters during the adoption wave, not before it.
**GDPR enforcement is intensifying** — €5.88 billion in cumulative GDPR fines since 2018, with €1.2 billion in 2024 alone. EU businesses are increasingly wary of US-hosted SaaS. LetsBe's EU-hosted, privacy-first architecture is becoming a requirement, not a nice-to-have.
**Enterprise AI is leaving SMBs behind** — OpenAI Frontier, Microsoft Copilot Studio, and Salesforce Agentforce are all targeting enterprise. The SMB market is underserved by purpose-built AI agent solutions. LetsBe fills that gap.
---
## 9. Open Questions
| # | Question | Notes |
|---|----------|-------|
| 1 | Monitor n8n's AI agent roadmap | They're the closest threat in the self-hosted space. Track their releases quarterly. |
| 2 | Track OpenAI Frontier SMB expansion | If they launch a small business tier, it changes the competitive story significantly. |
| 3 | Evaluate Dify/Flowise as potential threats | Open-source AI agent builders that could be combined with Cloudron/YunoHost. |
| 4 | Customer win/loss tracking | Once selling, track why customers choose LetsBe vs. alternatives — refine positioning accordingly. |
| 5 | Pricing pressure monitoring | If Lindy or Sintra drop prices significantly, assess whether LetsBe's "tools included" value prop justifies the premium. |
---
## 10. Changelog
| Version | Date | Changes |
|---------|------|---------|
| 1.0 | 2026-02-26 | Initial competitive landscape. Five competitor categories, detailed analysis of 9 competitors, comparison matrix, persona-based positioning, moat analysis, pricing comparison, battlecard quick reference, market timing assessment. |
---
*This document should be updated quarterly as the competitive landscape evolves. Customer conversations are the best source of competitive intelligence — track which competitors come up and why customers choose LetsBe (or don't).*

719
docs/strategy/LetsBe_Biz_Foundation_Document.md Normal file
View File

@@ -0,0 +1,719 @@
# LetsBe Biz — Foundation Document
**Date:** February 25, 2026
**Authors:** Matt (Founder), Claude (Architecture & Strategy)
**Status:** Version 1.1
**Companion Documents:** Technical Architecture v1.1, Product Vision v1.0, Pricing Model v2.2
---
## 1. Who We Are
LetsBe Biz is a privacy-first AI workforce platform. We give every small business their own private team of AI employees that run the business while the owner focuses on what they're actually good at.
Not AI-assisted tools. Not a chatbot. Not a workflow builder. A team of AI agents that operate 25+ business tools autonomously — reading data, sending campaigns, managing customer conversations, scheduling meetings, processing invoices, publishing content, handling IT operations — all on a server the business owns, with infrastructure secrets that never leave the machine.
Our background is enterprise infrastructure. We're channeling that into a productized offering where the AI does the work and humans steer the direction.
**Tagline:** "Where power meets privacy."
**Logo:** Current branding (logo_long.png, logo_square.jpg) — no redesign planned.
---
## 2. The Problem We Solve
Small business owners are drowning. They're running their entire operation across 10-30 SaaS tools — each with its own subscription, login, data silo, and terms of service. They pay €500-2,000/month in SaaS subscriptions, often can't afford a VA or IT person, and spend 60% of their time on admin instead of revenue-generating work.
Even those who've consolidated onto self-hosted tools still face a core problem: someone has to operate them. Configure the CRM. Send the newsletter. Manage the calendar. Process the invoices. Handle the IT issues. That requires either expensive human labor (€1,500-3,000/mo for a part-time VA) or deep technical knowledge most owners don't have.
The current landscape forces an impossible choice: powerful but fragmented (SaaS), private but complex (self-hosted), or AI-powered but not private (cloud AI). No one offers all three.
**What we replace:**
- 10-30 SaaS subscriptions (€500-2,000/mo)
- A part-time virtual assistant (€1,500-3,000/mo)
- Occasional IT contractor help (€100-200/hr)
- All with better privacy, better consistency, and 24/7 availability
---
## 3. What We're Building
### 3.1 Infrastructure Layer
Every customer gets their own isolated VPS with a full suite of open-source business tools deployed via Docker Compose, fronted by Nginx, and provisioned automatically.
**Current tool stack (28 applications):**
| Category | Tools |
|----------|-------|
| Cloud & Files | Nextcloud, MinIO |
| Communication | Stalwart Mail (email), Chatwoot (customer chat), Listmonk (newsletters) |
| Project Management | Cal.com, NocoDB |
| Development | Gitea, Drone CI, Portainer |
| Automation | Activepieces |
| CMS & Marketing | Ghost, WordPress, Squidex |
| Business & ERP | Odoo |
| Analytics | Umami, Redash |
| Design | Penpot |
| Security | Keycloak (SSO/IAM), VaultWarden (passwords) |
| Monitoring | Uptime Kuma, GlitchTip, Diun |
| Documents | Documenso (e-signatures) |
| Chat & AI | LibreChat |
*See Tool Catalog v2.2 for full details, licensing, and 27 expansion candidates. Removed since v1.0: Poste.io (→ Stalwart Mail), Windmill (managed-service license prohibition), Typebot (retained for internal use only), Twenty CRM, Akaunting, Budibase, Invoice Ninja.*
#### 3.1.1 Tool Selection Model
Users don't pick from a raw list of 30. The flow is:
1. **Business type selection** → Pre-configured default bundle (e.g., "Freelancer," "Agency," "E-commerce," "Consulting")
2. **Customization screen** → Full tool catalog with defaults pre-checked. Toggle switches to add/remove.
3. **Live resource calculator** → As tools change, required CPU/RAM/storage updates in real-time.
4. **Server tier auto-selection** → Only tiers that meet or exceed the resource requirement are shown. Users cannot select an underpowered server. The cheapest visible option IS the right option.
**Example bundles (defaults, all customizable):**
| Bundle | Default Tools | ~Resource Estimate |
|--------|--------------|-------------------|
| Freelancer | Nextcloud, Stalwart Mail, Cal.com, Ghost, Odoo-lite, Keycloak, VaultWarden | 4 vCPU, 8 GB RAM |
| Agency | Above + Chatwoot, Listmonk, NocoDB, Penpot | 8 vCPU, 16 GB RAM |
| E-commerce | Freelancer + Odoo-full, Chatwoot, Umami, Documenso, Redash | 8 vCPU, 16 GB RAM |
| Power User | Full 28-tool stack | 16 vCPU, 32 GB RAM |
#### 3.1.2 Server Sizing
Server tiers are dynamically gated by tool selection. Each tool has a known resource footprint. The live calculator shows minimum tier requirements and users cannot downgrade below calculated minimums.
**Server tiers (Netcup RS G12, primary):**
| Tier | Specs | Netcup Plan | Cost to LetsBe | Use Case |
|------|-------|-------------|----------------|----------|
| Lite (hidden) | 4 cores, 8 GB DDR5, 256 GB NVMe | RS 1000 G12 | ~€8.74/mo | Price-sensitive, 5-8 tools |
| Build (default) | 8 cores, 16 GB DDR5, 512 GB NVMe | RS 2000 G12 | ~€14.58/mo | Small business, 10-15 tools |
| Scale | 12 cores, 32 GB DDR5, 1 TB NVMe | RS 4000 G12 | ~€27.08/mo | Agency/e-commerce, 15-30 tools |
| Enterprise | 16 cores, 64 GB DDR5, 2 TB NVMe | RS 8000 G12 | ~€58.00/mo | Full 28-tool stack |
**Hetzner Cloud CCX (backup/overflow):**
| Tier | Specs | Hetzner Plan | Cost to LetsBe |
|------|-------|-------------|----------------|
| Starter | 2 vCPU, 8 GB RAM, 80 GB NVMe | CCX13 | ~€12.49/mo |
| Growth | 4 vCPU, 16 GB RAM, 160 GB NVMe | CCX23 | ~€24.49/mo |
| Scale | 8 vCPU, 32 GB RAM, 240 GB NVMe | CCX33 | ~€48.49/mo |
#### 3.1.3 VPS Provider Strategy
**Primary: Netcup RS G12.** Best price-to-performance in Europe. AMD EPYC 9645 (Zen 5), DDR5 ECC, NVMe, 2.5 Gbps networking. Provisioning automated via Ansible. Additional advantage: **domain reselling** through Netcup's reseller program (Level A free, 450+ TLDs) — customers can buy domains directly through us.
**Dual-region support:** Netcup offers data centers in both **Nuremberg, Germany** (EU) and **Manassas, Virginia** (US). Customers choose their region at signup. EU customers default to Germany; North American customers default to Virginia for lower latency. Pricing varies by approximately ±€1-2/mo depending on tier and region. Same RS G12 hardware in both locations.
**Provisioning model:** Maintain a pre-provisioned pool of servers at 12-month contract rates in both regions. When a customer signs up → assign from pool (matching their region) → provision tools → ready in minutes. Pool size managed dynamically based on signup velocity per region.
**Backup/Overflow: Hetzner Cloud.** Full Cloud API enables instant on-demand provisioning when Netcup pool is full. Hourly billing means no waste on overflow capacity. Acts as safety valve for signup surges.
**Note:** Hetzner prices rising 30-37% April 1, 2026. Netcup 12-month contracts are locked and significantly cheaper per core. Architecture is provider-agnostic — Ansible works on any Debian VPS regardless of host.
---
### 3.2 The AI Workforce
This is the product. Not "AI-managed infrastructure" — an **AI workforce** that operates the business tools on behalf of the user.
The AI runtime (**OpenClaw**) runs on the customer's VPS and connects to LLMs via OpenRouter. All config and history lives locally. We do not fork or modify upstream — OpenClaw is treated as a dependency. All LetsBe-specific logic (secrets redaction, command gating, Hub communication, tool adapters) lives in a separate **Safety Wrapper** layer that can pull upstream updates without conflicts.
#### 3.2.1 What the AI Workforce Does
Every deployed tool exposes APIs. The AI agents have full access to those APIs and execute autonomously within guardrails:
- **Marketing Agent** pulls last month's top blog posts from Ghost, composes a newsletter, and sends it through Listmonk — without being asked. Or on command: "Send the monthly newsletter with our best content."
- **Secretary Agent** receives a meeting request via Stalwart Mail, checks availability on Cal.com, sends a confirmation with a Zoom link, and adds a reminder. Handles all administrative correspondence.
- **Sales Agent** monitors Chatwoot for new leads, qualifies them based on conversation patterns, creates a quote in Odoo, and routes hot leads to the human for approval.
- **IT Agent** detects that Nextcloud storage hit 80%, identifies and removes old temp files, resizes if needed, and reports what it did. Reads Nginx configs, checks cert validity, restarts failed containers. Full sysadmin capability.
- **Custom agents** — Users create their own agents for domain-specific workflows: content planning, analytics reporting, customer segmentation, inventory management, compliance checking, anything the team needs.
The platform is deliberately open-ended. Users discover new capabilities organically — "can you do this?" → "oh shit, it can." Each user builds a unique, personalized workflow system they become attached to. That's the moat: not the tools (anyone can install Nextcloud), not the AI (anyone can use ChatGPT), but the *configured, trained, personalized AI team* that knows how *their* business works.
#### 3.2.2 Agent Architecture
Default agents pre-configured per business type:
| Agent | Role | Tool Access | Example Workflows |
|-------|------|-------------|-------------------|
| Dispatcher | Message router & coordinator | Inter-agent messaging | Routes user requests, breaks complex tasks into ordered steps, morning briefing |
| IT Admin | Infrastructure & security | Portainer, Uptime Kuma, Shell, Docker | Auto-fix container crashes, rotate certs, resize storage, security checks |
| Marketing | Content & campaigns | Ghost, Listmonk, Umami, Penpot, WordPress | Draft & send newsletters, schedule posts, analyze performance |
| Secretary | Communications & scheduling | Cal.com, Stalwart Mail, Nextcloud, NocoDB | Manage calendar, handle email, organize files, send confirmations |
| Sales | Leads & revenue | Chatwoot, Odoo, Documenso | Qualify leads, create quotes, send contracts |
Users can add/remove/customize agents anytime. Unlimited agents — no hardcoded limits. Each agent is configured via:
- **SOUL.md** — Personality, domain knowledge, behavioral rules, brand voice
- **Tool permissions** — Which APIs this agent can access, what operations it can perform
- **Model selection** — (Advanced mode) Choose different LLMs per agent
#### 3.2.3 Tool API Adapter Strategy
This is the critical engineering investment that creates the competitive barrier.
Each business tool has APIs. Tool API adapters turn those APIs into tools that OpenClaw agents can invoke. 24+ adapters covering the tool stack:
| Tool | API Type | Key Operations |
|------|----------|---------------|
| Nextcloud | WebDAV + OCS REST | Files, shares, users, calendar, contacts |
| Chatwoot | REST | Conversations, contacts, labels, assignments |
| Odoo | XML-RPC + JSON-RPC | Invoices, quotes, contacts, inventory |
| Ghost | Content + Admin REST | Posts, pages, tags, members, newsletters |
| Cal.com | REST | Events, bookings, availability, teams |
| Stalwart Mail | REST + SMTP/IMAP/JMAP | Send/receive email, manage accounts |
| Portainer | REST | Containers, stacks, volumes, networks |
| Umami | REST | Page views, events, referrers, reports |
| Listmonk | REST | Campaigns, subscribers, templates |
| NocoDB | REST | Tables, records, views, webhooks |
| ... | ... | (18 additional adapters) |
These adapters are built via a common framework (auth handling, error patterns, rate limiting, response formatting) then parallelized. Each adapter is isolated — Nextcloud's doesn't depend on Chatwoot's. Integration depth is the deepest moat: months of compounding engineering work per tool, tested against real tool versions with real edge cases.
---
### 3.3 Secrets Firewall & Safety Architecture
Highest security priority. Enforced at four independent layers:
#### 3.3.1 How It Works
The AI sees *everything* on the server — full configs, compose files, error logs, cert expiry — **except literal secret values**. Passwords, API keys, SSL private keys, and tokens are replaced with placeholders before reaching the LLM.
**Layer 1 — Secrets Registry:** All generated credentials (50+ per tenant) are logged in an encrypted local registry (SQLite) with key names, patterns, and locations. When credentials rotate, the registry updates.
**Layer 2 — Outbound Redaction:** Before any text leaves the VPS to the LLM, a middleware layer checks all outbound text against the registry. Known secrets are replaced with deterministic placeholders: `[REDACTED:postgres_password]`, `[REDACTED:nextcloud_admin_key]`. The AI can reason about which credentials are relevant without seeing values.
**Layer 3 — Pattern Safety Net:** Regex patterns catch secrets the registry might have missed: private key blocks, JWT tokens, bcrypt hashes, connection strings with credentials, high-entropy base64 blobs, common env var patterns.
**Layer 4 — Function-Call Proxy:** When the AI needs to *use* a secret (e.g., restart a service that needs a DB password), it doesn't receive the credential:
```
execute_with_credential("restart_postgres", credential_id="pg_main")
```
The Safety Wrapper injects the real value locally and executes. The AI gets the outcome but never sees the credential value.
**Privacy messaging:** "Your infrastructure credentials and secrets never leave your server. Your AI team manages tools through secure local commands — it never receives your passwords, keys, or certificates."
#### 3.3.2 Command Gating (Five-Tier)
Every tool call is classified and gated based on autonomy level:
**Green — Non-destructive (auto-execute at all levels):**
- `file_read`, `env_read` — Read files, logs, configs (output redacted)
- `container_stats` — List/inspect containers
- `query_select` — Database SELECT queries only
- `check_status`, `dns_lookup`, `cert_check` — Infrastructure health checks
**Yellow — Modifying (auto-execute at Level 2+, gated at Level 1):**
- `container_restart` — Restart services
- `file_write`, `env_update` — Modify files and configs
- `nginx_reload` — Reload web server
- `chatwoot_assign`, `calcom_create` — Internal business operations
**Yellow+External — External-facing (gated by default at all levels until user unlocks per agent/tool):**
- `ghost_publish` — Publish blog content visible to public
- `listmonk_send` — Send email campaigns to subscribers
- `poste_send` — Send emails to external recipients
- `chatwoot_reply_external` — Reply to customer conversations
- `social_post` — Post to social media
- `documenso_send` — Send documents for external signature
External communications are gated independently of autonomy levels. A misworded email to a client or a prematurely published blog post damages the business's reputation. Users must build trust with their AI team before allowing autonomous external-facing actions.
**Red — Destructive (auto-execute at Level 3, gated at Level 1-2):**
- `file_delete`, `container_remove`, `volume_delete` — Delete resources
- `user_revoke`, `db_drop_table`, `backup_delete` — Revoke access, drop data
**Critical Red — Irreversible (always gated at all levels):**
- `db_drop_database`, `firewall_modify`, `ssh_config_modify` — Infrastructure-critical
- `backup_wipe_all`, `user_delete_account`, `ssl_revoke` — Unrecoverable
---
### 3.4 AI Autonomy Levels
Customers control how much the AI can do without approval:
| Level | Name | Auto-Execute | Requires Approval | Use Case |
|-------|------|-------------|-------------------|----------|
| 1 | Training Wheels | Green only | Yellow + Red + Critical Red | New customers, cautious users, onboarding |
| 2 | Trusted Assistant (default) | Green + Yellow | Red + Critical Red | Established trust, daily operations |
| 3 | Full Autonomy | Green + Yellow + Red | Critical Red only | Power users, experienced teams |
**Invariants (all levels):**
- Secrets always redacted
- Audit trail always logged
- AI never sees raw credentials
- External comms gated until explicitly unlocked per agent/tool
- Destructive actions always gated
Each agent can have its own autonomy level independent of the tenant default (e.g., IT Admin at Level 3, Secretary at Level 1).
---
### 3.5 Dynamic Tool Installation
One of the most powerful capabilities in the platform.
A user says "I need a wiki" and the IT Agent can deploy BookStack or WikiJS from a curated catalog, configure it behind nginx with SSL, seed credentials in the secrets registry, and report back — all gated behind user approval.
**How it works:**
1. User requests a tool: "Can you set up a wiki for my team?"
2. IT Agent consults the **Tool Catalog** — a curated registry of pre-tested open-source tools with Docker Compose templates, nginx configs, and resource requirements
3. IT Agent presents: "I recommend BookStack — 256MB RAM required, you have 4GB free. Want me to install it?"
4. **User approves** (Red-tier operation — always gated)
5. IT Agent executes: deploys stack, configures nginx, generates credentials, stores in secrets registry, runs health check
6. IT Agent reports: "BookStack is live at wiki.yourdomain.com. [credentials via app]"
Tools are deployed only from the curated catalog — the IT Agent cannot deploy arbitrary Docker images. Resource checks prevent server overload. All deployments are audited and reversible.
---
### 3.6 Mobile App
React Native (iOS + Android). Primary client interface.
**Core features:**
- Chat with agent selection ("Talk to your Marketing Agent")
- Morning briefing from Dispatcher Agent (what happened overnight, what needs attention)
- Team management (agent config, model selection, autonomy levels)
- Command gating approvals (push notifications with one-tap approve/deny)
- Server health overview (storage, uptime, active tools)
- Usage dashboard (token consumption, activity)
- External comms gate management (unlock sending per agent/tool)
**Access channels:** App-only at launch. WhatsApp/Telegram as fallback channels ready at launch with security disclaimer. Hub acts as relay/proxy (JWT auth, WebSocket) — no exposed VPS ports.
---
### 3.7 Hub (Central Platform)
Next.js admin dashboard and API. Production-ready infrastructure for customer management, billing, provisioning, monitoring.
**Current capabilities:** Customer/order management, Netcup SCP integration, Stripe billing, 2FA, DNS verification, Docker provisioning, enterprise monitoring.
**New capabilities (this version):**
- Customer portal API (agent config, usage tracking, command approvals)
- Token metering and overage billing
- Agent management API (SOUL.md, TOOLS.md, permissions)
- Safety Wrapper communication endpoints (heartbeat, registration, config sync)
- Command approval queue (Yellow/Red commands surface here)
- Token usage analytics dashboard
- Founding member program tracking
All tenant servers communicate with Hub via the Safety Wrapper. The Safety Wrapper handles registration, heartbeat, telemetry, config sync, and approval request routing.
---
### 3.8 Website (letsbe.biz)
Separate from Hub. AI-powered onboarding flow:
| Step | Details |
|------|---------|
| 1 | Landing page with chat input: "Describe your business." |
| 2 | AI conversation (Gemini Flash) — 1-2 messages, constrained to business type classification |
| 3 | Tool recommendation — Pre-selected bundle for detected business type, full catalog visible |
| 4 | Customization — Add/remove tools, live resource calculator |
| 5 | Server selection — Only tiers meeting minimum requirement shown |
| 6 | Domain setup — User brings domain or buys one (Netcup reselling) |
| 7 | Subagent config — Optional. Template-based per business type |
| 8 | Payment — Stripe. Pay first, then provision |
| 9 | Provisioning status — Real-time progress. Email with credentials. App download links |
**Interactive demo (held loosely):** Single shared VPS with fake business data ("Bella's Bakery"). Prospects chat with AI, watch it operate tools in real-time. Not a video — hands-on experience. One VPS (~€25/mo), session timeouts, rate limiting.
---
## 4. Business Model
### 4.1 Pricing Structure
**Single subscription that scales with server resources. All 28 tools included. Unlimited agents.**
| Tier | Price | VPS Tier | Target | Monthly Cost to LetsBe |
|------|-------|----------|--------|----------------------|
| Lite (hidden) | €29/mo | 4c/8GB | Price-sensitive, 5-8 tools | ~€12.51 |
| Build (default) | €45/mo | 8c/16GB | Small business, 10-15 tools | ~€22.36 |
| Scale | €75/mo | 12c/32GB | Agencies, power users | ~€37.96 |
| Enterprise | €109/mo | 16c/64GB | Full 28-tool stack | ~€60.05 |
**Gross margins:** 45-57% depending on tier (at full token pool consumption; actual margins higher as most users won't exhaust pools). Lite hidden to avoid anchoring; Build/Scale/Enterprise marketed.
**Annual discount:** 15% for upfront annual commitment. Aligns with 12-month Netcup contract pricing.
**AI model tiers:**
- **Included (base subscription):** 5-6 cost-efficient models (DeepSeek V3.2, GPT 5 Nano, GPT 5.2 Mini, GLM 5, MiniMax M2.5, Gemini Flash — final selection pending) with generous monthly token pools. Cover 90%+ of daily usage. No credit card needed beyond subscription.
- **Premium (credit card required):** Top-tier models (Gemini 3.1 Pro, GPT 5.2, Claude Sonnet, Claude Opus) available at per-usage metered rates with sliding markup: 25% on cheap models → 8% on expensive models. Lower markup on expensive models encourages adoption.
- **Founding members:** 2× included token allotment for 12 months ("Double the AI"). First 50-100 customers. Extra cost ~€3-25/mo depending on tier. All tiers remain margin-positive at 2× (Lite 47%, Build 35%, Scale 31%, Enterprise 22%). ~€134/user/year effective CAC.
**Model selection UX:**
- **Basic Settings (no credit card):** Three presets — "Basic Tasks," "Balanced," "Complex Tasks." Non-technical users never see model names.
- **Advanced Settings (credit card required):** Full model catalog. Per-agent model selection. Premium models metered to card.
**Token pool:** Included tokens are monthly budget across all agents. Pool only covers the 5 included models. Premium models always metered separately — never draw from pool. When pool runs out, usage pauses or user opts into overage billing at tiered markup.
**Prompt caching:** SOUL.md and TOOLS.md structured as cacheable prompt prefixes. Cache read prices are 80-99% cheaper than standard input — direct margin multiplier.
> See companion document: **LetsBe_Biz_Pricing_Model.md** (v2.2) for full cost analysis, revenue projections, and unit economics.
### 4.2 Target Customer
**Horizontal with vertical templates.** Not building "LetsBe for restaurants" — building "LetsBe for businesses" with a restaurant template that pre-selects the right tools.
**Lead persona:** Solo founders and freelancers (Sarah). Solo founder who is drowning in 60-hour weeks doing admin, can't afford staff for marketing/IT/scheduling/invoicing, uses 10-12 SaaS tools costing €800/mo. Sees the demo, realizes LetsBe replaces €800/mo in SaaS + 20 hours/week of admin. *"It runs my business."*
**Secondary:** Small agency owners (David). Managing client work across 15 different tools. Needs operational leverage. Each client gets their own LetsBe instance.
**Tertiary:** Privacy-conscious businesses (Dr. Weber). Healthcare, legal, finance in regulated markets. Data sovereignty is non-negotiable. GDPR-compliant on infrastructure they control.
### 4.3 The Moat
The competitive moat builds in layers:
**Layer 1 — Integration depth:** 24+ tool API adapters with cross-tool workflows, error recovery, edge-case handling. Months of compounding engineering work. Each adapter tested against real tool versions with real data — not something you can shortcut.
**Layer 2 — Speed to market:** Being first with a working product. Every week in market is a week of real user feedback, bug fixes, refinement that a competitor starting from zero doesn't have.
**Layer 3 — User accumulated context:** Each user's SOUL.md configurations, agent memories, workflow patterns, brand voice training, client knowledge, operational preferences make their instance uniquely valuable. This isn't data you can export. It's months of accumulated learning the AI team has absorbed through daily use. Switching costs are enormous.
Integration depth creates the initial barrier. Speed to market exploits it. User accumulated context makes it permanent.
---
## 5. Competitive Landscape
### 5.1 Market Position
Nobody combines privacy-first infrastructure + pre-deployed business tools + autonomous AI agents + secrets firewall + cross-tool workflows.
The market breaks into quadrants:
| | **SaaS (cloud)** | **Self-hosted (private)** |
|---|---|---|
| **Workflow automation** | n8n Cloud, Make, Zapier | Activepieces, Dify, Flowise *(Note: n8n is a competitor, not in the LetsBe stack — Sustainable Use License prohibits managed service deployment)* |
| **AI workforce (operates tools)** | OpenAI Frontier, YC startups | **LetsBe (alone here)** |
LetsBe occupies an empty quadrant.
### 5.2 Competitor Analysis
| Competitor | What They Do | How We Differ |
|-----------|-------------|---------------|
| Cloudron / YunoHost | Self-hosted app management | No AI, no cross-tool workflows |
| Coolify | Self-hosted PaaS | Developer tool, not business operations |
| Traditional SaaS | Cloud business tools | No privacy, no AI workforce, fragmented |
| OpenClaw hosting | Managed AI agent hosting | Commodity hosting. No business tools, no secrets firewall |
| Virtual assistants (human) | Manual business operations | Expensive, limited hours, inconsistent, doesn't scale |
| n8n / Make | Workflow automation | Users build flows manually. No pre-deployed tools, no AI execution. *(Note: n8n is NOT in the LetsBe stack — listed here as competitor only)* |
| OpenAI Frontier | Enterprise AI agents | Enterprise-only, SaaS, expensive, not privacy-first |
---
## 6. Where We Are Today
### 6.1 Architectural Foundation
The Technical Architecture v1.1 document defines the complete system:
- **OpenClaw** (upstream dependency, not fork) runs the AI agents on each customer's VPS
- **Safety Wrapper** (Node.js) provides secrets redaction, command gating, Hub communication
- **Tool adapters** (24+ adapters) expose business tool APIs to agents
- **Local storage** (SQLite) for all on-server state — no per-tenant database
- **Total LetsBe overhead:** ~640MB RAM per tenant (down from ~1.5GB+ in earlier designs)
Key architectural decisions:
- OpenClaw treated as upstream dependency, not a fork (AD #1)
- Safety Wrapper is Node.js, not Python (AD #11)
- Orchestrator and Sysadmin Agent deprecated — capabilities absorbed into OpenClaw + Safety Wrapper (AD #3, #4)
- MCP Browser deprecated — replaced by OpenClaw native browser tool (AD #14)
- Five-tier command gating (Green/Yellow/Yellow+External/Red/Critical Red) with external comms gate independent of autonomy levels (AD #30)
- Dispatcher Agent is first-class default component (AD #31)
- Dynamic tool installation from curated catalog (AD #32)
- Two-tier model strategy: 3 included presets + premium pay-as-you-go (AD #33)
- Threshold-based sliding markup (AD #35)
- Founding member 2× token program (AD #34)
### 6.2 Component Status
| Component | Status | Role |
|-----------|--------|------|
| Hub (Next.js) | Functional | Central control plane, customer portal, billing, provisioning, monitoring |
| Provisioner (Bash) | Functional | One-shot server provisioning via Ansible |
| OpenClaw | Ready (upstream) | On-server AI agent runtime |
| Safety Wrapper | Ready to build | Secrets redaction, command gating, Hub communication |
| Tool adapters | Ready to parallelize | 24+ tool API adapters |
| Mobile app (React Native) | Ready to build | Primary client interface |
| Secrets registry | Ready to build | Encrypted SQLite vault for credentials |
| Autonomy level system | Ready to build | Per-agent, per-tenant gating configuration |
| External comms gate | Ready to build | Independent unlock mechanism per agent/tool |
### 6.3 What Needs Build (Critical Path)
**Tier 1 — Must build before launch:**
1. Safety Wrapper (secrets redaction, command classification, Hub communication)
2. Tool API adapters (24+ adapters, parallelizable)
3. Mobile app (React Native, iOS + Android)
4. Secrets registry (SQLite, encrypted)
5. Autonomy level system (per-agent gating, approval queue)
6. External comms gate (unlock mechanism)
7. Hub updates (customer portal API, token metering, agent management)
8. Command approval queue (Yellow/Red commands surface via app)
9. New letsbe.biz website + onboarding flow
10. Prompt caching architecture (SOUL.md + TOOLS.md as cacheable prefixes)
**Tier 2 — Important but can follow launch:**
1. Analytics dashboard (agent activity, token usage, cost tracking)
2. Telegram/WhatsApp fallback channel adapters
3. Direct API fallback (Anthropic, Google, DeepSeek) for OpenRouter outages
4. Interactive demo sandbox ("Bella's Bakery")
**Tier 3 — Roadmap (v2+):**
1. Data migration from Google Workspace / M365 (IMAP, CalDAV, WebDAV)
2. Workflow template marketplace
3. White-label / agency multi-tenant mode
4. User-created custom tool adapters
5. Community skills marketplace
---
## 7. Go-to-Market Strategy
### 7.1 Launch: Founding Member Program
Target 50-100 founding members in first 6 months.
**Why founding members:**
- Direct feedback on core product from real users
- Real usage data to optimize infrastructure, AI behavior, pricing
- Community evangelists who become reference customers
- Exclusive positioning creates urgency and prestige
**Founding member benefits:**
- 2× included AI token allotment for 12 months ("Double the AI")
- Direct access to founder for product feedback
- Early influence on product direction
- Public acknowledgment as early adopter (if desired)
- Lifetime 10% discount on future upgrades (optional)
### 7.2 Channels
- **Content marketing:** Blog posts on privacy-first AI, comparisons with SaaS stacks, tutorials on autonomous AI for SMBs. SEO play for long-term organic discovery.
- **Self-hosted communities:** Reddit (r/selfhosted, r/homelab, r/smallbusiness), Hacker News, privacy forums. These audiences already value self-hosting.
- **Social media:** Short videos showing "oh shit" moments — AI sending a newsletter, scheduling a meeting, fixing a server issue in 60 seconds. Target self-hosted communities, solo founder forums.
- **Google Ads:** Targeted keywords — "self-hosted business tools," "AI business assistant," "private business software," "alternative to [SaaS tools]." Low volume but high intent.
- **Interactive demo:** Hands-on sandbox (Bella's Bakery) where prospects chat with AI, watch it operate real tools in real-time.
- **Network:** Early introductions via advisory network, founder communities, privacy advocates.
### 7.3 Growth Strategy (Year 2+)
Horizontal with vertical depth. Build best-in-class experience for solo founders first. Secondary verticals emerge naturally from usage patterns. Expand upmarket to 50-200 person teams with multi-department AI workforces, advanced RBAC, dedicated support.
---
## 8. Three-Year Vision
### 8.1 Year 1: Prove the Model
Launch with founding member program. 50-100 customers using the full product. Validate the core value proposition: that an AI workforce on private infrastructure genuinely saves time, unlocks capabilities, and replaces costs.
**Success metrics:**
- Founding members measurably get 10+ hours/week back
- Multiple SaaS subscriptions cancelled per customer
- Retention rate above 90% after 3 months
- NPS > 50
### 8.2 Year 2: Scale and Deepen
Hundreds of customers. Self-service signup to AI team ready in under 30 minutes. Deep vertical templates for top-performing business types. Mobile app polished and feature-complete.
**New capabilities:** Data migration tools, more messaging channels, community-contributed agent skills, white-label option for agencies.
**Success metrics:** Self-serve pipeline working, month-over-month growth, positive unit economics including AI token costs.
### 8.3 Year 3: Platform
LetsBe becomes the operating system for small businesses. Marketplace of tools, skills, templates creates network effects. Supports third-party tool integrations (user-created adapters), opening ecosystem beyond core 28 tools.
**Expansion paths (choose based on traction):**
- **Vertical depth:** Specialized compliance and tooling for regulated industries (healthcare, legal, finance)
- **Upmarket:** Larger teams (50-200 employees) with multi-department AI workforces
- **Geographic:** Multi-region infrastructure (beyond EU)
- **Partner channel:** MSPs and IT consultancies reselling LetsBe to their client base
**Success metrics:** Platform effects visible, community contributing templates and skills, third-party integrations being adopted.
---
## 9. Technical Architecture Summary
**For complete technical details, see LetsBe_Biz_Technical_Architecture.md v1.1.**
### 9.1 System Overview
```
[Mobile App] ←→ [Hub (Relay/Proxy)] ←→ [Tenant VPS]
↓
[OpenClaw
Gateway]
↓
[Safety Wrapper]
├─ Secrets Redaction
├─ Command Gating
├─ Tool Adapters
└─ Hub Communication
↓
[Business Tools
(30 Docker
services)]
```
### 9.2 Key Principles
1. **Secrets never leave the server.** All credential redaction happens locally before any data reaches an LLM. Enforced at transport layer, not by trusting the AI.
2. **The AI acts autonomously within guardrails.** Non-destructive operations execute immediately. Destructive operations require human approval. The boundary is enforced by code the AI cannot modify.
3. **OpenClaw stays vanilla.** No fork. All LetsBe-specific logic lives in the Safety Wrapper. Clean separation enables pulling upstream updates without conflicts.
4. **Four layers of defense.** Security is not one wall — it's four independent layers (Sandbox → Tool Policy → Command Gating → Secrets Redaction), each enforced separately, each unable to be bypassed.
### 9.3 Per-Tenant Infrastructure
Each customer VPS runs:
| Component | Language | RAM | Role |
|-----------|----------|-----|------|
| OpenClaw Gateway | Node.js 22+ | ~512MB | AI agent runtime, conversation management |
| Safety Wrapper | Node.js | ~64MB | Secrets redaction, command gating, Hub comms |
| 28+ tool containers | Various | Varies | Nextcloud, Chatwoot, Ghost, Odoo, etc. |
| Nginx reverse proxy | - | ~64MB | HTTPS, routing, rate limiting |
| **Total LetsBe overhead** | - | **~640MB** | (Down from ~1.5GB+ in earlier designs) |
### 9.4 API Layer
Tool adapters expose 200+ operations across 24+ business tools. OpenClaw agents invoke adapters via standardized function-call interface. Secrets Wrapper injects credentials and enforces gating. Results returned sanitized and redacted.
---
## 10. Decisions Log (Critical Decisions)
| # | Decision | Rationale |
|---|----------|-----------|
| 1 | OpenClaw as upstream dependency, not fork | MIT license allows divergence; clean separation enables pulling updates |
| 3 | Orchestrator deprecated | Capabilities absorbed by OpenClaw + Safety Wrapper |
| 4 | Sysadmin Agent deprecated | Capabilities ported as Safety Wrapper tools; process separation doesn't add meaningful security |
| 5 | No per-tenant PostgreSQL — SQLite for all on-server state | Saves ~256MB RAM per tenant |
| 11 | Safety Wrapper is Node.js, not Python | Consistency with OpenClaw (Node.js), lighter footprint |
| 12 | Hybrid plugin model for tool adapters | Adapters registered as OpenClaw plugins; secrets redaction in separate process |
| 13 | OpenClaw hooks for security integration | `message:received`, `tool_result_persist`, `gateway:startup`, `agent:bootstrap` |
| 14 | MCP Browser deprecated — replaced by OpenClaw native browser | Native browser saves ~256MB RAM, more capable (CDP + Playwright) |
| 17 | Three autonomy levels (Training Wheels, Trusted Assistant, Full Autonomy) | Pragmatic balance between safety and user autonomy |
| 18 | One customer = one VPS, permanently | Simplifies infrastructure, security isolation, customization |
| 22 | Four-layer access control (Sandbox, Tool Policy, Command Gating, Secrets Redaction) | Defense in depth; each layer independent |
| 25 | OpenAI-compatible API locked down, not exposed | Internal only; prevents external API access |
| 26 | Web search/fetch via OpenClaw native tools | Simpler than sidecar service |
| 29 | User customization enabled (SOUL.md modification, custom agents, custom skills) | Users are experts in their domain; enable depth |
| 30 | External Communications Gate independent of autonomy levels | Product principle: misworded email worse than delayed newsletter |
| 31 | Dispatcher Agent is first-class default component | Primary user contact point; routes intent; coordinates workflows |
| 32 | Dynamic tool installation from curated catalog | Powerful user capability; safety maintained via catalog, resource checks, gating |
| 33 | Two-tier model strategy: 3 included presets + premium pay-as-you-go | Simple UX (Basic mode) for non-technical users; power users unlock Advanced |
| 34 | Founding member 2× token program ("Double the AI") | Marketing lever; 12 months for first 50-100 customers; all tiers margin-positive |
| 35 | Threshold-based sliding markup (25% cheap → 8% expensive) | Fairness; don't penalize power users; still profitable on cheap models |
| 38 | Netcup primary, Hetzner overflow | Best price-per-core in Europe; domain reselling; provider-agnostic architecture |
| 39 | Infrastructure provider positioning — LetsBe hosts, customer owns license | LetsBe is an infrastructure and AI orchestration provider, not a software vendor. Every open-source tool runs under its upstream license on the customer's dedicated server. Customers have full SSH access and all credentials. If a customer wants enterprise features (e.g., Stalwart Enterprise, Rocket.Chat Enterprise), they purchase the license directly from the vendor — we help deploy it. This framing is legally protective (AGPL/open-core compliant), competitively differentiating (transparency as trust), and reinforces the "your server, your data" message. |
| 40 | Public open-source tools page on website | Dedicated page listing every deployed tool with name, role, upstream link, and license type. Reinforces infrastructure-provider positioning, earns open-source community goodwill, generates backlink SEO value, and differentiates against opaque SaaS bundlers. Tool Catalog v2.2 is the source of truth. |
| 41 | BYOK (Bring Your Own API Key) deferred to post-launch | Architect the AI orchestration layer for provider-agnostic key injection from day one, but don't ship BYOK at launch. Rationale: early-stage support burden (misconfigured keys, rate limits, model compatibility issues) outweighs community goodwill gains. Launch BYOK as a Pro/Developer tier feature once the managed experience is stable and support load is predictable. BYOK users pay the same platform fee (margin is higher since we don't eat API costs). Protects core margins while keeping the door open for power users and self-hosting community. |
See Technical Architecture v1.1 for complete decision log (45+ decisions on technical specifics).
---
## 11. Open Questions (Product/UX Only)
Technical questions (Architecture Design Decisions) are resolved in Technical Architecture v1.1. Remaining product questions:
1. **Interactive demo UX spec** — Fake business data set, session management, rate limiting, abuse prevention. Decision held loosely — implementation can proceed without this.
2. **Agent personality customization depth** — How much guidance vs. freeform SOUL.md editing in Basic mode? User research needed post-launch.
---
## 12. Document Lineage
| Version | Date | Key Changes |
|---------|------|-------------|
| 0.1–0.7 | Feb 24-25, 2026 | Foundation Document evolution: problem definition, tool stack, AI workforce vision, subagent architecture, tool API layer, secrets firewall, command gating, pricing, competitive landscape. 63 cumulative decisions. |
| 1.0 | Feb 25, 2026 | **Complete rewrite.** Synthesized from Technical Architecture v1.1 (45+ technical decisions) and Product Vision v1.0 (customer journey, principles, vision validation). Removed outdated references (Python/FastAPI/Orchestrator/Sysadmin/MCP Browser). Updated to reflect: OpenClaw as upstream dependency, Node.js Safety Wrapper, five-tier command gating, external comms gate, Dispatcher Agent, dynamic tool installation, two-tier model strategy, sliding markup, founding member program. Preserved all business decisions, pricing model, VPS strategy, tool selection, competitive analysis, moat definition. Restructured for clarity: Who We Are, Problem, What We're Building (6 subsections), Business Model, Competitive Landscape, Where We Are Today, Technical Summary, Go-to-Market, Three-Year Vision, Decisions Log. |
| 1.1 | Feb 26, 2026 | **Tool stack + strategic updates.** Updated tool stack from 30 → 28 tools (Stalwart Mail replaces Poste.io; Windmill, Typebot, Twenty, Akaunting, Budibase, Invoice Ninja removed — see Tool Catalog v2.2). Added decisions #39-41: infrastructure provider positioning (hosting model + customer license ownership), public open-source tools page, BYOK deferred to post-launch. Updated bundle examples (Poste → Stalwart Mail, 30 → 28). |
---
## 13. Companion Documents
This Foundation Document references three companion documents for deeper dives:
| Document | Version | Purpose |
|----------|---------|---------|
| **LetsBe_Biz_Technical_Architecture.md** | 1.1 | Complete technical specification: system overview, component details, architectural decisions, access control model, autonomy levels, tool adapters, skills system, memory architecture, inter-agent communication, provisioning pipeline. The "how it works" document. |
| **LetsBe_Biz_Product_Vision.md** | 1.0 | North star document: one-liner, customer personas, product principles, customer journey (discovery through 3 months), business strategy, competitive position, moat analysis, three-year vision, vision validation checklist. The "why and what experience" document. |
| **LetsBe_Biz_Pricing_Model.md** | 2.2 | Detailed cost analysis and revenue modeling: per-tier cost breakdown, AI token cost modeling, founding member program impact, server pool economics, unit economics, sensitivity analysis, cash flow projections. The "financial details" document. |
---
## 14. Next Steps (Immediate)
### 14.1 Technical Builds (Critical Path)
1. **Safety Wrapper** — Secrets redaction (4 layers), command classification (5 tiers), Hub communication endpoints
2. **Tool adapters (24+)** — Base framework, then parallelize all adapters
3. **Mobile app** — React Native, iOS + Android, chat interface, agent team management, approval queue
4. **Secrets registry** — SQLite with encryption, rotation support, audit logging
5. **Autonomy level system** — Per-agent, per-tenant gating configuration, approval request routing
### 14.2 Hub & Platform
6. **Hub updates** — Customer portal API, token metering, agent management, command approval endpoints
7. **Website redesign** — AI-powered onboarding (business type classification, tool recommendation, server selection, payment)
8. **Provisioner updates** — Deploy OpenClaw + Safety Wrapper instead of deprecated components, migrate Playwright scenarios
### 14.3 Go-to-Market
9. **Founding member recruiting** — Target: 50-100 customers in first 6 months
10. **Interactive demo** — Bella's Bakery sandbox (single VPS, fake data, session management)
11. **Content marketing** — Blog, videos, SEO strategy
12. **Community presence** — r/selfhosted, r/homelab, Hacker News, privacy forums
---
## 15. Success Criteria
**For v1 launch:**
- Founding members can sign up, provision server, deploy all 28 tools, configure agents, send first command via app within 30 minutes
- AI workforce operates without human intervention for non-destructive tasks (Green tier)
- All external communications gated by default — user approves first email, then can unlock per agent/tool
- Secrets never visible in logs, transcripts, or LLM requests
- Mobile app supports chat, approvals, team management, usage dashboard
- No critical security breaches in founding member usage
**By month 3:**
- Founding members report 10+ hours/week time savings
- 80%+ retention rate
- Multiple SaaS subscriptions cancelled per customer
- NPS > 50
- Product feedback informs v2 roadmap (vertical templates, advanced customization, mobile polish)
---
This document represents the current state of LetsBe Biz strategy and architecture as of February 25, 2026. It is a living document — updates will be reflected in versioning and document lineage.
For questions or clarifications, refer to companion documents or consult the architecture and product teams.

348
docs/strategy/LetsBe_Biz_Product_Vision.md Normal file
View File

@@ -0,0 +1,348 @@
# LetsBe Biz — Product Vision
**Date:** February 25, 2026
**Author:** Matt (Founder)
**Status:** Version 1.1
**Purpose:** North star document. Every technical decision, feature, and priority is tested against this vision. If the architecture doesn't deliver this experience, the architecture changes.
---
## 1. The One-Liner
**LetsBe gives every small business their own private AI team that runs the business while the owner focuses on what they're actually good at.**
Not AI-assisted tools. Not a chatbot. Not a workflow builder. A team of AI employees that operate 25+ business tools autonomously — on a server the business owns, with data that never leaves their control.
**Tagline:** "Where power meets privacy."
---
## 2. The Problem
Small business owners are drowning. They're running their entire operation across 10-30 SaaS tools — each with its own subscription, login, data silo, and terms of service. They're the marketer, the IT person, the bookkeeper, the scheduler, and the salesperson. They work 60-hour weeks doing admin work instead of the thing they're actually good at.
Even the ones who've consolidated onto self-hosted tools still need someone to operate them. Configure the CRM. Send the newsletter. Manage the calendar. Process the invoices. Handle the IT issues. That's either expensive human labor or deep technical knowledge most owners don't have.
The current landscape forces a choice: powerful but fragmented (SaaS), private but complex (self-hosted), or AI-powered but not private (cloud AI). No one offers all three.
**What we replace:**
- 10-30 SaaS subscriptions (€500-2,000/mo)
- A part-time virtual assistant (€1,500-3,000/mo)
- An occasional IT contractor (€100-200/hr)
- All with better privacy, better consistency, and 24/7 availability
---
## 3. The Vision
### 3.1 What It Feels Like
When someone describes LetsBe to a friend, they say: **"It runs my business."**
Not "I have a cool AI tool" or "I use self-hosted software." They say: "I tell my AI team what I need and it handles everything. Marketing, IT, scheduling, invoicing, customer conversations — all of it. On my own server. And it never sleeps."
The experience is closer to having employees than using software. You don't configure workflows or build automations. You talk to your team. "Send the monthly newsletter with our best content." "Follow up with everyone from last week's demo." "Why is the website slow?" The AI team figures out the how — which tools to use, in what order, with what data — and does it.
### 3.2 The Proactive Team
LetsBe doesn't wait to be asked. The AI team is proactive by default — within the boundaries the user sets.
**What proactive looks like:**
- Morning briefing: "Here's what happened overnight. Your IT Agent restarted Nextcloud after a memory spike at 3am. Your Sales Agent qualified 2 new leads from Chatwoot. Your Secretary scheduled 3 meetings for this week. Here's what needs your attention today."
- The Marketing Agent notices blog traffic dropped 30% this week, investigates via Umami, identifies the underperforming posts, and drafts a recovery plan — without being asked.
- The IT Agent detects a certificate expiring in 7 days, renews it, and reports what it did.
- The Secretary sees a new Cal.com booking, checks for conflicts, sends a confirmation email with the meeting link, and adds a reminder.
**The user steers. The AI does.** Over time, as trust builds, the user increases autonomy levels and the AI team operates more independently. The product gets more valuable the longer you use it.
### 3.3 On-Demand When Needed
Alongside the proactive behavior, users can talk to any agent at any time:
- "Draft a proposal for the Acme deal" — Sales Agent pulls deal details from Odoo, AI drafts the proposal, creates a signable document in Documenso, sends to the client via Stalwart Mail.
- "Clean up old files on Nextcloud and tell me how much space I freed" — IT Agent handles it, reports back.
- "What were our top-performing blog posts this month?" — Marketing Agent queries Ghost + Umami, synthesizes the answer.
The interaction is natural language via the mobile app, or via WhatsApp/Telegram for people who prefer to stay in their existing messaging apps.
### 3.4 The "Oh Shit" Moments
The product sells itself through moments of surprise — when the user discovers the AI team can do something they didn't expect:
- "Can you monitor my website uptime and text me if it goes down?" → It already is.
- "Can you send invoices to my clients every month?" → Yes. It pulls data from Odoo, generates the invoice, and emails it.
- "Can you figure out why my email deliverability dropped?" → IT Agent checks DNS records, SPF/DKIM config, Stalwart logs, and reports back with a fix.
- "Can you create a weekly social media calendar based on my blog content?" → Marketing Agent reads Ghost, analyzes what performed well via Umami, drafts a week of posts in the user's brand voice.
These moments create the stickiness. Each one deepens trust, increases autonomy, and makes the product harder to leave.
---
## 4. Customer Personas
### 4.1 Lead Persona: The Solo Founder
**Name:** Sarah. Runs a consulting firm. 1 person, maybe a part-time VA.
**Her day:** She's good at consulting. But she spends 60% of her time on admin: scheduling meetings, sending follow-up emails, managing her website, creating invoices, handling IT issues when something breaks, posting on social media when she remembers to. She uses 12 different SaaS tools and pays €800/mo for them. She knows she's underinvesting in marketing but can't afford to hire someone.
**Her pain:** "I'm doing the work of 5 people and none of it well. I can't afford a marketing person, an IT person, and a VA. But I'm drowning without them."
**What LetsBe gives her:** A full team for less than she pays for her current SaaS stack. Marketing Agent handles her newsletter, blog, and social. Secretary handles her calendar, email triage, and follow-ups. IT Agent keeps everything running. Sales Agent qualifies leads and manages her pipeline. She focuses on consulting — the thing she's actually good at.
**What makes her say "take my money":** The demo. She watches the AI send a newsletter using content from her blog, check her site's uptime, and schedule a meeting — all in 3 minutes. She realizes this replaces €800/mo in SaaS + 20 hours/week of admin.
### 4.2 Secondary: The Agency Owner
**Name:** David. Runs a digital marketing agency. 8 employees, 12 clients.
**His pain:** He manages client work across 15 different tools. Each client has their own stack. He needs operational leverage — not another tool, but something that handles the operational overhead so his team can focus on client deliverables.
**What LetsBe gives him:** Each client gets their own LetsBe instance (or he uses one powerful instance). The AI team handles cross-client operations: scheduling, reporting, content distribution, IT maintenance. His human team focuses on strategy and creative work.
### 4.3 Tertiary: The Privacy-Conscious Business
**Name:** Dr. Weber. Runs a small medical practice in Germany.
**His pain:** GDPR means he can't use most cloud tools for patient-adjacent data. He needs scheduling, email, file storage, and basic CRM — but on infrastructure he controls. He has zero IT knowledge.
**What LetsBe gives him:** Everything on his own server, in a German data center, with secrets that never leave the machine. The AI team handles the IT complexity he can't. He talks to it like he'd talk to an office manager.
---
## 5. Product Principles
These are non-negotiable. Every feature and decision is tested against them.
### 5.1 Secrets Never Leave the Server
Infrastructure credentials — passwords, API keys, tokens, certificates — are redacted before any data reaches an AI model. The AI reasons about which credentials are relevant without seeing the values. This is enforced at the transport layer, not by trusting the AI to behave. It cannot be turned off.
User-entered data (messages, business content) flows to AI models transparently. We protect system secrets, not user choices.
### 5.2 Simple by Default, Powerful When Unlocked
Any person — regardless of technical skill — can use LetsBe on day one. The default experience is clean, guided, and jargon-free. No one sees markdown files, config schemas, or model names unless they go looking.
Power users who want deeper control can unlock advanced settings: per-agent model selection, autonomy level tuning, custom agent creation, raw configuration editing. This requires a credit card (for metered premium model usage) and signals the user understands what they're doing.
Two layers of simplicity:
- **Basic mode:** Three model presets ("Basic Tasks," "Balanced," "Complex Tasks"). Autonomy toggles with plain-English descriptions. Agent personality set via guided questions, not file editing.
- **Advanced mode (credit card required):** Full model catalog. Per-agent configuration. Direct SOUL.md editing. Custom agents. Unlocked autonomy options. Premium AI models with per-usage billing.
### 5.3 External Communications Are Gated by Default
The AI team operates business tools autonomously for internal operations — reading data, generating reports, managing infrastructure, organizing files, analyzing performance.
But any action that sends information to someone outside the business — emails to clients, published blog posts, sent newsletters, campaign dispatches — is gated by default. The user sees what the AI prepared and approves it with one tap.
Users can explicitly unlock autonomous sending per agent or per tool after they've built trust. This is a deliberate opt-in, not an autonomy level side effect. Even at the highest autonomy level, external comms start gated until the user unlocks them.
**Rationale:** A misworded email to a client is worse than a delayed newsletter. We err on the side of protecting the user's relationships.
### 5.4 Destructive Actions Always Require Confirmation
Deleting data, dropping databases, modifying firewall rules, revoking access — these are gated at every autonomy level, for every agent. No exceptions. One-tap approval in the app, with a clear description of what the AI wants to do and why.
### 5.5 The Product Gets More Valuable Over Time
Every interaction teaches the AI team something: the user's preferences, their brand voice, their client relationships, how they like meetings scheduled, which content performs well for their audience. Over time, the AI team becomes uniquely tailored to that business. This accumulated context is the deepest form of product value — and the strongest retention mechanism.
### 5.6 All Tools Included, Always
No per-tool pricing. No feature gating behind tiers. Every subscription includes the full suite of 28 business tools. Price scales with server resources (more tools need more horsepower), not with feature access. This keeps the value proposition clean: one subscription, everything included.
---
## 6. The Customer Journey
### 6.1 Discovery → Signup
The website tells the story: "Your AI team is ready. Tell us about your business."
1. **Landing page:** A chat input — "Describe your business." Hero messaging about the AI workforce. Not a feature list — a vision of what changes when you have an AI team.
2. **AI conversation (1-2 messages):** Gemini Flash (cheap, fast) classifies the business type from a natural-language description. "I run a freelance design studio" → Freelancer bundle.
3. **Tool recommendation:** Card-based UI with business type bundle pre-selected. Full catalog visible with toggles. Live resource calculator shows required server specs.
4. **Server selection:** Only tiers that meet the resource requirement are shown. The cheapest visible option is the right option. No underpowered choices.
5. **Domain setup:** User brings their domain or buys one (Netcup domain reselling). Each tool gets a subdomain (crm.yourdomain.com, mail.yourdomain.com).
6. **Agent configuration (optional, skippable):** Template-based per business type. "What's your brand voice?" "How do you like meetings scheduled?" Quick personality setup for each agent. Can be done later.
7. **Payment:** Stripe. Pay first, then provision.
8. **Provisioning:** Status page showing real-time progress. "Installing your tools... Configuring your AI team... Almost ready..." Email with credentials and app download links.
### 6.2 The First Hour
The user opens the app and their AI team is waiting.
**Quick wins based on business type:** The system suggests 2-3 immediate actions tailored to the user's setup — "Want me to set up your email accounts?" "I can check if your website is loading properly." "Let me import your calendar." These are low-risk, high-visibility wins that demonstrate the AI team's capability immediately.
After the quick wins, the user explores freely. They chat with agents, test capabilities, and start building trust. The early experience is designed to produce "oh shit" moments — the user discovers the AI can do things they didn't expect, and the relationship deepens.
### 6.3 First Week
The AI team is learning the business. The user has had several conversations, approved a few actions, and started to see the daily briefings. Key milestones:
- At least one agent has performed a useful autonomous action (IT Agent fixed something, Secretary scheduled a meeting)
- User has sent at least one message via WhatsApp/Telegram to their AI team
- The morning briefing has shown something the user didn't know (a failed backup, a trending blog post, a new lead)
- User has increased at least one agent's autonomy level from Training Wheels to Trusted Assistant
### 6.4 First Month
The AI team is part of daily operations. The user checks the morning briefing like they'd check email. They've built workflows they rely on — weekly newsletter, monthly invoicing, daily analytics checks. They've customized at least one SOUL.md (via the friendly UI). The AI team knows their brand voice, their scheduling preferences, their key clients.
**This is where switching costs kick in.** The configured, trained, personalized AI team is now uniquely valuable to this specific business.
### 6.5 Three Months
The trifecta is realized:
- **Time saved:** 10-20 hours/week of admin work is now handled by the AI team. The user spends their time on high-value work.
- **Capabilities unlocked:** The user is doing things they couldn't before — running analytics, sending professional newsletters, managing a CRM, monitoring infrastructure — because the AI handles the complexity.
- **Cost replaced:** 5-10 SaaS subscriptions cancelled. The VA contract isn't renewed. LetsBe replaced €500-2,000/mo of fragmented spend with a single subscription.
---
## 7. What LetsBe Is Not
Clarity on boundaries prevents scope creep and misaligned expectations.
- **Not a workflow builder.** Users don't drag and drop automations. They talk to their AI team in natural language. The AI figures out the workflow.
- **Not a chatbot.** The AI team doesn't just answer questions — it does things. It operates tools, manages infrastructure, sends emails, processes data.
- **Not a raw hosting service.** We don't sell VPS access or server management as standalone products. The infrastructure exists to power the AI workforce. Legally, we're an infrastructure provider — we deploy open-source tools under their upstream licenses on servers customers own. But the *experience* is talking to your AI team, not SSH-ing into a box. Users who want server access have it (full SSH, all credentials), but most never need it.
- **Not for enterprises (yet).** V1 is built for businesses with 1-50 people. Larger organizations have different needs (compliance, multi-department, SSO across hundreds of users) that we'll address later.
- **Not a replacement for human judgment.** The AI team handles operations and execution. Strategic decisions, client relationships, and creative direction stay with the human. The AI amplifies the human, it doesn't replace them.
---
## 8. Business Strategy
### 8.1 Pricing Philosophy
**Simple, all-inclusive, scales with resources.**
One subscription. All 28 tools included. Unlimited agents. Price scales with server tier (more tools need more horsepower). AI token usage has a generous included pool with the base models. Premium models and overage are metered separately.
| Tier | Price | Target | Includes |
|------|-------|--------|----------|
| Lite (hidden) | €29/mo | Price-sensitive, few tools | 4 vCPU, 8GB RAM, all tools, included AI pool (~8M tokens) |
| Build | €45/mo | Default marketed tier | 8 vCPU, 16GB RAM, all tools, included AI pool (~15M tokens) |
| Scale | €75/mo | Agencies, power users | 12 vCPU, 32GB RAM, all tools, included AI pool (~25M tokens) |
| Enterprise | €109/mo | Full 28-tool stack | 16 vCPU, 64GB RAM, all tools, included AI pool (~40M tokens) |
**AI model tiers:**
- **Included (base subscription):** 5-6 cost-efficient models with generous monthly token pools. Cover 90%+ of daily usage. No credit card needed beyond the subscription.
- **Premium (credit card required):** Top-tier models (Claude Sonnet, Claude Opus, GPT 5.2, Gemini 3.1 Pro) available at per-usage metered rates with sliding markup (8-25% — lower on expensive models to encourage adoption).
- **Founding members:** 2× included token allotment for 12 months ("Double the AI"). First 50-100 customers.
**Performance Guarantee upgrade:** Dedicated CPU cores (+€5-50/mo) for customers who need guaranteed performance under load.
### 8.2 Target Market
**Horizontal with vertical templates.** We don't build "LetsBe for restaurants" — we build "LetsBe for businesses" with a restaurant template that pre-selects the right tools and pre-configures the agent personalities. Market broadly, give each vertical a tailored first experience through business type bundles in onboarding.
**Lead persona:** Solo founders and freelancers (Sarah). Broadest market, most relatable pain, easiest messaging. "Your AI team so you can focus on what you're good at."
**Secondary:** Small agency owners (David). Higher willingness to pay, deeper operational pain, higher tier selection.
**Tertiary:** Privacy-conscious businesses (Dr. Weber). Strongest differentiation story, clearest competitive positioning in regulated markets.
### 8.3 Go-to-Market: First 50 Founding Members
Multiple channels, high-touch in the early days:
- **Social media marketing:** Content that demonstrates the "oh shit" moments. Short videos showing the AI team in action — "Watch this AI send a newsletter, schedule a meeting, and fix a server issue in 60 seconds." Target self-hosted communities, solo founder forums, and privacy-conscious audiences.
- **Interactive demo (Bella's Bakery):** A live sandbox with fake business data where prospects can chat with the AI team and watch it operate real tools in real-time. Not a video — a hands-on experience. One shared VPS (~€25/mo), session timeouts, rate limiting.
- **Google Ads:** Targeted keywords — "self-hosted business tools," "AI business assistant," "private business software," "alternative to [SaaS tools]." Low volume but high intent.
- **Content marketing:** Blog posts on the privacy-first AI opportunity, comparisons with SaaS stacks, tutorials on what autonomous AI can do for small businesses. SEO play for long-term organic discovery.
- **Self-hosted communities:** Reddit (r/selfhosted, r/homelab, r/smallbusiness), Hacker News, privacy forums. These audiences already value self-hosting — LetsBe adds the AI layer they didn't know they wanted.
- **Founding member program:** 2× token allotment ("Double the AI"), direct access to Matt, early influence on product direction. Positioned as exclusive: "Help shape the product and get double the AI power for a year."
### 8.4 Competitive Position
LetsBe occupies an empty quadrant in the market:
| | **SaaS (cloud)** | **Self-hosted (private)** |
|---|---|---|
| **Workflow automation** | n8n Cloud, Make, Zapier | n8n†, Dify, Flowise |
*† n8n is a competitor only — NOT in the LetsBe stack. Its Sustainable Use License prohibits managed service deployment.*
| **AI workforce (operates tools)** | OpenAI, YC startups | **LetsBe (alone here)** |
No competitor combines: privacy-first infrastructure + pre-deployed business tools + autonomous AI agents + secrets firewall + cross-tool workflows. Each piece exists in isolation elsewhere. The combination is the product.
### 8.5 The Moat
The competitive moat builds in layers, each harder to replicate than the last:
**Layer 1 — Integration depth (engineering barrier):** 24+ tool API adapters with cross-tool workflows, error recovery, edge-case handling, and secrets integration. This is 6+ months of compounding engineering work. A competitor can read the blueprint, but building and testing Odoo's XML-RPC quirks, Chatwoot's webhook timing, and Nextcloud's WebDAV idiosyncrasies only gets solved by doing it. Each adapter is tested against real tool versions with real data — not something you can shortcut.
**Layer 2 — Speed to market (time barrier):** Being first with a working product while competitors are still building. Every week in market is a week of real user feedback, bug fixes, and refinement that a competitor starting from zero doesn't have.
**Layer 3 — User accumulated context (permanent barrier):** Each user's SOUL.md configurations, agent memories, workflow patterns, brand voice training, client knowledge, and operational preferences make their instance uniquely valuable. This isn't data you can export to a competitor. It's months of accumulated learning that the AI team has absorbed through daily use. The longer someone uses LetsBe, the harder it is to leave — not because we lock them in, but because the replacement cost of rebuilding all that context is enormous.
Integration depth creates the initial barrier. Speed to market exploits it. User accumulated context makes it permanent.
---
## 9. Three-Year Vision
### Year 1: Prove the Model
Launch with the founding member program. 50-100 customers using the full product. Validate the core value proposition: that an AI workforce on private infrastructure genuinely saves time, unlocks capabilities, and replaces costs for small businesses. Iterate rapidly based on real usage data. Identify which agent roles, tool integrations, and workflow patterns deliver the most value.
**Success metric:** Founding members are measurably getting 10+ hours/week back and have cancelled multiple SaaS subscriptions. Retention rate above 90% after 3 months.
### Year 2: Scale and Deepen
Grow beyond founding members. Hundreds of customers. The product is self-service — signup to AI team ready in under 30 minutes. Deep vertical templates for the top-performing business types. Community skills marketplace where users share their best agent configurations and workflow templates. Mobile app is polished and feature-complete.
**New capabilities:** Data migration tools (import from Google Workspace, M365), more messaging channels, community-contributed agent skills, white-label option for agencies managing multiple clients, BYOK (Bring Your Own API Key) for advanced users who want to plug in their own AI model keys while using our orchestration layer.
**Success metric:** Self-serve signup-to-value pipeline working. Month-over-month growth. Unit economics are positive including AI token costs.
### Year 3: Platform
LetsBe becomes the operating system for small businesses. The marketplace of tools, skills, and templates creates network effects — each user's contributions make the platform better for everyone. The platform supports third-party tool integrations (user-created adapters), opening the ecosystem beyond the core 28 tools.
**Expansion paths (choose based on traction):**
- **Vertical depth:** Specialized compliance and tooling for regulated industries (healthcare, legal, finance in EU).
- **Upmarket:** Larger teams (50-200 employees) with multi-department AI workforces, advanced RBAC, and dedicated support.
- **Geographic:** Multi-region infrastructure (beyond EU). Local compliance, local data centers, localized agent personalities.
- **Partner channel:** MSPs and IT consultancies reselling LetsBe to their client base. White-label program.
**Success metric:** Platform effects visible — users discovering and installing community skills, templates reducing time-to-value for new customers, third-party integrations being contributed.
---
## 10. Vision Validation Checklist
This checklist is used to test every architectural and product decision:
- [ ] Does this make the product feel like "it runs my business"?
- [ ] Does this serve the solo founder (Sarah) on day one?
- [ ] Is the default experience simple enough for a non-technical user?
- [ ] Does this protect secrets at the transport layer?
- [ ] Are external communications gated by default?
- [ ] Are destructive actions always gated?
- [ ] Does this make the product more valuable over time?
- [ ] Does this deepen the competitive moat?
- [ ] Can a user explain this to a friend without using technical jargon?
- [ ] Would this survive a "can it do this?" → "oh shit, it can" test?
---
## Document Lineage
| Version | Date | Changes |
|---------|------|---------|
| 1.0 | 2026-02-25 | Initial vision document. Synthesized from Foundation Document v0.7 and founder interviews. Product experience, customer personas, principles, customer journey, business strategy, 3-year roadmap, validation checklist. |
| 1.1 | 2026-02-26 | Updated tool counts (30 → 28), Poste → Stalwart Mail references. Added BYOK to Year 2 roadmap. Clarified infrastructure-provider positioning in "What LetsBe Is Not." |
---
*This document is the north star. The Technical Architecture, Foundation Document, and all future specs are measured against this vision. If they don't deliver this experience, they change.*