Four customers came from your references.
The next sixteen come from conversations.

Prepared for
Arjun Ahlawat · Enginius.ai
Selling
A sovereign AI platform for regulated engineering, into medical device and life sciences teams
Prepared
August 2026 · Charm

Enginius was built the hard way: five years on a Department of Defense contract, a sovereign language model rather than a wrapper, deployed behind the customer's firewall where every output is traceable and deterministic. Since commercialization opened in early 2026, four medical device makers have signed, every one of them through your board and your references.

References are the best channel there is, and they do not run on a schedule. Getting from four customers to twenty takes a channel you control. Your team already built the sensors: agents that hear regulatory and leadership changes across the market. What is missing is your own phrase for it, the art of making it a conversation. This document is that conversation engine: who it talks to, what it says word for word, and what it costs.

Charm builds and runs outbound for
Hello Hero Rightworks VirtualFork Ben's Bites Highline + others

01 / SituationThe platform regulated buyers are allowed to want.

Why you'll win

You answer the one question this industry asks before any other: can I trust it?

1

Control and context, which is what this buyer actually trades on

Regulated industries will never trade control and context for capability. Your words, and they are the whole pitch. A sovereign model deployed behind the customer's firewall, on a single GPU, with no data leaving the building, is the only architecture a medical device quality organization can say yes to without a fight. Generic AI is disqualified before the demo starts. You are not.

2

The proof point fits in one sentence

A regulatory submission document that takes a team four months to draft, and your platform returns a first draft in under 30 seconds, from their own design history files and the standards themselves. Cold email lives and dies on one concrete sentence, and you own one of the best we have ever been handed.

3

Deterministic and auditable is the feature, not the caveat

Every output traceable, referenceable, and the same every time. A submission your customer can still defend in an audit ten years out, for devices that live for fifty. Where the rest of the AI market apologizes for hallucination, your architecture simply does not do it, and the buyer this proposal targets knows exactly why that matters.

4

Your buyer's world runs on public record

Medical device regulatory life is published as it happens: clearances, submissions, recalls, enforcement actions, MDR deadlines, leadership changes. Every one of those is a dated, public reason to write to a named person this week. This is the best signal terrain we work in, and it is the terrain your own agents already listen to.

5

Validation you did not have to buy

Funded by the U.S. Army, locked from commercializing until the work shipped, deployed behind Philips Healthcare's firewall on a seven-year-old GPU. Four paying medical device customers within months of opening the doors. The story survives the skeptical read, which in this vertical is the only read there is.

What's in the way

The sensors exist. The conversations don't.

1

The reference channel has a ceiling

Board introductions and industry references produced four excellent customers, and they will keep producing occasionally, on nobody's calendar. A Series A window at the end of this year does not wait for occasionally. Four to twenty is a volume of conversations the current channel cannot schedule, and everyone on your side already knows it.

2

Signals without execution

Your team built Claude-code agents that track regulatory and leadership changes across the market. That puts you ahead of most companies we meet. But a flagged signal is not a booked meeting, and by your own account the missing piece is the art of executing on it and making it a conversation. That art is the entire business we are in.

3

Rocket scientists writing cold email

Half your team are rocket scientists and half are data scientists, and every hour they spend on prospecting lists and outreach copy is an hour off the platform that wins the deals. The engine has to run without borrowing the people who build the product.

4

Your audience is allergic to exactly the wrong kind of email

Regulatory and quality leaders are the most hallucination-suspicious readers in B2B, and most AI vendors write to them in generated-sounding copy stuffed with claims. The outreach has to clear the same bar the product does: specific, referenced, and honest about what it is. Copy that smells automated does not just fail here, it damages the name on it.

5

Hiring SDRs before the message is proven is expensive twice

You want one or two hires now and a path to twenty. Hire them into silence and you pay salaries while they guess at the pitch. The engine's first job is finding the message that converts, so that every seat you add afterward inherits a script that already works.

02 / ApproachYour agents keep listening. We make it a conversation.

Nothing you built gets retired.
We bolt the execution layer onto your sensors.

First, straight volume. Every US medical device establishment is on public record, and the regulatory, quality and engineering leaders inside them are reachable by name. The plain offer, said clearly: first drafts of submission and quality documents from your own files, behind your firewall, deterministic. Sometimes the winning campaign is simply that sentence delivered to everyone it is true for, at full volume from day one.

Second, the signals. Clearances published weekly, recalls and enforcement actions as they land, MDR deadlines, leadership changes in regulatory and quality seats. Public, dated, specific. Your existing agents already flag several of these: their output becomes a campaign feed, not a casualty. We add the pulls you do not have and act on all of it.

The two race each other. Four new campaigns every two weeks, each a permutation of buyer, signal and angle. Neither track gets protected. Whichever books qualified conversations gets doubled in the next cycle, and by month three the message that scales is proven, not guessed.

