Map every way money arrives into three lanes: Time, Asset, and Recurring. Give each engine a mechanic, a target, and a sensor, then build them in order of distance to cash.
← All Claude SkillsMost businesses run on one offer, so revenue swings with your calendar and your energy. Growth Engine Designer sorts every stream into three lanes, gives each engine a mechanic and a revenue target, names the one engine that funds the tooling, and picks the build order by distance to cash. You get a revenue portfolio you can see, measure, and grow. Copy the two blocks below and give them to your Claude.
Step 1. Copy the skill block below.
Step 2. Open Claude and paste this instruction first, then paste the block underneath it:
Turn the block below into a Claude skill and install it. Create the skill file exactly as written. Then personalize it with smart defaults from what you know about me: my business, my offers, and how my revenue actually arrives. Confirm when it is installed and tell me 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.
Claude reads the block, builds the skill file, and installs it. From then on, you just run the skill in any conversation. No folders to find, no code to write.
Every week you see what's working, build it live, and put it to work in your business.
Here's the shape of what this skill hands you when it runs. Copy it, use it, keep moving.
You don't need to hold any of this in your head. That's the skill's job. If you're curious what it's doing for you, here's the idea underneath it.
One offer means one lane doing all the work, so the money swings every month. A portfolio spreads the work across three lanes that each do a different job. Time revenue brings the big checks, asset revenue makes every day produce, and recurring revenue makes every month predictable. You get a system you can see and steer.
Time revenue brings the big checks, asset revenue sells while you sleep, and recurring revenue sets the floor. Every stream lives in exactly one lane, and a healthy portfolio runs at least one live engine per lane.
Every engine gets five named parts: a mechanic, a target, an owner, a sensor, and a lane. When all five are named, you have something you can operate, measure, and hand off.
Rank every engine by how fast it reaches money and build in that order. The engines that monetize what you already have ship first, in days, and the ones that need new infrastructure wait their turn.
One engine is named to cover the cost of the tools and models that build everything else. When the system pays for itself from a lane it built, your build budget stops competing with groceries.
Done means all three lanes produce tracked revenue, the sensor reports every morning, and no lane carries more than 70% by your target date. Done is behavior you can watch.
The three-lane portfolio sorts every revenue stream in a business into one of three lanes. Time revenue is the big high-ticket checks that consume your hours. Asset revenue is products that sell without you. Recurring revenue is the predictable monthly base from memberships, retainers, and group programs. A healthy portfolio runs at least one live engine in each lane.
The Funding Engine Rule names one engine in the portfolio as the one whose revenue covers the cost of the tools, models, and infrastructure that build everything else. You write the math down and keep that tooling cost well under the engine's revenue target. 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 Concentration Rule caps any single lane at 70% of monthly revenue by your target date. When one lane carries almost everything, your income swings with that one lane. Spreading revenue across all three lanes is the swing you are designing away from, so the ceiling keeps the portfolio balanced and predictable.