MAC Matrix Downloadable Template - Status and Ship Plan
The question
The May 11 practitioner-newsletter-acquisition brief named MAC as the Phase 1 lead-magnet candidate for Sanity Check. The mechanic only works if the matrix is a one-click, copy-into-my-workspace artifact - not a markdown file in a private vault. Where does the MAC matrix template live today as a public downloadable, and is the lift from "currently exists" to "Notion / Google Sheet duplicable with email capture" low enough to ship this week, or is real design work in the path?
What we already know (from the vault)
- The canonical artifact exists as plain markdown at [[01-projects/data-quality-framework/testing-matrix-template]] (
testing-matrix-template.md, 19KB, last touched 2026-04-13). It contains:- Full Scope x Basis definition (3 scopes x 6 bases = 18 cells)
- System of Record prerequisite section
- Severity tiers (Stop / Pause / Go) with layer-aware (bronze / silver / gold) mapping
- A populated Salesforce Closed-Won worked example
- A blank fill-in-per-model template block
- A second populated worked example (ARR Waterfall)
- A SQL Patterns Reference appendix
- The MAC landing page is in build per [[01-projects/mac-landing/2026-05-05-build-spec]]: Astro on Cloudflare Pages, Resend Automations for the 7-email drip, Turnstile for bot protection, Fathom for analytics. Form-submission flow is fully specified (CF Pages Function -> Resend Audience add -> automation trigger -> cookie set). The page targets mac.raydata.co for prototype, modelacceptancecriteria.io for production.
- The MAC pre-launch readiness checklist [[01-projects/mac/2026-05-14-mac-prelaunch-readiness-checklist]] identifies a P0 blocker: every external MAC artifact must be scrubbed of MG client specifics (gold_txn_pipeline, Progress, Podio, PRO- ticket prefix, named individuals, exact bug counts). The current
testing-matrix-template.mduses generic Salesforce Closed-Won and ARR Waterfall examples - those are already clean and shippable. The scrub blocker applies to deck materials, not to the matrix template itself. - Founder approved Sanity Check piece "Your dbt models are about to get Tickered" [[06-reference/research/2026-05-11-sc-dbt-models-tickered]] - the matrix download is the natural CTA at the bottom of that piece.
- Design constraint from [[01-projects/mac-landing/2026-05-05-build-spec]]: black-and-white blocky/graffiti aesthetic, NOT flat/minimal. The matrix needs to render with that visual personality, not as a generic Notion gallery template.
- Vault gap: no existing Notion or Google Sheet copy of the matrix has been published. The artifact is markdown-only today. There is no
templates/directory on raydata.co or hq.raydata.co serving this asset.
What the web says
Conversion benchmarks for niche practitioner lead-magnets (2026)
The format-matters numbers across multiple sources converge tightly:
| Format | Opt-in rate | Source |
|---|---|---|
| Generic "subscribe to newsletter" box | 1-3% | DigitalApplied 2026 benchmarks |
| Generic PDF guide | 5-10% | DigitalApplied 2026 benchmarks |
| Niche checklist / calculator | 25-40% | DigitalApplied 2026 benchmarks |
| Interactive self-assessment | 25-40% | DigitalApplied 2026 benchmarks |
| Free tool / calculator (SaaS audiences) | 28-42% | NetPartners 2026 |
| Audit report | 15-25% | DigitalApplied 2026 benchmarks |
The 3-5x multiplier for niche vs generic lead-magnets is consistent across the surveyed sources. The MAC matrix sits in the high-converting band: it is concrete (18 cells, named severity tiers), it is industry-specific (analytics-engineering / dbt), and it is immediately useful in the persona's actual work (definition-of-done for a new dbt model).
Notion-as-template-mechanism: the canonical pattern
Notion has a first-class "Allow duplicate as template" toggle that converts any published page into a one-click copy into the visitor's workspace. The flow:
- Share button -> Share to web -> ON
- Toggle "Allow duplicate as template" -> ON
- Optional: turn OFF search-engine indexing (recommended for lead-magnets - you want the landing page indexed, not the raw template)
- Copy the public URL
When a visitor hits the URL, Notion shows a preview with a prominent "Duplicate" button that drops the page into their workspace (any plan, including free). This is the lowest-friction copy mechanism on the practitioner-tool internet today. Lower friction than Google Sheets (which requires a Google account and a File -> Make a copy step) and dramatically lower than a PDF (which requires the user to manually re-create the structure to use it).
The well-known cited examples confirm the mechanic works for senior practitioners:
- Lenny Rachitsky's "growth model spreadsheet" - PM teams pass it around in Slack; each duplicate is a soft list-build event (covered in the May 11 practitioner-newsletter brief)
- dbt's "How We Structure Our dbt Projects" Discourse post - de-facto reference doc analytics engineers pass around
- The Pragmatic Engineer's tech compensation report - engineers send to each other
The MAC matrix shape is closest to Lenny's spreadsheet pattern: a structured grid the persona fills in for their own model, then copies for the next model.
Format choice: Notion vs Google Sheets vs PDF for MAC specifically
The 18-cell matrix has three usage modes:
- Reading / understanding (one-time): the populated worked example. Static. Any format works. PDF is fine.
- Filling in for a real model (recurring): a blank template the engineer fills in per dbt model. This is the high-value use. Needs to be re-usable, version-controlled in the team's own workspace, and shareable internally.
- Reference patterns (lookup): the SQL appendix. Static reference. Markdown / code-snippet format is best.
Notion handles all three in one document - prose for #1, a duplicate-and-fill database or page-per-model pattern for #2, and code blocks for #3. Google Sheets handles #2 well but degrades for #1 and #3. PDF handles only #1.
Recommendation: Notion as primary, with a Google Sheets mirror for engineers who prefer that surface. The Notion version is the canonical artifact promoted on the MAC landing page. The Sheets version is a secondary download from the same page for engineers who live in spreadsheets (a real subset of the practitioner persona, particularly data analysts vs data engineers).
Friction points that kill conversion for senior practitioners specifically
Cross-checked against the May 11 practitioner-newsletter brief and the 2026 lead-magnet best-practice sources:
- Multi-field opt-in forms. The "name + role + company + how-did-you-hear" form reads as beneath the senior persona. Email-only with optional name is the maximum.
- Welcome quizzes / segmentation surveys before delivery. Senior audiences will close the tab.
- Gated downloads with marketing-copy walls between the form and the artifact. Show the artifact preview first, then the form.
- Generic "Ultimate Guide to Data Quality" framing. Specificity is the moat - "18-cell data-model acceptance matrix used to find 95 tests in a closed-won pipeline" is the right shape, not "Data Quality 101."
- Templates with the creator's branding splashed across them. The user will duplicate into their workspace and use it inside their company - branding should be a single discreet footer line, not a watermark.
Convergences and contradictions
Internal sources, web evidence, and the MAC product trajectory all point the same direction: the matrix template IS the lead-magnet shape that fits this persona, and Notion-with-duplicate-toggle IS the right delivery mechanism. No real contradictions in the inputs.
The one tension is the MAC landing page design directive (B&W blocky/graffiti aesthetic) vs Notion's neutral default styling. A duplicated Notion template will look like every other Notion template once it lands in the user's workspace. That is FINE for the artifact itself - the user wants it to blend into their team's existing Notion. The landing page is where the MAC visual personality lives. The Notion template is the utility hand-off.
The May 14 pre-launch checklist's P0 scrub blocker does not apply to the existing testing-matrix-template.md - it uses generic SF Closed-Won and ARR Waterfall examples, no MG client identifiers. The scrub blocker applies to deck and dashboard materials. The matrix template can ship as-is (with one small naming sweep below).
Synthesis for RDCO - the ship plan
Verdict: ship this week. Friction is low. No design work blocks it.
The work decomposes into 5 hours total, sequenced:
Step 1 (45 min): Port the markdown matrix into a Notion page.
- Create a new page in the RayDataCo Notion workspace titled "MAC: Model Acceptance Criteria - Testing Matrix Template"
- Three sections matching the markdown structure:
- Section A: How to read the matrix (the prose definitions of Scope x Basis, severity tiers, layer-aware severity)
- Section B: Worked examples (Salesforce Closed-Won and ARR Waterfall - both already clean, no MG identifiers)
- Section C: Blank template (the fill-in-per-model block) - implemented as a Notion database with one row per model OR as a duplicable sub-page, whichever the founder prefers
- SQL appendix as a collapsible toggle at the bottom
- One discreet footer line: "Built by Ray Data Co. More at raydata.co/mac"
Step 2 (30 min): Sweep the Closed-Won example for any remaining over-specific language. The existing markdown is already generic but worth one read-through. The ARR Waterfall example is fully synthetic and ships as-is.
Step 3 (15 min): Configure Notion sharing.
- Share to web: ON
- Allow duplicate as template: ON
- Search engine indexing: OFF (we want the landing page indexed, not the raw template)
- Copy the public URL
Step 4 (90 min): Wire the email-capture loop on mac.raydata.co per [[01-projects/mac-landing/2026-05-05-build-spec]].
- Single-field email opt-in (email only, no name field)
- POST handler: Turnstile verify -> Resend Audience add -> Automation trigger -> respond 200 with Notion duplicate URL
- The Notion URL is delivered both inline on the thank-you panel AND in the first Resend email (so engineers who close the tab still get the link)
- No welcome quiz, no role-segmentation question, no multi-step funnel
Step 5 (60 min): Mirror to Google Sheets as a secondary download.
- Just the blank fill-in-per-model grid - skip the prose sections
- "Make a copy" link presented on the landing page as "Prefer Google Sheets? [Get the spreadsheet version]"
- Same email gate, same Resend trigger
Step 6 (15 min): Update the May 11 practitioner-newsletter brief with the now-resolved status, and update this page in Notion with the published Notion URL.
Design work that is NOT required this week (deferred to Phase 2):
- Custom Notion branding theme
- A Figma/Canva visual version of the matrix for the landing page hero (the build spec already calls for a 3x6 graffiti-style grid visual - that is landing-page art, separate work from the template artifact)
- A version of the template integrated with dbt-expectations YAML codegen (interesting Phase 3 product feature, irrelevant to lead-magnet)
- The forthcoming MAC sample dbt project from the pre-launch checklist (P0 for the paid product launch, not a blocker for the free lead-magnet)
Why this ships now, not after the paid product: The lead-magnet's job is to build the Sanity Check list while the paid MAC product is still being de-MG-scrubbed. The two work surfaces are decoupled. The free Notion template is the practitioner-acquisition lever today; the paid sample-project + commercial drip campaign is the September product. Shipping the free template earns audience signal (download volume, share rate, email replies) that informs the paid product positioning at zero opportunity cost.
Open follow-ups
- Does the founder want the Notion template hosted under the existing Ray Data Co workspace, or in a dedicated "templates" workspace separated from internal RDCO operations? (Surface for audit if engineers explore upward in the URL.)
- Should the Sheets mirror be a Google Sheet, a downloadable .xlsx, or both? Slight preference for both - some engineers will not touch Google's surface.
- When the next Sanity Check piece ships ("Your dbt models are about to get Tickered"), should the matrix download be the in-body CTA or the footer-only CTA? Recommend in-body at the natural cliff-hanger point in the essay (after the framework is named but before the worked example).
- Open from the May 11 brief, restated here for completeness: does the founder have warm-network reach to ask Daniel Beach, Ananth Packkildurai, Benn Stancil, or Joe Reis to include the template in a curated link? Cheap distribution multiplier once the artifact is live.
Sources
- Notion - Allow Duplicate as Template mechanic
- Notion Help Center - Duplicate public pages
- DigitalApplied - AI Lead Magnets: 7 Templates That Capture Emails (2026 benchmarks)
- NetPartners - Lead Magnet Ideas 2026: examples and conversion rates
- Vault: [[01-projects/data-quality-framework/testing-matrix-template]]
- Vault: [[01-projects/mac-landing/2026-05-05-build-spec]]
- Vault: [[01-projects/mac/2026-05-14-mac-prelaunch-readiness-checklist]]
- Vault: [[06-reference/research/2026-05-11-practitioner-newsletter-acquisition-tactics]]
- Vault: [[06-reference/research/2026-05-11-sc-dbt-models-tickered]]
- Vault: [[06-reference/2026-04-30-mac-bet-architecture-audit]]