LeadGrow Client workspace: Opus Research pack v1 5 August 2026

Role intelligence, by consequence.

The market research behind the Opus campaigns, the angles we intend to run, and the short list of claims we need substantiated before any of them ship.

01  /  The position

Sell the delay, not the wage differential.

Every competitor in this category already claims fast shortlists, vetted global talent, timezone overlap and 40 to 80 percent savings. Athyna, Nearshore Business Solutions, Somewhere and Scale Army all say a version of it, and several publish more customer proof than Opus does today. Savings is table stakes, and leading with it invites a price comparison Opus should not want to win.

The defensible territory is the gap between role approved and independent output. Applicant volume is abundant. What is scarce is a small number of people who can own the outcome, exercise judgment, communicate in the buyer's operating context, and use AI in the real workflow rather than listing it as a skill. That is a verification problem, not a sourcing problem, and it is the one Opus is actually built to solve.

The expensive part of an open seat is not the posting. It is the value already waiting behind it, the expensive people temporarily covering it, and the forecast nobody can trust while it stays open. The organising idea for every campaign in this pack

The metric we build copy around

Vacancy-to-Productivity Exposure is the value delayed, leadership capacity consumed, and risk accumulated each week from role approval until someone owns the result independently. It beats time-to-fill because a started hire can still be a net drain on the manager. It beats salary savings because it counts blocked output rather than payroll.

Critically, the buyer supplies the business inputs. Public data proves the role exists and what it owns. It cannot reveal what the company is actually losing, so every number we put in front of a prospect stays an editable scenario, never an assertion about their P&L.

02  /  The consequence chain

Three things that happen while the seat sits empty.

Across more than fifty current first-party job postings, the same three consequences recur regardless of function. They are the raw material for every subject line and first sentence we write.

Consequence What it looks like Why it lands with the buyer
Value waiting to be realised Demand, pilots, signed contracts, installed accounts, invoices or acquired capabilities wait for an owner. Revenue has already been created. The buyer is not being asked to believe in upside, only to stop paying for delay.
Work transferred to expensive teams CROs maintain integrations, AEs research accounts, product engineers handle one-off deployments, CSMs project-manage onboarding. The vacancy is a capacity tax, not an empty box on an org chart. The cost is visible on people the buyer already knows are overloaded.
Forward visibility weakened Pipeline, launch readiness, adoption, renewal risk, cash or integration progress becomes harder to forecast. Executives feel this one personally. The miss shows up late, which is the part that damages credibility.

The sharpest line per role family

These are compact enough to carry a first line on their own. Each is framed as a hypothesis, never as a claim about what we know is happening inside the account.

Role The line
GTM EngineerYour CRO is still the integration layer, and reps are doing data work instead of selling.
Forward-Deployed / Solutions EngineerYour best pilots are stuck in demo purgatory while product engineering becomes the integration queue.
Implementation ManagerYour best CSMs are project-managing onboarding instead of growing accounts.
Enterprise AM / Strategic CSMIf leadership discovers account risk at renewal, the account was unmanaged months earlier.
Revenue Operations ManagerThe revenue teams exist, but leadership is still reconciling the operating model before it can trust the forecast.

03  /  Pain-qualified segments

Six ways to find a company that already knows it has a problem.

Scored on pain intensity, expected conversion and sales efficiency. Read the ranking as a prioritisation tool, not a market size.

Confirmed The modelled revenue column uses a $39,000 first-year value per seat, which matches Opus pricing of a $3,000 placement fee plus roughly $3,000 per month for one dedicated professional. The account pools are reachable-scenario estimates for comparing segments against each other, not counts of real companies.

Rank Segment Score Modelled Visible trigger
1 Failed search or early-attrition refill 92 $13.0M Role disappears and reappears, or the description is materially rewritten
2 Founder or COO capacity ceiling 89 $33.7M First or founding role, broad mandate, executive still owns the work
3 Approved critical seat in a lean scale-up 85 $16.7M Selectively approved seat with an explicit metric and multiple systems
4 PE value-creation clock 78 $4.25M Acquisition or verified sponsor ownership plus an operating role
5 Ecommerce throughput bottleneck 76 $16.5M Channel, catalogue or seasonal change alongside a relevant opening
6 AI mandate without a verified operator 71 $8.85M Role explicitly owns AI agents or LLM workflows, with no visible assessment standard

The PE figure excludes multi-seat and portfolio expansion, so it materially understates what a won sponsor relationship is worth. Track that segment on account value, not per-logo value.

The two we start with

Failed search or refill

92
Why it converts
The buyer has already paid for a miss. Pain is proven, the downside is remembered, and our guarantee is suddenly relevant rather than abstract.
How we detect it
Daily snapshots of the employer's own job board. A repost is the same normalised title returning after at least seven absent days, the same role under a new ID, or a description that comes back materially rewritten.
The opening move
A one-page failure-mode scorecard built from the diff between the two public versions: outcome, 30-day deliverable, autonomy test, interview evidence.
The hard line
Do not claim We say the public mandate changed. We never say or imply the last hire failed. We have no visibility into anyone's performance and must not sound like we do.

