Gen UX Consulting case study · Wellspring
Case study · signal-based outreach

Gen UX Consulting built a $1.05M pipeline in 90 days with signal-based outreach

How a senior human factors firm stopped waiting to be found after the FDA asks. Every email was timed to a public moment in a device program: a funding round, a recruiting trial, a fresh 510(k). This is what the 90-day build delivered.

Pipeline value $1.05M 14 qualified opportunities at a $75K average engagement
Opportunities 14 Device programs scoped after a free audit
Audits 29 47% of replies became a free audit
Prospects 2,311 Each one gated, scored and email-verified
ClientGen UX Consulting
ChannelEmail, signal-triggered
SystemSignal-based outreach
What shipped · 90-day buildDrawn to scale in days
Day 0Signal map drawn Day 37First sends Day 90$1.05M in pipeline
Context · the client

The team device makers need before the FDA asks

Gen UX Consulting is a human factors, UX research and UX design firm for medical devices. It takes device teams from early user research through formative and summative validation, and builds the usability engineering file the FDA actually reviews.

Team

Senior only

Every researcher holds a Master's or a PhD. No juniors learning on a client's device.

Model

One roof

Research and interface design in the same team, so findings turn into design changes without a handoff.

Scope

Formative to file

Formative studies, summative validation, use specification and URRA, through to a clean submission.

Diagnosis · found at the wrong moment

Great work, discovered after the deficiency letter

Most device teams treat human factors as a checkbox at the end. They go looking for a partner when the summative report is due or when the FDA sends questions back. By then the work is remediation, the budget is spent and the buyer is shopping on price. Gen UX's best work happens months earlier, and nobody was calling it then.

Found too late

New work arrived after a problem surfaced, when the value Gen UX protects early was already gone.

Referral-only reach

The pipeline moved at the speed of the network. Quiet months had no second source of new work.

No view of timing

No way to see which device teams had just raised, opened a trial or cleared a device, so no way to arrive early.

From waiting to be found, to arriving on time

The fix was not more volume. It was timing: reach each device team at the moment its program made human factors a live question, with a reason it could see in its own news. Flip the switch to see each layer before and after the build.

Business development setup
TargetingWhoever the network sentDevice teams passed through six gatesMissing Built
TimingAfter the FDA asks for moreAt funding, trial and clearance momentsMissing Built
DataNo view of where programs stoodFDA, ClinicalTrials.gov and Crunchbase in ClayMissing Built
PrioritizationEvery lead handled the same wayScored and tiered before any outreachMissing Built
MessageA general capabilities pitchOne angle per signal, framed for the readerMissing Built
First stepA sales callA free audit of the human factors planMissing Built

The sending layer, as built

Drawing · sending infrastructureWarmed
Domain 01 · secondary
Inbox 01
Inbox 02
Inbox 03
Domain 02 · secondary
Inbox 04
Inbox 05
Inbox 06
Warmup before first sendDay 21 of 21
Day 0Day 7Day 14Day 21
Send pace25emails per inbox per day
Daily ceiling1506 inboxes × 25 sends
Format
Plain text Verified only
Tracking pixels
Opens off Links off
MethodHow the engine thinks

Four principles, one rule: meet the program where it is

This is not cold email. Cold email starts from a list; signal-based outreach starts from a reason. A device program leaves public traces at every stage. We read where each team sat on the regulatory clock, decided whether it deserved an email at all, chose the angle its signal earned, and opened with a free audit instead of a pitch.

DetectPlace it on the clockFunding, trials, clearances
GateSix gates, one scoreThe tier sets the effort
RouteSignal picks the angleRole sets the frame
AuditValue before a pitchA reply, then a free audit
P-01Signal map · the regulatory clock

Every account was placed on its program's clock

A usability finding costs little in design and a lot after submission. So the question for every account was simple: where is this device program right now? Five public signals answered it, each pulled into Clay with its source kept on the row. Pick a signal to see where it lands.

