Pro tier essential · per-customer Mac mini The textbook 🟢 archetype Wave 1 · Cash engine PRD v1.0 · May 2026

Cold Outbound Ventura ADU
— per-customer Mac minis

AI-driven cold outbound campaigns sold to Ventura County's independent ADU builders. Every paying builder gets their own Mac mini running their own 5-agent fleet, their own sending domain, their own data. The 2026 California ADU law spike (SB 543, AB 462, AB 1154) is the timing wedge. Off-boarding is real: when a builder leaves, the Mac mini and everything on it transfers to them.

Target customers · M12
12–15
Most of Ventura ADU market
Target MRR · M12
$25k– $50k+
Plus 2% performance bonus tier
Avg ADU project size
$150k– $400k
One deal = 2–3 years of service
Mac minis at M12
13–16
1 operator + 1 per customer
First, three words Build Leads confuse here
Our customer

Builder

An independent ADU builder paying us $1.5k–$7.5k/mo for outbound services. Each builder gets their own dedicated Mac mini. Source of MRR.

Our reach-target

Prospect

A Ventura County homeowner we email or SMS on behalf of a builder. They've not asked to be contacted — compliance carries every send.

Our deliverable

Lead

A prospect who replied positively and got qualified into a calendar meeting on the builder's calendar. What the builder is actually paying for.

02The 2026 wedge

Four California laws signed in 2025 took effect this year. ADU demand is spiking. Builders are scrambling for pipeline. None have sophisticated outbound. The category-defining gap: no local competitor offers AI-driven cold outbound to ADU builders.

LawEffectiveWhat changes for ADU buyers + builders
SB 543Jan 1, 2026Eliminates school fees on ADUs <500 sq ft · caps permit intake review at 15 business days · three ADU types per lot allowed simultaneously
AB 462Oct 15, 202560-day Coastal Development Permit deadlines (down from 6–12 months) for Oxnard + Port Hueneme coastal properties
AB 1154Jan 1, 2026Removes owner-occupancy requirements for JADUs with separate bathrooms
SB 9EffectiveLot splitting for additional housing potential
The builder list (partial). USModular Inc · RnD Builders · National Development Group · Eagle Pride Construction · Ventura ADU Specialists (Legacy Construction Group) · Safeway Construction · Thousand Oaks Elite ADU Builder · Bodagger Builders · Todd Huff Construction · Shamrock Construction · plus 5–10 smaller design-build firms. Founders take the calls themselves. No BDR/SDR functions. High outbound receptivity.
03Fleet architectureMulti-Mac-mini · per-customer isolated

This is the most important diagram in the portfolio. One Mac mini per paying customer. Plus one operator Mac mini at the top. All connected via Tailnet. Per-customer isolation is not optional — it's the reason this business model works without catastrophic deliverability or compliance failures.

