Q3 — Jul–Sep · W27–39

SCALE THE PROOF — range (hub) → results (case studies) → the full engine + the Academy

Prove range (Hub launch) → prove results (Case studies) → open the always-on education engine

How it all connects — this quarter

Every campaign maps to a pillar and showcases a specific capability/topic — the same edges the content-index graph enforces (campaign · pillar · topic · asset).

Weeks Campaign Pillar Showcases (capability · topic)
W27–29 temerarii.xyz Hub Launch IT & Development n8n → typed Pydantic · the creative stack we control ([[x-n8n-to-python]] · [[x-creative-stack]])
W30–33 Case-Study Drops Performance Marketing Performance + custom dashboards · UTM→GA4 ([[x-custom-dashboards]] · [[x-omni-funnel]])
W34–39 Always-On — Minus the Hype Insights engine Social Marketing 9-channel distribution — aggregator vs custom API ([[x-distribution-stack]])
W38–39 Performance Marketing — stop guessing, start printing Performance Marketing Performance + custom dashboards · UTM→GA4 ([[x-custom-dashboards]] · [[x-omni-funnel]])

Section 1

the offer + the plan

1.1 Services & products

  • This quarter — SCALE THE PROOF — range (hub) → results (case studies) → the full engine + the Academy
  • Leads with: the outbound engine (Clay+signals, full) + the 8 pillars + the Academy (Fall)
  • 8 pillars: Performance Marketing, Brand Marketing, Multimedia, Social Marketing, Strategic Relations, IT & Development, Staff Training, Emerging Tech
  • SlotSlot — the marketing command center (the product) — the productized platform: modular · agent-powered · MCP-first · 7 integrated sub-MVPs, research → publishing. The temerarii-studio engine (4-4-5 · output policy · cadence · per-asset gate · content-index) is its spec; this office is the same machine run on ourselves first.
  • The content machine (back office) — goal → stages → gates harness that plans, composes, gate-checks + publishes the whole calendar — the operator engine + the run-on-ourselves proof behind Slotted
  • SIE — Sovereign Intent Engine — the consent/data-rights wedge product — compliance-as-a-service + declared-intent capture
  • The Lab — real-time WebGL proof-of-capability across the 8 pillars
  • Custom enrichment stack — our own Clay-style scrape→enrich→score outbound pipeline, built from MCPs we control

1.2 The wedge + the ladder

  • This quarter's framing: PROVEN across all 8 pillars + real case-study receipts — now pick your lane; the consult moves to $150 (the free window closed)
  • Wedge — Autonomous Outbound Machine: A Clay-enriched, signal-triggered outbound pipeline, built + handed off in ~3–4 weeks.
  • Pricing: fixed build + monthly run-rate (priced on Clay credit-per-enrichment so client run-rate stays profitable)
  • Why: Concrete, demoable, matches the AI×Automation + GTM-strategy pages — buyers pay premium for outcomes from systems, not 'marketing services'.
  • The ladder:
    1. Wedge: Autonomous Outbound Machine
    2. Omnichannel orchestration (search/social/email/SMS/web as one story)
    3. Custom web/app builds
    4. Staff training — 'think in data' (retention + expansion layer)

1.3 Campaign suite (live from the calendar)

Weeks Campaign Pillar Span
W27–29 temerarii.xyz Hub Launch IT & Development 3 wk
W30–33 Case-Study Drops Performance Marketing 4 wk
W34–39 Always-On — Minus the Hype Insights engine Social Marketing 6 wk
W38–39 Performance Marketing — stop guessing, start printing Performance Marketing 2 wk

1.4 Promotions — sales campaigns, timed

  • SIE Compliance Forcing-Function push — W31–33 (Aug 2026) — timed to the Delete Act broker-processing date (Aug 1 2026) + the CA enforcement news cycle · Consent infrastructure priced for you — turn a data-rights request into first-party intent you own
  • Performance — stop guessing, start printing — W38–39 (already a calendar campaign) + always-on Performance plays Q4 · Tie every dollar to a result — a first-outcome conversation, one number to move
  • Neutral-Builder partner outreach — Q3 Hub-Launch (W27–29) + ongoing Strategic-Relations cadence; Texas (SA–ATX) workshops Q3–Q4 · A neutral builder with range — white-label creative+data+dev, no ad-business conflict
  • Texas (SA–ATX) Operator Workshops promo — 2–3 week promo lead-in before each Q3–Q4 workshop date · Come build it live — a working AI/GTM play you leave with, run on your own data

