Passive Revenue Lab Playbook

What This Playbook Covers

This playbook documents the full operating system behind Engage Evolution’s Passive Revenue Lab. It is the same system we use to ship lead magnets, template drops, newsletter sponsorships, and automated checkout flows every week without meetings, without manual invoicing, and without guessing which assets are actually making money. Everything described here is battle-tested across dozens of drops, multiple sponsor deals, and real revenue tracked to the dollar.

You will walk away with:

• Newsletter automation wiring — our Automation Signal Report blueprint, including trigger schedule, sponsor blocks, and AI QA prompts.
• Template shop operating model — SKU tracker, pricing calculator, and the scripts we use to push new assets live without meetings.
• Lead magnet packaging checklist — how we bundle PDFs, videos, and Loom walkthroughs so each drop can be sold or sponsored.
• Attribution + payouts — Airtable + Make recipes that route affiliate revenue and sponsorship fees automatically.
• Drop lifecycle management — the full timeline from ideation to revenue recognition.
• Revenue tracking dashboards — P&L templates, audience telemetry, and operational health metrics baked into the Airtable base.
• Managed service conversion path — how every passive revenue drop becomes a retainer-ready service offering.

The playbook assumes you already have a content operation of some kind (newsletter, blog, resource library) and want to layer monetization on top of it. If you are starting from zero, the Airtable base templates included here will accelerate your first drop to under a week.

Newsletter Automation Wiring

The Automation Signal Report is our weekly newsletter and the single highest-leverage asset in the Passive Revenue Lab. It drives subscriber growth, surfaces sponsor inventory, and doubles as a lead magnet archive. Here is how the automation works end to end.

Trigger Schedule and Send Logic

We send the Automation Signal Report every Tuesday at 10:30 AM ET. The send is triggered by a Make scenario that:

1. Pulls the latest newsletter markdown from our content repository.
2. Renders it into the HTML email template stored in SFMC/Braze/Iterable (depending on the client stack).
3. Injects the sponsor block if a sponsor is booked for that week (pulled from the Airtable sponsor pipeline).
4. Runs the AI QA prompt to validate links, personalization tokens, and compliance copy.
5. Pushes the final payload to the sending platform’s API with a 15-minute delay for human review.
6. Fires a Slack notification to the managing editor with a preview link and a one-click “approve” or “hold” button.

The entire flow runs hands-free unless the QA prompt flags an issue. When it does, the scenario pauses and routes the problem to the editor with specific line-level callouts.

Sponsor Block Injection

Sponsor blocks sit between sections two and three of every newsletter. The block format is standardized:

Element	Spec	Notes
Logo	120x40 PNG, retina-ready	Hosted on our CDN, not hotlinked
Headline	Max 12 words	Must pass the slop filter (no “game-changer” language)
Body	Max 50 words	One CTA link, UTM-tagged with sponsor and campaign params
CTA button	Single button, branded color	Links to sponsor landing page or Motion booking
Disclosure	”Sponsored by [Name]“	Required for FTC compliance

Sponsors provide creative assets at least 72 hours before the send. The Make scenario validates the block against the spec and rejects non-conforming assets with a templated email requesting corrections.

AI QA Prompts

Before every send, an AI QA pass evaluates the newsletter against a rubric:

• All links resolve (no 404s, no redirect chains longer than two hops).
• Personalization tokens have fallback values.
• Sponsor disclosure language is present when a sponsor block is included.
• No internal-only language, API keys, or measurement IDs have leaked into the content.
• Reading level stays between grades 8 and 12 (Flesch-Kincaid).
• Word count stays within the 600-1200 word range for the body (excluding sponsor block).

The QA prompt writes results to a BigQuery table so we can track defect rates per drop and identify recurring issues over time.

Template Shop Operating Model

The template shop is the second revenue engine. It sells individual templates, bundles, and toolkits through a storefront integrated with Gumroad (for payment processing) and Airtable (for inventory and fulfillment tracking).

SKU Tracker

Every asset in the shop is tracked as a SKU in the Airtable base. The SKU record includes:

Field	Type	Purpose
sku_id	Auto-number	Unique identifier across all assets
title	Single line text	Display name on storefront
asset_type	Single select	Template, Bundle, Toolkit, Checklist
price_usd	Currency	Current price (supports $0 for lead magnets)
cost_hours	Number	Hours invested to produce (for margin calculation)
status	Single select	Draft, Review, Live, Retired
download_url	URL	Link to the hosted file (PDF, ZIP, or Notion template)
gumroad_product_id	Single line text	Maps to the Gumroad product for reconciliation
created_date	Date	When the asset entered the pipeline
last_updated	Date	Last content or pricing revision
lifetime_revenue	Rollup	Sum of all transactions linked to this SKU
affiliate_eligible	Checkbox	Whether affiliates can promote this SKU

