Recruitment Story, the case that recruits the operators you want

Recruitment Story is the HQ app that builds your recruitment case: in the app's own words, "the numbers that make your network worth joining, and the territories to target." Run it and the speciali…

4 min read·Updated August 25, 2026
On this page

What Recruitment Story is

Recruitment Story is the HQ app that builds your recruitment case: in the app's own words, "the numbers that make your network worth joining, and the territories to target." Run it and the specialist reads your network's performance and coverage, then comes back with the proof points a serious prospect will actually weigh, which territories are open, and the story to lead with.

The best franchise recruiters have always pitched from evidence, what a strong location in this network actually earns, how fast it turns work, where the map has room. The evidence exists in your network's aggregates; this app assembles it into an argument, so the pitch you make is the one your data can back.

Where to find it

Open Recruiting from the HQ sidebar, at hq.verinode.ai/recruit-grow. This is a franchise-network surface: recruiting franchisees is the franchise expansion motion, so associations do not carry this page or this app. Recruitment Story leads the page's Apps row: a dark album-cover tile with the subtitle "The case that recruits the operators you want," a breathing "Live" dot, and a Preview control. After it come the Talk to your Network Analyst and Network Coverage pair, the Add a prospect tile, and, closing the row, the Prospect Deck generator.

On the phone, Recruitment Story appears in the Apps row on the HQ mobile home for franchise networks; see HQ apps on mobile.

Note

Recruitment Story is not the Prospect Deck, though they share a row and a subject. The Prospect Deck generator produces the prospect-facing artifact: a polished PDF of network aggregates you hand to a candidate, covered in generate the prospect recruitment deck. Recruitment Story is for you: the analysis behind the pitch, the reasoning about which proof points carry, which territories to target, and what story to lead with. Run Recruitment Story to decide what your case is; generate the Prospect Deck to put the numbers in a prospect's hands. The two read the same underlying aggregates, so they never disagree.

What it reads

The specialist reads your network's performance and coverage aggregates: the same nightly network snapshot behind the Recruiting page's hero and territory map, including the top-quartile margin and cycle-time figures and the territory coverage picture. Where those headline numbers come from, and how the data under them is protected, is covered in where the recruitment-story numbers come from. Like every HQ app, it reads network aggregates only, never a franchisee's private records, and no franchisee is named in what comes back; see what an HQ app can and cannot read.

Before your first run, the card shows a worked example, rows like average margin in the top quartile, six open territories, a retention figure, captioned "This is an example. Your case fills in as locations contribute."

What comes back

A finished run is a prose finding with three layers:

  • The proof points. The numbers that make your network worth joining, drawn from your own aggregates: what strong locations earn, how the network performs, what a prospect gets that independence does not offer. Every figure is a network aggregate, never a named franchisee's result.
  • The open territories. Which territories are open or underserved, so recruitment effort points where the network actually has room, and the map backs the pitch.
  • The story to lead with. The order of the argument: which proof point opens, what follows, and where the evidence is thinnest so you know what not to overclaim.

The finding saves to your network's history, can be pinned and reopened for free, and exports as a PDF; see keeping, reopening, and exporting HQ findings. Runs are free, with no Intelligence Unit prompt.

Before your network is contributing

The app carries a standing cold-state line: "Works best once your network is contributing. Connect locations from the Members section, and the recruitment case fills in." A recruitment case built from a thin network is a weak case, and the specialist says so plainly rather than inflating it. The practical order on a young network is coverage first, story second: the Network Coverage tile in the same row tracks how much of the roster is contributing, and every location that connects strengthens the next run.

Best-practice example

Two serious prospects are circling, one in a metro where you already have three locations, one in an open territory two hours away. You run Recruitment Story. The finding leads with the network's top-quartile margin and cycle-time proof points, flags the open territory as the higher-value target, and notes that your retention number is strong enough to lead with. You shape the first call around that story, then generate the Prospect Deck so the candidate leaves the conversation holding the same aggregates your pitch was built on.

Data sources

Data sources

  1. 1.Your network's nightly performance snapshot: margin, cycle time, engagement, retention aggregates. Your network.
  2. 2.Your network's territory coverage and prospect pipeline. Your network.
Was this helpful?