CHRISTINE End the Feast-or-Famine Revenue Swing
Growth Engine Designer maps every way money arrives in your business into three lanes — Time, Asset, and Recurring — then turns each stream into a named engine with a target, an owner, and a sensor that reports every morning. So revenue stops swinging with your calendar and your energy.
← Back to the Skills LibraryInstalled in under a minute. No tech skills required.
You don't need to know how to code, and you don't need to set anything up. There are two blocks below. If you can copy and paste, you can install this.
Paste the instruction
Copy the first block and paste it into a brand-new Claude conversation. Don't hit send yet — it's the note that tells Claude what to do.
Paste the skill underneath, then send
Copy the full skill block and paste it right below the instruction. Send it. Claude builds the skill, personalizes it to your business, and confirms when it's ready.
Install the skill below for me. Keep the skill text exactly as written, then personalize its defaults from what you already know about me — my business, my voice, my priorities, and the places I keep my notes and files. Confirm when it's installed and show me exactly how to run it.
--- name: growth-engine-designer description: Design a complete revenue architecture for your business using the three-lane portfolio method (Time, Asset, Recurring), engine anatomy, distance-to-cash sequencing, and the Funding Engine rule. Use this skill whenever you say "design my growth engines," "revenue architecture," "run growth engine designer," "map my revenue," "build my revenue portfolio," "why does my revenue swing," or want to turn a single-offer business into a connected system of revenue engines with targets and sensors. Also trigger when you describe feast-or-famine revenue, over-dependence on one offer or one client type, or ask how to add products or recurring revenue to a services business. This is the bridge between "I sell things" and "I run a portfolio of engines I can see, measure, and grow." --- # Growth Engine Designer This method is the IP. Run it for yourself first, then run it for clients. ## The Big Idea Most businesses run a one-lane monopoly. One offer type carries everything, so revenue swings with your calendar and your energy. The fix is a portfolio: one connected system with three altitudes of revenue, each doing a different job, each with named engines, targets, and a sensor that reports every morning. **Time Revenue brings the big checks. Asset Revenue makes every day produce. Recurring Revenue makes every month predictable.** ## The Three-Lane Portfolio Every revenue stream in your business gets sorted into exactly one lane: | Lane | Job | Character | |---|---|---| | **Lane 1: Time Revenue** | The big checks | High-ticket engagements that consume founder hours. Partnerships, keynotes, workshops, 1:1. Grows by raising the ticket, never by adding hours. | | **Lane 2: Asset Revenue** | Sells without you | Products that transact while you sleep. Digital products, skill packs, templates, courses, productized systems. The lane most service businesses are missing entirely. | | **Lane 3: Recurring Revenue** | The floor | Memberships, group programs, retainers. The predictable monthly base that makes the other two lanes feel like upside instead of survival. | Rules of the portfolio: 1. Every engine lives in exactly one lane. If you can't place it, you haven't defined it. 2. A healthy portfolio has at least one live engine per lane. 3. **The Concentration Rule:** no single lane carries more than 70% of monthly revenue by your target date. Concentration is the swing you're designing away from. ## Engine Anatomy An engine is a revenue stream you can operate, measure, and hand off. Every engine gets five named parts. If a part is missing, the engine is a wish. 1. **Mechanic** — the repeatable path from stranger to cash, written as a chain (example: discovery call → live demo → proposal → engagement). If you can't write the chain, you don't have a mechanic yet. 2. **Target** — one number with a date. "First $10K booking." "25 sales in 30 days." "Fill to 20 members." Engines without revenue targets are sensors with extra steps. 3. **Owner** — who runs it day to day: you, a team member, or an agent. Be honest. "Me, for now" is a valid answer that creates a handoff candidate. 4. **Sensor** — where the engine's numbers show up without anyone assembling them by hand. One dashboard or one daily pulse beats five logins. 5. **Lane** — which of the three altitudes it lives in. ## Sequencing by Distance to Cash Never build engines in parallel from a standing start. Rank every designed engine by distance to cash, in time, and build in that order: 1. **Days/weeks:** engines that monetize assets you already have (package existing IP, open a checkout, revive a stale pipeline). 2. **30 days:** engines that need one launch cycle (a cohort, a webinar, a campaign). 3. **90 days:** engines that need new infrastructure or new audiences. The honest read matters here. Mark each engine **live**, **dormant**, or **designed-only**, and say which it is out loud. A dormant lane gets a wake-up build (its missing front door), never a bigger target. ## The Funding Engine Rule One engine in the portfolio gets named as the funding engine: the one whose revenue covers the cost of the tools, models, and infrastructure that build everything else. Write the math down. When the system pays for itself from a lane it built, you have a closed loop, and the build budget stops competing with groceries. The pattern to aim for: the fastest-to-cash asset engine (a product shipped in days) funds the AI tooling, and the tooling cost target stays under 5% of the revenue target. Self-Funding Intelligence. ## The Done Definition Pattern Every architecture document ends with two lines, and they keep everyone honest: - ✅ **Done means:** all three lanes have at least one live engine producing tracked revenue, the sensor reports every morning, and no lane exceeds the concentration ceiling by the target date. - ❌ **Not done means:** the portfolio exists only as a document, or the new lane still reads $0. Adapt the specifics, keep the shape. Done is observable revenue behavior, never a finished document. ## How To Run This Skill (the working session) 1. **Inventory.** List every way money currently arrives and every way it's supposed to. Include the dead ones. 2. **Sort into lanes.** Time, Asset, Recurring. Notice which lane is empty or nearly empty. That gap is usually the whole diagnosis. 3. **Design the engines.** For each stream worth keeping, write the five anatomy parts. Kill or merge anything that can't get a mechanic and a target. 4. **Honest read per engine.** Live, dormant, or designed-only, with the one missing piece named for anything not live. 5. **Sequence by distance to cash.** Order the build queue. Pick the funding engine. 6. **Name the sensor.** Decide the three numbers the owner sees every morning (yesterday by lane, month-to-date vs target, pipeline movement) and where they show up. 7. **Write the Done Definition.** The two lines. Get them approved by whoever owns the P&L. 8. **Ship the document** to wherever the business keeps its operating playbooks, with a Status of Active and a linked build queue. ## Worked Example: A Services Consultancy A generic run of this method, on a small firm that sold one thing, done-for-you projects: - **Lane 1 (Time):** the done-for-you consulting engagement as the flagship engine (mechanic: intro call → scoping session → proposal → signed project, target: first $25K project booked). A half-day strategy intensive read as dormant, so its wake-up build was a one-page offer plus a booking link, which shipped that week. Advisory hours as supporting cast under the never-more-hours rule. - **Lane 2 (Asset):** the missing lane, reading $0. Spearhead engine: a $99-$399 template kit assembled from three deliverables the firm already shipped to past clients, live on a checkout page inside the same week. Flagship swing: the full methodology packaged as a self-paced course for the next quarter. - **Lane 3 (Recurring):** a monthly retainer program as the predictable base (honest baseline: 3 clients), plus a small group workshop membership. - **Sensor:** a morning revenue pulse of three numbers reading the payment processor and the CRM. - **Funding engine:** template kit sales cover the software and AI tooling budget, a ceiling near $6K/year, under 5% of the revenue target. - **Done Definition:** all three lanes live with tracked revenue and no lane over 70% by the end of the quarter. The signature move the example proves: the empty lane got the spearhead, the dormant engine got a front door instead of a bigger target, and the whole design went from session to shipped assets in under a week. ## Voice and Delivery Notes Write architectures in plain language a non-technical founder reads in five minutes. Lead with the principle, then the table, then the engines. State honest reads with candor and zero shame. Every number traces to a source you rule (your price sheet, your CRM), never to this document's authority.
From then on, just say "Design my growth engines."
Want to go further than skills?
Skills like this are how Christine runs her own business every day. In the Heart-Led AI Signature Group Coaching, she teaches you the whole system — live, in plain English, at your pace.
Explore Signature CoachingOne architecture document. The whole money picture.
A run of Growth Engine Designer is a working session that ends in a plain-language architecture a non-technical founder reads in five minutes — not a strategy binder. These are its labeled parts, every time:
1 · The Three-Lane Portfolio
Every revenue stream sorted into exactly one lane: Time Revenue brings the big checks, Asset Revenue sells without you, Recurring Revenue is the floor. The empty lane is usually the whole diagnosis.
2 · The Engines, Five Parts Each
Each stream worth keeping becomes an engine with a mechanic, a target, an owner, a sensor, and a lane. If a part is missing, the engine is a wish.
3 · The Honest Read
Every engine gets marked live, dormant, or designed-only — said out loud — with the one missing piece named for anything not yet producing.
4 · The Build Queue
Engines ranked by distance to cash: days-to-weeks plays first (packaging what you already have), one-launch-cycle engines next, new-infrastructure builds last.
5 · The Funding Engine
One engine gets named as the one whose revenue covers the tools and infrastructure building everything else — with the math written down and tooling aimed under 5% of the revenue target.
6 · The Morning Sensor
The three numbers you see every morning without assembling anything by hand: yesterday by lane, month-to-date against target, and pipeline movement.
7 · The Done Definition
Every architecture ends with two lines that keep everyone honest. Done means all three lanes have a live engine producing tracked revenue, the sensor reports every morning, and no lane exceeds the concentration ceiling. Not done means the portfolio exists only as a document.
A pretty document doesn't count as done
This skill defines done as observable revenue behavior — never a finished document. If the new lane still reads $0, it's not done, no matter how good the plan looks. And the honesty cuts both ways: a dormant engine gets a wake-up build — its missing front door — never just a bigger target. Every number traces to a source you control, like your price sheet or your CRM, never to the document's own authority.
Keep stacking: pairs beautifully with Enrollment Engine
Growth Engine Designer maps your whole revenue portfolio and decides which engines to build — Enrollment Engine then fills one specific offer, building its sales narrative, objection bank, warm list, and nurture sequence from your real records.
Get Enrollment Engine →One offer carrying everything is why revenue swings.
Most service businesses run a one-lane monopoly: a single offer type carries the whole month, so revenue rises and falls with your calendar and your energy. The fix is structural, not more hustle.
Three lanes, three different jobs
Time Revenue brings the big checks, Asset Revenue makes every day produce, and Recurring Revenue makes every month predictable. When each lane does its own job, the other two stop feeling like survival and start feeling like upside.
Five parts turn a wish into an engine
"Sell more courses" is a wish. A written mechanic (the path from stranger to cash), one target with a date, a named owner, a sensor, and a lane — that's an engine you can operate, measure, and hand off.
Distance to cash sets the build order
Engines never get built in parallel from a standing start. Whatever monetizes assets you already have ships first, one-launch-cycle engines come next, and 90-day infrastructure builds wait their turn. Early wins fund the patience.
The concentration rule caps the risk
No single lane carries more than 70% of monthly revenue by your target date. Concentration is the swing you're designing away from — the rule turns that from a vibe into a number you can check.
The system pays for itself
One engine gets named the funding engine: its revenue covers the tools and infrastructure that build everything else. When that loop closes, the build budget stops competing with groceries.