Founder capacity ceiling

89
Why it converts
Largest reachable pool and the shortest buying chain in the set. One person can decide, and that person is personally feeling the cost every week.
How we detect it
First-of-function or build-from-scratch language, a broad cross-functional mandate, and a public milestone that visibly depends on the role.
The opening move
A vacancy-exposure worksheet with editable weekly values plus a 30/60/90 ownership plan, so the founder can decide whether to narrow, accelerate or sequence the role.
The risk
Hypothesis Role definition is often vague at this stage, which causes search churn. Qualify out anyone describing a future hire rather than an approved one.

04  /  Targeting

Twenty-five role families, scored on the mandate rather than the title.

A title starts discovery. What makes an opening worth a candidate-led introduction is the business conversion it owns. We store a normalised family and the raw title, match on synonyms, then score the description separately.

Tier A  ·  15 roles

Monitor continuously. Campaign immediately when consequence signals appear.

  • GTM Engineer pipeline created
  • Revenue Operations Manager forecast accuracy
  • Sales Operations Manager selling capacity
  • Marketing Operations Manager demand conversion
  • Growth Engineer / Ops activation
  • Implementation Manager time to value
  • Technical Implementation Mgr launch time
  • Enterprise Account Manager net revenue retention
  • Strategic Account Manager account growth
  • Enterprise CSM gross and net retention
  • Forward-Deployed Engineer production adoption
  • Solutions Engineer technical win rate
  • Customer Success Engineer technical adoption
  • Technical Account Manager technical health
  • Collections / AR Manager cash conversion

Tier B  ·  7 roles

Monitor continuously. Campaign only when the mandate is genuinely outcome-owning.

  • Key Account Manager concentrated revenue
  • Renewals / Expansion Manager on-time renewal
  • Partner / Channel Manager partner pipeline
  • Onboarding Manager first value
  • Solutions Architect deployment readiness
  • Sales Enablement Manager seller ramp time
  • FP&A Manager forecast reliability

Tier C  ·  3 roles

Event-triggered only. The title alone is too noisy to act on.

  • SDR / BDR qualified pipeline
  • Business Operations Manager throughput
  • Ecommerce Operations Manager commerce conversion

Tier C is not low value. An SDR posting becomes high priority when it is the first SDR, carries a pipeline number, or sits beside a GTM engineering opening.

The posting score

One hundred points, so monitoring does not degrade into title scraping. A campaign fires at 75.

Signal in the job description Points
Explicit commercial, cash, customer or throughput metric20
First, founding, build, unify or transform mandate15
PE backing, acquisition, funding, launch or expansion within 12 months15
Cross-functional ownership across three or more functions15
Numeric scale: portfolio, SLA, concurrent load, quota or target10
Executive or specialist workload implied explicitly10
Reposted role or materially changed description10
AI or automation tied to a named production workflow5
BandAction
75–100Pain-qualified. Campaign now.
55–74Monitor and enrich until a second independent signal appears.
35–54Retain for role-volume analysis only. No personalised outreach.
< 35Generic hiring demand. Suppress.

Where the signal comes from

Five public layers, with employer job boards as the anchor because they are the only source that proves work needs an owner right now. Greenhouse, Lever and Ashby all publish their job board data without authentication. Around that we layer SEC Form D filings for recent capital events, FTC merger notices and verified sponsor portfolio pages for acquisition clocks, first-party websites and archived snapshots for operating change, and public GitHub activity for the technical subset.

The gate is two signals. A relevant live role plus one independent corroborator, both with the source URL and observation timestamp preserved. Funding alone is capacity, not pain, and will flood the list with weak accounts if we let it through on its own.

05  /  The angles

Candidate-led on the way in. Consequence-led on the follow-up.

The house style is a short, conversational, candidate-first introduction. That is a deliberate choice: a specific person the reader could interview is more concrete than a diagnosis of their business, and it opens without presuming to know what is broken. The consequence framing does real work, but it belongs on the second and third touch once a conversation exists.

Variables stay visible as literal tokens until the evidence behind them exists. If we cannot fill {CANDIDATE_PROOF} with something true, the email does not send.

Draft one, first touch

Email 1 Subject: intro for you
{FIRST_NAME} I've got a GTM engineer who's an expert in everything from Clay to {THEIR_CRM}, based in South America. Thought they might be a fit since {ROLE_SPECIFIC_MANDATE}. They've also completed our six-module AI certification. Would you wanna learn a bit more about them?

Draft two, follow-up

Email 2 Follow-up in thread
Meant to mention {FIRST_NAME}, we place proactive, AI-certified LATAM talent. 97% stick around for over a year, but we still offer a lifetime replacement for the few that don't work out. We keep a constant pulse on GTM talent from orgs like x and y. I've got a few other relevant intros. Would you like to review one?

Draft three, alternate opener

