PIE research white paper

A research system,
not an idea prompt.

PIE combines open-web research, explicit evidence classifications, repeatable scoring, and programmed decision gates. Language models help investigate and synthesize. They do not receive permission to quietly turn an unsupported guess into a recommended SaaS business.

12PIE opportunity lenses adapted for SaaS research
9commercial decision gates weak ideas cannot bypass
3final opportunities shown after comparison
01

Origin

The Camden Model is the foundation.

The Camden Model was originally developed for a different commercial question: when a company produces a public signal, does that signal represent a current, credible, still-winnable services opportunity for a particular provider? A leadership appointment, funding announcement, technology program, or high score was never enough by itself.

The method forced the research to reconstruct the actual project, identify its workstreams and owners, test whether relevant work remained available, verify client fit, locate the buyer, examine timing, and preserve contradictory evidence. It separated opportunity strength from evidence confidence and allowed a hard gate to overrule an attractive score.

PIE adapts that discipline from lead qualification to product-opportunity research. Instead of asking whether a services firm should pursue a company, PIE asks whether a founder should test a particular SaaS business. The subject changed. The underlying principle did not: interesting activity is not the same thing as a commercial opportunity.

02

Division of labor

What is programmed and what is model-assisted?

Programmed controls

The rules that do not negotiate

  • Required input fields and output structure
  • Exactly three final opportunities
  • Opened-source verification
  • Minimum source diversity and evidence coverage
  • Competitor-domain verification
  • Consistent 0–100 score normalization
  • Fixed report and Blueprint sections
  • Minimum document depth and placeholder rejection
  • Idempotent run handling and failure refunds
  • Private account and report ownership
Model-assisted work

The work that requires interpretation

  • Exploring plausible problem spaces
  • Reading and synthesizing public sources
  • Recognizing repeated pain across different language
  • Comparing positioning and competitive openings
  • Explaining why a concept may work
  • Forming testable product and pricing hypotheses
  • Drafting the market report and go-to-market plan
  • Translating the decision into a detailed Build Blueprint
03

Evidence discipline

Every material claim has a status.

Confirmed fact

A claim directly supported by an opened source, such as a published price, documented feature, job requirement, or observed workflow record.

Evidence-backed inference

A conservative conclusion formed from several facts. The underlying facts are visible, and the interpretation remains labeled.

Hypothesis

A plausible commercial belief that must be tested, such as willingness to pay, a proposed price, or the best initial distribution channel.

Unknown

An unresolved fact. PIE does not quietly convert an unavailable budget, buyer, data source, or competitive weakness into a positive result.

Source quality is judged by origin, independence, and relevance—not raw link count. Five articles repeating one announcement remain one evidence origin. A competitor page is authoritative for its own pricing and features, but not for claims about customer satisfaction. A discussion can reveal pain, but it does not prove market size.

Contradictory evidence is part of the answer. Strong incumbents, adequate native features, low problem frequency, difficult permissions, weak distribution, or an oversized first build can all reduce the recommendation even when the idea initially sounds attractive.

04

Research coverage

Twelve PIE opportunity lenses prevent tunnel vision.

The Camden Model contributes the discipline: examine the whole commercial case instead of allowing one exciting fact to dominate the decision. PIE replaces the original company-signal categories with 12 SaaS-specific lenses covering customer pain, demand, spending, competition, reach, founder strengths, feasibility, and risk. Each lens must be researched, marked not applicable, or left visibly unknown.

01

Repeated customer pain

Do independent sources describe the same frustrating, recurring job instead of one isolated complaint?

02

Frequency and urgency

How often does the problem occur, and what forces the customer to deal with it now?

03

Cost of the problem

What time, money, risk, lost revenue, or customer harm does the current workflow create?

04

Existing workarounds

What combination of spreadsheets, services, manual steps, or disconnected tools do customers use today?

05

Observable demand

Do searches, communities, reviews, buying activity, or repeated requests show interest beyond polite enthusiasm?

06

Existing customer spending

Are buyers already paying for alternatives, labor, services, or adjacent tools that address the job?

07

Competitor strengths and complaints

What do established alternatives do well, and where do customers still report friction or unmet needs?

08

Underserved customer or workflow

Is there a specific buyer, segment, or step that broad products handle poorly enough to create an opening?

09

Buyer reachability

Can the founder identify and reach people who experience, influence, and purchase a solution?

10

Founder strengths

Does the founder have useful experience, credibility, judgment, relationships, or distribution in this market?

11

Proof-product feasibility

Can one small end-to-end workflow prove value without hiding the hardest technical or operational risk?

12

Timing and market risk

Do platform dependence, regulation, data access, changing behavior, or market timing strengthen or threaten the opportunity?

05

Decision gates

A score cannot rescue a broken opportunity.

The Camden Model uses commercial gates before disposition. PIE adapts the same logic: a concept can look exciting and still fail because the customer is vague, the pain is weak, software is the wrong answer, the market opening is not meaningful, or the first proof product is unrealistic.

01

Specific customer

Is there a clearly defined customer rather than a broad industry or vague audience?

02

Verified painful problem

Is there credible evidence of a recurring, consequential workflow—not merely an interesting trend?

03

Software is appropriate

Can software materially improve the job, or is the problem better solved by policy, staffing, services, or no action?

04

Meaningful market opening

Is an important part of the job still poorly served despite the strengths of current alternatives?

05

Founder strengths

Does the founder understand the workflow, buyer language, or distribution path well enough to gain practical leverage?

06

Identifiable buyer

Can the likely user, champion, purchaser, and decision owner be identified and reached?

07

Reason to act now

Is there a trigger, urgency, or market condition that makes this worth testing now rather than someday?

08

Credible commercial value

Can a narrow first product create enough measurable value to support a believable price?

09

Feasible and acceptable risk

Can the proof product be built and operated within the founder's constraints without an unacceptable dependency, compliance, data, or support risk?

06

PIE scoring

Six dimensions are normalized consistently.

Pain

Frequency, consequence, urgency, and the burden of the current workflow.

Demand

Observable spending, workarounds, category activity, and buyer behavior.

Founder strengths

Workflow understanding, credibility, judgment, and relevant access.

Reachability

A believable path to interviews, pilots, and the first customers.

Market opening

A meaningful reason a focused product can earn consideration despite alternatives.

Feasibility

Whether one small end-to-end workflow can test the business without hiding the hard part.

The score is recalculated from the component scores rather than trusting a prewritten total. The result is a comparison tool, not a forecast of success. PIE returns the three strongest useful opportunities even when one contains an explicitly disclosed weakness. It does not display a graveyard of rejected ideas because the customer is paying for a decision, not the internal sorting process.

07

Output contract

The answer must be usable.

1

Founder Strengths

Experience, roles, recurring problems, tools, access, constraints, budget, and timeline focus the search.

2

Market research

Public sources are opened, pain is clustered, alternatives and pricing are checked, and unsupported claims remain labeled.

3

Three opportunities

The strongest concepts are presented with customer, pain, why they may work, market opening, evidence, score, risk, and first test.

4

Report and Blueprint

The selected concept receives a complete human decision report and a detailed Markdown build handoff.

PIE does not promise that a business will succeed. It reduces a more common and expensive failure: committing time and money to an idea before the buyer, pain, demand, opening, and smallest credible test have been examined together.