How the engine writes — a worked example for Bowdark Consulting

What is real here and what is not

Real: the writing rules, word ceilings, banned-phrase lists, fabrication policy, signal types, signature structure, and the audit-and-regenerate step are all lifted from the live system. Nothing in the process section is aspirational.

Composite: the prospect company, its people, and its signal values are illustrative. Meridian Fabrication Group is not a real company. Every signal shown is a type the system actually collects, populated with plausible values so the sequence has something to be built from.

Not sent: these emails were generated for this document. Nothing has gone to anyone.

The sender profile, loaded once

Before any prospect is researched, the system holds a profile of you. It is loaded into every email the engine writes, and it is the only source of permitted claims about Bowdark. If a fact is not in this profile, the writer is forbidden from asserting it.

Below is what we could assemble from your public material. The rows marked confirm are the ones we would sit down and get right with you before a single send.

identity

Bowdark Consulting. Enterprise software consulting and custom business solutions, Dallas–Fort Worth. Four service lines: Spark Consulting, Beacon App Studio, Lighthouse Managed Services, BrightOps Labs. GSA contractor.

confirmed
bowdark.com

positioning

"Turning Bright Ideas into Reality." ERP, customer engagement, data & analytics, and modern-work delivery for mid-market and enterprise operators.

confirmed
site, verbatim

problem you solve

Your site is capability-led rather than problem-led, so this is the first thing we would sharpen together: the specific operational pain a Meridian-sized company feels the quarter before they call you.

confirm
onboarding

proof inventory

Named clients: CenterPoint Energy, Devon Energy, Lockheed Martin, Northrop Grumman, IBM. Client testimonial, verbatim: "delivered everything on time and within budget." GSA contract vehicle. These are the entire universe of claims the writer may make about you — and the named clients come with a hard rule, shown in section 06.

confirmed
site + testimonials

the offer

The specific low-friction thing a first reply gets them. A sequencing conversation, a migration scoping doc, an integration-inventory template.

confirm
your call, not ours

voice profile

Preferred phrasings, banned phrasings, and two or three real samples of how your team writes. The writer mirrors rhythm and word choice, never facts.

confirm
from your existing emails

guardrails

Claims we may never make, topics we may never raise, and the named standards we are allowed to reference. For a firm with defense-prime clients this list matters more than usual — section 06 shows why.

confirm
compliance review

security posture

Off by default. The engine reads every prospect's email-authentication posture, and for IT providers it uses the finding as an opener. A consulting brand usually can't act on a DNS record, so the switch stays off — though for a Lighthouse Managed Services campaign it's worth revisiting.

suppressed
per-brand setting

One prospect, and everything we would know about them

The engine does not write to a list. It writes to a dossier. Below is what a fully researched manufacturing prospect looks like at the moment the writer is handed the pen.

Each row carries its source and its age, because a claim without provenance is a claim the writer is not allowed to use. Rows marked live are collected by the system today. Rows marked niche are the custom sources we would build for your verticals during onboarding.

The company

S-1 firmographics

Meridian Fabrication Group — precision metal fabrication. Plants in Fort Worth TX, Waco TX, and Tulsa OK. Roughly 450 employees. Founded 1982.

live
Apollo · 9d old

S-2 open roles

"ERP Business Analyst" — posted 74 days ago, still open. "Supply Chain Systems Manager" open alongside it. Two systems seats vacant at once.

live
job postings · 2d old

S-3 tech in posting

The BA posting itself names SAP ECC and "supporting integrations to shop-floor and quality systems." Their own words, not our inference. That single line dates their platform and defines the writer's safest opener.

live
posting text · 2d old

S-4 expansion

Announced "Line 3," a new production line at the Fort Worth plant. Commissioning targeted for Q1.

live
news research · 5d old

S-5 defense adjacency

Listed on a defense prime's public supplier directory. Notable for what the writer is not allowed to do with this — see the blocked draft in section 06.

niche
supplier registries

S-6 incumbent read

No systems integrator or consulting partner named anywhere on their site or in press. Reads as in-house-run ERP. inferred