And LinkedIn runs where your buyers actually are. Regulatory affairs and quality leadership are professionally present on LinkedIn in a way few audiences are. Managed seats, human-paced, in a real voice, carrying the DoD origin story that cold email compresses too much.

Step 01 · Activate

LinkedIn live in week one

Two managed seats, human-paced and proxied, pointed at regulatory and quality leadership in medical devices. Nothing needs to warm, so this channel produces conversations while the email infrastructure is still building.

→ Live in week one
Step 02 · Enumerate

Public record, read as a target list

FDA registration and clearance records, enforcement and recall data, MDR cohorts, plus the signals your own agents already track. Pulled fresh for each campaign and resolved to the named leader, never to an info@ inbox.

→ Your agents feed this directly
Step 03 · Race

Signal plays against straight volume

Signal campaigns and plain-offer campaigns run in parallel against the same goal, and neither gets protected. Whichever books conversations with device makers gets doubled in the next cycle.

→ The numbers pick the winners
Step 04 · Cycle

Four new campaigns every two weeks

Eight campaigns a month, each a permutation of buyer, signal and angle. By month three you own a ranked answer to which buyer converts best, and every SDR you hire afterward inherits it.

→ Message-market fit, found on purpose
The opening cut, for you to argue with at kickoff

Every line here is a starting position, not a decision. The kickoff session exists so you can move these before anything is built, and Tuesday's call is where the arguing starts.

Parameter
Opening cut
Why
Where it moves
VerticalWhere outbound points, and where it doesn't
Med device
Medical devices first, life sciences second
aerospace & defense excluded
Your instruction, taken literally: A&D runs on partnerships and needs no outbound, so not one email points there. Medical devices carries the first phase. Life sciences joins as its own campaigns once the device tracks show which language lands.
UniverseSized live at the parameter session
US
US device makers on public record
onshore, like everything else you do
Every US device establishment registers with the FDA annually, so the universe is enumerable rather than estimated. At kickoff we size it live on screen, cut it by class, category and company size, and you approve the cut before anything is built.
Who we resolve toThe database names a company, we find the human
RA / QA / Eng
Named person, verified contact
never info@
Regulatory affairs and quality leadership first, since they live inside the documents your platform drafts. Engineering and R&D leadership as their own campaigns. Anything we cannot resolve to a person gets dropped, not sprayed.
Your agents KeptThe Claude-code signal trackers your team built
Integrated
Wired in as a campaign feed
nothing gets retired
The leadership and regulatory changes your agents already flag become inputs to campaign builds, alongside the pulls we run ourselves. At kickoff we map what they track, keep what is unique, and add only what is missing. Your engineering investment compounds instead of competing.
ExclusionsWritten before anything sends
Day 1
Suppression list
your relationships protected
Your four customers, your board and advisor network, active partnership conversations and any relationship you name at kickoff are suppressed before the first send. Nobody who already trusts Enginius ever gets a cold email from Enginius.

03 / The buyersFive buyers, each with a public why-now.

Buyer
Stage
The public moment
What it becomes for Enginius
The regulatory leader who just cleared Lead playThe submission grind is fresh, and the next one is forming
Just cleared
Clearances published weekly, on public record
the signal track's cleanest cohort
A team that just cleared knows exactly what the first draft cost them, and the next submission is already on the roadmap. The congratulations is real, the question lands while the pain is fresh, and the 30-second first draft is the counter-fact they cannot unhear.
The engineering org with a legacy portfolioChange orders against decades of documentation
Always on
Long-established registrations and product lines
the widest universe of the five
Devices run for decades, and every engineering change drags impact assessments and file updates behind it. This is your origin story pointed at its commercial twin: the change that cost five hundred dollars in engineering and half a million in process. The straight-volume track lives here.
The quality team under remediation load Handled gentlyDocumentation demand just spiked
Under load
Enforcement and recall records, public as they land
the signal finds them, the copy never says so
Remediation multiplies exactly the document work your platform drafts. The signal is how we find them and when we write, never what we lead with: the copy talks about documentation load in general, with respect, and lets them make the connection themselves.
The MDR cohortCE-marked portfolios with technical files still owed
On a deadline
MDR transition deadlines, set by regulation
a dated, industry-wide clock
Device makers selling into Europe owe technical documentation rewrites on a schedule nobody chose, with notified bodies backlogged. A why-now the whole cohort shares, and a document type your platform drafts from their own files.
The life sciences beachhead LinkedIn trackPhase one's second vertical, opened carefully
Phase one
Regulatory and quality leaders, present on LinkedIn
reached in a real voice
Your stated phase-one scope is medical devices and life sciences. Life sciences opens on the managed LinkedIn seats first, where the DoD origin story can breathe and the audience can ask questions, before it earns its own email campaigns.
5buyers, every one findable by name in public records, and every one living inside documents your platform drafts.

