Is this demand B2B or B2C? Reading the buyer out of creator content
The same workflow problem supports two completely different companies. The topic will not tell you which one to build — the asides about money will.
The short answer: ignore the topic and count the money asides. Mentions of expensing, approval, procurement or a company card mean business demand; personal price sensitivity and substituting effort for money mean consumer demand. When the same person both feels the pain and pays, you have prosumer demand, which is a third case with its own economics rather than a blend of the other two.
A surprising number of products are built for the wrong buyer with perfectly good evidence of demand. The research established that people have the problem and want it solved, which is true, and never established who writes the cheque. Those are different questions, and only the second one determines pricing, support model, sales motion and whether the product needs permissions at all.
The topic almost never decides it
Invoicing, scheduling, note-taking, file conversion, analytics — each of these supports a consumer product and a business product, and the two look nothing alike. One is self-serve at a low price with no human contact; the other has seats, an admin role, an export requirement and a security questionnaire.
Choosing by subject matter therefore produces a coin flip dressed as a decision. What separates the two markets is structural: who experiences the cost of the problem, who controls the budget, and whether anyone else needs to see the output.
Money asides are the reliable tell
People do not announce their buyer type, but they leak it constantly in asides. These fragments are valuable precisely because they are unguarded — nobody performs a procurement complaint.
| What the source says in passing | Reads as | What it implies |
|---|---|---|
| “I had to get it approved” / security review | B2B | Sales cycle, compliance surface, seat pricing |
| “We expense it” / company card | B2B or prosumer | Price insensitivity below an expense threshold |
| “I share it with the team” | B2B | Permissions and collaboration are core, not later |
| “Too expensive for what I get” | B2C or prosumer | Price anchoring against free alternatives |
| Builds a manual workaround to avoid paying | B2C | Time substitutes for money; low willingness to pay |
The last row is the sharpest consumer signal there is. A business user whose time is billed does not spend two hours building a spreadsheet to avoid a twenty-dollar subscription; a consumer routinely does, and enjoys it. Where that boundary sits is also the core of pricing, which is worked through in pricing a SaaS using creator content.
Enthusiasm is evenly distributed across both markets and predicts nothing about who pays. A single unprompted reference to approval, invoicing or a vendor review is far more informative, because it can only come from someone buying inside an organisation.
Prosumer is a third case, not a midpoint
The pattern where one person feels the pain, chooses the tool and pays for it — often expensing it afterwards — is common among freelancers, consultants and small teams. It behaves like consumer demand at acquisition, since there is no sales cycle, and like business demand at expectation, since the tool is load-bearing for their income.
Treating it as consumer produces a product too flimsy for work; treating it as business produces a sales motion nobody will sit through for a forty-dollar tool. The correct shape is self-serve signup with business-grade reliability and support, and recognising the case early avoids rebuilding for it later. The segment boundaries here are the same ones separated out in defining an ICP from video research.
- ✗Buyer inferred from the subject matter
- ✗Enthusiasm counted as purchase intent
- ✗Prosumer treated as small B2B
- ✗Permissions deferred as a later feature
- ✓Approval, expensing and procurement mentions counted
- ✓Manual-workaround behaviour logged as price evidence
- ✓Prosumer handled as its own case
- ✓Sharing requirements read before architecture is fixed
What each answer actually changes
The decision is worth getting right because it propagates into almost every subsequent choice. Business demand implies seats, an admin concept, audit and export requirements, a security posture, and a support expectation measured in hours. Consumer demand implies a low price point, zero onboarding friction, and support that must scale without headcount.
Most consequentially, it changes what the first version must contain. A business product without sharing is unusable by its buyer; a consumer product with a permissions model is slower to use and harder to explain. Getting this wrong is one of the more expensive scoping errors, which is why it belongs before the cut described in testing whether your idea is a feature or a product.
Moving upmarket later is sometimes a rewrite
“Start consumer, sell to teams later” works when the product already stores something a team would want to share — documents, records, history. It does not work when the product is strictly single-player, because adding collaboration then means rebuilding the data model around ownership and permissions.
The cheap version of this decision is to check, at design time, whether the core object has a plausible owner other than the individual. If it does, the upmarket path stays open at little cost. If it does not, the later move is a rewrite and should be planned as one — the same build-or-rebuild calculus as in deciding build versus buy versus integrate from research.
The two markets size completely differently
A consumer market is sized by population and conversion; a business market is sized by number of accounts and price per seat, and the same underlying problem can produce wildly different totals depending on which you assume. Deciding the buyer before sizing avoids the common failure of quoting a consumer-scale audience against business-scale pricing.
The signals that let you bound either number from public content — without a market-research report — are set out in the market-size sanity check from creator signals.
Two failure patterns worth naming
The first is building a business product on consumer evidence. The corpus is full of enthusiastic individuals, the problem is obviously real, and the product ships with no admin role, no audit trail and no export. It then meets its first real buyer, who asks about access control in the second meeting, and the answer is a quarter of engineering work nobody planned.
The second is the reverse and is quieter: building a consumer product on business evidence. Research done among people whose employers pay for tools produces price expectations that no self-funding individual shares, and the product launches at four times what the actual market will bear. Nothing looks broken — conversion is simply low forever, and it gets misdiagnosed as a positioning problem.
Both are avoidable by counting who was speaking rather than what they said. If most of your evidence came from people describing work they were paid to do, you have business evidence, whatever the topic looked like, and the pricing conclusions do not transfer to anyone buying for themselves.
What the read costs
This is a synthesis question rather than a sourcing question — the asides are already in whatever corpus you gathered for validation. As of September 2026 Hobby is $19 a month with 25 videos and 2 projects, Pro is $59 with 80 videos and 8 projects, and Studio is $199 with 250 videos, 20 projects and 3 seats. Every plan includes the same pipeline and a 7-day free trial — see the pricing page.
Run a synthesis across your corpus and get the buyer signals — approval, expensing, sharing, price anchoring — pulled out with sources. 7-day free trial.
Closing thought
Demand evidence tells you a problem is real. It says nothing about whose budget solves it, and that second question determines almost everything you will build.
Frequently asked
Can public content really tell you whether demand is B2B or B2C?
Yes, more clearly than most founders expect. People reveal who pays in passing — expensing something, asking a manager, mentioning a company card, worrying about a personal subscription. Those asides are unguarded and they separate the two markets far better than the topic does.
What if the same person is both the user and the buyer?
Then you are looking at prosumer demand, which behaves like consumer in acquisition and like business in expectations. It is a real third case, and treating it as either pure B2B or pure B2C produces the wrong pricing and the wrong support model.
Does the subject matter decide it?
Almost never. The same workflow problem supports a consumer product and a business product with different pricing, onboarding and support. What decides it is who feels the cost of the problem and who controls the money, which are frequently different people.
What is the strongest B2B signal in creator content?
Someone describing a process for getting approval — a budget conversation, a security review, a procurement step. Nobody mentions procurement about a tool they buy for themselves, so a single unprompted mention of it is close to decisive.
What is the strongest B2C signal?
Price sensitivity expressed in personal terms, and comparison against free alternatives with effort rather than money as the cost. Consumers substitute their own time for money in a way business buyers almost never do.
Can I start B2C and move to B2B later?
Frequently, but only if the product stores something a team would want shared. Moving upmarket from a strictly single-player product means rebuilding around permissions, and that is a rewrite rather than a feature.
What does this read cost to run?
As of September 2026, Hobby is $19 a month for 25 videos and 2 projects, Pro is $59 for 80 videos and 8 projects, and Studio is $199 for 250 videos, 20 projects and 3 seats, with a 7-day free trial on every plan. A buyer read runs over a corpus you already gathered, so it is usually a synthesis pass rather than new research.