1.5 Seasonal promos — launching this quarter (RUN-AHEAD)

  • The rule: Temerarii's seasonal promo launches ~6 weeks (1.5 months) before the holiday (more for Q4 tentpoles), and every piece STATES the lead-time math so the owner feels the urgency: 'St. Patrick's is 6 weeks out — your competitors are already designing. Let's get your campaign live first.'
  • Why early: Consumer buys 2–6 wk before → the business must LAUNCH 4–8 wk before (beat competitors to early buyers) → so WE pitch 6–10 wk before (12–16 for Q4 tentpoles, where shopping starts in October). NRF 2025: 51.9% of winter shoppers + 49% of Halloween + 67% of back-to-school started early — push launch/pitch earlier where a category buys early.
Holiday Holiday date OUR launch (run-ahead) Audience Why launch early
National Ice Cream Day 2026-07-19 W27 (2026-07-05, −2wk) B2C same-day promo; free-scoop offers
International Beer Day 2026-08-07 W29 (2026-07-24, −2wk) B2C same-day
National Dog Day 2026-08-26 W32 (2026-08-12, −2wk) B2C high social engagement
Labor Day 2026-09-07 W32 (2026-08-10, −4wk) B2C end-of-summer sale event
Hispanic Heritage Month 2026-09-15 W32 (2026-08-11, −5wk) both HUGE in the SA–ATX corridor + all Texas — a home-market differentiator
Q3 fiscal quarter-end 2026-09-30 W35 (2026-09-02, −4wk) B2B end-of-quarter deal pushes
Oktoberfest 2026-09-19 W33 (2026-08-22, −4wk) B2C US craft-beer Märzen seasonal releases
State Fair of Texas (Dallas) 2026-09-25 W33 (2026-08-21, −5wk) B2C DFW home-market tentpole event
National Coffee Day 2026-09-29 W37 (2026-09-15, −2wk) B2C free-coffee offers
Halloween 2026-10-31 W37 (2026-09-19, −6wk) B2C $13.1B (2025); 49% start Sep or earlier → launch early Sep
ACL — Austin City Limits 2026-10-02 W33 (2026-08-21, −6wk) B2C Austin's flagship festival — SA–ATX corridor brand moment
Customer Service Week 2026-10-05 W37 (2026-09-14, −3wk) B2B client + team appreciation
Breast Cancer Awareness Month 2026-10-15 W38 (2026-09-24, −3wk) both month-long cause marketing
Cybersecurity Awareness Month 2026-10-15 W38 (2026-09-24, −3wk) B2B month-long B2B education hook
Black Friday 2026-11-27 W35 (2026-09-04, −12wk) both winter holidays $1.01–1.02T; shopping starts October → pitch Aug–Sep
Cyber Monday 2026-11-30 W36 (2026-09-07, −12wk) both online focus; B2B SaaS deals — plan with BFCM
Christmas / Holiday season 2026-12-25 W39 (2026-10-02, −12wk) both winter $1.01T; launch Sep–Oct, pitch Jul–Aug for full programs

1.6 Our offers — book the free consult

  • Primary CTA — Free 1-hour strategy consultation (with Dom Davis or a senior team member): We map your next 90 days of campaigns — which holidays are yours, what to launch and when — and you leave with a plan whether or not you hire us.
  • Free 1-hour consultation (rest of Q2 only) (lead magnet) — No cost through end of Q2 — the front door; every campaign + ad CTA points here. After Q2 → $150/hr. We practice our own run-ahead: the free window is a limited promo with a deadline.
  • Launch discount (discount) — % off the campaign build for first-time clients + early-bird seasonal sign-ups (book the consult before the run-ahead date).
  • Campaign BOGO (buy-one-get-one-free) — Set up one seasonal campaign, get the next built free — locks in the run-ahead habit across two holidays.
  • Consult → build → retainer (retainer) — The ongoing run-rate: monthly retainer for always-on + seasonal campaigns + reporting.
  • EVERY asset — seasonal promo, holiday reminder, capability post — closes on the SAME CTA: book the free 1-hour consultation. One destination, UTM-tagged, attributed in GA4.

1.7 Seasonal — holiday posts (the on-the-day post)

  • Labor Day (2026-09-07) — 1 social post → all channels

