Replace the next-steps email with an auto-created sales room in HubSpot
When a deal reaches a chosen stage, this setup creates a shareable page for the buyer with the value proposition, team, next meeting and next steps, and suggests updates from calls and emails. Champions get one link to share internally.
Paste this into ChatGPT, Claude or your agent tool. See the prompt
- Content and Collateral
- beginner
- AE
- Sales leader
- RevOps
- Category
- Content and Collateral
- Difficulty
- Beginner
- Est. cost
- Not stated by source
Works with
Problem
After a demo, the next-steps email buries value props and attachments in a thread, the champion struggles to sell internally, and stakeholders nobody has met stall the deal.
Setup
A HubSpot workflow creates an Arrows sales room from a template when a deal reaches a set stage. The template holds blocks for a tailored value proposition, the team on both sides, the next meeting, deal milestones and next steps. Arrows reads HubSpot data, including call summaries synced from the call recorder, to extract next steps and suggest relevant content and milestone updates for the rep to accept. A task reminds the rep to send the room link, and room engagement is tracked on the deal record.
Prompt
Starter prompt by The GTM Agent Weekly, written from the setup described on this page. It is not the source's own prompt; see the source link below for their write-up.
# ROLE
You turn a deal's call history into the content of a short buyer-facing sales room page,
replacing the usual next-steps email. A rep reviews everything before the buyer sees it.
# INPUTS
- {{DEAL}}: the HubSpot deal record (stage, amount, contacts, close date).
- {{CALL_SUMMARIES}}: call summaries synced from the call recorder onto the deal.
- {{CONTENT_LIBRARY}}: case studies, one-pagers and docs the rep may share.
- {{TEMPLATE}}: the room sections: value proposition, team on both sides, next meeting,
milestones, next steps.
# TASK
1. Read the call summaries. Pull out the buyer's goals, concerns and anything agreed.
2. Fill each template section in plain language, two to four lines each:
- Value proposition: tied to the goals the buyer stated, in their words where possible.
- Team: names and roles from the deal contacts and calls.
- Next meeting: date and purpose if agreed; otherwise "to be scheduled".
- Milestones and next steps: owner and due date for each, only if stated on a call.
3. Suggest up to {{MAX_ASSETS}} assets from {{CONTENT_LIBRARY}}, each with one line on why it fits.
# OUTPUT
The filled sections, then "Suggested assets", then "Needs rep input" listing anything missing.
# GUARDRAILS
- Keep it short; long rooms go unread. Essentials only.
- Do not invent commitments, dates or pricing. If a summary is thin, say so under "Needs rep input".
- Nothing is shared with the buyer until the rep accepts it. Replace every {{PLACEHOLDER}} before running. Works with any capable LLM and runner.
Tools
Steps
- Make sure call summaries from your recording tool sync into HubSpot.
- Build a short room template: value proposition, team, next meeting, milestones and next steps.
- Add a HubSpot workflow that creates the room when a deal hits the chosen stage, plus a task for the rep to send it.
- Review AI suggestions for next steps and content, and accept the ones that fit.
- Track which stakeholders view the room and report on it from deal properties.
Results
Sponsored newsletter issue with a customer quote saying stuck deals moved faster. Self-reported, no data shown.
What goes wrong
Gotchas
- Suggestions are only as good as the call summaries synced into HubSpot, which the author calls out before setup.
- Long templates go unread; the author advises keeping them to essentials and letting suggestions add the rest.
- This issue was sponsored by the vendor, so treat the claims as marketing. (editor note)
Get 5 like this every week, free.
Real agent setups with sources and failure modes, in one short weekly email.
Free. One email a week. Unsubscribe anytime.
Source and credit
Stuart Balcombe, ConnectedGTM (sponsored by Arrows) · newsletter
Source dated 2025-02-07 · last reviewed 2026-10-11. Summarized in our own words; see the source for details.