🛠️ What tools are
So far, Jarvis thinks, talks, and decides—but all of this stays trapped inside the conversation. Tools are the resources that let Jarvis act in the real world: read and write in a spreadsheet, create a record in a system, send a message, charge an amount. Without tools, it’s a brilliant advisor with its hands tied. With tools, it takes action.
🤲 Talking is different from doing
Replying “I’ll record your request” doesn’t record anything. The tool is what turns words into facts: it’s the hand that opens the spreadsheet and types the row. A Jarvis without tools makes promises; a Jarvis with tools delivers.
✓ With tools, Jarvis
- ✓Records the order in the spreadsheet automatically.
- ✓Creates the contact in the CRM when the sale closes.
- ✓Send the confirmation on WhatsApp right away.
- ✓Checks inventory before promising a timeline.
✗ Without tools, Jarvis
- ✗You say “I’ll take notes”—and don’t write anything down.
- ✗Makes up a deadline without checking inventory.
- ✗Asks a human to do everything manually.
- ✗Becomes just a pretty chat, with no real impact.
💡 Practical tip
Whenever you think “and then Jarvis needs to do X in the company’s system,” you’ve just identified a tool. List those actions before choosing technology—the list of actions is your map of the tools you need.
📊 Spreadsheets, Notion, and CRM
The most common — and most underestimated — tools are the ones the company already uses every day: the Google spreadsheet, the team’s Notion, the sales CRM. Jarvis can read and write in all of them. You don’t need expensive new technology: you need to connect to what’s already there and organize what’s already being recorded by hand.
Spreadsheet (Sheets)
Record requests, leads, and simple tracking. The starting point for almost every project.
Notion
Knowledge base, tasks, documentation that Jarvis consults and updates.
CRM
Customers, opportunities, relationship history. The heart of sales.
🔁 Reading and writing: two directions
- Read: Jarvis checks the spreadsheet to answer "what's the status of order 482?" without bothering anyone.
- Write: Jarvis creates a new row in the CRM when a lead asks for a quote — no manual data entry.
- Together: read to decide, write to document — that’s the cycle that saves hours every day.
💡 Practical tip
Start with the spreadsheet the team already fills out by hand. Connecting Jarvis to it is the highest-return first automation: no new tool, immediate relief from repetitive work.
🗄️ Database and APIs
When volume grows, a spreadsheet isn’t enough. That’s when the database (a large, organized file of information that can handle many people at the same time) and the APIs (the "outlet" through which two systems communicate). You don't need to program this from scratch: you need to understand what each one does so you can ask for the right piece.
A request to an API, in plain language
Illustrative API call outline — clear question, structured response.
⚠️ Common mistake
Wanting a sophisticated database when a spreadsheet would do. A database and API are for when volume or integration calls for them—not to impress. Move up a level only when the pain point calls for it.
💬 Messaging: WhatsApp, Telegram, and email
Messaging is the tool that gives voice to Jarvis: WhatsApp, Telegram, and email. Here, it not only receives (an incoming channel, covered on Day 1) but also sends actively — confirms an order, gives a deadline update, sends a reminder. It’s the difference between a system that only responds when called and one that takes the initiative to communicate.
Where Brazilian customers already are. Confirmations, reminders, and quick support land right in the palm of their hands.
Telegram
Great for internal teams and alerts. Easy to connect and ideal for Jarvis operational notifications.
The formal channel: proposals, summaries, and records that need to be documented and searchable.
💡 Practical tip
Choose the channel based on your audience, not the latest trend. Selling to end customers in Brazil? WhatsApp. Technical team? Telegram. Formal record with a corporate client? Email. The right tool is the one the recipient already opens.
💳 Payments and internal systems
The most powerful — and most sensitive — tools are the ones that handle money and the company's own systems: generate a charge, issue a boleto/Pix, mark a payment as received, update the ERP. Here, mistakes can be truly costly, so these tools go hand in hand with the safety barriers from the previous module.
Billing / Pix
Generate a payment link or a Pix at the time of sale.
Download and notes
Confirm that a payment has come in and trigger the next step in the process.
ERP / internal system
Update inventory, order status, customer records—the system that runs the operation.
🛡️ Sensitive tools need strong safeguards
- Confirm before acting: charge or mark as paid only after a clear verification—never based on an assumption.
- Value limit: above a certain amount, require human approval before executing.
- Record everything: every money-related action is logged — who requested it, when, and how much.
⚠️ Common mistake
Give Jarvis the power to charge customers or change the ERP without any guardrails. The more dangerous the tool, the stricter the limits around it. Power without guardrails isn’t efficiency — it’s risk.
🎯 The tool serves the intent
This is the heart of the module — and wraps up Day 2. Most people start by asking the wrong question: "which tool should I use?". The architect asks "what result do I want to achieve?" — and only then choose the tool that delivers that result. The tool serves the intent, never the other way around. Changing the order is the number one reason projects end up full of technology and short on results.
✓ Start with intent
- ✓"I want to confirm orders without manual work."
- ✓Then you choose: a spreadsheet + WhatsApp will do the job.
- ✓The tool serves the result.
- ✓Simple, inexpensive, and it works.
✗ Starting with the tool
- ✗"I want to use that new database."
- ✗Then you look for a problem for the tool.
- ✗A lot of technology, little real-world impact.
- ✗Expensive, complex, and gone by the first month.
🧭 The right order for making decisions
What’s the result?
Define the intent first — what needs to change in the world.
What action produces this result?
Write a line? Send a message? Charge a fee?
What’s the simplest tool for this action?
The cheapest and easiest option that delivers—not the most impressive one.
Is it within the walls?
Sensitive actions require confirmation, limits, and a record. Only then: it runs.
🔑 The sentence that closes Day 2
Tools are arms, not brains. Intent is the brain; values and guardrails make the decisions; tools just execute. When someone asks you, “What stack do you use?”, answer first: “What result are we trying to achieve?” That reversal is the mark of an architect.
Self-check (optional): what is the right question to ask when choosing a tool?
🎯 Module summary
End of Day 2 — next day:
The “core identity,” services, agents, memory, safety barriers, and tools are in place. On Day 3, you bring it all together into a real solution inside a company — from intent to measured result.