Engagement Proposal — Sample Bakery
The client-facing proposal: how the operating partner comes in and runs a 3-month engagement to turn Sample Bakery into an agentic operation. This is the source for the proposal page on the website (
web/). Facts come fromoverview.yaml; commercials and named numbers are marked<...>until set.
Parties
- Operating partner:
<Operating Partner — your LLC> - Business: Sample Bakery (
overview.yaml)
1. The situation
Sample Bakery sells well to walk-ins but loses almost every online lead. WhatsApp and Instagram messages are answered by hand, only in shop hours; the website does not take orders. The owner has no time to chase inquiries, so they go cold.
2. What we bring — everything, installed and run
A turnkey agentic operation. For the engagement, the operating partner provides and runs all of it as one package:
- The AI customer-service agent across WhatsApp, Instagram, Telegram, and the website — 24/7, in English, Russian, and Kazakh.
- Channel integration & provisioning — the slow, fiddly Meta/Telegram setup.
- All subscriptions, bundled — model/API usage, hosting, channel APIs. One line item for the bakery, not ten accounts to manage.
- The owner admin — a Telegram Mini App: approve orders, manage the catalog, see daily reports. Mobile-first.
- A lightweight internal ops tool — tasks and a partnership CRM: a very light ERP for running the cake business, not a heavy system.
- Setup, tuning, and support — the agent is tuned against real conversations every week.
The owner provides the bakery, the catalog and pricing, and fulfilment. The operating partner puts in the connections and the payments to get it scaling.
3. The engagement — 3 months
| Month | Focus | Done when |
|---|---|---|
| 1 — Set up | Provision WhatsApp / Instagram / Telegram; catalog online; agent tuned; admin Mini App in the owner's hands | A real customer order completes end-to-end |
| 2 — Optimize | Marketing on the live channels; faster ordering; grow volume; weekly KPI tuning | Online orders are a steady, growing share |
| 3 — Scale & decide | Measure against goals; harden what works; decide the path beyond the engagement | Goals reviewed; a decision on Section 6 |
4. Goals & scale
Set jointly at kick-off and tracked in kpis.yaml:
- 24/7 response under 60 seconds on every channel.
<N>orders/week captured online by month 3 (target: ≥ 40% of all orders).- A clear, repeatable operating loop the owner runs in minutes a day.
- Scale target beyond the engagement:
<...>.
5. Commercials
- Covered by the operating partner during the engagement: all subscriptions, hosting, setup, and tuning.
- Engagement fee / model:
<...>. - Who pays for what after month 3:
<...>.
6. The bigger picture — open for discussion
Two paths beyond the engagement, to be decided together:
- Scale Sample Bakery's own brand — keep growing the bakery as an independent business on the platform.
- Partner with Happy Cake (Houston) — pursue a partnership or funding route with an established player, using Sample Bakery as the proven model.
Both are live options; the month-3 review is where the call gets made.
7. Next steps
- Confirm scope and commercials (Sections 4–5).
- Kick-off: set goals and scale targets in
kpis.yaml. - Start channel provisioning on day 1 — Meta review has lead time.
Related: business-plan.md · operating-model.md · kpis.yaml ·
../../../docs/3-business/ (the platform-level business & partnership docs)