The Pain: Most people talking about AI monetization get stuck on the same move — build the product first, then go find someone to buy it. The product ships and the customers are not there. You buy one batch of traffic, and next month you have to buy the next batch all over again. Greg Isenberg runs the order backwards: distribution first, services second, and only then do products and investing collect the upside.
What You'll Learn: What actually keeps each of Greg's five buckets alive (services, exits, advisory, media, investing), why a content flywheel keeps pushing customer acquisition cost down instead of up, the six directions he gives for making money with GPT-6 Astra, and a simple framework for judging how many buckets you are already holding today.
⚡ 10-minute fast read: jump to "2. How the flywheel turns", "5. Single-bucketing and distribution debt", and the one-liner at the end.
🎯 Read by need: for the business model, read sections 1 and 2; for concrete moves, read sections 3 and 4; to check yourself against it, read sections 5 and 6.
📖 Full read: about 10 minutes, and you come away with Greg Isenberg's revenue structure plus a flywheel lens you can move onto your own business.
1. Greg Isenberg's five buckets: five cash-flow entries for one person
The core claim: Greg's income is not one business. It is five cash-flow buckets stacked on top of each other — services, exits, advisory, media, investing — and each bucket has a different cash-flow personality.
First, who this person is. Greg Isenberg has been a head of product and a founder: 5by was acquired by StumbleUpon (2013), and Islands was acquired by WeWork. Those two exits are public, checkable facts, and they are the credibility floor under every advisory and investment opportunity he has had since. Today he runs a more complicated revenue structure, which I have organized into five buckets:
| Bucket | Contents | Cash-flow character |
|---|---|---|
| ① Late Checkout (holding company) | Agency (services) + Studio (own products) + Fund (investing) | Services = cash today; products/investing = upside tomorrow |
| ② Company exits | 5by → StumbleUpon (2013), Islands → WeWork | One-time lump sum + credibility |
| ③ Advisory | Reddit, TikTok | Cash / equity |
| ④ Media | YouTube / podcast / newsletter / courses | Builds distribution, lowers acquisition cost for everything else |
| ⑤ Angel investing | Consumer + developer-tool early-stage projects | Asymmetric upside |
Stare at that table for a moment and the first counter-intuitive point falls out: of the five buckets, only media does not collect money directly. Yet ordered by cash flow, it is the foundation of the whole structure.
The second counter-intuitive point: the five buckets do not carry risk on the same line. The services bucket has delivery pressure, but the money lands today. The exits bucket is a one-time event, monetizing credibility accumulated over years, and it is not repeatable. The media bucket is expensive up front and slow to pay back, and it pushes the acquisition cost of every bucket behind it down at the same time.
Pitfalls in this section:
- Do not read the five buckets as "five jobs" — what he is actually running is one portfolio of cash flows, where buckets feed each other, not a list of parallel side hustles
- Do not skip the bucket that does not charge money — media is the lever in this table that lowers acquisition cost for the other four; cut it and every remaining bucket has to be fed with paid traffic
2. How the flywheel turns: content in front, services in the middle, equity at the back
The core claim: the real job of the five buckets is to string themselves into a flywheel — content builds distribution → acquisition cost drops → services collect cash flow → products and investing collect equity → case studies feed the content back in.
Line the five buckets up along a timeline and the shape of the flywheel appears:
- Content builds distribution: YouTube, podcast, newsletter, courses — turning strangers into readers, continuously
- Acquisition cost drops: readers become leads, and clients for services and products walk in from the content instead of being bought one by one
- Services collect cash flow: the Agency delivers first, money lands today, and it feeds the products and the investments
- Products and investing collect equity: Studio's own products and the Fund's investments earn tomorrow's upside
- Case studies feed content: real cases that come out of service delivery become the raw material for the next round of content
The key to this flywheel is not that there are five buckets. It is whether step 5 really gets back to step 1.
A lot of people run a broken model: produce one round of content, close one batch of service clients, and then nothing — the next batch of clients needs a fresh round of content and a fresh batch of ads. In Greg's model, the case study is the content: on the day a delivery finishes, the next round of material is already collected.
Greg put the underlying problem plainly on his podcast: capability has gone up, but people's willingness to try new things has not. The flywheel sells exactly one thing — a lower threshold for trying. A reader who has seen several real cases is willing to pay for the first time, and every one of those cases came out of the previous delivery.
Pitfalls in this section:
- Do not read the flywheel as "build an audience first, monetize later" — every step of the flywheel produces cash flow, only in a different order; it is not "grind for free for a few years"
- Design the return path on purpose: write the delivery process up as content right after the delivery, instead of waiting for inspiration to arrive
3. Greg's six ways to make money with AI: from service-software to mini-games as a lead magnet
The core claim: of the six directions Greg lays out, exactly one is described as the highest-value one — turning a service into software. The other five all answer the same question: which slice of the work does AI actually take over?
In his "GPT-6 Astra: how I will make money with it" piece, he gives six concrete directions:
- Service → software: start from a service clients already pay for, break down the delivery process, let an AI product take the first-pass delivery, and charge a $500–5000/month subscription
- Optimize existing products: work on performance, security and UI — he gives one measured case where an application's response time went from 800ms to 20–30ms
- Company operating dashboard: pull docs, Stripe, analytics and call records together, ask once a week "what makes money, what wastes time, what should we stop", then commit to three things for the coming week
- Browser agent automation: let an agent walk real websites and fill real forms, and turn the process into a reusable SOP
- Cost-of-living optimization: bill negotiation and low-price monitoring on second-hand marketplaces
- Mini-games as a lead magnet: the game has to bring in clients, give people a reason to share it, and include a way to capture leads
Direction 1 and direction 6 are connected: one goes up, turning a service into a subscription product; one goes down, using a mini-game to pull leads in at the bottom. The four in the middle all answer the same question — which piece of work AI actually does.
The judgment underneath is plain: AI can do a great many things, but only one class of them can be charged for — the things somebody was already paying for.
Pitfalls in this section:
- Do not pick a direction by asking "what can AI do"; work backwards from "who has already paid for this"
- Service-software is not the same as building a SaaS: the core move is breaking the process into fine steps, keeping human judgment points with humans, and handing over only the rest
4. The starting point is not technology — it is a service clients already pay for
The core claim: Greg's starting point for product ideas is not a technology trend. It is the service clients are already willing to pay for — payment first, product second.
His own words are that services clients are already willing to pay for are where he starts looking for product ideas.
That sentence locks the order in place. Most people go: learn a tool → build a thing → find a buyer. Greg goes: see who is paying for what → take the delivery process apart → rebuild one slice of it with AI.
He is explicit about what "taking the process apart" means in practice: break it into steps, tools, inputs, outputs, and the points where a human has to make a judgment.
The most valuable half of that sentence is the end — the points where a human has to make a judgment. A lot of AI products fail because the parts that should stay with a person get handed to the model too, and delivery quality falls off a cliff. Keep the human. What AI takes over is the repetitive labor, not the right to decide.
There is outside confirmation for this direction, too. Anthropic's Building Effective Agents keeps coming back to one point: solve the problem the simplest way first, and if a fixed workflow can do it, do not rush into a more autonomous agent — define the steps, the inputs and the outputs clearly first. That points at the same thing as Greg's "break it down": define the process before you talk about automating it.
Pitfalls in this section:
- Do not swap payment validation for technical validation — a working piece of technology does not prove anyone will buy it; a paid transaction does
- When you break the process down, do not hand the human judgment points to AI as well; that line is where delivery quality lives
5. Single-bucketing and distribution debt: the two most expensive traps
The core claim: most people who stall on AI monetization are not blocked by ability. They are blocked by two structural mistakes — single-bucketing and distribution debt.
Single-bucketing first. It means reading AI monetization as "run one bucket": either build products with no distribution, or take orders without ever accumulating case studies — either way the income hangs off a single source.
It has two typical shapes.
The first: products with no distribution. You build something and nobody knows it exists. The micro-SaaS numbers from an earlier post in this series are what that road produces: among projects with revenue, the average is $4,298 MRR and the median is $145. Shipping the product is only half the job; the other half is letting the people who need it find it.
The second: taking orders without accumulating case studies. Every job starts from zero, client flow depends entirely on platform dispatch and your own ad spend, and when the job is done no asset is left behind.
Then distribution debt. It means running no content asset at all and buying traffic again for every new batch of clients, so the acquisition cost rolls up into a debt you have to keep servicing.
It compounds like this: no content asset → every client has to be bought → traffic gets more expensive → margin gets eaten → even less capacity to build content. Two or three turns of that, and you never get back to step 1.
Greg's fix is exactly to invert the order: build the media bucket first, let readers walk in on their own, and the acquisition cost of the other buckets falls together.
Pitfalls in this section:
- Do not use "accumulate first, monetize later" to justify single-bucketing — every step of the flywheel needs a cash-flow exit
- The expensive part of distribution debt is not the money spent on traffic; it is the absence of a content asset. Money spent gets spent again; an asset you build keeps working
6. The OPC interface: how many buckets are you already holding
The core claim: treat the five buckets as a self-check sheet — most one-person companies already hold two or three of them, they just have not noticed those buckets can be strung together.
Of the five, the lowest-barrier and most easily ignored is media. It needs no product and no inventory. It only needs you to keep writing about what you are already doing.
Ask yourself three questions against it: do you have a service capability (your day job is the services bucket)? Do you have case studies worth accumulating (the deliveries that bucket has already shipped)? Do you have a content outlet (a blog, a newsletter, a public account)?
The order I set for myself is: build distribution with the media bucket first, collect cash flow with the services bucket second, and only then think about products and investing — which is precisely Greg's ordering.
For most people the first action is not "build an AI product". It is "take the service you are already delivering, break it into steps, tools, inputs, outputs and the points that need human judgment", and then write it down. The writing is the distribution. The breakdown is the starting point of the product.
Pitfalls in this section:
- Do not wait until you feel "ready" to start writing — the media bucket earns its value from accumulated time, and starting earlier is cheaper
- Do not spread effort evenly across five buckets: close the loop on one bucket first, then stack the next
7. You, right now
One sentence: Greg's five-bucket model is not five roads to money, it is one cash-flow structure — media builds distribution, services collect cash, products and investing collect upside, and case studies feed the content back into step one.
Three things to take away
- Order matters more than effort: distribution first, cash second, upside last is the core of this structure. Run it backwards and you are paying the most expensive acquisition cost to sell the least certain product
- The starting point is a service someone already pays for: "services clients are already willing to pay for" is where product ideas begin — payment first, product second
- The flywheel closes on case studies: in a model where cases never return, every new batch of clients needs a fresh batch of bought traffic — that is where distribution debt starts
💎 The real value you should leave with
Value one: a five-bucket self-check sheet. Scenario: evaluating your own revenue structure. Method: walk the services / exits / advisory / media / investing buckets one by one and see which produce cash flow and which lower cost. Reusable value: you can tell at a glance whether your income hangs off a single source.
Value two: a process breakdown. Scenario: turning a service you deliver into an AI product. Method: break it into steps, tools, inputs, outputs and the human judgment points, and let AI take only the standardizable slice. Reusable value: you do not need to learn a tool first — get the process clear and you can already tell whether the thing can become a product.
Value three: a flywheel test. Scenario: deciding whether to keep investing in content. Method: use "can cases feed the content back" to test whether the content investment is worth it. Reusable value: it turns content from extra work into a required part of the structure.
Three steps to run this week
| Step | Action | Check |
|---|---|---|
| 1 | List every service you have been paid for (salary included) | For each one you can say who paid and how much |
| 2 | Pick one and break it into steps / tools / inputs / outputs / human judgment points | When you are done you can point at the slice that can go to AI |
| 3 | Write the breakdown up as one piece of content and publish it | Within 30 days you get your first real inquiry that came from content |
One-liner: the five-bucket model does not start from "what AI capabilities do I have", it starts from "who has already paid for what" — the first is a tool, the second is a business.
📖 Further reading from the Practitioner's series
- The One-Person Editorial Department: An AI Automated Content Factory
- Practice = Technology x Scenario x Value: What Cognitive Monetization Means in the AI Era
- Why the One-Person Company Is Inevitable in the AI Era: From Mass Advertising to Precision Matching
About the author: Guanlan (观澜) — AI / Agent / digital transformation practitioner. Practical, hands-on writing — follow along and it just works.
Top comments (0)