Pitchgrove

The primary buyer

Three buyers who actually buy this engagement.

The boutique retainer sells to one role per company — the role that owns the revenue number and the weekly review call. Three versions of that role show up in our pipeline. Each one buys for a different reason; each one needs the same motion to actually land.

VP Sales

First sales leader post-Series A

Inherited a motion that hasn’t been proven yet. Building outbound capacity from scratch while the team is still founder-led — and the calendar stays empty for the wrong reasons.

Surface signal — New VP Sales hire inside 90 days, ICP in motion, weekly review capacity, AE postings live.

Why they buy — Wants a working motion on day 60 — not a tool to staff, not a seat license to absorb. The boutique engagement hands them replies, meetings, and a weekly call they can actually run their forecast against.

Head of RevOps

Operating partner to the CRO, owns the data layer

Sitting between a sales team that needs pipeline and an exec team that wants attribution. The motion is half-built: a CRM and a sequence stack in place, but the boutique list and the handcrafted opener never landed.

Surface signal — CRM and sequence stack in place, ICP-locked territory map exists, attribution loop closes weekly.

Why they buy — Wants the meetings on the calendar and the data layer uninterrupted. Pitchgrove runs the engagements alongside their stack — no tool to swap in, no new dashboard to reconcile at month-end.

Founder wearing sales

Series A founder, founder-led to team-led in flight

Still carrying the first meetings themselves. The outbound motion is the founder’s calendar, the founder’s notes, the founder’s pipeline. The next hire should not inherit a blank slate.

Surface signal — Series A close in the last 12 months, no VP Sales in seat yet, founder still on the first calls.

Why they buy — Wants an outbound motion that survives the first sales hire. The engagement is run with the founder, and the handoff to the new VP is part of the brief — not a problem to solve six months in.

Fit signals

Signs you're a fit for the boutique engagement.

Seven conditions the buyer-side stack needs to clear before the engagement is worth starting. If you can check five of seven on the first call, the model is structurally a fit — the rest is timing, not diagnosis.

ACV north of $15k and a 30–180-day sales cycle.
Cycle length drives the territory size and the cadence depth. The boutique model is structured for deals that close inside a quarter — not for low-ACV / high-volume motions.
A named ICP, locked in writing, with disqualification criteria.
The ICP-lock call in week one is the first deliverable, not a discovery deck. If the list shape is still in motion, the engagement is not ready to start and a referral is the honest move.
A CRM and a sequence stack already in place.
Outreach, HubSpot, Apollo, or a comparable motion. The engagement hands off meetings into the stack you already operate — it does not ask you to swap in a new one.
Capacity to run a 45-minute weekly review call.
The weekly working call is the editorial rail of the engagement. Hot replies are reviewed, territory is rebalanced, and the cadence is reset against the data that surfaced in the last seven days.
AEs ready to absorb meetings and book the next step.
The boutique retainer books meetings into an AEs’ calendar. The motion only converts when the AEs can pick up the meeting, qualify against the ICP, and run a discovery the second session.
A compliance posture that respects LinkedIn and state-level rules.
California, Utah, and the evolving patchwork. The engagement works inside those boundaries; it does not run on accounts that put your program at risk three quarters in.
Territory overlap with a Series A–C B2B SaaS stage and a 20–200 headcount band.
The retainer is tuned for Series A–C B2B SaaS companies in the 20-to-200 headcount range. Pre-PMF, agencies, and sub-20 teams fall outside the model — see the section below.

Honest boundaries

Four profiles we say no to on the first call.

We run a small roster intentionally. The four profiles below map to a structural mismatch with the boutique retainer — not a pricing objection. We'll surface it on the first call so neither side burns three weeks on a motion that was never going to land.

Not built for

Pre-PMF teams. No ICP locked yet.
If the ICP is still in motion — no disqualification list, no territory map, no repeatable conversion motion — the boutique engagement has nothing to anchor to. The first call is the honest moment to redirect, not a discovery deck to write together.
Solo founders. No weekly call counterpart.
The retainer runs on a 45-minute weekly review call with a buyer-side counterpart. A solo founder has no one to sit in that chair with us — and no AE to absorb the meetings we book. The motion cannot run end to end without both.
Agencies. Reselling cycle, not end buyer.
A boutique engagement sells to one buyer per company. An agency is in a reselling cycle — the agency runs a campaign for an end client, and the end client’s buyer is not in the room. We are not a vendor-in-a-stack; we are the engagement.
Companies under 20 employees. Not enough outbound surface.
A 40–80-account boutique list needs enough territory to actually map against. Under 20 employees, the surface area is too small to justify a hand-built list, and the weekly call quickly turns into a founder coaching session — not the engagement we sell.