Pricing Calculator

Pricing follows a simple formula:

Base price = (cost_hours x hourly_rate) / target_units_sold_in_90_days

We use a $150/hour internal rate and a target of 50 units in the first 90 days. A template that took 4 hours to build prices at ($150 x 4) / 50 = $12. We round to the nearest $5 increment for clean pricing. Bundles get a 20% discount off the sum of individual SKU prices.

Free lead magnets (price = $0) still get a SKU so we can track downloads, attribute conversions, and measure the managed service pipeline they feed.

Publishing Workflow

Pushing a new asset live follows this sequence:

1. Writer delivers the asset and marks the SKU status as “Review” in Airtable.
2. Editor runs the packaging checklist (see next section) and confirms the asset meets quality standards.
3. Web producer creates the Gumroad product, uploads the file, sets the price, and pastes the gumroad_product_id back into Airtable.
4. Web producer publishes the site page by running npm run export:resources and pushing the update.
5. Airtable automation fires a Slack message to the distribution channel with the live URL, price, and suggested social copy.
6. LinkedIn post and email announcement go out within 24 hours of the SKU going live.

No meetings. The entire handoff happens through Airtable status changes, Slack notifications, and the publishing script.

Lead Magnet Packaging Checklist

Every lead magnet, whether it is a PDF playbook, a video walkthrough, or a Loom-narrated toolkit, goes through the same packaging checklist before it ships. This ensures consistency, sponsor-readiness, and a clean experience for the person downloading it.

Pre-Packaging Requirements

• Title is under 60 characters and describes the deliverable, not the topic.
• Description is under 160 characters and answers “what will I walk away with?”
• Hero image is 1792x1024 (DALL-E 3 spec) or 1536x1024 (gpt-image-1 spec), WebP format.
• PDF is styled with the Engage Evolution template (cover page, headers, footer with URL).
• All links in the PDF resolve and use UTM parameters (utm_source=resource&utm_medium=pdf&utm_campaign={slug}).
• Sponsor slot is present on page 2 if the asset is sponsor-eligible (even if currently unfilled — use a placeholder block).

Content Quality Gates

• Minimum 2000 words for playbooks and guides; minimum 800 words for checklists.
• At least 6 level-2 sections for playbooks; at least 4 for checklists.
• At least 1 table with actionable data (not decorative).
• No AI slop phrases: “game-changer,” “fast-paced digital landscape,” “harness the power of,” etc.
• At least 2 external citations or references to vendor documentation.
• Internal cross-link to at least 1 other published resource or blog post.

Delivery Automation

After the gated form is submitted:

1. Web3Forms captures the submission and fires a webhook to Make.
2. Make scenario sends the download link via a transactional email (SFMC or Braze, depending on client stack).
3. The same scenario adds the subscriber to the newsletter list with a tag matching the resource slug.
4. A 48-hour delay automation sends a follow-up email asking if the resource was useful and offering a 15-minute strategy call via the Motion booking link.
5. CRM record is updated with the resource download event for attribution.

Video and Loom Bundling

For assets that include video:

• Host Loom recordings on the Engage Evolution Loom workspace (not personal accounts).
• Embed the Loom link inside the PDF on a dedicated “Video Walkthrough” page with a QR code for mobile access.
• Include a transcript as an appendix. This adds word count, improves accessibility, and gives the AI QA agent more content to validate.
• Tag the Loom with the SKU ID so analytics can tie video views back to the revenue tracker.

Attribution and Payouts

Attribution is the backbone of the Passive Revenue Lab. Without it, you are guessing which drops make money and which sponsors are worth renewing. We automate the entire chain from click to payout using Airtable, Make, and the payment processor’s API.

Attribution Architecture

Every revenue-generating touchpoint carries a composite tracking ID:

{source}_{medium}_{campaign}_{content}_{term}

For example: newsletter_email_asr-2025-w04_sponsor-block_braze

This ID flows through:

1. UTM parameters on all outbound links (newsletter CTAs, social posts, storefront links).
2. Gumroad webhook payloads that fire on every purchase event.
3. Web3Forms submission metadata that captures the referring URL and UTM params.
4. GA4 events that log CTA clicks, resource downloads, and Motion booking completions.

A Make scenario listens for Gumroad webhooks and Web3Forms submissions, extracts the tracking ID, and writes a row to the transactions table in Airtable.

Transaction Table Schema