This table is the heart of the engagement, not the whole of it. The signal plays run next to straight-volume campaigns against the wider device-maker universe, and the two race each other. Nothing about Enginius needs repositioning. The platform needs to be put in front of the right regulatory, quality and engineering leaders with a reason to talk this week, and that is a campaign-count problem. The plays themselves are opening thinking: some ship as written, some change at kickoff, and some never go to market.

It is also the honest frame for the tier question in section 09. Eight campaigns a month works the device tracks properly. Sixteen runs life sciences and the engineering permutations in parallel rather than after. Either way, by month three you own a ranked answer to which buyer converts, and every SDR hire you make afterward starts with it.

04 / How it runsPublic record to booked conversation.

01
The volume layer

The plain offer, at full volume, from day one.

The wider universe of US device makers, offered the platform plainly: first drafts of submission, change and quality documents from your own files, behind your firewall, deterministic and auditable. No trigger required, because every company in this universe is producing regulated documentation every single week.

Every sequence is three touches with one consistent ask: a fresh first email, a short threaded follow-up, then a fresh third angle, and then it stops. No breakup emails, no fake urgency, no "just bumping this." Sending runs on separate domains built for the campaign, never on enginius.ai, so your own domain and deliverability stay untouched.

→ Full volume from day one, three-touch sequences, one ask → Separate sending domains, warmed before anything scales → Replies route straight to you, same day
02
The signal layer

Public trails that name the buyer and date the moment. Including the ones you already track.

Clearance records, published weekly, naming the company and the device that just made it through. Enforcement and recall data, marking the quality organizations whose documentation load just spiked. MDR cohorts, the CE-marked portfolios with technical files owed on a regulated clock. And your own agents' output: the leadership and regulatory changes your Claude-code trackers already flag, wired in as a feed instead of sitting in a channel nobody acts on.

How the data actually works, said plainly. A campaign pulls its records at the moment we build it, resolved to a named regulatory, quality or engineering leader with a verified contact. The campaign runs, we score it, and the plays that earn it get promoted to a standing pull so they keep feeding themselves. Everything is deduplicated and suppressed across plays, so no buyer hears from Enginius three different ways in the same fortnight.

→ Pulled at build, resolved to a named person, never to info@ → Your customers, board and partners suppressed before the first send → Scored plays promoted to evergreen, decided together off the numbers
03
Two things we will not do

We will not retire what you built, and we will not write email your buyers can smell.

Your team's agents represent real engineering investment and real market coverage, and the answer to "will we have to throw this away" is no, in writing. At kickoff we map what they track, integrate their output as campaign inputs, and build only what is missing. Where they are ahead of our own pulls, theirs win. The value we add sits after the signal: the list, the copy, the infrastructure, the send, and the conversation.

And the copy itself has to survive the most AI-suspicious readership in B2B. A quality director who spends her days rejecting unsupported claims will reject an email built from them in one glance. Every line is written to be read aloud, every claim traces to something you have actually said or shipped, and anything that smells generated dies in review. You approve the voice before the first send, and the sequences in section 05 are written so you can hold them to that standard right now.

→ Your agents integrated as inputs, mapped at kickoff, kept where they win → Every email a three-step sequence: fresh, threaded, then a fresh third angle → Claims in copy limited to what Enginius has said and shipped

05 / CampaignsFive plays. Written, not described.

The clearance that just published

Recommended lead

Clearances are published weekly, in public, naming the company and the device. A regulatory team that just cleared knows precisely what the submission cost them in draft-assembly months, and the next submission is already forming on their roadmap. The congratulations is real, the question is one they have been asking themselves, and the 30-second first draft is a fact they will repeat internally whether they reply or not.

Signal → target set US device makers with a clearance published in the last 60 days, resolved to the named regulatory affairs or quality leader with a verified contact. Recency-scored, so last week's clearance outranks last month's. If this play scores, the follow-on wave runs against companies with submissions in progress, where the draft grind is not a memory but the current week.
E1 · the months before reviewDay 0
Subject: the {{device_name}} clearance
Hey {{first_name}}, Congrats on the {{device_name}} clearance. Question while it's fresh: how much of that submission timeline went into assembling the first draft, before a single reviewer judgment call? Enginius generates first drafts of submission documents from your own design history files and the standards themselves, in under 30 seconds, deployed behind your firewall. Four device makers run it today. Want to see a first draft built from one of your own documents, or is the drafting side already where you want it?
P.S. Nothing leaves your network. The whole platform runs on a single GPU inside your environment.
85 words · score 93
E2 · the ten-year auditDay 4 · threaded
Subject: none, threads to E1
Hey {{first_name}}, quick follow up. The part regulatory teams push on first: the output is deterministic. Same inputs, same draft, every line traceable to the source document it came from. So the submission can still be defended in an audit ten years out, which is the bar a device that lives for decades has to clear. That is why it was built for regulated engineering only. No general-purpose model underneath. Want to see a first draft built from one of your own documents, or is the drafting side already where you want it?
P.S. It was originally built under a U.S. Department of Defense contract. Same trust bar, different regulator.
90 words · score 92
E3 · fresh angle, the reviewersDay 9 · fresh
Subject: what your reviewers were hired for
Hey {{first_name}}, last one from me. Different angle: the people. The senior folks on a submission were hired for judgment calls, and most of their submission weeks go to document assembly instead. When the first draft arrives already assembled and referenced, review starts on day one, and review is where your team actually earns its keep. Want to see a first draft built from one of your own documents, or is the drafting side already where you want it?
P.S. If the timing is wrong, keep us on file for the next submission. There is always a next submission.
79 words · score 92
Published weekly, public record Pain is days old, not hypothetical Submissions-in-progress wave if it scores One consistent ask

