The most common use
Copy, paste, adjust, try again.
That is the default flow. It solves one-off situations.
The cost of that flow
You resend files, dig through conversations and retell decisions.
The result depends on how much context fit into that one chat.
That is why quality swings so much from one conversation to the next.
An advanced way of working
Each agent comes in with a role, context, tools and clear limits.
You set the direction and approve the delivery.
Picture this flow
“I want to list this product. Use the photos in Drive, research the price, prepare the listing and keep track of the people who reply.”
One agent compares prices on marketplaces. Another edits the images in Figma and writes the listing.
The system creates the opportunity in Salesforce and opens the follow-up in Notion.
The work arrives ready for you to review and approve before anything goes out.
The agents publish, follow the messages and keep the negotiation history up to date.
For that flow to run smoothly, there is a well-architected setup behind it.Clear roles, connected tools, rules and approval points.
The flow
The goal and the bar stay yours. Execution stops depending on a loose chat.
Bringing a concrete goal will always be your job. So is setting the bar for the delivery.
Your “CFO”, the lead agent, stays plugged into WhatsApp, your second brain, email, Drive, history and external sources.
With context in hand, a squad is assembled: a team of specialist agents.
Each agent does its job with the right repertoire and tools: design, finance, research and other roles.
The boss reviews, compares and asks for changes. Only then does it hand over to you, with quality far above a simple chat.
Continuous learning
When you approve
The delivery becomes the reference for the whole team.
When you correct or reject
The reason becomes a rule, a limit or an example for the next job.
After 10, 20, 50 jobs, you are no longer running the team from day one. Your agents know your business better, make fewer mistakes and land much closer to your standard on the first delivery.
Next step
A conversation about your operation.
Routines, tools and what gets stuck today.Scope and plan in writing.
What is in, what is out, and how many weeks.Day 1 on the calendar.
Setup ready before the first session.Not to memorize. This is the essential vocabulary. During the sessions, each term shows up at the moment it enters the real build.
Context, specification, source, skill, agent, rule, test.
API, MCP, connector, permission, setup.
Repository, GitHub, commit, branch, PR, review, merge.
“Prepare the proposal for client X with what we agreed yesterday.”
The agent retrieves the conversation and looks the client up in the CRM.
It looks for the proposal or contract in the connected sources: local folders, Drive, Notion or ClickUp.
It confirms scope, price and rules at the source. Then it prepares the proposal, shows where each piece of information came from and sets apart the decisions that still depend on you.
Context gathers everything the agent needs to consult.
Specification defines what it must deliver and how you will judge it.
During the sessions, we organize where each piece of information lives and how the agents should find it before they work.
Carries information and commands between systems.
Presents the tools to the agent and explains how each one can be used.
[IF A SOURCE IS MISSING, THE AGENT SHOWS THE GAP. IT DOES NOT GUESS.]
Hermes is a platform with its own engine for coordinating models, tools, memory, skills, permissions and work sessions.
The history stays searchable. Approved memories and skills carry into the next sessions, without resetting context on every request.
You send a voice note with the direction.
Hermes retrieves what it already knows about the job.
It picks the model and triggers the tools it needs.
The answer lands in the same conversation, ready for review or approval.
Obsidian connects projects, people, meetings, decisions, proposals, contracts, files and next actions.
The same second brain holds the agents' instructions, quality criteria, approved templates, read and write rules and accumulated lessons.
“Gather everything we have on client X. Show me the last decision, the current proposal, what is pending and the source of each piece of information.”
During the sessions, we build this structure and define what the agents may consult, propose or update.
[CHATGPT · CLAUDE · GEMINI · HERMES] → THE SAME BASE, EVEN WHEN THE MODEL CHANGES.
Telegram, WhatsApp, iMessage, meetings, documents and voice notes.
Hermes, specialist agents, Obsidian and connected tools.
To follow projects, priorities, calendar, decisions and next actions.
To organize contacts, find the right person and follow relationship opportunities.
[NEXT: HOW IT ALL COMES TOGETHER IN PRACTICE AND WHAT FITS INTO THE EIGHT WEEKS.]
A personal base of operations
A simple personal platform gathers what deserves attention now: priorities, projects, calendar, decisions, people and next actions.
Example 01 · built for a client
A personal, visual, simple platform you open, glance at and understand where each front stands, what needs attention and what the next action is.
Conceptual prototypeThe home, in practice
Pulse does not try to replace every tool. It shows the essential state of the operation and takes you to the next decision.
From the work to Pulse
A new decision shows up in the real work.
It retrieves the people, history, rules and linked sources.
It separates what changed from what is still open.
Nothing sensitive is written before approval.
Every update stays linked to its source.
Example 02 · built for a client
A platform to organize people, preserve the context of each relationship, find the right connection for each need and follow the next action.
Conceptual prototypeProduct · active relationship
The same context runs through both products
One confirmation can update the project and preserve the relationship context, without losing the meeting, the decision or the source that led to the next action.
Project Pulse ↔ Network Radar · context and source preserved
Guided build
The goal becomes a written success criterion, before any code.
Out: an approved architecture that guides the other seven
Every piece of your information gets an address: nothing depends on memory anymore.
Out: frozen scope and a base ready for agents
Your first agents, with permissions and confirmation before writing.
Out: Hermes answering on your phone
Scattered contacts become searchable relationships, each with a next action.
Out: your network mapped, with real contacts
Each front with its state, pending decision and next step in view.
Out: the home showing your week's operation
Monday's meeting becomes a project update, with source, on Tuesday.
Out: both products reading the same context
The system runs a full week on real work, not a demo.
Out: zero open items for the handoff
You run, maintain and change the system without depending on anyone.
Out: your system, documented and live
It starts with a diagnostic of your operation: routines, tools, processes and what gets stuck today. From there, we design the system and build it together, session by session, in your real context.
The assets already built, skills, agent contracts and pipeline, come in ready. You pay for the deployment in your context, not for building from scratch.
Your whole network organized: who is who, the history of each relationship and the next action, on the platform and in your pocket.
Projects, people, meetings, decisions and next actions in one place: you ask, the system answers with its source.
The Integrated format does not just add another product. It shares context across every part.
The limits exist to deliver well in eight weeks and make clear what is being built.
Included: +1 follow-up session, 15 days later
A 45-minute conversation to understand your operation, your tools and what makes sense to build first. Investment and format come out of that conversation, in writing.
Rotate your phone
This presentation was built for portrait mode.