OPERATOR MAC MINI · #1 ventura-ops.hatchstacks.tail Sales pipeline · billing oversight · cross-customer dashboard · crawlers C T E Q M + Ventura Assessor & Permits crawlers HUMAN OPERATORS 🧑‍💼 Dawson 👷 Build Lead PAPERCLIP SUPERVISOR Per-mini risk policies enforced. Cross-mini cost monitoring + escalations. TAILSCALE MESH · NO PUBLIC INTERNET EXPOSURE All Mac minis. All Build Lead access. FileVault on every disk. CUSTOMER MAC MINI · #2 USModular Inc C T E Q M own integrations: ▸ outreach.usmodular.com ▸ Smartlead domain ▸ GHL location ▸ Stripe customer ▸ Builder dashboard tier: PRO · $3,500/mo CUSTOMER MAC MINI · #3 RnD Builders C T E Q M own integrations: ▸ outreach.rndbuilders.com ▸ Smartlead domain ▸ GHL location ▸ Stripe customer ▸ Builder dashboard tier: PREMIUM · $7,500/mo CUSTOMER MAC MINI · #4 Eagle Pride Construction C T E Q M own integrations: ▸ outreach.eaglepride.com ▸ Smartlead domain ▸ GHL location ▸ Stripe customer ▸ Builder dashboard tier: STARTER · $1,500/mo CUSTOMER MAC MINI · #5 Bodagger Builders same shape ↑ own everything tier: PRO · $3,500/mo CUSTOMER MAC MINIS #6 · #7 · #8 · #9 · #10 · #11… ··· scales linearly with customer count target 12–15 at M12 L4 · PER-CUSTOMER OUTBOUND (each mini sends to its own builder's prospects, isolated reputation) Smartlead / Instantly Primary email · warmed domain per customer Twilio (via GHL) SMS · TCPA-compliant opt-in only Direct mail · premium tier High-ROI for ADU homeowners GHL AI Receptionist Reply qualification + calendar booking Stripe Connect Per-customer subscription billing L5 · PROSPECT SOURCES (operator-side, shared across customers, scrubbed per-customer) Ventura Assessor Crawler Parcel size · value · owner-occupancy Ventura Permit Records Recent ADU / garage conversion filings Apollo / Clay (backup) Enrichment fallback Suppression lists · DNC registries Global + per-customer · CAN-SPAM/TCPA enforced
The architectural mistake to never make: a shared sending infrastructure. One bad customer's list would poison every customer's reputation. The Mac mini-per-customer pattern is the moat. Pro tier is required, not overkill.
04The 5-agent fleetRuns on every Mac mini

Same 5-agent pattern as the rest of the portfolio. What changes per project is the skill bindings — what each agent actually does. Below are the skills the PRD binds explicitly for this project.

C
CEOIndigo · Customer ops
Customer onboarding, sales pipeline, ICP extraction, billing, performance bonus tracking. Books builder demos. Drafts contract renewal proposals.
customer_intake process_stripe_subscription book_calendar_meeting
T
CTOCyan · Infra & data
Ventura Assessor + Permits crawlers. Apollo/Clay enrichment fallback. Sentry + PostHog monitoring. Mac mini health across the fleet.
extract_property_data crawl_permit_records monitor_reputation
E
EngineerGreen · Sending infra
Per-customer domain provisioning + warm-up curve. Smartlead/Instantly account setup. List processing, deliverability validation, suppression list enforcement at send time.
provision_sending_domain warmup_domain scrub_list
Q
QAAmber · Compliance
CAN-SPAM + TCPA enforcement on every send. Daily deliverability audit. Vets any customer-imported list before launch. CSLB license verification at customer onboarding.
validate_compliance audit_deliverability verify_csl_license
M
MarketerPink · Copy & replies
Drafts sequences per customer brand voice (Sonnet). Classifies replies (Haiku). Routes interested replies into the AI Receptionist for qualification + booking. Builder approves messaging tone.
compose_cold_outreach_email classify_reply qualify_lead
05The 4-channel contact model