The change that costs more than the change

Straight volume

The widest universe of the five: established device makers whose products have been on market for years, where every engineering change drags impact assessments, file updates and regulatory review behind it. This is your own origin story pointed at its commercial twin, and it needs no signal at all, because in this universe change documentation is happening somewhere in the building every week.

Universe → target set US medical device manufacturers with established registrations and multi-year product lines, resolved to VP-level engineering, R&D and quality leaders. Segment permutations run as their own campaigns: device class, company size, single-product versus portfolio companies. If this play scores, the follow-on splits engineering leadership from quality leadership and lets each cohort's language win on its own numbers.
E1 · the real cost of smallDay 0
Subject: a $500 change at {{company}}
Hey {{first_name}}, What does a small engineering change actually cost {{company}} once the documentation is counted? Impact assessment, file updates, regulatory review, all of it. Enginius exists because a defense customer paid half a million dollars in process for a change that cost five hundred in engineering. We were funded by the U.S. Army to fix that. Today medical device teams use the platform to draft change documentation from their own files, behind their firewall. Worth a look at how that runs on one of your change packages, or is change documentation not where your engineers' time goes?
P.S. First drafts come back in under 30 seconds, referenced to your own source documents.
99 words · score 92
E2 · the fifty-year paper trailDay 4 · threaded
Subject: none, threads to E1
Hey {{first_name}}, quick follow up. The longer arc: devices run for decades, and every change stacks another layer onto files somebody will have to defend years from now. Because every output the platform generates is traceable to its source, the paper trail assembles itself as the change moves, instead of being reconstructed later by whoever drew the short straw. Worth a look at how that runs on one of your change packages, or is change documentation not where your engineers' time goes?
P.S. Deterministic output. Same inputs, same document, every time. Auditors notice.
84 words · score 92
E3 · fresh angle, why generic AI can'tDay 9 · fresh
Subject: why the copilots stall on engineering docs
Hey {{first_name}}, last one from me. Different angle. Generic AI stalls on engineering documentation because it reads text without knowing your ontology: what a part is, how a requirement traces, which standard governs what. Enginius builds a knowledge graph from your own documents first, then drafts inside it. That is why the output comes back in your language instead of an approximation of it. Worth a look at how that runs on one of your change packages, or is change documentation not where your engineers' time goes?
P.S. Behind your firewall, on your hardware. Nothing about your product ever leaves the building.
86 words · score 93
No trigger needed, the work is constantThe origin story is the pitchSegment permutations per cycleEng and QA cohorts split if it scores

The quality system under new load

Signal, handled gently

Enforcement actions and recalls are public the moment they land, and they multiply exactly the documentation work your platform drafts: remediation plans, CAPA records, responses on a clock. This cohort gets found by the signal and written to with respect. The copy never recites what happened to them. It talks about documentation load the way a good peer would, and lets the reader make the connection privately.

Signal → target set Quality and regulatory leadership at US device makers where public records show a recent spike in documentation demand, resolved to the named leader. The trigger governs timing and inclusion only, and is never referenced in copy. If this play scores, the follow-on runs a slower, smaller-volume version against the same cohort ninety days later, when the remediation grind is fully real.
E1 · where the time comes fromDay 0
Subject: documentation load at {{company}}
Hey {{first_name}}, When documentation demand spikes on a quality team, remediation work, CAPA records, responses due on a clock, where does the time actually come from at {{company}}? Most quality leaders tell me the honest answer is nights, and other projects. Enginius drafts those documents from your own quality system and standards, deployed inside your network, every line traceable to its source. Open to seeing it draft from your own quality system, or is the documentation load manageable as it stands?
P.S. Four medical device makers run it today, all behind their own firewalls.
85 words · score 92
E2 · the most skeptical readerDay 4 · threaded
Subject: none, threads to E1
Hey {{first_name}}, quick follow up. One thing worth being direct about: remediation documents get read by the most skeptical audience a company ever writes for. That is exactly why the platform's output is deterministic and referenced. Every statement in a draft traces to a source in your own files, so what you send upward is defensible line by line. Open to seeing it draft from your own quality system, or is the documentation load manageable as it stands?
P.S. No hallucination by architecture, not by promise. The model only writes inside your document graph.
79 words · score 93
E3 · fresh angle, fast without carelessDay 9 · fresh
Subject: fast, without looking fast
Hey {{first_name}}, last one from me. Different angle. In this industry, fast can read as careless, and quality leaders are rightly wary of anything that promises speed on regulated paper. The point is not the 30-second draft. The point is that the draft arrives already referenced to your own files, so your team's time goes to judgment instead of assembly. Open to seeing it draft from your own quality system, or is the documentation load manageable as it stands?
P.S. If now is the wrong season, no follow-up after this one. We are easy to find when it turns.
80 words · score 92
Signal governs timing, never copyPeer tone, zero ambulance chasingNinety-day second wave if it scoresStops cleanly after three