1.8 Strategic relations & events

  • Events / conventions:
    • Temerarii Academy — Fall cohort launch — Staff-Training pillar + 'Think in Data' made real; the mission/credibility proof (cominc.org) (Fall 2026 (Q3→Q4, ~W36+))
    • Texas (SA–ATX) operator workshops — Staff-training pillar in market — learn-by-doing labs (Q3–Q4 2026)
    • Lab walkthrough sessions — Hub-launch tie-in (W27–29) — run an experiment live (Q3 2026)
  • Partnerships / warm-intro motion:
    • Schools · nonprofits · community centers · employers (via Community Incubator) — LEARN/BUILD/CONNECT distribution + borrowed credibility + a talent pipeline
    • Compliance / data-rights partners — Distribution for SIE; borrowed credibility
    • Agency + platform neutral-builder deals — Shared distribution, white-label range
  • Community Incubator / Temerarii Academy: Fall 2026 (Q3→Q4, ~W36+) — the give-it-away mission, in market.

1.9 Operational KPIs & goals

  • This quarter's KPI emphasis: pipeline from outbound · pillar coverage · case-study receipts · Academy enrollment · BFCM/Christmas prep (pitched Sep–Oct)
  • Case studies → Convert (book a first-outcome call); SIE plays → SIE demo/declared-intent; always-on → Capture (nurture). CTA → destination → UTM → funnel stage on every asset
  • ICP focus: Compliance-exposed (SIE push W31–33) + broken-attribution (Performance W38–39)
  • Sales push: SIE Compliance push (W31–33) · Performance (W38–39) · Neutral-builder (Hub W27–29 + workshops)
  • Masters this quarter: 104 (13 cells + 91 threads)
  • Targets: pipeline · declared-intent captures · bookings · partnerships · events run · content shipped

1.10 Output policy — what every asset ships as

  • Video aspects: 9:16 1080×1920 · 1:1 1080×1080 · 16:9 1920×1080 + 4K masters
  • Image formats: blog_og · blog_hero · email · sms_mms · thumb · master_4k
  • Text assets: email · sms · blog
  • Audio: VO -16 LUFS · bed -26 ducked · final -16 / TP -1.5 dB
  • Enforced by: verify_content_alignment (every cell has aspects + channels) · verify_variety (no-redundancy) · render-matrix.json enumerates cell × aspect

Section 2

media + creative

2.1 Content summary & objectives

  • Case studies → Convert (book a first-outcome call); SIE plays → SIE demo/declared-intent; always-on → Capture (nurture). CTA → destination → UTM → funnel stage on every asset
  • Every asset: CTA → destination → UTM → funnel stage, in the locked dark-humor-educational voice.

2.2 The asset suite this quarter

  • 13 cells (Sunday heroes + topic deep-dives, 28–140s)
  • 91 long-form (5–7 min, 16:9 YouTube, chaptered)
  • 91 daily threads (18–30s)
  • 1 holiday posts
  • Creative System: Signal Field · 8 pillar shapes · heavy MG every scene · caption→VO→card chain.

2.3 Creative automation — the whole pipeline

  • This quarter's creative focus: PILLAR-SPECIFIC creative — each character/shape leads its lane; the daily long-form engine at full tilt
  • We automated the ENTIRE creative process, end to end — ideation → script → storyboard → scene → render (Remotion + R3F, the Signal Field, heavy MG) → VO (Piper) + music + captions → 3 native aspects → publish. 342 video masters/yr + the daily long-form + the non-video lanes, briefed once. Most agencies automate a step; we automated the pipeline.

2.4 Creative control — driven like code

  • The generative + 3D stack is driven PROGRAMMATICALLY from Claude Code, not hand-clicked: ComfyUI (local GPU, RTX 4070/WSL2, via MCP/HTTP — on-brand imagery · LoRA · upscale, palette-locked to the §08 recipe; API-only, operator runs the app) + Blender MCP (text/image → 3D molds of anything → GLB → R3F/the Lab) + TouchDesigner (realtime generative visuals). So the creative pipeline — type, motion, 3D, imagery — is controlled like code.
  • FFmpeg, local: We run it LOCALLY — ffmpeg 8.0.1 with NVENC/CUDA on the RTX 4070 — driving the whole video matrix (compose · VO mux · duck · caption-burn · 3 aspects · 4K) from workflows/ffmpeg_compositor.py + generators/video/ffmpeg.py. No cloud render bill.
  • 'just a CLI' / 'outdated' / 'too hard' — actually it's a battle-tested library with a CLI on top, current, and scriptable to anything.

2.5 Storyboard — Something is coming to the Temerarii hub

W27-hub-launch-beat-1 · 45s · 6 scenes · comp SceneReel

