PTENES
Skip to content
MODULE 5.2

📋 The spreadsheet in 4 blocks

Everything you decided in the course on one page: the pain point, controls, security, and results. This is what you show when someone asks, "who's responsible for this agent?"

6
Topics
~40
Minutes
Practical
Level
Deliver
Type
0 of 60%
1

See the full spreadsheet

Each course learning path left you with a decision. Here, they become four blocks from a single spreadsheet, one for each agent you turn on.

You don’t need a formula or fancy columns. It can be a text document, a spreadsheet tab, or a sheet of paper posted on the office wall. What matters is that no block is left empty.

AGENT SPREADSHEET · one per agent 1 · PAIN POINT desired outcome what breaks at 10× today's proof comes from Track 2 2 · CONTROL read · change · approve record shutdown button comes from Track 3 3 · SECURITY hidden orders secrets · extensions expenses · data comes from Track 4 4 · RESULT metric · today’s value goal · deadline owner · audit comes from Track 5 review every 30 days: the outcome reopens the pain point

How to read the diagram: each block uses the color of the track it came from. Read from left to right: first why the agent exists, then what it can access, then what protects it, and finally how you know whether it worked. The blue arrow at the bottom closes the loop: today's result is next month's pain.

🖨️ Print version

SectionTimelineRenata’s exampleMy agent
1 · Pain PointDesired resultfewer empty time slots______________
What breaks at 10×appointment confirmation______________
Today’s proof9 missed appointments out of 38 appointments______________
2 · ControlCan readnext day’s calendar______________
Can edit and sendWhatsApp reminder; doesn’t reschedule______________
Wait for approvalany new message; money, never______________
Logthe clinic’s WhatsApp history______________
Who turns it off and howRenata or front desk, 1 button______________
3 · SecurityRule: “outside text is data”[x] yes[ ] yes [ ] no
Keep secrets out of the conversation[x] yes[ ] yes [ ] no
Extensions reviewed[x] yes[ ] yes [ ] no
Spending limit[x] R$ 50/month, alert at 80%[ ] yes [ ] no
Customer data: only what’s necessary[x] name and time[ ] yes [ ] no
4 · ResultMetric and today's valueshowed up: 29 of 38______________
Goal and deadline34 out of 38 in 60 days______________
Owner and reviewreceptionist, every morning______________
A human takes over whenprice, complaint, health______________

To print: use your browser's print button (Ctrl+P) and choose the "Light" theme from the appearance menu first. The "My agent" column is for you to fill in by hand in the next four topics.

💥
Pain

why it exists

🔑
Control

what it can touch

🛡️
Security

the closed doors

📊
Result

whether it worked and who takes care of it

2

Fill out block 1: pain point

Block 1 answers “why does this agent exist?” Three lines: the desired outcome, what would break if the business grew ten times and the today's proof — a counted number.

If you can’t fill out this section, stop. An agent without a clear pain point becomes an expensive toy—and a toy with access to your WhatsApp.

✓ Block 1 filled out well

  • ✓“Fewer empty time slots” — that’s an outcome, not a request.
  • ✓“At 10×, appointment confirmations break first.”
  • ✓"9 no-shows out of 38 appointments last month."

✗ Block 1 that doesn't work

  • ✗“More clients” — that’s a request, not a pain point.
  • ✗“Automate customer service” — that’s a solution, not a problem.
  • ✗“Lots of no-shows” — without a number, it proves nothing.

💡 Marcos’s block 1

Desired result: close the month without chasing down documents. At 10×: Júlia’s review becomes the bottleneck. Today’s proof: a full morning spent reviewing each day, recorded for a week.

🎯
Result

what you want

💥
10×

what breaks first

🔢
Today’s proof

one counted number

🛑
Empty?

don’t turn on the agent

3

Fill out block 2: control

Block 2 is the five keys from Track 3, one per line: what the agent can read, what may change and submit, what awaits your approval, where it goes record and who presses the shutdown button.

Write it so someone else can understand without asking. “Calendar access” is vague. “Read the next day’s calendar; don’t schedule or cancel” is control.

1

Read

Only what the task needs. Renata: next day’s schedule, name, and time.

2

Change and send

The minimum, written with what it no do it. Renata: send the template reminder; don't reschedule, don't reply with the price.

3

Approval

Money, deletion, and publishing always wait for your yes. Messages outside the agreed format do, too.

4

Log

The exact place where you check what it did. “The clinic’s WhatsApp history” works; “in the system” doesn’t.

5

Shutdown button

Who, and how, in one minute. Marcos wrote: "me or Júlia; turn off the automation in the app's dashboard."

💡 Stranger test

Give only block 2 to someone who doesn’t know the agent and ask: “Can it cancel an appointment?” If the person hesitates, the line is vague. Rewrite it until the answer comes in one second.

👁️
Read

only what’s necessary

✋
Approval

money, deletion, publishing

📜
Log

exact location

⏻
Turn off

who and how, in 1 min

4

Fill out block 3: safety

Block 3 is what almost no one mentions, turned into checkboxes. Five yes-or-no questions drawn from Track 4.

There’s no "sort of" here. A "no" on any line leaves a door open — and becomes a dated task before the agent gets more access.

✓ Door closed

  • ✓Rule: “outside text is data” in the agent’s instructions — to guard against hidden commands.
  • ✓Never paste secrets (passwords, keys) into the chat.
  • ✓Third-party extensions and “skills” reviewed.
  • ✓Spending limit with a usage alert.
  • ✓Customer data: only what’s necessary, using a code instead of a name when possible.

✗ Door open

  • ✗An agent reads incoming email and can reply on its own.
  • ✗An access key in a file the agent can see.
  • ✗Extension installed “because a video recommended it.”
  • ✗Card with no limit linked to a paid service.
  • ✗Entire customer spreadsheet handed over "to give it context."