Field	Type	Purpose
transaction_id	Auto-number	Unique key
tracking_id	Single line text	Composite attribution string
source	Formula (parsed from tracking_id)	Newsletter, LinkedIn, Storefront, Affiliate
sku_id	Linked record	Maps to the SKU tracker
amount_usd	Currency	Gross revenue
fee_usd	Currency	Payment processor fee
net_usd	Formula	amount_usd - fee_usd
affiliate_id	Linked record	Maps to the affiliate roster (if applicable)
affiliate_payout_usd	Formula	net_usd x affiliate_rate
sponsor_id	Linked record	Maps to the sponsor pipeline (if applicable)
timestamp	Created time	When the transaction was recorded

Affiliate Payout Automation

Affiliates earn a flat 20% of net revenue on referred sales. The payout process runs monthly:

1. On the 1st of each month, a Make scenario queries the transactions table for the previous month, grouped by affiliate.
2. It generates a payout summary and sends it to the affiliate via email for confirmation.
3. Once confirmed, the scenario triggers a PayPal or Wise payout via API.
4. The payout record is written back to Airtable with the payment reference ID.

Sponsor payouts follow a different cadence. Sponsors are invoiced per drop (newsletter send or resource co-branding) with net-30 terms. Airtable automation sends the invoice reminder at day 0, day 14, and day 28.

Drop Lifecycle Management

Every drop — whether it is a newsletter edition, a template release, or a sponsored resource — follows the same lifecycle. This consistency is what makes the system scalable without adding headcount.

Phase 1: Ideate (Days 1-2)

Task	Owner	Output
Pick topic based on signal backlog or sponsor brief	Managing Editor	Topic brief in Airtable
Assign persona and monetization path	Managing Editor	Updated SKU record
Commission hero image (DALL-E or designer)	Web Producer	WebP file in /public/images/heroes/generated/
Confirm sponsor participation (if applicable)	Partnerships	Sponsor block creative assets

Phase 2: Build (Days 3-5)

Task	Owner	Output
Draft the resource or newsletter body	Writer	Markdown file in src/content/
Run AI QA pass and fix flagged issues	Editor	Clean markdown, QA log in BigQuery
Package the download (PDF export, Loom recording)	Web Producer	Files in /public/downloads/
Set up auto-response email and list tagging	Marketing Ops	Make scenario configured

Phase 3: Launch (Day 6)

Task	Owner	Output
Publish site page via npm run export:resources	Web Producer	Live URL
Push LinkedIn announcement with UTM-tagged link	Web Producer	LinkedIn post
Trigger newsletter send (if newsletter drop)	Managing Editor	Email delivered
Update storefront listing (if template drop)	Web Producer	Gumroad product live

Phase 4: Monetize (Days 7-30)

Task	Owner	Output
Monitor download and purchase velocity	Growth Lead	Daily Slack digest from Airtable
Send sponsor attribution report	Partnerships	PDF report with impressions, clicks, conversions
Identify managed service conversion opportunities	Account Lead	Qualified leads in CRM
Run 48-hour follow-up automation	Marketing Ops	Strategy call bookings

Phase 5: Retrospective (Day 30)

Task	Owner	Output
Close the drop P&L in the revenue tracker	Finance	Final margin calculation
Archive sponsor assets and update the pitch deck	Partnerships	Updated deck
Log lessons learned and update playbook	Managing Editor	Airtable changelog entry
Decide: restock, retire, or bundle the asset	Managing Editor	SKU status update

Revenue Tracking and Metrics

We track three categories of metrics for every drop. The Airtable base includes pre-built views and formulas for all of them.

Drop P&L

Each drop gets a P&L card that auto-calculates:

• Gross revenue: Sum of Gumroad sales + sponsor fees + affiliate-referred revenue.
• Cost of goods: Hours invested x $150 internal rate + any contractor or tool costs.
• Margin: (Gross revenue - COGS) / Gross revenue, expressed as a percentage.
• Break-even timeline: Number of days from launch to the point where cumulative revenue exceeded COGS.

The P&L updates in real time as transactions flow into the Airtable base. A weekly Slack digest summarizes top-performing and underperforming drops.

Audience Telemetry

• Net-new subscribers: Count of new email addresses added during the drop window, tagged by source (organic, paid, referral, sponsor co-reg).
• Source attribution: Breakdown of where subscribers came from, tied to UTM parameters.
• Churn: Unsubscribes and hard bounces that occurred within 7 days of the drop, segmented by whether the subscriber was new or existing.
• Engagement depth: Open rate, click rate, and scroll depth (for web-hosted versions) compared to the trailing 8-week average.

Operational Health

