Route by anything
CRM ownership, territories, form answers, firmographics, account tiers, rep capacity, custom fields, or your own API response.
Qualify, route, and book every inbound buyer with the right rep, instantly. Powerful routing rules, readable by actual humans.

Hot Potato handles the messy middle between “someone filled out the form” and “the right rep has a meeting.”
See the full route →Enterprise East
Build rules around CRM ownership, territory, company data, rep availability, or whatever your GTM motion requires. Then see exactly why every lead went where it did.
// enterprise inbound
when(lead.employees >= 500)
.territory(lead.region)
.prefer("account_owner")
.fallback("weighted_round_robin")
.require("calendar_available")
.route();
Built for the inbound motion you already have, without forcing your team into an enormous workflow builder.
CRM ownership, territories, form answers, firmographics, account tiers, rep capacity, custom fields, or your own API response.
Show the right rep's availability while the buyer is still on your site.
Update your CRM with ownership, meeting details, route metadata, and the reason behind the decision.
Searchable route logs turn “why did this lead go there?” from a Slack archaeology project into a ten-second answer.
Hot Potato reads the data you already trust and writes the route back where your team already works.
Read the docs ↗The core stays open source. Run it yourself, or use Hot Potato Cloud when you don't feel like owning another server.
For builders and small teams running Hot Potato themselves.
⌘ Get the repoFor GTM teams that want the router without running the router.
Start with Hot Potato →For larger teams with tighter controls and stranger routing problems.
Contact us →The routing engine lives in the open. Inspect it, extend it, self-host it, or contribute the weird integration your company somehow still depends on.
harrisonoconnorhover/HotPotatoPublicgit clone https://github.com/harrisonoconnorhover/HotPotato.git
Your form already did its job. Hot Potato handles what happens next.