Email 3 Sales-team variant
{FIRST_NAME} are you considering remote talent for your sales team? I've got an intro to a former account executive who ran sales for two Series C funded startups. No stranger to {WHAT_THEY_SELL}. Open to reviewing their resume?

Draft four, the proactivity proof

Email 4 Why this person
Oh yeah, the reason they caught my eye {FIRST_NAME} is because I saw them being extremely active in a few relevant sales group chats. On our side that's how we separate the growth-minded doers from a more laid back hire. We've already screened them and they've completed our AI certification. Can I share a bit more info about them?

The consequence-led architecture

For the second and third touches, and for any account where the segment signal is strong, one shared structure with role-specific variables. This is preferable to five unrelated sequences because it gives every campaign one consequence, one transferred-cost detail and one proof-oriented offer.

Template Shared campaign architecture
If {role_exposed_workflow} is still sitting across {teams_absorbing_work}, the open {role} is likely costing more than vacancy time. It is delaying {realized_outcome_delayed} and keeping {forward_metric_exposed} harder to trust. Opus assesses candidates against that exact handoff and can show you three {role_archetype} operators worth interviewing in five days, including evidence of what they have built and the first outcome they should own.

Required framing "If" is doing essential work in that first sentence. The consequence is a hypothesis we are offering, not a diagnosis we are asserting. Conditional language stays in every filled version.

Six campaign tests

CampaignSegmentPermissionless value we lead with
Reopened Seat DiagnosticFailed search / refillRole-version diff and a failure-mode scorecard
Still on Your DeskFounder capacityFounder capacity and vacancy-exposure map
One Approved SeatLean scale-upCritical-seat evidence scorecard
Portfolio Execution MapPE value-creationPortfolio vacancy-to-value map from public roles and events
Ecommerce BottleneckEcommerceOperating-complexity to role-priority map
Applied AI Work SampleAI mandateRole-specific workflow assessment and governance rubric

06  /  Rules of the road

What every email has to survive before it leaves the building.

  • Never reveal the posting. The job ad is private research evidence that told us where to look. It is never a fact we disclose, and copy must not imply we have been reading their careers page.
  • One observed fact, one framed hypothesis. Anything we did not see publicly gets conditional language: usually, often, looks like, if this is still sitting with.
  • Define AI fluency by the workflow. Name the process, the safeguards and the metric. A badge or a certification claim ages badly and invites a question we cannot answer.
  • Savings comes last, if at all. Only after quality, management load, compliance and retention have been normalised. It is never the category claim.
  • No invented proof. No fabricated availability, certifications, outcomes, employers or private knowledge.
  • No named candidate in outbound until interest, availability, compensation, references and permission to represent are confirmed. An open-to-work badge is a lead, not consent.
  • No em dashes, no banned words in outbound copy.

Claim grading

Every sentence in every campaign carries one of these five states. The operator's last check before send is to name the state of each claim.

Verified fact

Source-backed and accurately scoped. A public filing, a first-party page, an observable posting.

Approved proof

Three candidates in five days. 97% at one year. Lifetime replacement. Cleared for use.

Hypothesis

A reasoned inference about the mandate or its consequence. Ships only in conditional language.

Unresolved

Keep the literal token. Never smooth a missing variable into plausible fiction.

Prohibited

Invented availability, certification, outcomes, employers, or anything implying private-source knowledge.

07  /  The full pack

Everything sitting behind this summary.

Fifteen research artifacts, all generated 2 August 2026 and cited back to primary sources. The interactive Role Intelligence app covers the operational layer: all 25 roles with their monitoring signals and evidence standards, 50 drafted emails, and 10 campaign strategies. Its link and access details are in the covering note rather than on this page.

Market and demand

  • market-analysis.mdLabour market, competitive structure, segment economics
  • market-context.mdSkills-first hiring, AI recruiting, regulation
  • edp-discovery.mdSeven candidate urgency metrics, evaluated
  • edp-framework.mdThe chosen metric and its formula

Who we sell to

  • buyer-persona.mdFive personas, drivers, language
  • segment-evaluator.mdThe six segments, scored
  • customer-quotes.md25 sourced buyer quotes
  • competitive-analysis.mdAthyna, NBS, Somewhere, Scale Army, direct hiring

How we find them

  • niche-data-sources.md14 sources evaluated, five selected
  • 25-role-monitoring-taxonomy.mdRole families, tiers, scoring model
  • linkedin-job-search-link-review.mdPrebuilt search URLs, US and Canada
  • priority-role-consequences.mdFive priority roles and their consequence chains

What we say

  • messaging.mdNarrative, core message, per-segment vocabulary
  • pvp.md30 permissionless value messages, self-critiqued
  • opus-takeover-playbook.mdThe whole thesis in one document
  • opus-playbook-structured.yamlMachine-readable version for the pipeline

Prepared by LeadGrow for Opus, 5 August 2026. Company consequences throughout this document are reasoned hypotheses drawn from public job postings and filings, not statements about any named company's internal performance. Candidate profiles referenced in the research are public professional evidence only and confer no permission to represent anyone. Every economic figure is an editable scenario until replaced with Opus's own booked data.