# beat dur on-screen card motion (MG) music cue
1 open 8s Something is coming spatial-parallax tmr-bed-01.mp3
2 hook 8s Tools that run in-browser kinetic-build tmr-bed-01.mp3
3 build 8s No demo request, no call type-on tmr-bed-01.mp3
4 diff 7s Bookmark it. Live soon. type-on tmr-bed-01.mp3
5 proof 7.0s Built in the open receipts-count tmr-bed-01.mp3
6 resolve 7s temerarii.xyz/build coalescence tmr-bed-01.mp3

2.6 Storyboard — The Temerarii hub is live

W28-hub-launch-beat-2 · 60s · 8 scenes · comp SceneReel

# beat dur on-screen card motion (MG) music cue
1 open 8s The hub is live spatial-parallax tmr-bed-01.mp3
2 hook 8.0s Pick a workflow. Press run. kinetic-build tmr-bed-01.mp3
3 build 8.0s Built on Claude Code + MCP type-on tmr-bed-01.mp3
4 diff 8.0s From 27 nodes to one prompt type-on tmr-bed-01.mp3
5 proof 7.0s Watch it work in public receipts-count tmr-bed-01.mp3
6 hook 7.0s Your stack, your keys kinetic-build tmr-bed-01.mp3
7 build 7.0s One machine, all of it type-on tmr-bed-01.mp3
8 resolve 7s temerarii.xyz coalescence tmr-bed-01.mp3

2.7 Per-asset updates under review (before → after)

  • Length: threads/holidays render full (18–30s), not the old ~10s — minimums met, varied
  • Heavy MG: every scene now carries motion + pillar shape + audio cue
  • Caption-sourcing: the rich caption is the source → VO + on-screen card derive (no robotic repeat)
  • Long-form: new 5–7 min chaptered YouTube lane, ≥1/day
  • Proven render-ready: the 10× gauntlet passes at 522 assets, 0 errors

Section 3

demand + measurement

3.1 Outbound practices

Ethics: Public / consented business data only · honor ToS + robots · no PII harvesting or surveillance · the same consent posture SIE sells

  • Define ICP → scrape candidates → detect the consent/attribution signal → enrich → Claude scores fit + personalizes → send → UTM→GA4 attribution. Human-in-the-loop at the decision point.
Stage Tools What it does
Source / scrape Apify (store scrapers: Shopify/store directories, LinkedIn company + people, Google Maps for local SA/real-estate, niche directories) · reddit-scraper · Google News build the raw candidate list per vertical
Signal detection Apify + Playwright (site crawl) · custom checks flag the buying signal — a privacy-policy/consent banner, a data-rights link, live Meta/Google ad pixels, intake/lead forms, CA/EU shoppers
Enrich / research Perplexity · Tavily · Exa (semantic) · Apify firmographic actors append firmographics + intent + a context paragraph per account
Score + personalize Claude (reasoning) over the enriched row score ICP fit 0–100, pick the segment, draft the personalized first-line tied to the account's real signal
Store Airtable (the custom CRM) via MCP the system of record — synced across email/outbound/calendar; client owns the data + IP
Send + attribute Resend (email) · LinkedIn (founder-led) · UTM (engine/lib/utm.py) → GA4 sequence the touch, tag every link, tie the reply to the source

3.2 The autonomous outbound engine

  • This quarter's outbound focus: GO FULL — the whole scrape→enrich→score→send machine live + signal-led; the SIE compliance push fronts it
  • Deliverability Gate: FIRST, before volume: separate sending domains from primary · SPF/DKIM/DMARC · inbox warmup · verify every address · drop catch-all/risky · keep bounce < 2%. Skip this and the machine burns the domain.
  • Waterfall Enrichment: Clay queries providers in sequence (A→B→C, 3–5 chained) → 85–95% email coverage vs 40–60% single-source; stop on first valid, auto-verify (NeverBounce/ZeroBounce).
  • Signals Not Lists: Trigger on events, not cold static lists: job changes (new VP Sales = tool overhaul), funding (budget), 'Head of RevOps' postings (tool need), competitor mentions. Claygent visits URLs + answers custom research (tech-stack from career pages/eng blogs) → specific, credible personalization.
  • Score And Filter: Clay formula scoring; message only rows >60–70/100. Don't message everyone you enrich.
  • Cost Note: Clay dual-credit pricing (Mar 11 2026) — build unit economics on credit-per-enrichment.
  • Proof: OpenAI went 40% → 80% enrichment coverage on inbound leads via Clay workflows.
  • The architecture (closed loops, human gates):
    • Signal layer — monitor job changes · funding · hiring · web/intent · social mentions (Clay + intent sources)
    • Enrichment + scoring — waterfall enrich · verify · ICP-score · segment
    • Routing — high-fit accounts auto-route to the right sequence/rep in minutes (speed-to-lead is a conversion ranking factor)
    • Orchestration — one coherent story across email/LinkedIn/SMS/retargeting, not siloed blasts (the homepage 'omni-channel, data-shared' promise, made literal)
    • Measurement — every touch tied to pipeline/revenue, fed back to re-score
  • Human gates: sending-domain/volume changes · anything posted publicly · list sources. Automate the enrichment, scoring, drafting, routing in between.

