9.1 KiB
LetsBe Biz — Case Study Template
Version: 1.0 Date: February 26, 2026 Purpose: Template for documenting founding member success stories for use in sales, marketing, and investor conversations Companion docs: Objection Handling Guide v1.0, Founding Member Program v1.0, GTM Strategy v1.0
How to Use This Template
Case studies are collected from founding members — ideally at 30 days, 60 days, and 90 days after signup. A great case study answers three questions a prospective customer is actually asking:
- Is this person like me? (profile — who they are, what they do)
- Was the pain real? (problem — the before state, in their words)
- Did it actually work? (results — specific, quantified, honest)
Interview format: 20-30 minute conversation (not a survey). Record it if the customer consents. Extract the quotes yourself — don't ask customers to write quotes for you.
Output format: One page max for the shareable version. The full version (this template, completed) lives in docs/sales/case-studies/ for internal reference.
Part 1: Customer Profile
Fill in after onboarding call. Update at each check-in.
| Field | Details |
|---|---|
| First name / handle | [Name or pseudonym if anonymous] |
| Industry | [e.g., Freelance copywriter, Digital marketing agency, Accountant, E-commerce store] |
| Business size | [Solo / 2-5 people / 5-10 people] |
| Location | [Country or region — relevant for EU/NA hosting decision] |
| LetsBe tier | [Lite / Build / Scale / Enterprise] |
| Founding member # | [#1–100] |
| Signup date | [Month and year] |
| Primary use case | [The main thing they use LetsBe for — e.g., "Automated client follow-ups and CRM management"] |
Part 2: The Before State
This section captures the problem. Get this in the customer's words — don't paraphrase too much.
2.1 What was the tool stack before LetsBe?
List the tools they were using and what they were paying. Estimate if they don't know exactly.
| Tool | Purpose | Monthly Cost |
|---|---|---|
| Total | €___/mo |
2.2 What was the time cost?
Estimate or ask directly:
- Hours per week on manual operational tasks (data entry, follow-ups, scheduling, reporting): ___ hrs/week
- Estimated monthly cost of that time (at their effective hourly rate): €___/mo
- Biggest time sink (their words): "___"
2.3 What was the main frustration?
Use their exact words if possible. This becomes the "hook" of the case study.
Quote: "___"
2.4 What made them try LetsBe?
What was the trigger? What were they hoping to solve?
"___"
Part 3: The Setup Experience
Captures the "getting started" story — used to address the "too technical / too much effort" objection.
3.1 Time to first value
- Time from signup to first AI task completed: ___ hours/days
- First tool they configured or AI task they ran: ___
- Onboarding friction (1 = painless, 5 = significant effort): ___
- What surprised them about setup: "___"
3.2 Tools migrated / activated
Which LetsBe tools did they activate?
- Odoo (CRM)
- Stalwart Mail (email)
- Nextcloud (files)
- Plane (project management)
- Ghost (website/blog)
- Listmonk (email marketing)
- Cal.com (scheduling)
- Bigcapital (invoicing/accounting)
- Umami (analytics)
- Activepieces (automation)
- Chatwoot (customer support)
- Documenso (e-signing)
- Formbricks (forms)
- Vaultwarden (passwords)
- Other: ___
Part 4: The Results
The core of the case study. Be specific. Vague results ("saved time," "more efficient") are useless for sales.
4.1 Financial results
| Metric | Before LetsBe | After LetsBe | Change |
|---|---|---|---|
| Monthly tool costs | €___ | €___ | -€___ (___%) |
| Monthly labor cost (ops tasks) | €___ | €___ | -€___ (___%) |
| Total monthly savings | -€___/mo | ||
| Annual savings | -€___/yr |
4.2 Time results
| Task | Before | After | Time saved/week |
|---|---|---|---|
| [e.g., CRM updates] | ___ hrs | ___ hrs | ___ hrs |
| [e.g., Email follow-ups] | ___ hrs | ___ hrs | ___ hrs |
| [e.g., Scheduling] | ___ hrs | ___ hrs | ___ hrs |
| [e.g., Reporting] | ___ hrs | ___ hrs | ___ hrs |
| Total | ___ hrs/week |
4.3 Specific workflow wins
Describe 2-3 specific things the AI team does for them that they didn't expect or that made the biggest difference. These become the "oh shit moments" in the case study.
Win 1:
- What it does: ___
- Time before: ___
- How it works now: ___
- In their words: "___"
Win 2:
- What it does: ___
- Time before: ___
- How it works now: ___
- In their words: "___"
Win 3 (optional):
- What it does: ___
- Time before: ___
- How it works now: ___
- In their words: "___"
4.4 Unexpected benefits
Things they got that they weren't looking for:
"___"
Part 5: Privacy / Ownership Value
Specifically for use with privacy-conscious prospects. Skip if the customer doesn't care about this angle.
5.1 Did privacy matter to them?
- Was this a decision factor at signup? Yes No Somewhat
- What was their concern, if any?
- How did they feel about it after using LetsBe?
"___"
5.2 Did they migrate away from a cloud provider?
- What did they move off of?
- What changed?
- How did they describe the feeling of owning their data?
"___"
Part 6: Objections They Had (and How They Were Resolved)
This section is pure gold for the Objection Handling Guide.
6.1 Objections before signing up
List each one and what resolved it:
| Objection | What resolved it |
|---|---|
6.2 Early frustrations after signing up
Be honest about what didn't work well initially:
| Friction | Resolution |
|---|---|
Part 7: Shareable Case Study (Draft)
This section is the final, one-page version for use in sales emails, the website, and pitch decks. Write this after completing Parts 1–6. Keep to 300-450 words.
[Customer Name / Handle] — [Industry] — [Location]
[One-line headline capturing the main result] Example: "How a 3-person marketing agency cut their SaaS spend by 68% and reclaimed 12 hours a week."
The situation: [2-3 sentences about who they are and what their business does. Make the reader see themselves in this person.]
The problem: [2-3 sentences about what their operational life looked like before LetsBe. Use their words where possible.]
"[Direct quote about the pain — their words, not yours]"
The switch: [1-2 sentences about why they decided to try LetsBe and what they were hoping for.]
What changed: [3-4 sentences describing the specific workflows the AI now handles. Be concrete. Not "the AI helps with email" but "the Sales Agent reviews every Chatwoot conversation daily, flags prospects who haven't been followed up in 5 days, and drafts the follow-up — I review and send with one click."]
"[Direct quote about the experience — something specific and surprising]"
The results:
- [Metric 1]: [Specific number — e.g., "Monthly tool costs dropped from €340 to €75"]
- [Metric 2]: [Specific number — e.g., "8 hours/week freed from CRM updates and follow-ups"]
- [Metric 3]: [Specific number or qualitative win — e.g., "Zero missed follow-ups in the first 6 weeks"]
In their own words:
"[The best quote from the interview — the one that you'd want a skeptical prospect to read]"
[Customer name], [Job title / description], [Company name if permitted] LetsBe [Tier] — Founding Member #[number]
Part 8: Usage Rights
| Item | Permission |
|---|---|
| Use full name | [ ] Yes [ ] First name only [ ] Anonymous |
| Use company name | [ ] Yes [ ] No |
| Use on website | [ ] Yes [ ] No |
| Use in pitch deck / investor materials | [ ] Yes [ ] No |
| Use in email outreach | [ ] Yes [ ] No |
| Quote directly | [ ] Yes, with attribution [ ] Yes, without attribution [ ] No |
| Follow-up contact for prospective customers | [ ] Yes (LinkedIn/email) [ ] No |
| Permission confirmed by customer | [ ] Yes — [date] |
| How permission was obtained | [ ] Email [ ] Verbal (noted) [ ] Written form |
Internal Notes
For Matt / team use only — not shared externally
- Collected by: ___
- Collection date: ___
- Check-in type: 30 day 60 day 90 day Ongoing
- Priority for website use: High (use immediately) Medium (good story, queue it) Low (internal reference only)
- Best objection addressed: ___
- Target persona match (from Competitive Landscape personas): Solo Founder (Maria) Agency Owner (Tom) Privacy-Conscious Pro (Dr. Weber) Other: ___
- Notes from interview: ___
Changelog
| Version | Date | Changes |
|---|---|---|
| 1.0 | 2026-02-26 | Initial template. Eight-part structure covering profile, before state, setup, results, privacy, objections, shareable one-pager, and usage rights. |