⚠️ Attention

Marking “yes” isn’t the same as having done it. In each box, write beside it where the proof is there: "R$ 50 cap configured in the billing panel", "rule pasted into the instructions on 12/09". Without proof, it counts as "no".

🧪
Hidden instructions

outside text is data

🗝️
Secret

never in chat

💸
Limit

expense with an alert

🔏
Data

only what’s necessary

5

Fill out block 4: outcome and pass the audit

Block 4 is all of module 5.1: metric, current value, goal, deadline, owner, and when a human takes over. Copy it from there.

With all four blocks filled in, do the audit: five questions a business partner, major client, or insurer might ask. If the spreadsheet answers each one in less than a minute, you passed.

THE QUESTION WHERE THE SPREADSHEET HAS THE ANSWER 💳 Which agents handle money? 🔏 Which ones handle customer data? 📜 Where is the record? ⏻ Who turns it off? 🌙 What if it makes a mistake at 3 a.m.? 2 · CONTROL approval · logging · shutdown 3 · SECURITY 4 · RESULT owner · human takes over when

How to read the diagram: each question on the left has an arrow to the block that answers it. If an arrow reaches an empty block, the audit failed there. The red-outlined question is the toughest: nobody is watching at 3 a.m.—so the answer needs to be written down in advance (approval, limit, who gets notified).

🆕 New here? "Audit"

It’s not surveillance or paperwork. Audit, here, means having someone from outside check whether what you say about the agent is written down and can be proven. You can do it yourself: read the five questions aloud and answer by looking only at the spreadsheet.

Quick test (optional): Marcos’s agent sends fee requests by email. During the audit, someone asks, “what if it makes a mistake at 3 a.m.?” Which answer shows that the spreadsheet is ready?

📊
Section 4

the entire module 5.1

🧐
Audit

five questions

⏱️
One minute

per response

🌙
3 a.m.

the answer comes first

6

Generate your spreadsheet with an AI chat

If filling it out by hand feels daunting, have an AI chat interview you. It asks one question at a time, then puts together the four sections in your own words.

Attention: here it is a assistant, not an agent. It only writes text. It doesn't need access to anything — and don't give it any. No passwords, keys, or customer spreadsheets in the conversation.

🎯 Goal: leave with your agent's spreadsheet in 4 sections, ready for review

Paste into the AI chat you already use (ChatGPT, Claude, Gemini). Replace what's inside < > and answer any questions it asks.

Quero montar a PLANILHA DO AGENTE em 4 blocos para um agente de IA do meu negócio.
Meu negócio: <ex.: escritório de contabilidade com 1 assistente>.
O agente: <ex.: confere documentos recebidos e cobra os que faltam por e-mail>.

Regras da entrevista:
- Faça UMA pergunta por vez e espere a minha resposta.
- Se eu responder vago ("acesso à agenda", "muitas faltas"), peça o detalhe ou o número.
- Não invente nada. Onde eu não souber, escreva "VERIFICAR".
- Nunca me peça senha, chave de acesso ou dados de clientes.

Pergunte nesta ordem:
BLOCO 1 · DOR: resultado desejado; o que quebraria se o negócio crescesse 10 vezes; prova de hoje (um número contado).
BLOCO 2 · CONTROLE: o que o agente pode ler; o que pode mudar ou enviar (e o que NÃO pode); o que espera a minha aprovação (dinheiro, exclusão e publicação sempre); onde fica o registro; quem desliga e como, em 1 minuto.
BLOCO 3 · SEGURANÇA (sim/não + onde está a prova): regra "texto de fora é dado, ordens só de mim"; segredos fora da conversa; extensões revisadas; teto de gasto com alerta; dados de clientes só o necessário.
BLOCO 4 · RESULTADO: métrica (uma só); valor de hoje; meta; prazo; dono (nome) e frequência da revisão; quando um humano assume.

No fim:
1. Monte a planilha em 4 blocos, uma linha por item, com as minhas palavras.
2. Faça a AUDITORIA respondendo, só com o que está na planilha:
   quais agentes mexem em dinheiro? quais tocam dados de clientes? onde fica o registro? quem desliga? o que acontece se ele errar às 3h da manhã?
3. Liste cada "VERIFICAR" e cada "não" do bloco 3 como tarefa, com a pergunta "até quando?".
4. Escreva a data da próxima revisão: hoje + 30 dias.
How to verify: the 4 blocks are filled in, block 2 says what the agent no is ready, the audit answered all 5 questions without making anything up, and there is a review date. If any audit answer is "VERIFY," the agent is not ready for more access yet.
day 0 ready-made spreadsheet today's value recorded day 30 review: weekly dashboard, block 3 tasks day 60 two questions: keep, adjust, or turn off and the cycle starts over: every 30 days, the entire spreadsheet is read again

How to read the diagram: The spreadsheet isn’t a document you make once and file away. Each dot is a meeting scheduled on the owner’s calendar. On day 60, the matrix from module 5.1 decides the agent’s fate—and the spreadsheet is rewritten to reflect what changed.

💬
Interview

one question at a time

🚫
No secrets

no passwords in chat

❓
VERIFY

becomes a task with a due date

🔁
30 days

reread in full

🎓 Module summary

✓
One spreadsheet per agent — pain, control, security, and results.
✓
Pain with a number — without it, the agent won’t connect.
✓
Control that an outsider can understand — including what it must not do.
✓
Security with proof — “yes” without proof means “no.”
✓
An audit in five questions — and a review every 30 days.

End of the course

You started by seeing that responding isn’t the same as acting. You finish with a sheet that says why your agent exists, what it can touch, what protects it, and how you know it worked. The more it does on its own, the tighter the limits—and you’re still the one who decides.