The technical file owed to Europe

Device makers selling into Europe owe technical documentation under MDR on a schedule nobody chose, with notified bodies backlogged and the same teams responsible for everything else. It is the rare why-now an entire cohort shares at once: dated, external, and nobody's fault, which makes it comfortable to say out loud in an email.

Signal → target set US device makers with CE-marked products, resolved to the regulatory leader who owns the European file. Prioritized by portfolio size, since more products means more files owed. If this play scores, the follow-on extends to adjacent recertification and standards-transition cohorts, which repeat this exact shape on their own clocks.
E1 · who owns the writingDay 0
Subject: the MDR files at {{company}}
Hey {{first_name}}, How many technical files does {{company}} still owe under MDR, and who actually owns the writing? For most portfolios the answer to the second question is "the same people who own everything else." Enginius ingests your design masters and the standards themselves, then drafts the technical file behind your firewall, referenced line by line to your own source documents. Want to see a technical file draft built from one of your own products, or is the MDR work already resourced?
P.S. First drafts in under 30 seconds. The review is yours, the assembly is not.
86 words · score 92
E2 · the notified body's readerDay 4 · threaded
Subject: none, threads to E1
Hey {{first_name}}, quick follow up. The detail that matters for MDR specifically: reviewers reward traceability. Because every statement in a draft traces to a source in your files, the document holds up under a notified body's reading, and under the audit that comes years later. Deterministic output, same draft every time. Want to see a technical file draft built from one of your own products, or is the MDR work already resourced?
P.S. Built for regulated engineering only. It has never written a marketing email, including this one.
75 words · score 92
E3 · fresh angle, the portfolio mathDay 9 · fresh
Subject: one file, times your whole portfolio
Hey {{first_name}}, last one from me. Different angle: the multiplication. One technical file is a project. A portfolio of them is a program, and programs are where documentation teams sink. Whatever the file count is at {{company}}, the assembly work scales linearly and the platform makes it stop doing that. Want to see a technical file draft built from one of your own products, or is the MDR work already resourced?
P.S. If Europe is not the priority this year, fair enough. The same platform drafts your FDA submissions too.
76 words · score 92
Cohort-wide dated deadlineExternal and nobody's faultRecertification cohorts nextPortfolio-size prioritized

The founder story, told where it can breathe

Runs on LinkedIn

The DoD origin story is your best asset and the one cold email compresses too hard. On LinkedIn it can breathe: five years building under a Department of Defense contract, locked from commercializing until the work shipped, now open for exactly two verticals. This runs on the managed seats, human-paced, in a real voice, and it reads like a person because the sender is one. It also opens life sciences, the second phase-one vertical, without spending email volume on an unproven segment.

Channel → cadence LinkedIn only, from the managed seats, human-paced. Regulatory affairs, quality and R&D leadership at US medical device and life sciences companies. Connection request, then two messages across a fortnight, then it either becomes a conversation or it stops. The voice is founder-adjacent and written with you at kickoff, so nothing below carries a merge field.
Connection requestDay 0 · 300 char limit
Sent from: the Enginius seat
We spent five years building engineering AI under a U.S. DoD contract, and were barred from selling it commercially until the work shipped. That ended this year. I'm connecting with regulatory and quality leaders as we open up to medical devices. No pitch attached, glad to be connected either way.
Craft note: no merge fields, no flattery. Sent at human pace from a warmed, real profile.
50 words · score 93
DM 1 · the actual reasonDay 2 after accept
Sent from: the Enginius seat
Quick context, since connection notes never say the real thing. The platform we built for the DoD drafts regulated engineering documents from a customer's own files: submissions, change packages, quality records. Sovereign model, deployed behind your firewall, every output traceable to its source. Four medical device makers run it today. If documentation load is a live topic on your team, I would trade a twenty-minute look for your honest reaction. And if it is not, no follow-up needed on my side.
Craft note: the reason for writing is the actual reason. The ask is an exchange, not a favor.
80 words · score 93
DM 2 · smaller door, same askDay 9 · then stop
Sent from: the Enginius seat
No pressure either way on this. If a look at the platform feels early, the useful version might be one page: how a behind-the-firewall deployment actually works, what it runs on, and what the security review asks about. Most regulatory teams want that answered before anything else anyway. Worth sending that over, or is this not a this-quarter topic for your team?
Craft note: lower commitment, then it ends clean. No breakup message, no guilt.
62 words · score 92
Reads like a personThe origin story gets roomOpens life sciences cheaplyZero merge fields

