The working sample is the subject line.

What is sample-first outreach in Nerxus One?

Sample-first outreach is a first email that leads with a live working preview tied to a named finding, not with a paragraph about your agency. The subject can be the link. The first line can be I noticed this problem, so I already built you a DEMO. Here is the live URL. The buyer is the marketer. The shop is your customer. You still send. They still decide.

The loop is short when you do not skip pieces. Scout saves the listing. A detector stamps a state. Radar writes the sentence and the fulfillmentActionId. Forge opens that builder and leaves the asset in DEMO. Relay drafts from the finding, runs ComplianceGate, and waits for you in Supervised. Pulse tracks the deal. Steward inherits if they pay.

Most outbound tools start at a merge field. Most audit tools start at a PDF. Most site builders start after a signed SOW. This wedge starts when the preview loads, because a specific failure plus a working sample is the sentence owners finish.

If you cannot open the URL in a private window, you do not have sample-first. You have a promise. Promises are what every other vendor mailed Tuesday.

Wedge names in sequences stay detector-led: No-Website, No-SSL, Permit-Lead, Chair-Hour Loss, Service-Gap. Merge fields do not invent a personality. The DEMO URL is the merge that matters.

Scout found. Radar named. Forge built. Relay sent. Pulse tracks the deal. Steward inherits if they pay. Skip Forge and you are back to a PDF. Skip ComplianceGate and you are back to a burned domain.

Why the working sample is the subject line

The working sample is the subject line because owners delete agency introductions and they click things that look like their shop. A subject that names the gap and carries a short live link outperforms a subject that names you. You can still put your brand in the footer. The cover of the email is their problem, already half-handled.

I noticed you have no booking button and a dropping rating, so I built a preview that takes a Tuesday 3 pm. Here is the link. Book me if you want it on your domain. That is the whole motion. Calendar in that mail is your book link, not their patient book, unless you already sold them the other calendar.

Sequences that start with value then pitch still stop on reply. Quiet hours still apply. Warmup caps still apply. Sample-first is not a license to spray DEMOS at a metro. ICP exclusions still run. Unknown still does not go in the first line.

If your ESP cannot put a tracked URL in a subject, put it in the first sentence in the same words. The product noun stays DEMO. Do not write complimentary mockup. Do not write AI-generated concept. Those sentences teach them to wait for the real thing, which you already have.

How I noticed this problem becomes a DEMO link

I noticed this problem becomes a DEMO link because the finding already knows the builder. no-website opens the website tool on that business uuid. You confirm CTA, accent, services, hero. The preview renders. You copy the URL into the Relay draft that already has the finding merge vars. ground_lint wants X and Y bound. The offer clause names the enabled action.

No SSL can still be a site DEMO if you sell the rebuild, or a smaller trust note if you only sell the certificate work. ADA is a labeled draft plus professional review recommended, or a code-level DEMO if that is what you fulfill. Do not attach an overlay and call it a sample. Hiring receptionist becomes an inbound demo number they can call. You do not call them.

Service-gap becomes a service page that says the missing line in the first screen. AEO becomes a page that answers the prompt you actually sampled, if a probe block exists. Collect-page gap becomes Echo's collect page with public buttons for every visitor. Private recovery sits alongside. There is no gating branch.

Persist first. Pass the uuid. If you paste a Yelp URL into a disconnected builder, you have left the seam and the names will drift. The DEMO should still look like the listing Radar diagnosed, because it is the same row.

What DEMO means, and what DEPLOY still waits for

DEMO means a working, shareable Forge preview in asset mode DEMO. You can click CTAs. You can change device width. You can toggle Preview and Code where the shell offers it. The shop can open it without Clerk. DEPLOY means a human promoted that object toward a client domain or a live line, approval-gated, lineage kept.

Mixing the modes is how agencies point real hostnames at half-finished previews because a progress bar looked done. The header should say DEMO until a person says otherwise. Job rows start queued. Failures persist as failed jobs. The route returns the stored job, not a vibe from the engine.

Voice DEMO is a demo number. Live line is after they pay. Inbound only, locked on the Autonomy Matrix. Website DEMO is a preview host. Client domain is DEPLOY. Collect DEMO is a shareable page. Their reputation program is a later Echo campaign with consent.

BYO slots for Lovable, Bolt, v0 are designed. The live engine is a pure builder that can see a secret exists and does not currently call the connected provider account. Do not tell a prospect their DEMO is rendering on a vendor we never invoked.