• Cycle time: Days from brief to live. Target is 6 days or fewer.
• QA defect rate: Number of issues flagged by the AI QA pass per drop. Target is fewer than 3 per drop.
• Hours invested vs. profit: Actual hours logged against the drop compared to the revenue it generated. This is the single most important efficiency metric.
• Sponsor pipeline velocity: Days from sponsor outreach to signed deal. Target is under 14 days for returning sponsors, under 30 for new.

Airtable Base Setup

The Airtable base is the operational hub. It contains six core tables, each linked to the others through relationship fields.

Core Tables

1. Drops — One record per drop (newsletter edition, template release, sponsored resource). Fields include topic, persona, monetization path, status, launch date, and linked SKU.
2. SKUs — Product catalog for the template shop. Fields described in the SKU Tracker section above.
3. Transactions — Every revenue event. Fields described in the Attribution section above.
4. Sponsors — Pipeline of sponsor prospects and active deals. Fields include company name, contact, deal stage, contracted fee, drop assignments, and renewal date.
5. Affiliates — Roster of affiliate partners. Fields include name, referral code, commission rate, lifetime earnings, and payout history.
6. Team — Internal roster mapping people to roles and RACI assignments for each drop phase.

Key Views

• Active Drops (Kanban) — Cards grouped by phase (Ideate, Build, Launch, Monetize, Retro) with color coding for monetization path.
• Revenue Dashboard (Grid) — All transactions with rollups showing total revenue, average order value, and revenue by source.
• Sponsor Pipeline (Kanban) — Deals grouped by stage (Prospect, Pitched, Negotiating, Signed, Delivered, Renewed).
• SKU Performance (Grid) — All SKUs sorted by lifetime revenue with margin calculations and restock flags.
• Overdue Items (Filtered Grid) — Any drop, sponsor follow-up, or payout that has passed its deadline without completion.

Automation Recipes

The base ships with these automations pre-configured:

1. New Drop Created — Assigns default tasks, sets deadlines based on the 6-day cycle, and notifies the managing editor.
2. SKU Status Changed to Live — Fires the distribution notification to Slack with the live URL and suggested social copy.
3. Transaction Recorded — Updates the drop P&L, recalculates affiliate payouts, and checks if the sponsor attribution threshold has been met.
4. Sponsor Deal Signed — Creates the sponsor block template, sets creative asset deadlines, and notifies the web producer.
5. Overdue Alert — Sends a daily digest of items past their deadline to the team channel.

Import the base using the shared link included in the playbook download. Replace our example data with your own offers, and the automations will work immediately.

Converting the Lab Into a Managed Service

The Passive Revenue Lab is not just an internal operation. It is a productized service that we sell to clients who want the same system running on their behalf. Here is how we make the conversion.

The Pitch

Every drop we publish becomes social proof. When a prospect asks “can you do this for us?” we point to the live newsletter, the template shop, and the revenue numbers. The pitch is simple: “We already run this system. You can license the playbook and run it yourself, or you can pay us to operate it for you.”

Service Tiers

Tier	What You Get	Monthly Fee Range
Self-Serve	Playbook + Airtable base + 1 onboarding call	One-time $500-$1,500
Assisted	Everything above + weekly office hours + QA reviews	$2,000-$4,000/mo
Fully Managed	We run the entire lab on your behalf — content, distribution, sponsor sales, attribution	$6,000-$12,000/mo

The pricing calculator in the Airtable base lets you model these tiers against your own cost structure. Adjust the hourly rate, target margin, and expected drop cadence to generate pricing that works for your market.

Sponsor-Ready Recap Deck

After every 4-week sprint, we generate a recap deck that shows:

• Total drops shipped and their revenue outcomes.
• Audience growth and engagement trends.
• Sponsor performance (impressions, clicks, conversions delivered vs. contracted).
• Operational health metrics (cycle time, defect rate, margin).

This deck serves double duty: it is a client deliverable for managed service engagements and a sales tool for prospecting new clients.

Cloneable Automation Backlog

The playbook includes a backlog of 30+ automation ideas, prioritized by effort and expected revenue impact. Examples:

• Automated sponsor renewal reminders 30 days before contract expiration.
• Dynamic pricing for template bundles based on purchase history.
• Referral program automation that issues discount codes when a subscriber refers a new sign-up.
• Win-back sequences for lapsed template shop customers triggered by new SKU launches.

Each backlog item includes estimated hours, required integrations, and a link to the relevant section of the playbook.

Case Studies

Case Study 1: B2B SaaS Newsletter Monetization

A mid-market SaaS company with 12,000 newsletter subscribers wanted to generate revenue from their weekly product update email without alienating readers. We installed the Passive Revenue Lab system and ran it for 90 days.