06 / Tool stackThe stack costs more than the fee.

Data & enrichment
Clay
Data orchestration
$800/mo
DiscoLike
Lookalike discovery
$199/mo
LeadMagic
Email verification
$249/mo
Ocean.io
B2B lookalikes
$600/mo
Infrastructure & sequencing
Hypertide
Inbox infrastructure
$1,850/mo
Charm Sequencer
Private IP pool
$500/mo
HeyReach
LinkedIn, human-paced
$197/mo
PhantomBuster
Social automation
$49/mo
Signals & glue
Apify
Clearance, enforcement and registry pulls
$100/mo
RB2B
Site deanonymisation
$149/mo
n8n
Workflow glue
$100/mo
Regulatory & registry pulls
Built per campaign by us
Included
Your Claude-code signal agents
Integrated as a campaign feed
Yours, kept
Licensed by yourself
$4,793/mo

Plus the person who runs them. Which, on a team where half are rocket scientists and half are data scientists, is a hire that takes the wrong people off the platform that actually wins your deals.

VS
Included with Charm
$0

Every tool above sits on our licenses and is run by our team. At the Engine tier you pay $4,000 a month and the stack behind it lists at more than that on its own, before anybody's time.

07 / TimelineDevice makers hear from Enginius in week one.

01

Parameters set, LinkedIn live

The working session: universe sized live on screen and cut by class and company size, the five buyers ranked, your agents' signal feeds mapped. Customers, board and partner relationships loaded as suppression. Both LinkedIn seats connected and the founder-story track goes out. Cold domains ordered and warming starts in parallel.

02

Lists built, agents wired in

Clearance, enforcement, MDR and registry pulls built and resolved to named regulatory, quality and engineering leaders with verified contacts. Your agents' output connected as a campaign feed. First target lists back to you for review before anything sends.

03

Copy written, scored, soft launch

All sequences written against the top two buyers and scored line by line, every product claim checked against what Enginius has actually said and shipped, in a voice you have approved. Low-volume soft launch on the new domains to prove deliverability before anything scales.

04

All tracks live, full volume

Cold plays running at full volume, replies routing to you same day. First two-week cycle scored and the next four campaigns built from what it showed. By the time your first SDR hire starts, the message they inherit has numbers behind it.

08 / ProofWe have solved every piece of this before.

The story you already heard on our call, in writing

The regulatory signal that reached GE Aerospace's COO before his own team did.

Our agentic systems listen to every US regulatory body continuously. When the FAA released a regulation affecting grounded-fleet predictive maintenance, the system found the affected operators, checked what each company's own site said about predictive maintenance, found the gap at GE Aerospace, resolved the right executive, and sent the message. The COO's reply asked how we got to it before he did. That deal closed for our client last week.

That is the exact mechanic this proposal points at medical devices: a regulator publishes, the affected cohort is identified the same day, and the message lands while the change is still news. Your own agents already do the listening half. Sections 02 through 05 are the other half.

Hello Hero

Youth mental health platform · Same shape: public records → entity → named human
Challenge

Needed direct contact with decision-makers across thousands of US school districts, a universe that exists only inside public records, with the actual humans buried behind institutional names.

Solution

Mapped every administrator in every US public school district from public data, resolved them to verified direct contacts, and ran parallel campaigns off that dataset. That is the identical build to turning FDA registration, clearance and enforcement records into the named regulatory and quality leaders behind each device maker. It is the single most transferable thing in this list.

$35M
Pipeline generated
300+
Institutional leads
15+
Specialists recruited
6 mo
Timeline

Rightworks

Cloud accounting & practice management · Same shape: technical product, skeptical professional buyer
Challenge

A saturated mid-market category, a sales team stretched thin, and a professional audience of accountants who dismiss generic outreach on sight. Regulatory and quality leaders read email the same way.

Solution

Intent-based outbound triggered on firms' own public activity, multi-touch across email and LinkedIn, with copy specific enough to survive an expert reader. The clearance and MDR triggers in your plays one and four are that exact mechanic pointed at regulated engineering instead.

$4.2M
Pipeline generated
180+
Demo requests
28%
Reply rate
5 mo
Timeline

Ben's Bites

AI education SaaS · Same shape: which angle actually sells?
Challenge

Real credibility in the space but no systematic outbound, and no clarity on which of many possible angles would produce pipeline. Your question has the same shape: does the submission draft, the change package, or the MDR file open the door first?

Solution