live
site probe · inference-labelled

S-7 email posture

Collected, stored, and never used, because your brand's security-finding switch is off. Shown here only to make the point that collection and use are separate decisions.

suppressed
DNS · 2d old

The person

S-8 contact

Sara Okafor, IT Director. Roughly three years in the role. Based at Fort Worth.

live
Apollo · verified email

deliverability

Address verified before a single word is written. Catch-all and risky addresses are held back rather than burned on a send.

live
bulk verification

why this company

Multi-plant manufacturer inside the size band, running an end-of-road ERP by their own posting, with two systems seats open and a capital project landing on top of both.

live
discovery evaluator

why this person

IT Director owns the platform decision at this size of company. The CFO signs it, but this seat writes the shortlist — and consultants live or die by the shortlist.

live
discovery evaluator

fit score

89 / 100 against your ICP. Below the floor and the company never reaches a writer at all.

live
scored pre-spend

The part that matters

Everything above is gathered before the decision to write. Companies that fail the fit gate are dropped without ever costing a research call or a send. The intelligence comes first, and the outreach is what is left over once the intelligence has done its filtering.

Turning a dossier into four different conversations

A sequence fails when four emails say the same thing four times. So each step is assigned its own angle, drawn from a different signal, with a defined job in the arc. No step is allowed to reuse a previous step's hook.

Step	Day	Job in the arc	Angle	Built from
1	1	Observation, then a challenge. No pitch.	A 74-day-old BA req that names ECC means the roadmap is parked while the team keeps the lights on.	S-2, S-3
2	4	Validation. Deepen with new evidence, one clause of positioning.	Line 3 lands new processes on a platform already flagged for replacement. Sequencing is the real project.	S-4, S-3
3	9	Fresh thread. A different failure mode entirely.	Three plants means integration debt, and a migration is the one chance to collapse it cheaply.	S-1, S-6
4	16	Honest exit. Nothing about us at all.	Acknowledge the quarter they are about to have, and step back.	S-4, S-2

The rules the writer runs under for an IT Director

Tone and length are calibrated to the recipient. An IT Director gets the technical calibration, which is stricter than any other tier.

Length ceiling. Steps 1 and 2 stay under 105 words. Steps 3 and 4 under 80. When a research signal and the word ceiling conflict, the ceiling wins and the signal gets cut.
Peer voice, zero softening. Precise and technical, one technical peer to another. Consultative phrases like "we'd love to walk you through" are on the banned list for this recipient tier — they read as marketing to a technical reader.
Verified facts only. The writer may reference only what is explicitly in this dossier. Inferring their stack, their security controls, or their project status beyond the posting's own words is treated as fabrication.
Collective voice only. "We" and "our", never "I built" or "I noticed". The email is from a firm, not a persona.
One ask. A single closing question, answerable in one line. No calendar links in the body, no "thoughts?", no thirty-minute requests in the first touch.
Plain text only. No bold, no bullets, no images, no em dashes. Em dashes in particular are the clearest tell that a machine wrote it.
No invented anything. No made-up case studies, percentages, client counts, pricing, or regulations. If a claim is not in your proof inventory or this prospect's dossier, it does not get written.

The sequence

Four emails to one person. Every claim carries a marker back to the signal that produced it. Nothing in these emails exists that the dossier did not supply.

Step 1 · Day 1Observation

erp business analyst

To: Sara Okafor, IT Director, Meridian Fabrication Group

Your ERP business analyst req has been open since early May.S-2 The posting itself lists day-to-day support of ECC and the integrations around it.S-3 That combination usually means the roadmap work is parked while whoever's left keeps the lights on.

With mainstream maintenance on ECC winding down, parked gets expensive.

Is the migration question owned by anyone at Meridian right now, or is it waiting on the hire?

Best,

[sending rep]

Bowdark Consulting

[phone]|bowdark.com|LinkedIn|Book a call

S-2Open req with its age. Not "I saw you're hiring" but the specific seat and the specific month.

S-3Their platform, cited from their own posting text. The ECC maintenance timeline is public vendor fact, and it's only usable because the dossier establishes they run ECC.

