Heros H. creates B2B sales content about building referral processes and preparing salespeople for customer meetings. The posts explain practical sales routines and describe an automated meeting-preparation agent that turns company research into pain-point hypotheses, opening observations, and discovery questions.
Heros H. is most useful for Portuguese-language B2B sales content on referral routines and meeting preparation.
Best for
A B2B sales-enablement campaign for Portuguese-speaking sales teams seeking referrals and meeting preparation.
Not for
English-language broad-reach awareness campaigns for general business audiences outside sales tools.
Key takeaways
Ask for three specific referrals at the end of every meeting, starting with the first.
Preparation matters only if it ends in a hypothesis about the customer's pain.
An agent briefs each meeting the night before with pain hypotheses, observations, and discovery questions.
Check first: Confirm audience analytics, rate card, sponsorship policy, and performance results with Heros H.
Main ideas
Asking for referrals should be a mandatory step in every meeting, not something a seller does only when feeling confident · Preparation is worth the time only if it ends in a hypothesis about the customer's pain · The fix they keep proposing is an agent that briefs each meeting the night before
Heros H. publishes Portuguese-language B2B sales content about referral routines and preparing for customer meetings.
The posts explain practical steps, such as asking for three specific referrals at the end of each meeting and following up with the person who made the introduction.
In a series of overlapping posts, they describe an agent that turns company research into meeting briefings with pain hypotheses, opening observations, and discovery questions.
Readers interested in sales processes and meeting preparation will find concrete examples to consider.
The posts connect sales problems to repeatable actions and explain why each step matters.
The referral post distinguishes a vague request from asking for three names, then treats follow-up as part of the process rather than an afterthought.
The meeting-preparation posts make a related case: research is useful when it becomes a specific hypothesis and questions for the call.
Turning routine sales work into a process is the clearest distinctive thread in the posts.
The meeting-prep agent appears in three substantially overlapping posts, making it one recurring idea rather than three separate examples.
Heros H. writes on LinkedIn, in Portuguese, for a B2B sales audience, returning to two connected arguments.
Read more
First, referral generation fails when it depends on a seller's confidence instead of being built into the meeting as a mandatory step.
Second, sellers spend hours researching accounts but still walk into meetings without a hypothesis about which pain matters, using the meeting for discovery that should have happened beforehand.
The proposed fix is an AI agent that reads the next day's calendar and delivers a briefing before the workday starts.
Both threads favor repeatable process over individual effort, but they point in different directions: the referral post praises a 19th-century routine that needed no CRM or automation, while the meeting-prep posts describe automating the routine with a tool.
Asking for referrals should be a mandatory step in every meeting, not something a seller does only when feeling confident
Heros H. argues that most B2B teams have a wish for referrals rather than a referral channel, because the ask depends on the seller's mood and comfort.
Read more
The ask has to be designed into the meeting itself, with four specific elements: ask for a fixed number of named people, ask at the end of every meeting from the first one, make the ask protocol rather than a target, and report back to the referrer to close the loop.
A vague request produces vague answers; a specific number produces specific names.
Protocol happens every time, while optional steps happen only when someone feels confident.
Follow-up matters for the same reason: a referrer who hears how the introduction went is more willing to refer again.
The post uses Prudential's agents in 1875 as its case.
They could not end a meeting without asking for three specific names of people the client could connect them with; the ask was protocol, not a goal.
The agent then returned to the referrer with a short update, which Heros H. says makes the referral cycle feed itself.
The post closes by asking readers whether their own team has a referral-request protocol and how it works.
It is the only post in the material that treats process discipline, rather than a tool, as the whole answer.
Preparation is worth the time only if it ends in a hypothesis about the customer's pain
The recurring complaint in the meeting-prep posts is not that reps skip research, but that the research does not lead to a decision.
Read more
Scrolling a prospect's LinkedIn, glancing at the company site and reading CRM history reveal more about the account without answering which pain to prioritize.
Heros H. calls this wasted effort: the rep arrives in discovery mode and spends the opening of the call collecting what should have been gathered earlier, and the prospect notices.
The proposed standard is to form three specific pain hypotheses before the call, so the meeting confirms them instead of searching for them.
The 25-hours post lays out the arithmetic: a team of five sellers spends 25 hours a week preparing for meetings, while a seller should need three minutes. It traces where the time goes and reaches the same conclusion as the other two prep posts: researching data without turning it into a hypothesis is wasted effort.
The fix they keep proposing is an agent that briefs each meeting the night before
All three meeting-prep posts describe the same tool as the answer to the preparation problem: an agent that reads the previous night's calendar, identifies the next day's meetings and delivers a briefing for each participant before anyone opens their computer.
Read more
Each briefing contains the company's current situation from real sources, what the participant's role likely prioritizes, three specific pain hypotheses for that company, a non-pitch opening observation based on a real signal, and three ready-to-use discovery questions.
The claim is that this cuts a five-person team's weekly preparation from 25 hours to roughly three minutes.
The posts also make the same offer: a Claude Code setup guide sent to people who connect and comment a keyword, with reposts moving the commenter up the queue.
Each of the three posts lists five outputs in near-identical wording, making the claim clear: situation, role priorities, three pain hypotheses, an opening observation and three discovery questions, all produced before the seller's day starts.
They reduce the argument to a before-and-after: the 12 hours before the call, not talent, decide which seller gets answered
One post compresses the preparation argument into a contrast between two sellers with equal ability.
Read more
The seller who is ignored enters the meeting to understand the customer's problem; the seller who is prioritized enters to confirm three hypotheses already formed about it.
In this framing, what separates them is what happened in the 12 hours before the call.
The post adds a consequence the longer posts state less directly: a rep who spends the first 15 minutes of the call on discovery signals to the prospect that preparation was missing, and the deal cools before any objection is raised.
The two-column structure contrasts the ignored rep with the prioritized rep line by line, then attributes the difference to the hours before the meeting rather than ability. It is the same idea as the longer prep post, delivered as a before-and-after instead of a walkthrough.
This post narrows the argument. Read alongside the 25-hours post, it restates the same claim in a shorter, sharper message, putting the consequence for meeting quality up front.
This post answers a newcomer's first question: is there a concrete method behind the sales posts, or only opinions?
Read more
It lays out the fullest argument in the set and shows the teaching pattern: one historical example, broken into numbered steps, each paired with a one-line reason.
Written in Portuguese, the post contrasts Prudential's agents in 1875 with B2B teams in 2026: no CRM, no automation, no SDR, just a process a salesperson could run in 30 seconds at the end of every meeting.
The model has four parts.
The number: always three specific names of real people the client can actually connect, not “someone who might benefit,” because a specific number produces specific names.
The moment: the end of every meeting, starting with the first, because the best time to ask is when the client has just seen value.
The obligation: Prudential agents could not end a meeting without asking — protocol, not a goal, since protocol happens every time and optional tasks happen only when the seller feels confident.
The follow-up: the agent returns to the referrer (“I spoke to João, thanks for the referral”), making them feel the referral was treated with respect and more willing to refer again.
The post closes by asking readers whether their team has a referral-request protocol and how it works.
For brands planning a campaign
For a sales-enablement brief, this is the most directly usable piece in the set.
It gives brands a teachable four-part routine — number, moment, obligation, follow-up — for a sponsored guide, workshop, or checklist.
Its closing question shows how Heros H. draws replies.
This post shows the operational problem Heros H. addresses and the tool they describe in response: a five-person sales team losing a full workweek to meeting preparation.
Read more
It lets newcomers judge whether the advice is grounded in a recognizable process.
The post opens with the gap: three minutes is what a salesperson should need to walk into a meeting prepared, while 25 hours is what a five-person team spends each week preparing.
Most of that time goes to the wrong place — scrolling the prospect's LinkedIn, glancing at the company site, reading CRM history — and the seller still enters without a clear hypothesis about which pain to prioritize.
Research that is not turned into a hypothesis is called wasted effort, and the meeting ends up being used to discover what the seller should already have known.
The agent described reads the previous night's calendar, identifies each meeting, and delivers a briefing per participant before anyone opens their computer, with five outputs: the company's current situation based on real sources, what the participant's role likely prioritizes, three specific pain hypotheses for that company, an opening observation based on a real signal and no pitch, and three ready discovery questions.
The post offers a setup guide for Claude with a comment-to-DM mechanic: connect, comment "Prep," receive the link, and reposts move up the queue.
A companion post carries the same five outputs under a "while they sleep" framing, so the two should be read as one idea rather than two.
For brands planning a campaign
The “Prep” comment-to-DM offer is a working lead-capture pattern, and the agent itself is built on Claude — an AI-tooling angle a brand could sponsor without displacing the sales message. Its five specific outputs also give a sponsor a ready-made structure for a co-branded template.
This frames the meeting-prep idea as a before-and-after contrast, making the case for the preparation habit especially clearly.
Read more
Read it after the longer prep post to see how the argument is compressed.
The contrast is set out plainly: a seller who is ignored enters the meeting to understand the client's problem, while a seller who is prioritized enters to confirm the three hypotheses already formed about that problem.
Both can be equally talented; what differs is what happens in the 12 hours before the call.
Most sellers do prepare, but in the wrong way — LinkedIn scrolling, a look at the site, reading CRM history — and 30 minutes later they know more about the company yet still have no clear hypothesis about which pain to prioritize.
They then spend the first 15 minutes of the meeting collecting what should have been collected earlier, the prospect notices, and the deal cools before any objection is raised.
The agent reads the calendar the night before and delivers the briefing before the workday starts, with the same five per-meeting outputs listed in the other prep posts, followed by the same guide offer: connect, comment "Prep," and reposting moves you up the queue.
For brands planning a campaign
The “12 hours before the meeting” framing is a sharper hook than the hours-saved angle and could anchor a sponsored campaign narrative. The comment-to-DM call to action also recurs across posts, giving a sponsor's message an established, familiar response pattern.
Meeting preparation should produce hypotheses, not just research3
An automated pre-meeting briefing agent3
Lead magnet through a comment keyword3
Referral generation as a fixed protocol, not an optional ask1
Contrast framing: ignored versus prioritized sales behavior1
Referral generation as a fixed protocol, not an optional ask
Using an 1875 Prudential example, Heros H. describes a referral channel built on four rules: ask for three specific names, ask at the end of every meeting, make the ask mandatory rather than optional, and close the loop with the person who made the referral.
Read more
They contrast a vague desire for referrals with a process that does not depend on a salesperson's mood.
Three named people, a fixed time (the end of every meeting), a mandatory protocol, and follow-up feedback to the referrer.
For brands planning a campaign
For sales enablement brands, this topic supports training content on referral process design, scripts for requesting named contacts, and CRM or coaching workflows that enforce follow-up. The four-part framework can be adapted into a workshop, checklist, or pipeline-generation campaign.
Meeting preparation should produce hypotheses, not just research
Heros H. argues that salespeople often spend prep time scrolling LinkedIn, checking the company site, and reading CRM history, yet enter the meeting without a clear view of which pain to prioritize.
Read more
They recommend forming three specific pain hypotheses before the call so the meeting confirms them rather than spending its first part on discovery.
Prepare before the meeting, identify the pain most likely to matter, and enter with concrete hypotheses to confirm.
For brands planning a campaign
Useful for sales training, enablement, and AI preparation tools. Brands can evaluate Heros H. for content that teaches reps to turn account research into specific hypotheses, opening observations, and discovery questions.
Across three posts, Heros H. describes an agent that reads the next day's calendar and delivers a per-participant briefing before the workday starts.
Read more
Each briefing includes the company's current situation from real sources, what the participant's role likely prioritizes, three specific pain hypotheses, a non-pitch opening observation, and three discovery questions. The posts frame the agent as reducing a five-person team's weekly preparation from 25 hours to about three minutes.
Night-before calendar scan, per-participant briefing, role-based priorities, three pain hypotheses, opening signal, and discovery questions.
For brands planning a campaign
This is the clearest product-adjacent topic. Sales technology and enablement brands can evaluate Heros H. for explainers, demos, or campaign content about AI meeting-prep workflows.
Contrast framing: ignored versus prioritized sales behavior
One post uses a two-column contrast to show how an ignored salesperson enters a meeting to discover the problem while a prioritized salesperson enters to confirm three hypotheses already formed.
Read more
Heros H. attributes the difference to what happens in the 12 hours before the meeting, not to talent.
Ignored rep: discovery in the meeting. Prioritized rep: three pre-formed hypotheses before the call.
For brands planning a campaign
This format works for short LinkedIn posts, sales kickoff talks, or training modules that show a before-and-after behavior shift. Brands can use it to make abstract preparation advice concrete.
The meeting-prep posts end with an offer to send a Claude Code setup guide in exchange for connecting and commenting a keyword, with an incentive to repost.
Read more
The guide is described as a 10-minute setup that automates briefing before each meeting.
For brands planning a campaign
This is a familiar LinkedIn lead-capture pattern. Brands can evaluate Heros H. for co-marketing or sponsored content built around a defined keyword, a gated resource, and a practical setup guide as the call to action.
Three of the four posts describe a meeting-preparation agent the author built with Anthropic's Claude and Claude Code, and offer a setup guide for running it in Claude Code.
Read more
The posts do not state sponsorship, employment, or a formal partnership with Anthropic.
A fourth post uses Prudential's 1875 agent referral process as a historical case study, not as evidence of a working relationship.
Ask about any other sponsor, affiliate, client, owned business, or investment relationship, none of which is mentioned in the posts.
Anthropic (Claude, Claude Code)
Mention
Three posts describe an automated meeting-preparation agent that reads the next day's calendar and creates a briefing for each participant, covering the company's current situation, likely priorities for each attendee's role, three pain-point hypotheses, an opening observation, and three discovery questions.
Read more
Each post offers a guide to configuring the agent in Claude Code, with setup described as taking 10 minutes. Claude Code is presented as the tool the agent runs in; the posts do not state any sponsorship, employment, or formal partnership.
Heros H. posts on LinkedIn in Portuguese for people who sell and manage B2B sales teams.
Read more
Two threads are worth working through.
Start with the referral post: it recounts how Prudential agents in 1875 built a referral channel on four fixed rules — ask for three named people, ask at the end of every meeting starting with the first, make the ask a required step rather than a target, and report back to the person who referred — and contrasts that channel with a team that merely wants referrals.
Then read the three meeting-preparation posts together: they repeat the same complaint and list of outputs, while showing the argument in increasingly compressed form, from a 25-hours-a-week breakdown, to a walkthrough of an agent that reads the next day's calendar, to a two-column contrast between a rep who is ignored and one who is prioritized.
Check the specific claim about the briefing: it provides company situation from real sources, what the participant's role likely prioritizes, three pain hypotheses, a non-pitch opening line, and three discovery questions.
The posts offer a Claude Code setup guide to readers who connect and comment a keyword; the creator describes the agent and guide as part of their own setup.
For a wider view of AI integrated into a revenue process, read Paulo D'Elia; for the management side of the same sales problems, read Diego Lorenzo Carvalho; for a different application of AI in sales operations, read Fernanda Oi.
Paulo D'Elia writes about putting AI into a B2B revenue operation as an operating layer rather than a prompt trick.
Read more
The same premise runs through Heros H.'s meeting-prep posts: settle the process before the tool can help.
Both describe agents doing concrete internal work.
The agent in their posts reads the next day's calendar and briefs each meeting attendee, while Paulo D'Elia's checks CRM hygiene against funnel stage, watches expansion volume and forecasting, reviews task queues and financial data, and flags client ad accounts losing performance.
Both write for people responsible for a B2B revenue operation, not readers comparing models.
Paulo D'Elia works higher up the stack.
The post about a GTM Engineering and Theory of Constraints course lays out a three-layer pyramid — RevOps integration between marketing, sales, and CS first, then revenue, then engineering and AI — plus five pillars that must exist before any agent: data architecture, one shared methodology, documented processes, a standard connected stack, and a named owner.
A roadmap-sprint-deploy-review loop is expected to produce results in 60 to 90 days.
Heros H. focuses on what one seller does before one meeting.
Paulo D'Elia also names the components behind their own agent setup and covers finance and ad accounts; Heros H.'s two threads cover a referral protocol and meeting briefings, offered as a setup guide for individuals.
Diego Lorenzo Carvalho writes B2B sales posts in Portuguese for managers, using the same structure Heros H. favors: a before-and-after of current practice followed by an arrowed or numbered list readers can act on.
Read more
Both argue that a fixed routine and ownership of the numbers, not talent or mood, should determine the outcome. Diego Lorenzo Carvalho wants a rep below quota to arrive at the pipeline review with their own funnel data and at least one root cause identified; Heros H. wants the referral ask and pre-call pain hypothesis to be mandatory steps, not things that happen only when a seller feels confident.
Diego Lorenzo Carvalho covers the sales manager's changing role as quota responsibility moves to the individual rep: servant leadership, developing specific skills, less pipeline policing and deal-by-deal checking.
The posts point readers to an operation review as a next step.
Heros H. stays at the level of one conversation, with a four-element referral protocol and a pre-meeting briefing agent; the call to action is a keyword-gated guide rather than a consulting offer.
Fernanda Oi writes about how AI performs inside a knowledge-work process, testing a tool on a real task and reporting what the output was actually good for — the same test Heros H. applies to a pre-meeting briefing.
Read more
Both judge AI output by whether it holds up: Heros H. checks whether pain hypotheses come from real sources; Fernanda Oi checks whether sources fall within the requested period and come from credible places. Both write step-by-step accounts readers can follow rather than general commentary about models.
Fernanda Oi focuses on research method, not sales: a side-by-side test of Deep Research in OpenAI and Gemini for consumer behavioral research, covering the research plan, source quality, three reports on the same theme, and a cross-report analysis.
Heros H. focuses on sales execution, with posts that end in a gated setup guide.
Fernanda Oi's posts read more like a practice diary, including one about a UX research team's public recognition, so readers who come for AI in sales will find a different kind of work.
Use Heros H. as a narrow, topic-fit test for Portuguese-language B2B sales teams, not as a broad-reach placement.
Read more
The content addresses referral generation and meeting preparation, matching campaigns focused on those goals.
The only measured audience figure stated is a LinkedIn profile snapshot listing 2,370 followers as of October 11, 2026.
The four posts, published April 9–24, 2026, are written in Portuguese, indicating a Portuguese-speaking sales audience.
Selected examples of the topical fit include the Prudential referral-process post and the meeting-preparation agent posts.
Before committing budget, ask them for a recent audience survey or platform analytics report covering geography, age, gender, and job attributes, along with recent performance results for comparable referral and meeting-preparation topics and formats.
Heros H. shares sales-method content, including a referral process modeled on the Prudential agent protocol: ask every client for three named contacts at the end of every meeting, make the ask mandatory, and follow up after each referral.
Read more
Three posts promote an automated pre-meeting preparation agent that turns calendar entries into per-participant briefings with pain hypotheses, an opening observation, and discovery questions.
The only commercial call to action is a direct-message request for a setup guide to configure the agent in Claude, gated behind connecting and commenting a keyword.
This is a lead-generation offer for a guide, not a sponsorship package; it includes no price, deliverables, or usage terms.
The posts disclose no sponsor policy or partnership and publish no format, rate, or official partnership contact.
Ask whether they accept sponsors and request their rates, deliverables, usage terms, and preferred inquiry route.
Sales-enablement campaign — a B2B sales-enablement company selling to Portuguese-speaking sales teams, whose goal is stronger referral generation and better meeting preparation.
Read more
Decision: the clearest fit in the posts here, on topic rather than reach.
Heros H.'s most developed post addresses referral generation directly, setting out a four-part protocol: ask for three specific names rather than a vague “someone who might benefit”; make the ask at the end of every meeting, starting with the first; treat it as mandatory protocol rather than an optional goal dependent on the seller’s confidence that day; and return to the referrer afterwards to close the loop and encourage future referrals.
The structure can be used as-is for a sponsored checklist, workshop segment, or coaching module, with a stated rationale for each rule.
Three meeting-preparation posts describe a pre-meeting briefing with five outputs: the company's current situation, drawn from real sources; what the participant's role likely prioritises; three specific pain hypotheses; an opening observation based on a real signal, with no pitch; and three ready discovery questions.
Those outputs provide a template skeleton for an enablement buyer.
The posts are written in Portuguese, pointing to a Portuguese-speaking readership.
The only published audience figure is a LinkedIn profile snapshot listing 2,370 followers, with no engagement, view, or subscriber data; treat this as a narrow test placement, not a broad-reach buy.
Heros H. already ends the meeting-preparation posts with a call to action: connect and comment “Prep” to receive a Claude Code setup guide, with reposts moved up the queue.
The sponsor's offer should fit that response pattern or attach to the guide rather than compete for the same comment thread.
When to choose a specialist
English-language awareness campaign — an English-language enterprise software brand outside the sales-tools category, planning a high-reach awareness push for a general business audience, with verified outcome claims and a priced sponsored format booked up front.
Read more
Decision: poor fit based on the posts here.
All four posts are in Portuguese and show neither English-language content nor a non-sales audience.
The only measured audience figure published is 2,370 LinkedIn followers, with no engagement or view data; this does not support a reach-led buy.
The commercial requirement is also unmet: the posts contain no sponsor policy, disclosed sponsorship, media kit, rate card, or published format.
Ask for a rate card and sponsorship details before planning a priced package.
The verification requirement fails too.
The central performance claim—that a five-person team's weekly meeting preparation drops from 25 hours to about three minutes—is the creator's own description of the process, with no independent measurement, so a campaign requiring validated numbers cannot use it.
The prep posts already route readers to the creator's gated guide, so a sponsor's separate lead magnet would compete for the same comment replies.
A worked campaign example
Campaign angle for the sales-enablement campaign, built on the referral-protocol post.
A sales-enablement vendor sponsors a “referral protocol” toolkit that turns the four rules into something a sales manager can run on Monday morning.
The package includes a one-page protocol card with four boxes—the number (three named contacts), the moment (end of every meeting, from the first), the obligation (protocol, not a goal), and the follow-up (return to the referrer and say what happened)—plus a short recorded walkthrough with Heros H.
They take one rule and show what a rep actually says at the end of a call.
Run the placement as a follow-up to the Prudential post: the post establishes the argument, the sponsored toolkit gives readers something to take away, and the seller's comment-to-DM habit preserves the response pattern the audience already recognises.
Ask reps to try the protocol on their next three meetings and send back the number of names they actually collected.
Before committing budget, ask Heros H. for audience geography and job attributes for posts on referral and meeting-preparation topics, and performance data for comparable posts at that depth; neither is published here.
Judge the placement by referral asks completed per rep and the share of readers who complete the blank card, not impressions.
Do not present the 25-hour and 3-minute figures as measured results; they are the creator's own description of the process.
Choose Diego when the challenge is improving sales managers’ pipeline reviews and coaching—not preparing an individual seller for a meeting.
Read more
In their post on pipeline reviews, they argue that a rep who misses quota should bring their own funnel analysis and a plausible root cause to the review.
Their work offers a useful starting point for manager-coaching or pipeline-review content.
These posts focus on how managers and sellers share responsibility for diagnosing performance. A campaign about referral asks or meeting preparation would need a different content foundation.
Choose Paulo when the question is how AI should fit into a company’s operating system.
Read more
In his account of AI in daily operations, he describes agents monitoring CRM quality, forecasts, task progress and other recurring work—not just answering prompts. His GTM Engineering reflections make the prerequisite clear: connect teams and establish sound data, processes and ownership before adding automation.
Paulo’s examples focus on systems and operations, making them better suited to a RevOps or AI-adoption discussion than a practical sales-rep toolkit. If you need a rep-facing referral protocol or meeting-briefing outputs, ask for examples tailored to those tasks.
Choose Fernanda when the campaign is about research practice rather than sales execution.
Read more
In her comparison of AI research tools, she tests the same prompt in two products and compares source quality, adherence to constraints and depth of synthesis.
She then checks whether separate reports can be cross-analysed for patterns and outliers.
The post suits a campaign about research grounded in findings or research workflows.
Fernanda’s examples focus on UX research rather than sales execution.
Her tool comparison may inform how a team gathers information for account research, but it does not offer a sales enablement method.
Four complete Portuguese-language LinkedIn posts published April 9–24, 2026, cover referral generation and meeting preparation; three repeat the meeting-briefing-agent idea.
The agent and guide are described by Heros H. in the posts, not independently evaluated.
The posts do not establish earlier signature work, other channels, or sponsorship terms.