Read the recap

Back to Hubsessed Office Hours: AI-Native
Hubsessed Office Hours: AI-Native

Hubsessed Office Hours - AI-Native - Oct 5, 2026

  • Nico LafakisHost
  • Trisha MerriamHost

Monday, October 5, 2026

Sign in to watch the full replay and read the transcript.

Sign inSubscribe free
SharePost on X (opens in a new tab)Share on LinkedIn (opens in a new tab)

In the first Hubsessed Office Hours for AI-Native, Nico Lafakis and Trisha Merriam spend most of the hour on one attendee question: how do you get a HubSpot agent to follow a template the same way every time? Nico opens a customer lifetime value agent he built to show how he structures its instructions and rules, and when examples help, and Trisha shares her own writer and checker setup. They also cover Dots, agent-to-agent connections and reverse engineering your data.

Clips from this session

Key takeaways

If two jobs would ever be used apart, give each its own agent and run them one after the other. One job per agent keeps the starting instructions from getting lost in a long run.

If it has to be one agent, the fix is in the instructions: markdown headings to signal importance, the role first and the goal second, and a defined scope, execution mode and method.

Keep a rule set of guardrails, and add a rule every time testing shows something you do not want.

Examples are the best way to get a fixed output, but one or two examples become the only shapes the model will use. If you cannot give several, describe the template precisely: columns and rows, headers and sections.

Pair a writer with a checker, or run a review agent as a workflow action so one reviewer can check several agents, and test what each run costs in credits.

Nico's distinction: an MCP connector lets your agent look at everything, while an agent-to-agent connection only talks to the agent that curates the information.

Reverse engineer your data. Start from the deals that were won and the relationships behind them to see which reps work best with which people, and build playbooks around people as well as companies.

Questions answered

Chapter times not yet verified

  1. 00:00Welcome: Nico and Trisha open the first AI-Native sessionTopic
  2. 03:34What Dots is, and why it feels like one assistant for everythingTopic
  3. 07:53Many HubSpot portals, many tools: can one assistant hold them all?Question
  4. 10:25Agent-to-agent and MCP, and checking before anything is sentTopic
  5. 12:47Models reaching the same level, and asking the right wayTopic
  6. 13:58How do I get a HubSpot agent to follow a template the same way every time?Question
  7. 16:58Inside a customer lifetime value agent, and the change to agent instructionsTopic
  8. 21:26Two agents: a writer and a checkerTopic
  9. 23:39Markdown headings, a rule set, and the role before the goalTopic
  10. 27:58Scope, examples, and a reviewer as a workflow actionTopic
  11. 35:39Do long instructions make an agent forget its rules?Question
  12. 38:28Knowledge as skills, and test, test, testTopic
  13. 44:09Asking Breeze which model runs under the hoodTopic
  14. 47:34Reverse engineer itTopic
  15. 48:38Matching sales reps to the people they work with bestTopic
  16. 53:21Playbooks built around peopleTopic
  17. 55:26Wrap: see you next MondayTopic

Resources

Related episodes