40+ campaign types A/B tested weekly, doubling down only on what converted. This is the direct answer to the thing nobody can decide from a standing start: which buyer and which document type leads for Enginius? You do not have to pick in advance. Campaign velocity finds out with data instead of an opinion.

$2.5M
Pipeline generated
156x
ROI in 120 days
40+
Campaigns tested
4 mo
Timeline

VirtualFork

Restaurant technology platform · Same shape: timing decides the reply
Challenge

Owner-operators who do not answer generic email, in a category that closes on relationship, where the message had to reach the buyer at the moment the problem was live rather than whenever the campaign happened to send.

Solution

Signal data identified operators at the right moment, with sends timed to when those buyers were actually reachable. The finding that transfers to Enginius: a message that arrives inside the buyer's moment, a fresh clearance, a spiking document load, outperforms the same message sent cold. Your plays are built around exactly those moments.

$1.8M
Pipeline generated
200+
Operator leads
35%
Reply rate
3 mo
Timeline

09 / AcceptAccept, sign and start, right here.

Recommended

Engine

$4,000/mo

Four campaigns every two weeks, eight a month. The medical device tracks worked properly, with your existing signal agents wired in from week one.

  • 4 campaign deployments every two weeks, 8 per month
  • Up to 100,000 emails a month as three-touch sequences
  • Full cold infrastructure: domains, DKIM, SPF, MX, warming, private IP pool
  • 2 LinkedIn seats managed end to end, running the founder-story track
  • Clearance, enforcement, MDR and registry data pulled fresh per campaign
  • Your Claude-code signal agents integrated as a campaign feed, not retired
  • Straight-volume campaigns raced in parallel with the signal plays
  • Plays that score get promoted to a standing pull, decided together off the numbers
  • Parameter session, universe sized live and approved by you
  • All copy written, scored and iterated cycle over cycle
  • Weekly strategy call in month one, then every other week · dedicated account manager

Engine ×2

$8,000/mo

Eight campaigns every two weeks, sixteen a month. All five buyers plus the life sciences vertical run in parallel rather than sequenced.

  • Everything in Engine
  • 8 campaign deployments every two weeks, 16 per month
  • All five buyers run in parallel: clearances, change orders, quality, MDR, life sciences
  • Life sciences email campaigns from month one instead of after the device tracks prove out
  • Segment permutations tested from month one: device class, company size, portfolio depth
  • Additional LinkedIn seat
  • Visitor deanonymisation on enginius.ai, so we see which device makers come looking
Add-ons · optional, select any

SDR / BDR staffing, employer-of-record compliant

Scoped together at kickoff

Named, trained callers working your replies and dialing behind the email and LinkedIn touches. US and nearshore options, employer-of-record compliant, hired against the message the engine has already proven. Sized and priced per head once the first cycles show the reply volume.

  • Works the replies the engine produces, same day
  • Cold calling layered onto the two digital channels
  • Scales from your first one or two heads toward twenty, on proven scripts
Order summary · updates live
Onboarding & infrastructure setupOne-off$1,000
Total recurring
Total due today
ORDER FORM

Client: (fills from your signature) · Contact: (fills from your signature) · E-mail: (fills from your signature)
Selected Package: · Add-ons: none · Service Fees: , payable in advance per Section 7 · Billing Option: · Amount Due at Acceptance:
Onboarding Fee: , one time · Initial Service Term: months from kickoff, followed by month-to-month. Address and phone are captured on the onboarding form.

Services: Charm is a Go-To-Market Business Process Outsourcer (GTM BPO) providing Enginius.ai sales expertise and lead generation services per the selected package: lead acquisition against ICP criteria agreed at kickoff, systems and infrastructure setup, and campaign development with ongoing strategic support.

MASTER SERVICES AGREEMENT

This Master Services Agreement ("Agreement") is entered into as of the acceptance date recorded on this page (the "Effective Date"), by and between Charm, registered as Didin Customer Service, LLC ("Charm"), located at 1220 E. Henry St, Tempe, Arizona 85281, and the client identified on the Order Form above ("Client").

1. Services

Charm provides an AI-powered lead generation system with outbound efforts via email and LinkedIn campaigns promoting Client's goods and services for the purpose of generating and nurturing leads for Client (each, a "Campaign"). "Lead" means a potential customer contacted through LinkedIn or email for the purpose of Client offering its goods or services. Charm performs the services in a timely and workmanlike manner. Scope changes require written agreement before work begins, and Charm may charge reasonable costs associated with such changes.

2. Charm's Representations and Warranties

Charm has full power and authority to enter this Agreement; performing it violates no other contract; lead sources infringe no third-party rights and promote no prohibited content; and performance complies with applicable law.

3. Client Responsibilities

Client has full power and authority to enter this Agreement; performing it violates no other contract; and contact data Client furnishes has been diligently verified as serviceable and current.

4. Content

All creative campaign assets are created by Charm. Charm may request existing content from Client to leverage in Campaigns. Client grants Charm a limited, non-exclusive, revocable, royalty-free license to use Client's marks solely to perform the services, ending with the Campaign or this Agreement. Client retains all rights in its intellectual property.