How One Free Fix is the DEMO, not a magic button

One Free Fix is the DEMO, not a magic button, because the only honest free objects in the loop are a working preview you already built or a pasteable schema block Atlas can fill from stored fields. Radar does not auto-spawn a live site on diagnostic load. FreeFixCard is not on that DTO.

Report R7 can embed JSON-LD with no empty placeholders, no guessed https, no fake aggregateRating. That is a gift an owner can paste today. It is not a website. If your pitch needs a website, open Forge. If your pitch needs a number, provision the demo line. If your pitch needs replies, draft them in Echo and hold low-star ones.

Marketing that says one click remediates ADA, ranks you in ChatGPT, and deploys DNS is the magic we refuse. Professional review recommended stays on legal drafts. Probe claims stay sampled. DEPLOY stays gated.

When a report says free fix, the surrounding copy should name the object. Schema block. Preview URL. Demo number. If the section cannot name it, delete the section. A promise is not a fix.

Why Relay still has to pass ComplianceGate

Relay still has to pass ComplianceGate because a live DEMO does not make a cold email legal or deliverable. The send is still email-first on the tenant's verified sending domain. Unverified is a blocking gate. Physical address and unsubscribe still lint at draft time. Stop-on-reply still exists.

The gate brands the message. send() cannot run without a GatedMessage produced by evaluate(). A hand-built verdict does not typecheck. Adding a new channel later cannot slip past a rule by not being named in a switch. autonomousSafeChannels is derived from the registry.

No cold SMS. No autonomous cold voice. No review gating in any copy the sequence proposes. Forms consent is the only birth path for a compliant SMS list, and that list is not this wedge. Sample-first is mail plus a link.

Supervised means you see the draft, the lint, the DEMO URL, and then you say yes. Autonomous send is an opt-in per action, never a mood you set because the queue was long. Kill switch still precedes everything.

What Forge opens from fulfillmentActionId

Forge opens from fulfillmentActionId the exact sub-tool the detector registered: website builder, inbound voice, instant responder, conversion widgets, local SEO and AEO, compliance drafts, retention sequences, incentive and offer builders, content via Muse. Shared BuildShell: config and refine on the left, live preview on the right.

You can start from Radar Fix this, from a Pulse next action, from an ICP demoMode prebuild, or from a saved business. The business context is already there. You do not retype the NAP into a blank canvas and hope.

Muse drafts a month if content is the finding. Publish stays gated. Echo drafts replies if reputation is the finding. Low-star holds. Collect pages cannot hide public buttons. Compliance fixers stay drafts. We are not their law firm.

Asset Library tracks DEMO to DEPLOY lineage per business. If you cannot find last Tuesday's preview, you are in the wrong folder or you never persisted. Persist first is not a slogan. It is how the uuid stays one.

Who sample-first is for, and who should send a PDF instead

Sample-first is for marketers who can fulfill this week and who will open the builder before they open Gmail. Web studios, local SEO shops, reputation people who will actually ship a collect page, inbound-voice sellers with the action enabled. If that is your week, the DEMO is cheaper than a deck.

Send a PDF instead when the finding is a leave-behind after a meeting, a monthly client pack, or a funding pre-screen that must not look like a site you already built. Atlas is good at paper. Paper without a next DEMO is still paper.

If you only broker introductions, you will hate this motion. If you only want a list, Scout is enough and this page is surplus. If you sell to LinkedIn titles, the sample is a different object and a different company.

Agencies with two books still isolate DEMOS by tenant. There is no white-label sub-account resale in v1. Your mark on the preview comes from branding profiles and templates, not from a franchise switch.

Common mistakes that make a DEMO sound like a scan

The first mistake is I scanned your site in the subject. Owners have been scanned. They have not been handed a Tuesday 3 pm that works. Name the problem and the link. Skip the autobiography of the crawler.

The second mistake is a generic theme with the wrong city in the hero. Vertical templates change section order. You still review public facts. A hallucinated phone number on a DEMO is how you lose the meeting you have not booked.

The third mistake is attaching twelve previews. One headline finding. One URL. The roadmap can live in Atlas if they ask. The inbox gets a single object.

The fourth mistake is sending from personal Gmail because the verified domain felt like paperwork. The gate will block you in-product. If you bypass the product, you bypass the reason sample-first does not burn the tenant. Do not. A fifth mistake is a DEMO with a hallucinated phone. Review public NAP before you send the link. A sixth is twelve previews in one thread. One finding, one URL.