3.3 Performance-marketing practices

  • The measurable stack — tie every dollar to a result, minus the hype
  • UTM spine → GA4 — every link tagged (source·medium·lane·campaign·cell)
  • Funnel: Reach → Capture → Convert → (retain) — measured per stage
  • Run on ourselves: the GA4 + the office dashboards are the live receipt
  • Framing: CPA / ROAS before→after, attribution the walled gardens can't grade

3.4 Data transparency + consent-first

  • Data transparency across companies is becoming the price of entry — and the durable moat. As the training-data wall bites and privacy rules tighten, the winners are explicit about what they collect, why, and with whose consent.
  • The shift: Third-party signals are decaying; opaque scoring is a liability. The durable asset is zero-/first-party DECLARED intent — data a person/company knowingly shares, portable + auditable.
  • Our stance: SIE (Sovereign Intent Engine) productizes it: 'signals, not scores · intent, not eligibility' — consent-first capture, transparent provenance, the person/company owns + can see their data. Our outbound runs on public/consented data only (the ethics rail). Transparency isn't a compliance tax — it's the trust that makes the data worth more.
  • Across companies: Across companies, transparency = shared, declared, portable intent signals (with consent) instead of bought-and-blasted lists — cleaner data, higher conversion, lower legal risk, and a reputation that compounds.

3.5 Open by design — give the method away

  • We chose to open our work to the world — the office, the Lab, the method, the brand book — because education levels people up, and giving it away IS the marketing.
  • Why: Most agencies hide the method behind a black box. We do the opposite: the back office (office.temerarii.xyz), the live Lab (temerarii.xyz), and the playbooks are public, and we TEACH exactly how we do it — AI, APIs, MCP, the pipeline. Openness is the proof of capability AND the on-ramp.
  • The mission: We give the method away so people can level up their own lives + work — the same conviction behind Community Incubator / Temerarii Academy (free/accessible AI + digital skills for underserved learners). Demystify, don't gatekeep.
  • Why it compounds: Transparency earns trust; teaching earns authority; both compound into demand. 'Minus the hype · receipts over rhetoric' only works because the receipts are public and the method is shared.

3.6 How we operate — the honest pros & cons

  • Workflows are JSON: Workflows are JSON — structured data. n8n is the on-ramp; typed Python is the destination.
  • The arc: STUDY → BUILD → OPERATE → TRANSFORM → TEACH. (1) STUDIED at scale: cloned + organized a 2,053-workflow corpus (Zie619 + ai-agents) via n8n-workflows-import. (2) BUILT our own: 13 production flows (avatar/video · content-gen · 9-platform distribution), 21–59 nodes, 20+ APIs wired (Perplexity·OpenAI·HeyGen·ElevenLabs·Veo3·Blotato·Airtable·Apify·Reddit). (3) OPERATE the infra: self-hosted n8n on DigitalOcean — Docker + Postgres 15 + Caddy HTTPS + backups. (4) TRANSFORM: n8n JSON → typed Pydantic Python, MCP-ready (flows/active/viral-news-avatar). (5) TEACH: n8n-ai-workflows-workshop → the Academy.
  • Distribution: Blotato now (staging-gated) to ship; selectively build direct integrations where control/margin/feature-depth earns it.
  • Staying current: Fatigue is real, but giving in costs you the opportunities you then aren't ready to receive — you can't catch what you've stopped tracking.
Option Pros Cons
n8n fast to learn · visual · huge node library · API-able · great teacher JSON sprawl · hard to test/version/diff · runtime lock-in · brittle at scale
Typed Pydantic typed+validated · unit-testable · git-native · portable · agent-native · scales needs engineering · no visual canvas · higher upfront build
Blotato (aggregator) one API → 9+ platforms · maintained · fast (24 channels live) · no per-platform OAuth upkeep middle-man cost/limits · their roadmap not yours · less control · another dependency to audit
Your own API full control · own the tokens + IP · no per-post fee · platform-native features · no flag-from-a-shared-vendor OAuth + token refresh per platform · ToS/rate-limit/review risk you carry · ongoing upkeep as APIs change