69 words subject 20 chars mentions of us 0 asks 1 links in body 0

Why it opens there. Step 1 is not allowed to say anything about Bowdark. No client list, no service lines, no years of delivery. The reader does not need to know who you are yet, they need to recognise their own backlog. The pitch is held to step 2, and even there it is capped at a single clause.

Step 2 · Day 4Validation

line 3

To: Sara Okafor, IT Director, Meridian Fabrication Group

Following up on the roadmap question.

The Line 3 announcement caught our eye.S-4 A new production line lands new scheduling, quality, and inventory flows on a platform already flagged for replacement.S-3 Wiring those in twice, once into ECC now and again after a migration, is the expensive version of this project.

Sequencing that is exactly the work we do, and the phrase our clients keep using is on time and within budget.P-1

Would a sequencing conversation before Line 3 breaks ground be useful?

Best,

[sending rep]

Bowdark Consulting

[phone]|bowdark.com|LinkedIn|Book a call

S-4The expansion, used for its systems consequence rather than as congratulations.

S-3The thread from step 1 continues without repeating step 1's hook.

P-1The one clause of positioning the step is allowed, built from the verbatim client testimonial. It is not permitted to become a client-list dump.

84 words subject 6 chars proof claims 1 asks 1

Step 3 · Day 9New thread

integration debt

To: Sara Okafor, IT Director, Meridian Fabrication Group

Different question.

Three plants usually means three flavors of the same process, and the integrations quietly encode all of them.S-1 A migration is the one moment you get to collapse that for free. Teams that skip the inventory step rebuild the same mess on the new platform, just with newer plumbing.

Does an integration inventory exist at Meridian today, or would it need to be built?

Best,

[sending rep]

Bowdark Consulting

[phone]|bowdark.com|LinkedIn|Book a call

S-1The multi-plant footprint, turned into a technical argument the recipient can immediately test against their own environment. That testability is what earns a reply from a technical reader.

67 words subject 16 chars asks 1 closing type binary

The closing question is doing work. "Exists today, or would it need to be built" is answerable in five words by someone reading on a phone between meetings. It is not asking for thirty minutes, it is asking for a reflex — and either answer opens the same conversation.

Step 4 · Day 16Exit

Sara

To: Sara Okafor, IT Director, Meridian Fabrication Group

No reply needed on this one.

Between the Line 3 build-out and a BA seat still open, this quarter looks full from where we sit.S-4S-2 Timing may just be wrong.

Door's open if the roadmap question comes back around.

Best,

[sending rep]

Bowdark Consulting

[phone]|bowdark.com|LinkedIn|Book a call

S-4 S-2The only content permitted in a step 4 is something about them. Not one word about Bowdark, the service lines, the client list, or the testimonial.

44 words subject first name mentions of us 0 asks 0

Why step 4 gives up. The breakup email is the highest-replying step in most sequences, and the reason is that it is the only one asking for nothing. The moment it slips a pitch back in, it stops working. So the rules ban it outright: no company mention, no differentiators, no "closing the loop" subject line, no last-chance framing. It reads the room and leaves.

The signature, and why it looks like that

The writer never composes a sign-off. It is banned from the body entirely, and any closing it tries to sneak in gets stripped. The signature is applied afterwards, identically, to every step of the sequence.

That separation matters for two reasons. The body stays purely about the prospect, and the signature stays consistent no matter which mailbox sends it or which rep's name appears.

Applied to all 4 steps

Best,

[sending rep]

Bowdark Consulting

[phone]|bowdark.com|LinkedIn|Book a call

[your lead magnet, one line]

rep name

Resolved per mailbox at send. The same sequence sent from three reps carries three names and one voice.

variable

no images

No logo, no banner, no social icons. Image-heavy signatures are a spam signal on cold mail and they are the first thing a filter weighs.

deliverability

one bold link

Only "Book a call" carries emphasis. Everything else stays quiet so there is exactly one thing to click.

design

calendar lives here

Never in the body. A calendar link in a first-touch body reads as a pitch and depresses replies. In the signature it is available without being asked for.