How marketers attach the live link in a real week

Marketers attach the live link in a real week by picking Monday's ICP, saving a short list, deep-diagnosing three rows Tuesday, building three DEMOS, and approving three Relay drafts Wednesday. Thursday is replies. Friday is Watchtower or a second DEMO for the one who asked a question.

Pulse campaign names stay signal-led: No-Booking Dentists Austin. Forecast sums FEE. Do not pitch the modeled monthly as your invoice. The DEMO is free as a sample. The DEPLOY is the job.

Nova can be asked to draft outreach for the businesses Radar flagged this morning. It should route to Relay with Radar's findings and Forge's URLs, then come back last. If it tries to send, Supervised says no.

Get started if you want into the next batch. Describe the kind of marketer you are. We will not invent a customer who closed from a DEMO, and we will not invent a price for the preview host. Instant responder and conversion widgets are the same DEMO then DEPLOY spine when speed-to-lead was the finding. Muse calendars stay drafts until you approve a post. ComplianceGate still brands the envelope. Supervised still waits on a yes.

If Forge is still rendering, do not send the draft. A 404 in the first email is worse than waiting an hour. The subject promised a working sample. Dead links teach the owner to ignore you.

How Pulse, Atlas, and Steward inherit the same DEMO

Pulse, Atlas, and Steward inherit the same DEMO because the asset is keyed to the business uuid, not to a campaign nickname you typed. Pulse can show the preview on the deal. Atlas can embed the URL or the schema block in a report. Steward can attach the promoted asset when the stage goes Closed.

Campaign names stay signal-led so the board reads like the wedge: No-Website Roofers Austin, Permit-Lead HVAC, Chair-Hour Loss Dental. The DEMO is the object on the card. If two deals share a shop, you already have a duplicate problem. Dedupe on the listing’s own ID still applies.

When they reply interested, the sequence stops. Suggested reply is gated. You can send the report token next, or a book link. You should not send a second unrelated DEMO because you were proud of the catalog. One object, then a meeting.

Lost is a stage. The preview can stay in the library. Watchtower can still watch the listing. A year later the same uuid can become a new deal without a new import. If you deleted the DEMO, Asset Library lineage is how you find the parent.

Invoices after close are your own Stripe account in M07, not a number this site will print. Health is a band. Upsells come from leftover findings, not from a second personality. The DEMO you used to win should still be the ancestor of what they click as a client.

What the email must contain besides the live link

The email must contain, besides the live link, the finding in the owner's language, a required physical address, an unsubscribe path, and a book link that is yours. Spam-lint runs at draft time. Missing pieces fail the draft, not the inbox after a suspension.

ground_lint wants X and Y bound to signals. I noticed your site has no SSL is a signal. I help businesses grow is not. The offer clause names the enabled action: I built a preview site, I provisioned a demo number, I drafted a collect page. If the action is off, the sentence should not exist.

Attachments are optional. A 360 token can ride along. A screenshot of Radar internals should not. Internal bands stay off the thread. Modeled dollars, if you dare them in mail, still need assumptions. Most wedges do not need a dollar in the first note.

Reply classes are interested, question, not now, unsubscribe. SLA clocks sit on the thread. A question about the DEMO is a good hour to hop on your calendar. A not now is a Watchtower candidate, not a reason to send the same link four more times this week.

If they ask who built it, you can say your agency. Powered by Nerxus is off on reports by default and should stay off in the email unless you want the conversation to become a software demo. Sample-first sells the fix. The platform is how you made it.

ICP demoMode is how the loop is allowed to pre-build. preview_site, demo_number, or none. None is weaker. Prebuild after readiness, not before. Forty previews for rows that will die on named-buyer is wasted Forge time.

Quiet hours and mailbox warmup are still math. A perfect DEMO sent at 2 a.m. on an unwarmed domain is how you meet the spam folder. The wedge does not outrun the gate.

Guides on this site can teach the motion even if you never buy. The product page is the nouns. The guide is the week. Do not mix a generic scan pitch into either.

What does sample-first mean if I have not built a site yet?

Sample-first means the Forge DEMO is the subject, so if you have not built a site yet you do not have the wedge. You have a finding. Open the builder from fulfillmentActionId. Wait for the preview to load. Then write.

Atlas can still embed a pasteable JSON-LD block from stored fields. That is a gift an owner can paste today. It is not a website. If your pitch needs a website, open Forge. If your pitch needs a number, provision the inbound demo line.