A device program timeline from raising money to the next device, with the cost of a late usability finding rising toward submission, and a marker showing where the selected signal places an account. Human factors is cheapest here Cost of a late usability finding · illustrative
Where it sitsRaise, entering design
SourceCrunchbase
In the listOver 900 contacts
What it tells us

Money just landed and the clock on clearance started. Design decisions are being made now, which is when human factors is cheapest.

Angle it triggers

Runway to clearance. Spend the round on a file that clears the first time.

Cycling through signals until you pick one

Two segments, one shared clock

The device makers were the buyers. The firms around them, CROs, regulatory and quality consultancies and contract engineering shops, meet those buyers at exactly the moments that matter. They became a second segment with their own angle.

Segment A · device makersBuyers
1,362

US device and healthtech companies, mostly under 200 people, Seed to Series D. Founders, CTOs, regulatory and clinical leads. Split into a Priority and a Secondary tier by the six gates.

Segment B · partner ecosystemChannel
949

CROs, regulatory and quality consultancies, contract engineering and design firms across 477 companies. Principals, partners and heads of business development.

P-02Scoring · six gates

A signal earned attention. Six gates earned an email.

A funding round at a software company is noise for a human factors firm. Before any account was contacted, it passed six gates. Three were knockouts. The other three set the score, and the score set the tier and the effort. Switch the gates on the example account and watch it move.

Account 01 · exampleKnockouts marked
ICP score
5/ 6
Priority Lead campaign, angle routed by signal

Up to two contacts per account, each framed for their role. 960 prospects reached in this tier.

Score 5 or 6Priority
Score 4Secondary
Knockout or 3Not contacted

Example account with simplified rules. Real scores ran as an ICP prompt in each segment's Clay table, with the evidence for every gate kept on the row.

P-03Routing · signal times it, role frames it

The signal chose the moment. The role chose the risk.

A founder, a regulatory lead and a head of product fear different things about the same device. So every angle had two parts: a reason to talk now, taken from the account's own signal, and the human factors risk that particular reader already carries. Select any cell to see how the two combine.

Founder
Regulatory
Product
Clinical
Why now · from the signalFunding round

The round set the clock on clearance.

The risk · from the roleFounder

The submission window.

The angle

Runway to clearance, framed around the date.

Cycling through combinations until you pick one

Simplified view of the routing logic. Partner firms received one angle for every reader, built on the client programs they already support.

P-04Conversion · value before a pitch

Every first conversation was a free audit

Device leaders hear vendor pitches every week. Gen UX opened with something useful instead: a free audit of the team's human factors plan, read against where the program sat on the clock. The findings made the case for the work, not a sales deck.

Step 1 · reply 62

Human replies to a signal-led email

Step 2 · audit 29

Free audits of the human factors plan, one per program

Step 3 · opportunity 14

Audits whose findings became a scoped engagement

One audit, read against the clock

The audit covered the same six parts of the file for every device team. What changed was what counted as a gap, because a team in design and a team that just cleared are missing different things. Switch the stage to see an example readout change.

Example audit readout
Gaps found2

Finding: start formative work now, while design changes are still cheap.

No pitch in the audit

The audit stood on its own. Teams kept the readout whether or not they worked with Gen UX.

Tailored to the clock

The signal that started the conversation told the audit where to look first.

Findings become the scope

Each gap the audit surfaced was a piece of work the team could already see it needed.

Workflow · the build

Public records in, audits out

Every source fed the same two Clay tables, one per segment. Each row kept its source, its signal count and the evidence behind every gate, so every account contacted could be traced back to the record that justified it.

Step 1SignalsFive data sources
  • FDA 510(k) database
  • ClinicalTrials.gov
  • Crunchbase funding and leadership
  • Apollo and Sales Navigator for people
2,324rows sourced
Step 2 · coreRevenue engineClay, two tables
  • Source column and signal count
  • Dedup across sources
  • Enrichment waterfall
  • Six-gate ICP prompt, then tier
2,317unique contacts
Step 3SequencesVerified, then sent
  • Every address verified first
  • Three campaigns: two tiers, one partner segment
  • Angle routed by signal and role
  • Short, plain-text sequences
