🚪 Onboarding and expectations
The first impression determines retention. Structured onboarding in the first few days— access gathering, setup, first delivery, and alignment — turns an anxious client into a confident client. Poor onboarding leads to churn even with an excellent product.
Kickoff and access checklist
A short meeting + a clear list of what you need (logins, APIs, examples). Without access, the clock doesn’t start.
First quick win
Deliver something visible early. Seeing the automation run right away builds confidence and eases the “will this work?” anxiety.
Align expectations
Make deadlines, scope, and how support works explicit. Aligned expectations are half the battle for satisfaction.
Organized start.
Unblocks delivery.
Value visible early.
Aligned = satisfied.
🔧 SLA, support, and maintenance
Automations aren’t “install and forget”: APIs change, sites break, and business rules evolve. One Clear SLA (response time, availability) and a monitoring routine are exactly what justify and sustain recurring revenue. Predictable support is as much the product as the automation.
SLA example (mono)
DISPONIBILIDADE alvo: 99% / mês
TEMPO DE RESPOSTA:
• Crítico (parado): 2 h úteis
• Alto (degradado): 1 dia útil
• Normal (ajuste): 3 dias úteis
CANAIS: WhatsApp + e-mail
MANUTENÇÃO PREVENTIVA: revisão mensal de fluxos
INCLUI: correção de quebras por
mudança de API/integração
✓ Support that retains customers
- ✓Monitor before the client notices.
- ✓Response time defined in writing.
- ✓Scheduled preventive review.
✗ Support that loses customers
- ✗Only discovers the failure when the customer complains.
- ✗"I’ll get back to you when I can."
- ✗Zero monitoring, everything is reactive.
Service promise.
Find the failure before it does.
Where to get help.
Review before it breaks.
🔁 Recurring revenue (retainer / subscription)
A one-off project makes you start from scratch every month. Recurring revenue — retainer or subscription—provides predictable cash flow, increases business value, and turns sales effort into a growing base. It's the difference between chasing deals and building up momentum.
📈 Why recurring work changes the game
- •Predictable MRR — you know how much is coming in next month.
- •Higher LTV — each client is worth much more over time.
- •Compound effort — new sales add up; they don't replace existing ones.
📊 The math of recurring revenue
- 10 clients × R$ 800/month = R$ 8.000 in predictable MRR.
- Low churn (client stays for 18 months) → LTV ≈ R$ 14.400 per client.
- Each new client adds to the base — doesn't start from scratch.
Monthly recurring revenue.
Fixed monthly package.
Who cancels — keep an eye on them.
Total value per customer.
📚 Document and hand off
If everything only works because it’s in your head, you’re hostage to your own service—you can’t get sick, travel, or delegate. Document and hand off (how the flow works, credentials, failure runbook) is a prerequisite for scaling and reduces the business's "bus factor".
What every service needs to document (mono)
RUNBOOK DO CLIENTE X • Arquitetura: o que cada nó faz • Credenciais: onde estão (cofre), quem acessa • Gatilhos: o que dispara o fluxo • Falhas comuns: sintoma → causa → correção • Contatos: cliente, suporte das ferramentas • Histórico: mudanças e datas OBJETIVO: outra pessoa opera sem te ligar
💡 Practical tip
Document while you build, not afterward. The best documentation test: ask someone who has never seen the workflow to resolve a simulated failure using only your runbook.
Operations manual.
Gets you out of the bottleneck.
Hand it off to the person who operates it.
Don’t depend only on yourself.
🏭 Productize and standardize for repeatability
Infinite customization doesn’t scale. Productize is turning the custom deliverable into a standardized package — same scope, same price, same process — that you can replicate from client to client. Standardizing is what lets you serve more clients without working proportionally more.
✗ Custom-built (doesn't scale)
- ✗Each client, a unique project from scratch.
- ✗Price and scope negotiated every time.
- ✗Unpredictable delivery time.
✓ Productized (scales)
- ✓Fixed package with a known scope.
- ✓List price, no need to reinvent it.
- ✓Repeatable, timed process.
💡 Practical tip
After the 3rd similar client, stop and ask: "what did I rebuild that could have been a template?". Anything that repeats is a candidate for standardization — base flow, proposal, onboarding, runbook.
A service becomes a package.
Same scope every time.
Predictable process.
Easy to buy and deliver.
📈 Scale with templates and a team
Scaling by doing everything yourself has a ceiling—and leads to burnout. The leverage comes from combining templates (of the flow, proposal, onboarding) with delegation to a team. Templates remove repetitive work; people remove the capacity limit.
Create the template library
Base workflow, proposal template, onboarding checklist, standard runbook. Each new client starts from an advanced point, not from scratch.
Delegate repeatable tasks first
Start by transferring standardized tasks (setup from a template, first-level support) and keep only what requires your judgment.
Become the manager, not the bottleneck
Your role shifts from execution to ensuring quality and selling. Delivery capacity no longer depends only on your hours.
Don’t start from scratch.
Repeatable work comes from you.
A team multiplies output.
Grow without burning out.
🚀 Module Summary
Next Track:
Track 6 · Practice — exercises, a prompt library, and ready-to-use skills to apply everything you’ve learned.