5. Placement and Approvals

Before launch, Charm sends test materials for review. Client has a 24-hour window to object; silence is approval. Client may review each email before every new send, with the same 24-hour window.

6. Term and Termination

The engagement runs an initial term stated on the Order Form (the "Initial Term"), then month-to-month. Fees for the Initial Term are committed at acceptance; neither Party may terminate for convenience during it. Either Party may terminate for material breach uncured within fifteen days of written notice. After the Initial Term, either Party may terminate on thirty days written notice. On termination, Client pays fees accrued through the effective date; if Client terminates for Charm's uncured material breach, prepaid fees for whole unstarted months are refunded.

7. Payment and Invoicing

All fees are payable in advance. The onboarding fee and first monthly period (or the discounted Initial Term fee, where paid-in-full is selected) are due at acceptance and presented for payment on this page through QuickBooks. Client authorizes payment by card or bank transfer through Intuit QuickBooks Payments; card and bank details are held by Intuit, never by this page. Subsequent monthly fees are invoiced in advance of each monthly anniversary of kickoff, invoice delivered seven days prior. Paid-in-full reflects the discount stated on the Order Form; the onboarding fee is not discounted. Late amounts incur 1.5 percent per fourteen days past due, and the program pauses seven days after written notice of nonpayment.

8. Data Access

Charm retains access to Client data to perform the services. Client may view and export all Campaign data at its discretion.

9. Confidentiality

Each Party protects the other's Confidential Information with at least commercially reasonable care, uses it only to perform this Agreement, and limits disclosure to those under equivalent obligations. Standard exclusions apply (public information, prior knowledge, independent development, rightful third-party receipt, Campaign materials and metrics). Trade secrets are held indefinitely; other Confidential Information for five years. Legally compelled disclosure requires reasonable prior notice.

10. Non-Compete

Charm shall not use Leads provided by Client for the benefit of competing ventures, during the term and for one year after.

11. Indemnification

Each Party indemnifies the other against losses, including reasonable attorneys' fees, arising from its breach of this Agreement.

12. Governing Law

Arizona law governs; exclusive jurisdiction lies in Arizona courts.

13. Severability

Invalid provisions do not void the remainder; the Parties negotiate replacements in good faith preserving original intent.

14. Successors and Assigns

No assignment without written consent, except to a merger successor, asset purchaser, or commonly controlled entity.

15. Independent Contractors

Charm performs as an independent contractor. No partnership, joint venture, agency, or employment is created.

16. DNC Compliance

Both Parties comply with all applicable Do Not Call and Do Not Contact regulations, maintain lists against registries, honor DNC requests promptly, and keep required records.

17. Waiver and Remedies

No waiver except in signed writing. Remedies here are in addition to those at law or equity.

Electronic Acceptance

Acceptance through this page, together with the typed name and the recorded SHA-256 hash of the Order Form and this Agreement as displayed, constitutes a binding electronic signature under the U.S. ESIGN Act and UETA. Charm: Didin Customer Service, LLC, by Chris Booth, Owner.

E-signature
✓ Proposal accepted
Signed
Email
Organization
Package
Record ID
Terms hash · SHA-256 of exactly what you signed
Payment · due today
Pay now →
Your secure payment link is being prepared. If checkout does not open, use the button above (card or ACH through QuickBooks).
⬡ Our guarantee

If we miss ROI, month four is on us.

If the engagement has not returned its cost by the end of month three, we run month four entirely at our cost, full effort, nothing held back, and we will connect you with people we have run that month for so you can hear how it went. And at month three you choose: keep going, or take the campaign matrix, the copy and the target pulls and run them yourself, with the SDRs you hire inheriting all of it. They are yours either way.

Claim your guarantee →

10 / What happens nextWhen Enginius signs.

01

The parameter session

The working session where we size the device-maker universe live, rank the five buyers, map what your agents already track against what we pull, and load your customers, board and partners as suppression. It ends with a target list on screen, not with a follow-up email.

02

Buyers hear from Enginius inside week one

The founder-story track goes live on LinkedIn in the first few days while domains warm in parallel. The clearance, enforcement and MDR pulls get built, your agents' feeds get wired in, and you review every target list before a single message sends.

03

Full volume, then your first hires inherit it

Cold plays live around week four at full volume. Every two weeks a fresh cycle of four campaigns ships, built from what the last cycle showed. When the numbers say which message converts, your SDR hires start with a proven script instead of a guess. At month three, you choose what happens next.

Four customers proved the platform.
Twenty is a conversation count.

Pick a kickoff date. Week one is the parameter session, the ranked buyers, your agents wired in as a feed, the suppression list loaded, and the founder story already reaching regulatory leaders on LinkedIn. None of that waits on infrastructure to warm.

Pick your kickoff date →