2,311prospects reached
Step 4MeetingsReplies to audits
  • Replies routed same day
  • Free audit of the human factors plan
  • Findings scoped into a proposal
  • Notes back to the account row
29audits
Results · the 90-day build

$1.05M in pipeline from 2,311 prospects

Everything here happened inside the 90-day build. Each dot below is one prospect. Switch segments to see where replies and opportunities came from, and select a number to light up just those dots.

Prospects reached2,311Across all three campaigns
Pipeline value$1.05MAt a $75K average engagement

Every email was triggered by a signal and sent to a verified address. No ads and no cold calls.

The funnel, step by step

Reached2,311prospects2.68%
Replied62human replies47%
Audited29free audits48%
Qualified14opportunities$75K
Pipeline$1.05Maverage $75K per engagement

Earlier on the clock, warmer the reply

The Priority tier, funded teams in active development, replied at more than twice the rate of the partner firms and produced nine of the fourteen opportunities. The Secondary tier, larger sponsors with trials and clearances, replied almost as often but sat further along the clock. Partner firms replied least, and every partner audit opens a door to many device teams.

Priority device teamsSecondary sponsorsPartner firms
No open tracking, by designOpen and link tracking were off and every email went out as plain text, so there is no open rate to report. We traded the metric for inbox placement.
Verified or not sentOnly verified addresses entered a campaign. The bounce rate stayed at 1.0% for the whole build.
Takeaways

What carried the result

  1. Timing is the signal

    In a regulated market, the best reason to write is the moment a program makes your work urgent. Funding, trials and clearances are public, dated and specific to one company. Reaching device teams at those moments put Gen UX in the room at formative, when its work is worth the most, instead of after the deficiency letter.

    Priority tier: 3.65% reply rate, 9 of 14 opportunities
  2. Gates before volume

    Six gates kept software-only, idea-stage and fully staffed teams out of the campaigns. Fewer emails, and every one of them to a team that could buy.

    3 knockouts, 3 scored gates, 3 tiers
  3. Value before a pitch

    No first conversation was a sales call. Each one was a free audit that left the team with a readout of its own file. Nearly half of all replies became an audit.

    29 audits from 62 replies
  4. Verified or not sent

    Two secondary domains, six warmed inboxes, plain text, no tracking pixels and no unverified address. The floor that keeps the sending domains out of spam.

    1.0% bounce rate
  5. Partners compound

    Partner firms replied least, but each one sits beside dozens of device programs. Their audits looked at human factors gaps across their client work: slower to convert, wider in reach.

    7 partner audits
Closing note

Gen UX stopped waiting for the deficiency letter. It now arrives at formative.

Engine 1 · ReferralsUnchanged. Scales with network depth.
Engine 2 · Signal-based outreachFires every weekday. Scales with public records.

Gen UX already had what device teams need: senior researchers, design in the same room, and files that clear. What it lacked was a way to reach teams before the problem was visible to them. The engine reads the regulatory clock every week and writes to the teams for whom human factors just became a live question. The expertise is unchanged. What changed is when buyers meet it.

EpilogueAfter the build · months 4 and 5

The same engine, pointed at a second regulated market

The 90-day build ended with the engine handed over and live. Because the method runs on public regulatory records rather than on a list, it transferred. As part of our ongoing work with Gen UX, the same system was rebuilt for nicotine and tobacco-alternative companies facing FDA premarket review, and went live in October 2026.

Time
90-day buildMedTech · months 1 to 3Second marketNicotine · months 4 and 5
Markets on the engine2One method, two FDA pathways: 510(k) for devices, premarket review for nicotine products
Quarterly FDA refresh

New clearances and newly recruiting trials are pulled every quarter, so the device list never goes stale.

New gates, same logic

The nicotine build swapped device gates for public FDA decisions on tobacco products. Scoring and tiers did not change.

Same audit-first model

A free audit first, a scoped proposal after. The conversion model moved over untouched.

Want this built for your pipeline?

We build and run outbound for B2B companies with a sales team that closes. You only pay when qualified calls land on your calendar.

Book a call