O que aprendi construindo SaaS em cima do WhatsApp 🧵
1/ O WhatsApp não é um canal. É onde o seu cliente já mora. Isso muda tudo no produto.
4
7
424
Heads up if you use Zod: 4.5 changed datetime validation in a minor release. It now requires seconds.
Example: "2026-10-24T10:30-03:00" used to pass. Now it fails.
If your API already accepts that format, z.stringFormat("datetime", regex) with optional seconds keeps the contract exactly as it was.
Contract tests are what flag this kind of change during the upgrade. Minor versions can change contracts too.
1
Mandou a oferta para a sua lista. E agora, quem respondeu?
No Botozap, nos planos pagos e no teste grátis, o disparo pelo WhatsApp já alimenta um funil em kanban, sem configurar nada. Quem recebeu e ainda não está em nenhuma etapa entra em "Não respondeu". Se responder em até 7 dias, vai para "Respondeu". Dali você acompanha cada um até fechar a venda.
Na semana da Black Friday, isso evita a pior perda: o cliente que respondeu "quero" e ficou sem resposta no meio de todas as outras conversas.
2
A PostgREST detail worth knowing if you write SQL functions behind an API.
If a function raises serialization_failure (40001), PostgREST treats it as safe to retry and runs the whole transaction again.
So using 40001 to say "this booking slot is already taken" can turn into a retry loop instead of a fast, clear error.
A cleaner pattern: give business conflicts their own SQLSTATE and map it to HTTP 409. Leave 40001 for real serialization failures raised by Postgres.
12
Se você usa agentes de código com git worktree, vale olhar quanto espaço elas ocupam. Cada worktree é uma cópia de trabalho inteira, às vezes com node_modules próprio.
Três comandos resolvem:
git worktree list
mostra todas as worktrees do repositório.
git worktree remove caminho/da/worktree
apaga uma que você não usa mais.
git worktree prune
limpa o registro das que já foram apagadas do disco.
6
Para quem atende cliente pelo WhatsApp:
qual é a mensagem que você mais repete no dia?
"Qual o endereço?", "aceita Pix?", "tem horário amanhã?"... Conta aqui a sua.
8
Solo founders and small teams: how do you handle customers who write at 2am?
A person on call, an AI agent with clear handoff rules, or an honest "we reply in the morning"?
Tell me what your customers prefer.
3
11
Vibe coding is fine for a prototype. I build plenty of throwaway things that way.
What changes for anything with paying customers is what happens before it ships: tests against a real database, a human review, secrets out of the repo, and limits on anything that costs money per call.
The AI writes the code faster. The checklist stays the same size.
1
12
We decided early not to spend on ads. Instead we write content that answers the exact questions our customers type into search.
More and more of those questions are now typed into AI assistants instead of Google. Clear answers work for both.
Are you seeing AI assistants send people to your product?
1
51
WhatsApp oficial conectado em minutos, na maioria dos casos.
No Botozap você entra pela janela de cadastro da própria Meta e escolhe como quer usar: só pela API ou em coexistência, mantendo o WhatsApp Business no celular.
Na coexistência, o histórico do celular aparece no painel e a equipe responde por lá. Você continua respondendo do app quando estiver na rua.
Sem programador e sem trocar de número.
1
1
53
If your product needs a tutorial, you already lost.
A small business owner wants to click "connect" and start working. Everything else is our problem.
1
1
77
Lots of vibe coded apps on the timeline this week with exposed API keys and no rate limits.
If you use coding agents, the basics still apply:
1. API keys never go into git.
2. Agents start with read access.
3. Writes are scoped and reviewed.
4. No full-access production keys in an agent's hands.
None of this is new. Agents just make skipping it faster.
2
1
124
Claude Code's new Code Mode writes JavaScript to chain tool calls instead of calling them one by one.
@grok in what kinds of coding tasks would that approach save tokens and round trips, and where could it make things worse? Give one example of each.
1
14
We got an app approved in ChatGPT three weeks after the first idea.
The design decision I am happiest with: no API key. The user connects with their own login and grants permission, the same way you connect Google Drive.
And sending a message to a customer is designed to happen only after the user confirms it on a card. When an assistant can talk to your customers, that confirmation step is the feature.
1
17
Validating the idea is still the priority.
What changed is that with AI you can launch something more polished and more complete than before, for the same effort.
That is why the bare-bones MVP makes less sense to me every year.
Do you still ship ugly on purpose?
5
When I started our SaaS, I was sure the first feature request would be AI.
It was a CRM funnel. A kanban tied to WhatsApp broadcasts: the contact who gets a broadcast lands in "No reply". If they answer within 7 days, they move to "Replied". No setup. From there the business owner tracks them until the sale closes.
People who run a business want to know who replied and who is close to buying. The rest can wait.
2
2
67
Question I get from people building their first API that sends messages or charges money:
@grok what is the practical difference between retrying a request and sending it with an Idempotency-Key? Explain with one concrete example where a retry alone sends the same message twice.
1
5
Good read from MIT CSAIL (Alex Zhang, Souradip Chakraborty, Omar Khattab) on agent harnesses.
A harness is the program between the outside world and the model. It decides what each model call sees.
Their claim: a well designed harness keeps every call close to what the model already knows. In their tests, a recursive harness trained only on short tasks held up on tasks 8 to 32 times longer.
It matches what we see day to day with coding agents. A small, well scoped briefing works better than one giant prompt with the whole repo in it.
7
What is the one thing you never let a coding agent do on its own?
Ours never merge and never deploy. They work in their own worktree, inside a scope written in the briefing, and everything goes through review before it touches main.
Curious where other people draw the line.
1
11
Muita gente ainda confunde as duas categorias de template do WhatsApp oficial, e isso muda custo e aprovação.
@grok qual a diferença entre template de utilidade e de marketing no WhatsApp oficial? Dá um exemplo de cada para uma loja pequena.
1
6