doctrine

lead magnet slot

One line, one link, changed per campaign. For Bowdark this is where a migration-readiness scorecard or an integration-inventory template would sit.

confirm

What gets caught before it ships

Every sequence is audited after it is written and before it can be sent. This is the part that is hard to see from the outside, so here is a real failure mode: a first-pass step 3 that did not survive. For a firm whose prospects sit near the defense supply chain, this section is the one to read twice.

Step 3 · first passBlocked

Different question.

With CMMC 2.0 audits starting this fall, suppliers to primes like Lockheed and Northrop will need third-party certification before contracts renew. Most manufacturers your size aren't close.

We've taken 14 manufacturers through NIST 800-171 readiness; most finish in about six weeks.

Worth exploring?

dead_regulatory_deadline The CMMC certification-deadline framing is factually false: DoD suspended the Phase 2 rollout on 13 July 2026, ten days before this document was written, and the writer's ban list was updated the same day. The recipients most likely to catch a stale compliance claim are exactly the defense suppliers Bowdark would be writing to. The engine's regulatory bans move when the regulations move.

cross_profile_leak Lockheed and Northrop are Bowdark's own clients, from the sender profile. The writer dragged them into a claim about the prospect's world. Sender facts calibrate voice and credibility; they are never allowed to migrate into statements about the recipient.

fabricated_stat "14 manufacturers" and "six weeks" appear nowhere in the proof inventory. Invented numbers survive right up until a prospect asks about them.

banned_cta "Worth exploring?" is on the blocked list for technical recipients. Too vague to answer, too soft to act on.

What happens next. The auditor flags the offending step only, and only that step is rewritten. Steps 1, 2, and 4 were clean, so they are preserved untouched rather than regenerated, which keeps the narrative thread intact. The rewrite is handed back with the specific violations attached, then audited again. If a step cannot be written cleanly, the lead is pulled from the campaign rather than sent something weak.

That last point is the one worth holding onto. The system is built to not send when it cannot send something true.

Where these four emails sit in the bigger picture

It takes roughly seven touches to convert. Email is the engine's highest-volume channel, not its only one. The same dossier that produced the sequence above feeds every other touch, which is why they sound like one firm rather than four disconnected efforts.

This document Researched email

Four steps over sixteen days, written per person from the dossier.

Same dossier LinkedIn

Connection and message on the highest-scoring prospects only, timed against the email cadence.

Same dossier Call sheet

Phone days come pre-briefed with the same signals, so a rep opens with the BA req rather than a script.

Same dossier On-site route

Doors clustered by geography for the days when someone is driving the DFW metro anyway.

Ambient Social

Keeps the name familiar before the first email lands.

Ambient Lead magnets

The signature link, built per vertical, that gives a not-yet-ready prospect a reason to raise a hand.

Inbound Managed inbox

Replies land with the full dossier attached, so whoever answers already knows why the email was sent.

What we would need from you to make this real

The sequence above was built from your public website in an afternoon. A live campaign runs on better inputs than that, and all of them come from you.

The offer. What a first reply actually gets someone. This is the single highest-leverage input and it is the one we cannot guess.
The proof inventory. Named clients, real outcomes, actual numbers you are willing to stand behind — and which client names are cleared for cold outreach versus reference calls only. Every claim you give us is one the writer is permitted to make. Everything you withhold, it writes around.
The guardrails. Claims your delivery side will not allow, and the standards and frameworks you are comfortable naming to a defense-adjacent audience.
Voice samples. Two or three emails your team has actually sent and been happy with.
The ICP. Company size, verticals, platform profile, and the titles worth writing to. The tighter this is, the less of your budget goes to companies that were never going to buy.
The niche sources. Which registries, postings, and filings tell us a manufacturer is heading into a platform decision. You know these better than we do. We build them into the engine.

That last one is where the leverage sits. Anyone can send email. The reason a sequence like the one above works is that the company receiving it had an ERP seat open for seventy-four days and a capital project landing on a sunsetting platform, and we knew both before we wrote a word.