demoMode none is allowed on an ICP and weaker. Prebuild happens after readiness, not before. Building forty previews for rows that will die on named-buyer is how you burn Forge time.

If you cannot open the URL in a private window, you do not have sample-first. You have a promise. Promises are what every other vendor mailed Tuesday.

Is the DEMO a sales meeting or a working preview?

DEMO is a working Forge preview you can open, not a sales meeting and not a Figma file. You can click CTAs. You can change device width. The shop can open it without Clerk. DEPLOY is the gated publish.

Mixing the modes is how agencies point real hostnames at half-finished previews because a progress bar looked done. The header should say DEMO until a person says otherwise. Job rows start queued. Failures persist as failed jobs.

Voice DEMO is a demo number, inbound only. Live line is after they pay. Website DEMO is a preview host. Client domain is DEPLOY. Collect DEMO is a shareable page. Their reputation program is a later Echo campaign with consent.

BYO slots for Lovable, Bolt, v0 are designed. The live engine is a pure builder that can see a secret exists and does not currently call the connected provider account. Do not tell a prospect their DEMO is rendering on a vendor we never invoked.

Can I send the report without a live link?

You can send a report without a live link. You should not call that sample-first. The report is proof. The live URL is the subject. Atlas without Forge is a prettier audit.

The finding and the link are the wedge. A branded 360 is optional proof. A report with no DEMO is what every audit vendor already mailed. Sequences that start with value then pitch still stop on reply.

Share tokens on /r/ can ride along. A screenshot of Radar internals should not. Internal bands stay off the thread. Modeled dollars, if you dare them in mail, still need assumptions. Most wedges do not need a dollar in the first note.

If they ask who built it, you can say your agency. Powered by Nerxus is off on reports by default and should stay off in the email unless you want the conversation to become a software demo. Sample-first sells the fix.

What happens if DEPLOY is still gated when they love the preview?

If DEPLOY is still gated when they love the preview, that is the product working. The thing you showed and the thing that goes live should be the same object with a parent id. A human promotes it toward a client domain or a live line. Steward inherits it if they pay.

Asset Library tracks DEMO to DEPLOY lineage per business. If you cannot find last Tuesday's preview, you are in the wrong folder or you never persisted. Persist first is how the uuid stays one.

Do not promise a DNS flip from a Relay draft. Do not point a real hostname at a half-finished preview because a progress bar looked done. The header should say DEMO until a person says otherwise.

Invoices after close are your own Stripe account in M07, not a number this site will print. The DEMO is free as a sample. The DEPLOY is the job. Forecast sums FEE, not a poetic monthly from the preview.

Does sample-first require autonomous send?

Sample-first does not require autonomous send. Supervised is the default. You see the draft, the lint, the DEMO URL, and then you say yes. Autonomous send is an opt-in per action, never a mood you set because the queue was long.

Relay still has to pass ComplianceGate. The send is still email-first on the tenant's verified sending domain. Unverified is a blocking gate. Physical address and unsubscribe still lint at draft time. Stop-on-reply still exists.

No cold SMS. No autonomous cold voice. No review gating in any copy the sequence proposes. Forms consent is the only birth path for a compliant SMS list, and that list is not this wedge. Sample-first is mail plus a link.

Dry-run first on any playbook. Kill switch still precedes everything. Quiet hours and mailbox warmup are still math. A perfect DEMO sent at 2 a.m. on an unwarmed domain is how you meet the spam folder.

When is a pasteable schema block the sample?

A pasteable schema block is the sample when the finding is missing machine-readable identity and Atlas can fill LocalBusiness JSON-LD from stored fields with no invented properties. The owner pastes it into a head. It works. It is not a website.

url only if the stored website already parses as absolute http or https. aggregateRating only if rating and count both exist. Absent properties stay absent. HTML-sensitive characters are escaped.

If the finding needs a site, a number, or a collect page, the sample is Forge. Schema you can paste. Rankings you cannot paste. A report that says free fix should name the object. Schema block. Preview URL. Demo number. If the section cannot name it, delete the section.

Radar does not auto-spawn that block on diagnostic load. FreeFixCard is not on that DTO. M05 is where the honest embed lives. M06 is where working previews are born. Keep those rooms straight when you write the first line.

One Free Fix as marketing copy still means you attach a working sample. It does not mean a magic button that ships a live site from the diagnostic header. DEMO first. DEPLOY stays gated. Supervised still waits on a yes.