Results:

• 8 sponsored newsletter editions at $1,200 per sponsor block = $9,600 gross revenue.
• 3 lead magnets published, generating 1,400 net-new email subscribers.
• 2 managed service deals closed from strategy call bookings triggered by the 48-hour follow-up automation, worth $18,000 in annual contract value.
• Cycle time averaged 5.2 days per drop. QA defect rate was 1.8 per drop.

Key Takeaway: The sponsor block format and FTC-compliant disclosure language removed the friction that had previously prevented the client from monetizing their newsletter. The automation handled creative validation so the editor never had to chase sponsors for corrected assets.

Case Study 2: Lifecycle Consultancy Template Shop

A lifecycle marketing consultancy wanted to sell their internal templates and checklists but did not want to build an e-commerce operation. We set up the template shop model on Gumroad with the Airtable SKU tracker.

Results:

• 14 SKUs launched in the first 60 days (mix of free lead magnets and paid templates priced $9-$29).
• $4,200 in template sales in the first quarter.
• 38% of free lead magnet downloaders booked a strategy call within 14 days.
• 12% of strategy call attendees converted to managed service retainers averaging $5,500/month.

Key Takeaway: Free lead magnets were not a cost center — they were the top of a measurable funnel that generated retainer revenue at a 22:1 ROI when attributed properly through the transaction table.

Implementation Timeline

If you are starting from scratch, follow this 4-week implementation plan. If you already have some of the infrastructure in place (newsletter, content library, payment processor), you can skip ahead.

Week 1: Foundation

• Import the Airtable base and customize the tables for your team, personas, and monetization paths.
• Connect your RSS feeds and signal sources to the intake table.
• Set up the Gumroad storefront (or Stripe checkout, if you prefer) and link it to the SKU tracker.
• Configure the Make scenario for Gumroad webhook capture and transaction recording.

Week 2: First Drop

• Pick your first topic from the signal backlog or sponsor pipeline.
• Draft the resource, run the packaging checklist, and publish it using npm run export:resources.
• Wire the auto-response email and list tagging through Make.
• Push the LinkedIn announcement and monitor download velocity in Airtable.

Week 3: Newsletter Integration

• Set up the newsletter automation in your sending platform (SFMC, Braze, Iterable, or even Mailchimp).
• Configure the sponsor block injection logic in the Make scenario.
• Run the AI QA pass on a test send and fix any flagged issues.
• Send the first edition and track opens, clicks, and conversions through the attribution system.

Week 4: Monetize and Measure

• Reach out to 5 potential sponsors using the outreach templates included in the playbook.
• Close your first sponsor deal and deliver the attribution report after the send.
• Run the drop retrospective and close the P&L in the revenue tracker.
• Plan the next 30-day content calendar using the backlog and drop lifecycle framework.

After week 4, you should have a repeatable system that produces one drop per week with measurable revenue. Scale by increasing drop cadence, adding affiliate partners, or converting high-performing drops into managed service offerings.

Operational Playbooks and Troubleshooting

When a Drop Underperforms

If a drop generates less than 50% of projected revenue within 14 days:

1. Check the attribution data. If clicks are high but conversions are low, the landing page or checkout flow has friction. A/B test the CTA copy and page layout.
2. Check the audience telemetry. If opens are low, the subject line or send time missed. Resend to non-openers with a revised subject line within 48 hours.
3. Check the pricing. If the template shop SKU is not selling, test a lower price point or bundle it with a complementary asset.
4. If all metrics are healthy but revenue is still low, the audience may not be ready for the offer. Repackage the asset as a free lead magnet and use it to feed the managed service pipeline instead.

When a Sponsor Churns

• Immediately reassign the sponsor block to a house ad promoting your own template shop or managed service offering. Never send a newsletter with an empty sponsor block.
• Send the churned sponsor a brief exit survey (3 questions, takes 60 seconds) to understand why they did not renew.
• Update the sponsor pipeline in Airtable and begin outreach to replacement candidates using the warm list.
• Review the attribution report for the churned sponsor’s drops. If performance was strong, use those numbers in outreach to the next prospect.

When the Automation Breaks

• The Make scenario dashboard shows error logs for every failed step. Start there.
• Common failures: expired API tokens (Gumroad, Braze, SFMC), Airtable rate limits (batch your writes), and webhook URL changes after a platform migration.
• The playbook includes a “break glass” manual process for every automated step so you can keep shipping drops while the automation is being repaired.

Use the playbook end-to-end or cherry-pick the assets you need. Everything is versioned in the Airtable base with changelog tables so future drops stay profitable and on-brand.