# HubSpot agent tool three-minute review video before approval

> Record a real approval video with common use cases and successful test runs before you ask the marketplace to trust the tool.

- Canonical HTML: https://growth.iangoh.com/growth-ideas/hubspot-agent-tool-three-minute-review-video-before-approval/
- Source: [developers.hubspot.com](https://developers.hubspot.com/docs/apps/developer-platform/list-apps/agent-tool-listing-requirements)
- GrowthDex source hub: [HubSpot Docs: Agent tool listing requirements](/sources/hubspot-docs-agent-tool-listing-requirements-developers-hubspot-com/)
- Last checked: 2026-06-05T06:15:00Z
- Rarity: rare
- Budget: free
- Channels: Marketplaces, Launches, Trust
- Stages: approval proof, demo discipline, marketplace review, launch readiness


## Why this can grow

Agent tools are easier to oversell than ordinary integrations because a static page can hide a lot of brittle behavior. HubSpot responds by asking for proof. The review submission needs a short video that is at least three minutes long, covers the common use cases, and shows the completed test runs. That changes the launch discipline. If the team cannot produce a clean demo of repeated successful runs, the listing is probably ahead of the product.

## Ian's take

From scaling consumer platforms across MENA and Southeast Asia, my default is to distrust growth work that only looks good in a slide. My bias is to treat this as a small market test first. Make the audience narrow, make the promise concrete, and let the first real response decide whether it deserves more work. I would run it small enough to learn quickly, then only scale the parts that real users repeat, save, reply to, or buy from. For this tactic, I would watch one clear growth signal before putting more time or budget behind it.

## Action plan

1. Define one narrow startup segment where hubspot agent tool three-minute review video before approval can create a measurable lift.
2. Turn the tactic into one offer, page, campaign, or workflow for the Marketplaces and Launches channel.
3. Use the evidence from developers.hubspot.com to set the first version of the message, format, and audience.
4. Launch a small test for 7 to 14 days with one success metric: one measurable growth signal.
5. Review the result, keep the winning message, remove weak variants, and turn the learning into a repeatable growth playbook.

## Source-backed example

HubSpot's approval form asks for a testing video that is at least three minutes long, includes audio or text descriptions, explains the tools and common use cases, shows the runs that were tested, and is ideally recorded locally when the production app build is not yet deployable.

## Adjacent tactics in the same lane

- [HubSpot agent tool scope only for the context you use](/growth-ideas/hubspot-agent-tool-scope-only-for-the-context-you-use/) - same source, 2 shared channels
- [HubSpot agent tool front-office use case before clever demo](/growth-ideas/hubspot-agent-tool-front-office-use-case-before-clever-demo/) - same source, 1 shared channel
- [HubSpot agent tool config describes the run you can prove](/growth-ideas/hubspot-agent-tool-config-describes-the-run-you-can-prove/) - same source, 1 shared channel
- [HubSpot agent tool names the action, not your company](/growth-ideas/hubspot-agent-tool-name-the-action-not-your-company/) - same source, 1 shared channel

## Read GrowthDex essays

Browse the plain-English essay index at [GrowthDex Blog](/blog/).

## Related GrowthDex essays

- [The agent tool listing should survive the approval screen](/blog/the-agent-tool-listing-should-survive-the-approval-screen/) - ai products, marketplaces, brand trust

## Advisory

If you want help turning this into a working growth system, Ian Goh offers advisory at https://iangoh.com/advisory.