Each customer Mac mini exposes its own four channels. Builder-side comms run via Telegram + Dashboard; prospect-side comms run via Email + SMS (with Website Chat for the customer's own dashboard interactions).

Telegram

Build Lead · Operator · Builder

Deliverability alerts, agent escalations, builder approval requests (sequence changes, ICP updates). Each builder gets their own Telegram bot. Highest-priority queue.

Dashboard

Builder · Operator

Builder: sends/replies/meetings booked, cost per meeting, current pipeline. Operator: cross-customer fleet view, deliverability across all minis. Tailnet-only.

Website Chat

Builder onboarding intake

Day-1 intake form for new builder customers — ICP description, brand voice samples, monthly capacity. CEO Agent extracts structured customer profile from this.

06Pricing tiers

Three tiers. Each gets its own Mac mini regardless of tier — the difference is volume + channel coverage. Setup fee covers initial provisioning. Optional 2% performance bonus on closed deals attributable to campaigns.

Starter
$1,500 /mo
+ $2,000 setup
  • 1 campaign
  • 500 contacts/mo
  • Email-only
  • Reply qualification + booking
  • Monthly performance report
Target builder: single-owner, 5–10 ADUs/yr, just hitting capacity
Premium
$7,500 /mo
+ $5,000 setup
  • Unlimited campaigns
  • 5,000+ contacts/mo
  • Email + SMS + direct mail
  • Dedicated Mac mini upgrade (M4 Max if needed)
  • Bigger Sonnet budget
  • SLA on reply latency
Target builder: 25–50 ADUs/yr · regional brands like USModular, RnD
Performance bonus tier (optional add-on, any tier): 2% of any deal closed with attribution to a campaign. Since the average ADU is $150–400k, a single closed deal = $3,000–$8,000 bonus — typically more than the monthly retainer. This is the alignment-of-incentives lever.
07Customer onboarding workflowTarget: <2 hrs operator time by Month 3

The repeatable per-customer onboarding. Every paying builder goes through this exact sequence. By Month 3 of operations, agent automation should compress operator time to under 2 hours. Months 1–2 are slower while the playbook is being calibrated.

HOUR 1

Discovery

  • 30-min intake call (Telegram, Zoom, or phone)
  • CEO Agent extracts: ICP, brand voice, value prop, target geos, monthly project capacity
  • Builder approves the structured customer profile
HOUR 2

Infrastructure

  • Provision Mac mini from pre-provisioned standby pool (~30 min bootstrap)
  • Domain procurement (e.g. outreach.{builder}.com)
  • GHL location · Stripe customer · 1Password vault for credentials
HOUR 3–4

Campaign Setup

  • Marketer Agent drafts first 3 sequences from customer profile
  • Customer reviews + approves messaging tone
  • QA Agent compliance audit · suppression list applied
  • First 500 prospects compiled from Ventura Assessor + Permits crawlers
DAYS 5–35

Warm-Up

  • Send volumes scale: 50 → 100 → 200 → 300/day over 30 days
  • Engagement metrics monitored daily by QA Agent
  • Customer dashboard live; real-time visibility
  • First meeting bookings expected by Day 15–20
Pre-provisioning rule: always keep 2–3 Mac minis bootstrapped and idle. New customer signing = same-day provisioning. Without this, you'll lose the urgency premium at sales close.
08Domain warm-up curve

Every new customer's sending domain takes 30 days to ramp from zero to full volume. Skipping this is the fastest way to destroy deliverability. The curve is conservative on purpose — engagement metrics gate progression to the next step.

0 50 100 200 300 SENDS / DAY D1 D7 D14 D21 D30 D35 D60+ Days 1–7 · 50/day Days 8–14 · 100/day Days 15–21 · 200/day Days 22–30 · 300/day First meeting booked typically Day 15–20 GATING METRICS · QA AGENT • Bounce rate < 2% • Spam complaint < 0.1% • Reply rate ≥ 4%
If any gating metric trips, the QA Agent pauses progression and alerts the Build Lead via Telegram. Never override a QA pause — domain reputation, once destroyed, is hard to rebuild.
09Reply classification routing

Replies aren't just yes/no. The Marketer Agent classifies every inbound into five buckets. Each bucket has a different handling path. Hostile replies always escalate immediately to the operator.

PROSPECT REPLY Email · SMS · voicemail MARKETER AGENT Classify reply Haiku · <200ms typical 5-bucket schema ▸ INTERESTED AI Receptionist (GHL) Qualifies · books on builder calendar ▸ NOT NOW 90-day quarterly nurture sequence ▸ UNSUBSCRIBE Suppression list · CAN-SPAM compliant ▸ WRONG PERSON Record updated · sequence paused · flagged ▸ HOSTILE Immediate operator escalation · no agent reply LEAD CREATED → BUILDER CALENDAR Meeting booked · prospect record promoted to Lead If performance-bonus tier: tracked for attribution TELEGRAM → OPERATOR · IMMEDIATE Pause campaign · review wording · log incident
10Phase timeline52 weeks · 4 phases

Sales is the bottleneck in Phase 1. Builder customer #1 has to sign before infra investment is worth it. Phase 2 proves the funnel. Phase 3 is the scale ramp. Phase 4 is market saturation + first vertical expansion.

W1 W8 W16 W24 W32 W40 W48 W52 PHASE 1 Foundation + 1st customer PHASE 2 1st meeting · customer 2–3 PHASE 3 Scale to 8–10 customers PHASE 4 — market saturation + vertical expansion 12–15 customers · $25–50k MRR · SOC 2 · LA County / Santa Barbara test INFRA Ops Mac mini · OpenClaw · Paperclip Pre-provisioned Mac mini standby pool · always 2–3 ready CRAWLERS Assessor + Permits crawlers Maintenance · ToS-respectful · cache-aggressive SALES Top-10 builder outreach · 1st sign Customer 2–10 sales pipeline Customers 11–15 + geo expansion + new vertical CUSTOMERS #1 #2 · #3 onboarded Customers 4–10 onboarded Customers 11–15 · churn watch · renewals OPS TIME Operator hours/customer/week: 8 → 4 → 2 (target by Month 3) 1st customer live 3 customers · $4.5–10.5k MRR 8–10 customers · $15–30k MRR 12–15 customers · $25–50k MRR $1.5–7.5k $4.5–10.5k $15–30k $25–50k+ MRR target MRR
11Risk heatmap

11 risks. Three are existential: R1 (deliverability collapse), R2 (customer-imported bad list), and R3 (TCPA lawsuit). R5 (LLM cost) is the most likely day-to-day grind. R11 (off-boarding) is treated as a feature, not a risk — plan for it from Day 1.

Low
Medium
High
Critical
High
R3
R10
R1
R2
Medium
R4
R6
R8
R9
R11
R5
Low
R7
— Likelihood →
Risk register
R1Deliverability collapsePer-customer domain isolation · warm-up discipline · daily reputation monitoring
R2Customer brings bad (purchased) listStrict opt-in proof required · QA audit before any list goes live
R3TCPA lawsuit (SMS)Documented opt-in for every recipient · QA daily audit
R4CAN-SPAM violationEngineer Agent enforces at send-time
R5LLM cost overrunsPer-campaign caps · Haiku before Sonnet · Ollama for offline tasks
R6Customer cancels in month 2Expectation-set in sales · case study from first deal critical
R7ADU regulatory rollbackDiversify ICP to adjacent verticals (pool, kitchen)
R8Mac mini provisioning bottleneckStandby pool of 2–3 minis · <2 hr provisioning
R9Competitor enters nicheHyper-local Ventura specialization · speed-to-install moat
R10Builder uses service to deceive homeownersQA messaging audit · accountability clause in contract
R11Customer asks for off-boardingTreated as feature, not risk — full transfer to customer. See §15.
12Data modelEach entity scoped to a single customer Mac mini

Six core entities. BuilderCustomer is the root; everything else (Campaign, Prospect, Message, etc.) is per-customer scoped. SuppressionList is dual-scoped — per-customer plus a global suppression list shared across all customers (anyone who opts out anywhere is opted out everywhere).

erDiagram
    BUILDER_CUSTOMER ||--o{ CAMPAIGN : "runs"
    CAMPAIGN ||--o{ PROSPECT : "targets"
    PROSPECT ||--o{ MESSAGE : "exchanges"
    BUILDER_CUSTOMER ||--o{ SUPPRESSION_LIST : "has private"
    SUPPRESSION_LIST }o..o| BUILDER_CUSTOMER : "global if null"
    MESSAGE }o--|| AGENT_ACTION : "created by"
    PROSPECT ||--o{ AGENT_ACTION : "may trigger"

    BUILDER_CUSTOMER {
        uuid id PK
        string business_name
        jsonb primary_contact
        string csl_license_number
        text_array service_cities
        int ideal_project_value_min
        int ideal_project_value_max
        int monthly_capacity
        text brand_voice
        text value_proposition
        jsonb_array case_studies
        enum tier "starter|pro|premium"
        string stripe_customer_id
        decimal performance_bonus_pct
        enum status "onboarding|active|paused|churned"
        string mac_mini_hostname
    }
    CAMPAIGN {
        uuid id PK
        uuid customer_id FK
        string name
        text icp_description
        enum list_source "assessor|permits|apollo|imported_csv|enrichment"
        enum status "draft|warming|active|paused|complete"
        timestamp start_date
        int total_prospects
        jsonb_array sequences
        enum_array channels "email|sms|direct_mail"
    }
    PROSPECT {
        uuid id PK
        uuid campaign_id FK
        uuid customer_id FK
        string email
        string phone
        string name
        jsonb address
        jsonb property_data
        jsonb enrichment
        enum status "queued|sent|opened|replied|meeting_booked|unsubscribed|dnc|bounced"
        bool do_not_contact
        jsonb consent_record
    }
    MESSAGE {
        uuid id PK
        uuid prospect_id FK
        uuid campaign_id FK
        enum channel "email|sms|direct_mail"
        enum direction "outbound|inbound"
        string template_used
        text rendered_content
        timestamp sent_at
        timestamp opened_at
        timestamp replied_at
        enum reply_classification "interested|not_now|unsubscribe|wrong_person|hostile"
        text qualification_notes
        timestamp meeting_booked_at
        string meeting_calendar_event_id
        uuid agent_action_id FK
    }
    AGENT_ACTION {
        uuid id PK
        enum agent "ceo|cto|engineer|qa|marketer"
        string action_type
        text prompt_used
        jsonb result
        string model_binding_used
        decimal cost_usd
        timestamp created_at
    }
    SUPPRESSION_LIST {
        uuid id PK
        uuid customer_id FK
        string email_or_phone
        string reason
        uuid source_message_id FK
        timestamp created_at
    }
13Build Lead · Days 1–10Longer than the pilot · per-customer provisioning is recurring work

Two weeks because Cold Outbound requires building infrastructure to repeat the customer-onboarding workflow, not just standing up one site. Days 1–7 are the operator Mac mini + crawlers + compliance tooling. Days 8–10 are the first customer's onboarding.

DAY 1Read-in
  • Tailnet, 1Password, Notion access
  • Read Advanced PRD end-to-end
  • Read Build Guide §6, §7, §11
  • Review Visuals 3a–3i
  • Tier Scope Discriminator Matrix 5c
Outcome: contextually loaded
DAY 2Read-in cont.
  • 4-channel contact model (1d, 1e, 1f)
  • CAN-SPAM + TCPA reference reading
  • CCPA / CPRA reference reading
  • Map customer onboarding workflow on paper
Outcome: compliance-aware
DAY 3Ops Mac mini
  • Provision Mac mini #1 (operator's)
  • FileVault, Tailscale, 3 user accounts
  • OpenClaw + Paperclip + Ollama
  • Daily backup tested
Outcome: ops mini online
DAY 4Operator agents
  • 5 agents configured on ops mini
  • Operator dashboard (multi-customer view)
  • Sales pipeline tracking
  • Telegram bot test all 5 agents
  • Paperclip risk policies enforced
Outcome: agent fleet live
DAY 5Assessor crawler
  • Build Ventura County Assessor crawler
  • Parcel, value, year built, owner-occupant
  • Rate-limit, cache aggressively, ToS-safe
  • Version-controlled, documented
Outcome: prospect source #1
DAY 6Permits crawler
  • Build Ventura Permits crawler
  • Recent ADU + garage conversion filings
  • Apollo / Clay API as enrichment backup
  • Test full 500-prospect generation
Outcome: prospect source #2
DAY 7Compliance
  • CAN-SPAM validator skill
  • TCPA opt-in proof checker
  • Global + per-customer suppression list infra
  • Smartlead operator account
  • Deliverability validator: bounce, spam, reputation
Outcome: compliance tooling ready
DAY 8Builder sales
  • CEO Agent compiles top-10 builder list
  • Build Lead approves outreach script
  • First outreach sent (manual approval each week 1)
  • Ready for inbound replies + demos
Outcome: sales pipeline live
DAY 9Customer #1 prep
  • Customer signs (target W3–4)
  • Provision customer Mac mini (#2)
  • Configure customer's agents from ICP
  • Domain procurement · GHL · Stripe
Outcome: customer infra
DAY 10Customer #1 live
  • Customer dashboard handover
  • Telegram bot bonded to customer
  • First 500 prospects compiled + scrubbed
  • First sequences approved by customer
  • Domain warm-up begins
Outcome: customer #1 warming
14Pro tier conformance

Unlike the pilot, every aspect of Pro tier applies here. This is the textbook archetype.

Fits Pro perfectly

  • Per-client Mac mini for each builder customer — isolated data, reputation, billing
  • 5-agent fleet per mini — same canonical pattern
  • 4 channels all in use — Telegram, Dashboard, Website Chat (onboarding), Email
  • Tailnet mesh — Build Lead reaches every customer mini privately
  • Off-boarding ownership transfer — real and operationally critical (see §15)

Stretches Pro tier

  • High per-customer compute — 5k+ sends/day + reply handling + crawlers. Premium tier customers may need M4 Max.
  • SOC 2 Type 1 target within 6 months — heavier compliance than other Pro projects.
  • CAN-SPAM/TCPA enforcement — dedicated QA Agent + external compliance contractor for legal review.

Pro tier required, not overkill

  • Shared sending = shared catastrophe. A Hatchstacks Base tier with multi-tenant sending infrastructure would mean one bad customer destroys every customer's reputation.
  • Per-customer isolation is the business model, not an upgrade.
  • This is why Cold Outbound is the textbook 🟢 archetype — the per-Mac-mini pattern is the only way to operate this responsibly at scale.
15Off-boarding ownership transferPro tier signature feature · plan for it from Day 1

When a builder customer leaves, their Mac mini and everything on it transfers to them. This is a feature, not a failure mode. It's the moat for retention (we make it easy to leave, so they don't fear the lock-in) and the responsible-exit story for legal/insurance counsel.

BEFORE · UNDER HATCHSTACKS CUSTOMER MAC MINI outreach.usmodular.com Hatchstacks-managed: ▸ Domain registrar (under HS) ▸ Stripe billing → HS account ▸ Smartlead account → HS-owned ▸ GHL location → HS subaccount ▸ 1Password vault → HS ▸ Paperclip supervisor active ▸ Tailnet member ▸ Audit log retained by HS TRANSFER ~2-4 days DURING · TRANSFER PROTOCOL Handover sequence Build Lead executes Per the off-boarding playbook: 1. Domain transferred to customer registrar 2. Stripe billing closed · final invoice 3. Smartlead account ownership reassigned 4. GHL subaccount converted → standalone 5. 1Password vault exported · keys rotated 6. Paperclip detached 7. Mac mini removed from HS Tailnet 8. Data + audit log handed over · signed receipt DONE AFTER · UNDER CUSTOMER CUSTOMER MAC MINI Owned by USModular Inc Customer-owned: ▸ Domain on customer registrar ▸ Stripe direct (no HS layer) ▸ Smartlead account under customer ▸ GHL standalone account ▸ Customer holds all credentials ▸ Customer can re-engage anytime ▸ Mac mini still runs their agents ▸ Hatchstacks no longer supervises
Practice this before you need it. The first time you off-board a customer should not be when they're already frustrated. Run a tabletop exercise in Phase 2 — pick a hypothetical customer, walk the 8-step protocol, document anything that turned out harder than expected.
16Cross-project map

Cold Outbound is the cash engine of the Ventura Trifecta. It funds others. It also shares the most reusable infrastructure: the Ventura crawlers, CSL verifier, and CEO Agent sales skills transfer across the whole portfolio.

THIS PROJECT Cold Outbound 🟢 PRO · WAVE 1 Website Landlord Ventura 11 city sites · rank & rent SHARED CRAWLER Ventura Assessor 🟢 PRO · WAVE 1 ADU Directory V1 / V2 Builders here are customers there SHARED POOL ADU builders ↔ 🟡 HYBRID · WAVE 2 Vacation Rental Turnover Same host-acquisition skill SHARED SKILL CEO B2B sales pattern 🟡 HYBRID · WAVE 2 Network for Creators Brand acquisition same shape SHARED SKILL Reply classification Solid lines = direct shared infrastructure (build once, reuse). Dashed = transferable agent skills (rebuild lightly per project).
Built here · reused elsewhere
AssetUsed by
Ventura Assessor crawlerWebsite Landlord · ADU Directory · this project
Ventura Permits crawlerADU Directory enrichment · this project
verify_csl_licenseWebsite Landlord · ADU Directory · Vacation Rental
audit_deliverabilityWebsite Landlord tenant notifications · ADU Directory digests
CEO B2B sales workflowVacation Rental hosts · Creators brand sales
Customer-pool overlap
From→ To
ADU Directory buildersCold Outbound paying customers (same population)
Website Landlord tenants (defensible-space)Potential Cold Outbound customers (cross-sell)
Ventura homeowners (prospect target)Website Landlord leads · ADU Directory inquiries
17Glossary

Terms specific to this project. Note that customer and tenant mean different things in Cold Outbound vs Website Landlord — careful when cross-referencing.

Builder / Customer
Our customer. An independent ADU builder paying us monthly for outbound campaigns. Gets their own Mac mini.
Prospect
Our outreach target. A Ventura County homeowner we email or SMS on the builder's behalf. Hasn't opted in — compliance carries every send.
Lead
Our deliverable. A prospect who replied positively and got qualified into a meeting on the builder's calendar.
ADU
Accessory Dwelling Unit — a secondary dwelling on a residential property. California has aggressive pro-ADU laws since 2020 and four new ones for 2026.
JADU
Junior ADU — capped at 500 sq ft. AB 1154 (2026) removed owner-occupancy requirements if separate bathroom.
SB 543 / AB 462 / AB 1154 / SB 9
The four 2025-signed California laws driving 2026 ADU demand. SB 543 = no school fees on small ADUs. AB 462 = 60-day Coastal permits. AB 1154 = JADU rules. SB 9 = lot splitting.
CAN-SPAM
Federal email law: unsubscribe link, sender ID, physical address required on every commercial email. Engineer Agent enforces at send time.
TCPA
Telephone Consumer Protection Act. Governs SMS. Requires documented opt-in for every recipient. Penalties are per-message — six figures fast if violated.
CCPA / CPRA
California consumer privacy regs. Data subject access requests handled within 45 days. Relevant because all prospects are California residents.
DNC
Do-Not-Contact list. Federal, state, and per-customer scoped suppression lists must all be honored before any send.
Warm-up
The 30-day domain reputation ramp from 50 → 300 sends/day. QA Agent gates progression on bounce/spam/reply metrics. Never skip.
AI Receptionist
The GHL AI Employee that handles inbound prospect replies — qualifies and books meetings. Backed by Sonnet for reasoning, Haiku for routing.
SOC 2 Type 1
Compliance audit some builder customers will require before signing. Target: complete within 6 months of first paid customer.
Performance bonus
Optional 2% of closed deals attributable to a campaign. Often exceeds monthly retainer. The alignment-of-incentives lever.
← Portfolio