TCYM — Signup-to-Live Readiness

The honest read

The ads are the easy half. Demand generation is mostly built. What breaks at 10 signups is fulfillment — turning a "yes" into a real funeral home running a customized Grace on their own line, billed, under contract. That machine isn't built yet. Ten simultaneous yeses against an unbuilt fulfillment line is how a good problem becomes a reputation problem.

Recommendation: waitlisted pilot cohort of 3, not 10 at once Enrollment pipeline exists in GHL · fulfillment rails do not

★ Account architecture — one sub-account per home

Correction (7/12, Topher's catch): a customer does not run on the demo Grace or the TCYM sub-account. That account is your storefront. Every funeral home gets its own GHL sub-account with its own tailored Grace and its own number. Director paging defaults to automated voice call + email (no A2P, no website); per-home SMS registration is an optional upgrade, not a requirement. Two tiers, and it's the thing that makes the whole model scale cleanly.

Tier 1 · TCYM sub-account (Aspire-owned)

The storefront + demo. One, forever.

· The public demo line (740) 272-5590, Grace answering as fictional Harmony
· The site Get Started form → lands leads here
· The Marketing + Enrollment pipelines (your CRM for prospects)
· A2P registered under Aspire Digital LLC — for your marketing/demo sends only

Tier 2 · Per-home sub-account (one per customer)

The product they actually pay for.

· Their own Grace — cloned from your template, KB swapped to their real facts
· Their own phone number that Grace answers on
· Director paging by voice call + email (no A2P); optional per-home SMS brand (their EIN) if they want texts
· Their contacts, call records, paging workflow — isolated, billable, deletable on churn

Clone, don't rebuild

Build one TCYM template snapshot (Grace prompt, workflows, custom fields, pipeline, tags). Per home: new sub-account → load snapshot → swap the KB. Verify in console whether Voice-AI config travels in a GHL snapshot — if not, the prompt/KB paste is quick either way.

Page by voice + email → no A2P at all

A2P 10DLC governs SMS/MMS only — automated voice calls and email are entirely outside it. So the default paging channel is an automated phone call + email to the director: zero brand, zero website, zero carrier clock, and a ringing phone is harder to miss at 2am than a text. This makes the "no website" problem disappear.

SMS is optional — and doesn't need their website

Only if a home insists on text paging: register that home's own brand — Sole Proprietor if no EIN (website not strictly required), Low-Volume Standard if they have one. No website → use their Facebook/Google Business page + an Aspire-hosted Privacy Policy + Terms page (required on every campaign since 2026). Reviewers still prefer a live site, so expect resubmits — another reason voice+email is the default.

Two knock-ons to keep in view: (1) each per-home sub-account carries GHL cost — SaaS sub-account fee + phone + AI usage — so confirm the $399/mo clears it with margin at 1, 10, and 50 homes. (2) There's no compliant "one Aspire brand texts every director" shortcut — the rules push SMS registration down to each client entity. You don't need one anyway: voice+email removes the need for SMS. EIN is only a hard intake field for homes that opt into SMS (CLI-165).

1. The reframe — you're running two funnels

A signup doesn't stress the website. It stresses you. Everything you've built so far feeds the top funnel. Almost nothing exists for the bottom one — and the bottom one is where the money, the promises, and the liability live.

Demand funnel — mostly built ✅

· Site (studio live), demo line, Get Started form → GHL
· FB Page, Pixel, ad account, creative pipeline
· Grace demo answering as Harmony
· Marketing + Enrollment pipelines exist in GHL

This half converts a stranger into a "yes." It scales with ad spend.

Fulfillment funnel — mostly NOT built ⚠️

· No way to collect $1,995 setup or start $399/mo
· No service agreement / contract
· No client intake questionnaire (the data to build their Grace)
· No per-home provisioning kit (new sub-account + cloned Grace + their A2P)
· No phone-forwarding playbook (how calls reach Grace)
· FD script review still open (the grief-liability gate)
· No support / uptime plan once a home is live

This half turns a "yes" into a live, paying, defensible customer. It scales with your hours — until you systematize it.

The trap: ads are the fun part, so it's tempting to floor the top funnel. But every "yes" you generate before the bottom funnel exists becomes a person waiting on a promise you can't yet keep — in the one industry where a dropped promise around a death is unforgivable. Build the bottom funnel to the depth of 3 clients first. Then open the ad valve.

2. The signup-to-live pipeline

This already exists in GHL (TCYM sub-account, TCYM Enrollment pipeline). The stages are real; what's missing is the machinery at each stage. Here's each stage, who moves it, and where it stalls today.

Stage	What has to happen	Owner	Gap today
New Inquiry	Form submit or demo call creates the contact + opportunity	Automated	Lead-alert still fires on hang-ups (noise)
Demo Booked	Prospect books a call to see Grace on their own scenario	Topher	No booking calendar wired yet (v1.1)
Demo Completed	You walk them through Grace, answer objections, quote	Topher	Needs a repeatable demo script + one-pager
Enrollment Started	They say yes → send contract + intake questionnaire	Topher / Aria	No contract, no intake form exist
Setup Paid	$1,995 setup collected; $399/mo subscription starts	Topher	No payment rails built (fake Stripe was removed)
Provisioning	New sub-account + cloned Grace, real KB, their number, paging, their A2P, forwarding, QA	Aria + Topher	Documented, never run end-to-end on a real home
Live	Grace answers real families; you monitor + tune weeks 1–2	Aria + Topher	No monitoring, no support SLA, no on-call plan
Closed/Lost	Track why deals die → feed back into ads + demo	Aria	Fine for now

Read: the top three stages are demand (built). The bottom five are fulfillment (the gaps). Every red cell is a promise you can't yet keep at scale.

3. Onboarding one client — the runbook

This is what "getting one funeral home live" actually is. Most of it is Aria-buildable; the human-judgment and client-coordination steps are yours. Time estimates assume the rails from §6 exist — without them, double everything.

1 · Intake — collect the truth about their home

~30 min client · Topher

Name, address, hours, directors + on-call rotation, services & real pricing, packages, facilities, aftercare, what to say / never say — plus their legal business name, EIN + business address for A2P. Grace can't invent facts — this is the input that makes her safe, and the EIN is what starts their text-alert clock. Gate everything on it.

2 · Spin up their sub-account + clone Grace

~2–3 hr · Aria (automatable)

Create their own GHL sub-account, load the TCYM template snapshot, and swap the Harmony fiction for their real KB. This — not the demo account — is where their Grace lives. Biggest labor chunk and the most templatable; the intake → KB pipeline is the #1 thing to automate before scaling. (See ★ Account architecture.)

3 · Provision the number + call routing

~1–4 hr · Topher + client's carrier

Buy a number in their sub-account for Grace, then get the home's calls to reach it — after-hours forwarding on their existing line. This depends on their phone system (POTS / VoIP / RingCentral / whatever). This is the #1 place onboarding stalls — it's their telecom, not yours. See §5.

4 · Wire paging (voice + email)

~30 min · Aria

Default page = automated voice call + email to the on-call director, plus the urgent-hold escalation for coroner/ME cases — confirm they actually receive a test page. Neither channel touches A2P, so this goes live day one with no carrier clock. SMS paging is an optional later upgrade for a home that asks (then register their own brand — sole-prop if no EIN; see §5).

5 · QA gauntlet in their context

~1 hr · Aria + Topher sign-off

Re-run the 10-call gauntlet against their real facts. Director listens to at least the at-need + removal calls and signs off before go-live. A wrong price or wrong service quoted to a grieving family is the failure mode that ends the company.

6 · Go live + watch weeks 1–2

ongoing · Aria monitors, Topher owns relationship

Flip forwarding on. Review every call transcript daily for the first two weeks, tune, and check in with the director. This is where a pilot becomes a testimonial — or a refund.

Realistic first-client cost: ~5–8 hours of combined Aria+Topher work, spread over ~1–2 weeks of calendar time (the client's forwarding + sign-off are the slow parts, not our build). By client 3–4, if you've automated the intake→KB step, that drops toward ~2–3 hours.

4. Capacity math — what 10 at once really costs

Your scenario: 10 people say yes in a short window. Here's the arithmetic honestly.

~50–80

combined work-hours to onboard 10, at today's hand-built pace

$19,950

setup revenue (10 × $1,995) + $3,990/mo recurring — if all 10 close & stay

botched at-need call, live and public, can cost you the next 10

The bottleneck isn't the site or Grace — it's you + verification.

Grace scales infinitely; trust doesn't. Every home needs a human (you) to demo, close, sign off on QA, and own the relationship. And every home shares one A2P registration, one support pager (you), one reputation. Ten homes going live the same week means ten first-week-monitoring windows stacked on one person. That's not a capacity problem you solve with more compute — it's one you solve with sequencing.

Recommendation: Don't onboard 10 in parallel. Run a waitlisted pilot cohort of 3. Onboard them hand-built, learn what breaks, systematize it (automate intake→KB, write the forwarding doc, harden the QA checklist), then open the gate to the next cohort. "We onboard in structured 2-week waves so every home gets it right" is a stronger sell to a funeral director than "sign up instantly." Scarcity + care beats speed in this market.

5. The 8 things that will bite

Ranked by how likely they are to actually stop you cold once signups start.

1. Getting calls to Grace is the client's telecom, not yours.

Every home has a different phone setup. After-hours forwarding is per-client fiddly work and the top reason onboarding stalls. Prep: a plain-English "how to forward your after-hours line" guide per major carrier, plus a fallback — publish a fresh number they advertise, so you never depend on their carrier at all.
2. You can't collect money yet.

The fake Stripe checkout was removed for launch. There's no live rail for the $1,995 setup or the $399/mo subscription. Prep: stand up a real payment path (GHL payments or Stripe) — this is the difference between "Setup Paid" being a real stage and a wish.
3. No contract = no protection.

Signing a paying B2B client who handles death needs a service agreement: SLA, liability cap, recording/data terms, the fair-use clause, cancellation. Prep: a simple MSA template. This is your call (Tier-3) and worth 30 min of a lawyer's eyes.
4. The grief-liability gate is still open.

The retired-FD review of Grace's scripts ($500–1.5K, CLI-158) must close before a real grieving family hears her. Demo-Grace answering fictional Harmony is low-stakes; real-Grace on a real at-need call is not. Prep: book the FD review now so it's not the thing blocking your first close.
5. SMS is the trap — page by voice + email instead.

A2P 10DLC governs SMS/MMS only; voice calls and email are entirely outside it (verified 7/12, Twilio + GHL docs). So the fix for "many clients have no website" is to not use SMS for paging — an automated voice call + email needs no brand, no website, no 1–4 week clock, and rings through at 2am. If a home specifically wants SMS: register their brand (Sole Proprietor if no EIN — website not strictly required; Low-Volume Standard if they have one), substitute their Facebook/Google Business page for a site, and host their Privacy Policy + Terms yourself. Prep: make voice+email the product default; treat SMS as an opt-in upgrade.
6. Per-client fact accuracy is a safety issue, not a nicety.

Grace quoting the wrong price or a service the home doesn't offer, to a grieving family, is catastrophic and triggers FTC Funeral Rule exposure. Prep: the intake questionnaire is the gate — no go-live until the KB is verified against the home's real price list, director-signed.
7. Once live, you own the 2am uptime.

A funeral home's phone line going dark is an emergency. As a ~1-person op you need a monitoring signal and an honest SLA. Prep: decide what "support" means (business-hours? on-call?), what the fallback is if Grace fails (ring-through to the director's cell), and say it in the contract. Under-promise here.
8. Recording consent varies by state.

Grace records. Two-party-consent states need her disclosure worded and configured accordingly. Ohio is one-party (disclose anyway), but your first out-of-state client changes the rule. Prep: a per-state disclosure config + note it as a pre-go-live checklist item.

6. Build before the ads convert

The minimum fulfillment rails so the first "yes" doesn't catch you flat. Marked by who owns it — most are Aria-buildable this week.

Rail	Why it's on the critical path	Owner
Client intake questionnaire	The input that makes each Grace true + safe. Gates provisioning.	Aria — this week
Payment rail (setup + subscription)	"Setup Paid" is fiction without it. Blocks revenue.	Aria builds · Topher connects bank
Service agreement / MSA	Liability + SLA + recording terms before any real client.	Topher (Tier-3) · Aria drafts
Phone-forwarding playbook	Removes the #1 onboarding stall. Reusable per client.	Aria — this week
Per-home provisioning kit	The repeatable sub-account spin-up: template snapshot + clone-Grace + swap-KB + A2P submit checklist. Turns each home into a runbook, not a project.	Aria — with pilot 1
Intake → KB automation	Turns the 2–3 hr build into minutes. The scaling unlock.	Aria — after pilot 1
FD script review	The grief-liability gate. Blocks first real family call.	Topher — book now (CLI-158)
Demo script + one-pager	Makes "Demo Completed" repeatable, not improvised.	Aria — this week
Waitlist / cohort mechanism	Lets you capture 10 yeses but onboard 3 at a time, with dignity.	Aria — this week

Seven of these nine are mine to build or lead. Give me the go and I'll knock out the intake questionnaire (with the A2P/EIN fields), forwarding playbook, demo one-pager, and waitlist first — those unblock the fastest.

7. Decisions only you can make

The tips you asked for are really a short list of forks. None are urgent this second, but each one shapes what I build.

Cohort size + cadence.

My rec is 3 at a time in 2-week waves. Your call on the number. It sets the whole capacity plan.

Pilot pricing.

Setup fee is waivable. Do the first 3 get free/discounted setup in exchange for a testimonial + case study + a real reference call? That trade is usually worth more than the $1,995. Revenue timing is your lane — I'll never press it.

Call-routing default.

After-hours-only (safest first sell — Grace only catches what a human would've missed) vs. full-time answering (bigger value, bigger risk). I'd start after-hours-only for pilots.

Support commitment.

What do you promise for uptime + response when Grace hiccups at 2am? Be honest — a solo op should promise business-hours support + an automatic fail-through to the director's cell, not 24/7 heroics.

Contract depth.

DIY template vs. one pass by a real attorney. In an industry adjacent to death + AI + recording, I'd spend the few hundred dollars once.

8. Recommended posture + next 5 moves

If ads run tomorrow and yeses start landing, here's the plan that keeps quality high and you sane.

Posture: capture unlimited interest, fulfill in disciplined waves. The ad's job is to fill a waitlist, not a queue you're obligated to clear this week. Every prospect hears: "We onboard funeral homes in small, careful cohorts so yours is done right — here's your wave." That protects the product, the families, and your name in a small, referral-driven industry.

1This week (Aria): build the intake questionnaire, phone-forwarding playbook, demo one-pager, and a simple waitlist capture. These unblock everything downstream.
2This week (Topher): book the FD script review (CLI-158) and decide cohort size + pilot-pricing trade. Those are the two things only you can move.
3Before first close: stand up the payment rail + MSA template. No signed, paid client without both.
4Pilot cohort of 3: hand-build each, watch weeks 1–2 like a hawk, collect a testimonial + reference. This is your proof + your marketing.
5Then systematize + open the gate: automate intake→KB, harden the runbook, and let the next wave in. Now 10 is easy because the machine is real.