Build the SaaS money-page system
Design product, use-case, integration, comparison, and alternative pages that answer buying questions and create qualified action.
Build the small set of pages that actually close deals: product, use case, comparison, pricing, trust. Each one answers a single buying decision with proof.
You will have a page map and one complete brief for the highest-value revenue page.
Blog traffic rarely compensates for missing buying pages. Money pages must satisfy a specific decision, prove the claim, answer objections, and make the next step obvious.
IF YOU SKIP IT / Without money pages, every visitor your content earns arrives with nowhere to convert, and every commercial prompt gets answered by a competitor's comparison page instead of yours.
- Money page
- A page whose job is to close: product, use case, comparison, pricing, trust. Judged on pipeline, not traffic.
- Search intent
- What the person actually wants when they type a query: to learn, to compare, to buy. The ranking pages reveal it.
- Use-case page
- A page about one job for one audience ('agency reporting'), as opposed to a generic feature tour.
- Comparison page
- Your page about 'you vs competitor'. A useful version states fit, differences, evidence, limitations, and a next step; measure its search and conversion performance after publishing.
- DPA
- Data Processing Agreement, the contract procurement asks for. Mentioning how to get it on your trust page removes a stall from every deal.
Each phase feeds the next. Don't skip ahead, the artifact at the end is only trustworthy if every phase ran.
- 01Inventory
Export every product, feature, solution, use-case, industry, integration, comparison, pricing, and proof URL.
- 02Classify
Assign each page one buyer decision, page type, funnel stage, and primary conversion.
- 03Map demand
Merge GSC, keyword platform, paid search, CRM, and AI prompt language into canonical families.
- 04Detect overlap
Flag families mapped to multiple URLs and URLs mapped to incompatible decisions.
- 05Score proof
Check every page for product evidence, quantified outcomes, customer proof, limitations, and next-step clarity.
- 06Choose action
Keep, rewrite, consolidate, redirect, create, or noindex based on demand and portfolio role.
- 07Sequence
Build high-pipeline gaps first, then connect supporting pages and navigation.
- ✓You now have
Money-page blueprint
Match intent to page type
Different decisions need different page structures.
Google already ran the experiment for you. Type your target question into it and look at what ranks: if the results are listicles, a lone product page will not crack that page, and if they are product pages, a blog post will not either. The SERP is a free intent report, and most teams never read it.
So map one page to one decision. Category demand gets a product page, jobs get use-case pages, workflows get integration pages, evaluations get comparisons. Then delete the fake variants. Two pages that differ by one synonym in the H1 are the same decision wearing different hats, and they split your authority between them.
A lone product page will not crack this result set.
A blog post will not crack this one either.
One decision, one canonical query family.
Ranks fine. Closes nothing.
Same query family, split authority. Merge with a 301 from the weaker URL to the stronger one. Merging is not deleting; a deleted page takes its links and history with it.
- 01
Assign product pages to category demand, use-case pages to jobs, integration pages to workflows, and comparison pages to evaluation.
- 02
Give each page one primary decision and one canonical query family.
- 03
Remove page ideas that differ only by swapping a keyword.
- Take the top-ten sheet from Module 01 and add a Page Type column. Assign one type per question: product, use case, integration, comparison, alternatives, pricing, trust.
- Google each question and look at what ranks. If the top results are listicles, a single product page will not rank; if they are product pages, a blog post will not either. The SERP is the intent oracle.
- List your existing URLs against the map. Anything covering the same decision twice gets marked Merge, with the stronger URL as survivor.
Every planned page names one decision and one query family, and no two pages on the map compete for the same one.
- WATCH OUT
Merging means 301 redirects from the losing URL, not deletion. Deleted pages take their links and history to the grave.
- PRO TIP
If two pages differ only by a synonym in the H1, they are one decision. Pick the phrasing your buyers used in Module 01 and merge.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
GSC, plus keyword universe from Semrush / Ahrefs / SE Ranking.
| Demand family | Decision | Page type | Primary URL | Competing URLs | Action | Owner |
|---|---|---|---|---|---|---|
| Agency reporting software | Choose category | Product | /agency-reporting/ | /features/reporting/ | Consolidate | SEO |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 03: Build the SaaS money-page system. Current lesson: Match intent to page type Objective: Different decisions need different page structures. Required artifact: Money-page blueprint BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Query/page export exported from GSC - Keyword universe exported from Semrush / Ahrefs / SE Ranking - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Assign product pages to category demand, use-case pages to jobs, integration pages to workflows, and comparison pages to evaluation. 2. Give each page one primary decision and one canonical query family. 3. Remove page ideas that differ only by swapping a keyword. REQUIRED OUTPUT Return a table using these exact columns: Demand family | Decision | Page type | Primary URL | Competing URLs | Action | Owner. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: “Reporting software for agencies” deserves a use-case page; “reporting definition” belongs in educational content.
Every page owns one buyer decision. A named human owner must verify this before the lesson is complete.
“Reporting software for agencies” deserves a use-case page; “reporting definition” belongs in educational content.
Write the decision-first outline
Lead with the answer the buyer needs, then supply proof.
Journalists write the headline fact first because most readers never reach paragraph four. Your buyer is that reader. She arrives mid-decision with three tabs open, and the first screen either answers 'is this for me' or she is gone.
Look at your current product page with that in mind. Does it open with who it is for, the job it does, and why this one instead of the alternatives? Or does it open with 'Unlock the power of insights'? Write the outline in decision order: answer, mechanism, proof, objections, next step, with every heading phrased so it could stand alone in a search result. In an AI answer, it will.
- 01
State who the product is for, the job it completes, and the differentiator in the opening screen.
- 02
Add workflow, capabilities, proof, limitations, objections, integrations, and next action in decision order.
- 03
Use descriptive headings that remain clear in search results, shared excerpts, and page scans.
- Draft in a doc before the CMS. Write the H2s first, phrased as the buyer's questions, then fill sections in decision order: answer, mechanism, proof, objections, next step.
- Write the first screen last: who it is for, the job it does, the differentiator, in three sentences. If you cannot, the positioning work from Module 01 is not finished.
- Read two competitor pages for the same decision and list the questions they leave unanswered. Those gaps are your outline's advantage.
A stranger reading only the first screen and the headings can say who the product is for and what makes it different.
- PRO TIP
Question headings can help buyers scan the page. In Module 07 you will use them as editorial QA units, without assuming a retrieval mechanism.
- WATCH OUT
Do not open with the origin story. The buyer arrived mid-decision; meet them there and put the story at the bottom for the three people who want it.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
Semrush / Ahrefs / SE Ranking, plus revenue page crawl from Screaming Frog.
| Section | Buyer question | Direct answer | Required proof | CTA | Reviewer |
|---|---|---|---|---|---|
| Opening | Is this built for agencies? | Yes, for multi-client reporting teams | Product screen + customer | See demo | PMM |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 03: Build the SaaS money-page system. Current lesson: Write the decision-first outline Objective: Lead with the answer the buyer needs, then supply proof. Required artifact: Money-page blueprint BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Keyword universe exported from Semrush / Ahrefs / SE Ranking - Revenue page crawl exported from Screaming Frog - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. State who the product is for, the job it completes, and the differentiator in the opening screen. 2. Add workflow, capabilities, proof, limitations, objections, integrations, and next action in decision order. 3. Use descriptive headings that remain clear in search results, shared excerpts, and page scans. REQUIRED OUTPUT Return a table using these exact columns: Section | Buyer question | Direct answer | Required proof | CTA | Reviewer. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: Heading: “Automate multi-client reporting without rebuilding dashboards each month,” followed by a 3-step workflow.
The outline answers fit, proof, objection, and next step. A named human owner must verify this before the lesson is complete.
Heading: “Automate multi-client reporting without rebuilding dashboards each month,” followed by a 3-step workflow.
Build proof into every claim
Claims without evidence sound interchangeable.
In a courtroom, 'my client is trustworthy' is noise; a signed receipt is evidence. Marketing pages work under the same rules now. 'Save time' appears on every vendor's site, so buyers and models both discount it to zero.
Every claim needs its receipt attached: a screenshot, a customer number with a date, a stated method. And add the sentence that feels wrong but works: who the product is not for. 'Best suited to 5-50 person agencies, not enterprise data teams' reads as honest, gets quoted as honest, and quietly filters your demo calls down to people who fit.
- 01
Pair product claims with screenshots, product behavior, customer results, or methodology.
- 02
Name the source and date for external facts.
- 03
Include fit and non-fit guidance so the page helps buyers self-qualify.
- Build a claims sheet for the page: claim, evidence type, source, date, limitation. Every sentence that asserts something goes in.
- Capture product screenshots with realistic demo data (never lorem ipsum, never a real client's numbers without written approval).
- For customer results, email the customer a one-line approval request with the exact sentence you will publish. Save the reply.
Every claim on the page has attached evidence, external facts carry a source and date, and the page names at least one non-fit.
- NO BUDGET?
No case studies yet? Publish your own numbers: your onboarding time, your uptime, your support response median, with the measurement method stated. Real beats borrowed.
- WATCH OUT
A screenshot of an empty dashboard is an anti-proof. If the product shot does not show the outcome, use a diagram of the workflow instead.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
Screaming Frog, plus business-value overlay from CRM + product analytics.
| Claim | Evidence type | Source | Freshness | Limitation | Reviewer | Status |
|---|---|---|---|---|---|---|
| Cut reporting time 60% | Customer result | Case study 12 | 2026-05 | 18-person agency | Customer success | Approved |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 03: Build the SaaS money-page system. Current lesson: Build proof into every claim Objective: Claims without evidence sound interchangeable. Required artifact: Money-page blueprint BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Revenue page crawl exported from Screaming Frog - Business-value overlay exported from CRM + product analytics - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Pair product claims with screenshots, product behavior, customer results, or methodology. 2. Name the source and date for external facts. 3. Include fit and non-fit guidance so the page helps buyers self-qualify. REQUIRED OUTPUT Return a table using these exact columns: Claim | Evidence type | Source | Freshness | Limitation | Reviewer | Status. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: Replace “save time” with a dashboard screenshot and a customer result showing reporting hours before and after.
Claims are paired with evidence. A named human owner must verify this before the lesson is complete.
Replace “save time” with a dashboard screenshot and a customer result showing reporting hours before and after.
Connect the page system
A money page should sit inside a useful decision network.
Watch a good salesperson work. They answer the question you were about to ask. A money page inside a network does the same thing: the use-case page hands you to the integration workflow, the workflow to the comparison, the comparison to the demo, each link arriving exactly when its question does.
That is the whole rule for internal links: after reading this page, what does the buyer ask next? Link to that. Never to a generic pile of related content. And the same trail you build for buyers is the trail a model walks when it assembles a recommendation.
- 01
Link guides to relevant product pages and product pages to comparisons, integrations, and proof.
- 02
Add related paths based on the next buyer question, not a generic “related content” widget.
- 03
Track visits, CTA actions, assisted opportunities, and query groups by page type.
- At the end of each major section, add one link to the page that answers the question that section just raised, with descriptive anchor text.
- Keep the links sheet from the steps updated: source URL, target URL, the buyer question the link answers.
- Verify the walk monthly in GA4: Explore > Path exploration, starting from a money page, and check that real visitors follow the chain.
You can walk from any entry page to a demo in clicks that each answer a real "next question", and analytics shows the walk happening.
- PRO TIP
The link belongs at the moment of doubt. A pricing objection paragraph should link to the comparison; a data question should link to the integration page.
- WATCH OUT
Use related widgets and navigation when they genuinely help, but add contextual links where a buyer naturally needs the next answer. Verify discovery and engagement after the change.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
CRM + product analytics, plus query/page export from GSC.
| Source URL | Target URL | Buyer next question | Anchor | Placement | Status |
|---|---|---|---|---|---|
| /reporting-kpis/ | /agency-reporting/ | Which tool automates this? | agency reporting software | After framework | Planned |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 03: Build the SaaS money-page system. Current lesson: Connect the page system Objective: A money page should sit inside a useful decision network. Required artifact: Money-page blueprint BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Business-value overlay exported from CRM + product analytics - Query/page export exported from GSC - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Link guides to relevant product pages and product pages to comparisons, integrations, and proof. 2. Add related paths based on the next buyer question, not a generic “related content” widget. 3. Track visits, CTA actions, assisted opportunities, and query groups by page type. REQUIRED OUTPUT Return a table using these exact columns: Source URL | Target URL | Buyer next question | Anchor | Placement | Status. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: Use-case page -> integration workflow -> competitor comparison -> demo, with each link answering the next objection.
Internal links follow the buying journey. A named human owner must verify this before the lesson is complete.
Use-case page -> integration workflow -> competitor comparison -> demo, with each link answering the next objection.
Answer the deal-killers
Pricing opacity and missing security answers can stall evaluation and leave third parties to describe your offer. Publish verifiable answers, then measure how assistant-referred visitors behave before choosing a route.
It is Friday afternoon and a procurement email lands: 'Is your product SOC 2 compliant, and what does it cost for 15 seats?' Two questions. If your site cannot answer both in plain text, the answer will come from somewhere else, probably a competitor's comparison table.
'Contact us' pricing does more damage than teams realize. It does not just annoy buyers; it removes you from every pricing answer in every engine, because there is nothing to quote. Publish real numbers, or at minimum a 'starts at' price. Then write the trust page: certifications, subprocessors, data residency, how to get the DPA. Procurement asks these questions whether or not you have a page; the only choice is whose answer they read.
And one routing rule: a visitor sent by ChatGPT arrives pre-qualified and mid-decision. Send them to the demo, not the newsletter.
- 01
Publish the pricing detail the business can support: tier logic, entry price or a documented custom-pricing process, and onboarding or usage costs.
- 02
Ship a trust page covering certifications (SOC 2, GDPR), subprocessors, data residency, uptime, and how to obtain the DPA.
- 03
Track assistant referrals separately, compare their stage and conversion with other channels, and route them based on observed behavior rather than assuming every visit is bottom-funnel.
- Pricing: publish tiers, entry price, what changes between tiers, and additional costs where possible. If exact numbers cannot be public, explain the pricing inputs, minimum commitment, quote process, and expected response time.
- Trust page: one HTML page (not a PDF) covering SOC 2 or equivalent status, GDPR posture, subprocessor list, data residency, uptime, and the email that returns the DPA.
- Routing: in GA4, build a segment where session source contains chatgpt.com, perplexity.ai, copilot.microsoft.com, or gemini.google.com. Watch its conversion rate, and make sure those landing pages lead to a demo path.
Your pricing page explains how price is determined, your trust page answers security and privacy questions in accessible page text, and assistant referrals have their own measured cohort and route.
- PRO TIP
Compare how competitors explain pricing, then publish the clearest accurate detail your commercial model permits. Measure buyer actions and answer accuracy after the change.
- WATCH OUT
Do not hide essential trust answers only in a PDF. Accessible HTML is easier for buyers to navigate and for Google to render and index; keep downloadable documents as supporting evidence.
- NO BUDGET?
No SOC 2 yet? Say what you do have: encryption at rest, access controls, backup policy, and the audit you are working toward, with dates. Honesty about the roadmap beats silence.
OPTIONAL / AI CO-PILOTRun this lesson with AI, the prompt, sources and expected output+
Choose the business priority, interpret exceptions, protect confidential data, challenge weak evidence, and approve the final decision.
Clean, classify, compare, calculate, and draft rows from supplied evidence. AI may surface patterns; it does not own strategy.
GSC, plus keyword universe from Semrush / Ahrefs / SE Ranking.
| Buyer question | Owning page | Answer present | Quotable passage | AI-referred CTA | Owner | Status |
|---|---|---|---|---|---|---|
| Is it SOC 2 compliant? | /trust/ | Yes | Yes, certifications section | Demo path | Security + PMM | Live |
CLAUDE / CHATGPT PROMPTAnalyze the evidence without outsourcing the decision+
Remove personal or confidential data. Attach the named exports, explain every column, and tell the model when the dataset was collected.
You are assisting a human B2B SaaS SEO and AEO operator with Module 03: Build the SaaS money-page system. Current lesson: Answer the deal-killers Objective: Pricing opacity and missing security answers can stall evaluation and leave third parties to describe your offer. Publish verifiable answers, then measure how assistant-referred visitors behave before choosing a route. Required artifact: Money-page blueprint BUSINESS CONTEXT I WILL PROVIDE - Product, category, target market, pricing model, sales motion, and geography - The priority customer segment and the commercial outcome for this 90-day cycle - Query/page export exported from GSC - Keyword universe exported from Semrush / Ahrefs / SE Ranking - Definitions for any internal fields, stages, scores, and abbreviations TASK 1. Publish the pricing detail the business can support: tier logic, entry price or a documented custom-pricing process, and onboarding or usage costs. 2. Ship a trust page covering certifications (SOC 2, GDPR), subprocessors, data residency, uptime, and how to obtain the DPA. 3. Track assistant referrals separately, compare their stage and conversion with other channels, and route them based on observed behavior rather than assuming every visit is bottom-funnel. REQUIRED OUTPUT Return a table using these exact columns: Buyer question | Owning page | Answer present | Quotable passage | AI-referred CTA | Owner | Status. For every recommendation, cite the source row, URL, call note, or data point that supports it. Add a confidence column in your analysis: High, Medium, or Low. List missing evidence separately instead of guessing. Finish with a section named HUMAN DECISIONS REQUIRED. RULES - Do not invent search volume, revenue, customer statements, product capabilities, or competitor facts. - Do not treat correlation as causation. - Preserve contradictory evidence and explain why it conflicts. - Do not make the final priority or publishing decision. Prepare the evidence for a human owner. - Use this example only as a format reference, not as evidence: A buyer asks “Is [product] SOC 2 compliant and what does it cost for 15 seats?” Your site should provide an accurate answer or a precise path to obtain it.
Internal links follow the buying journey. A named human owner must verify this before the lesson is complete.
A buyer asks “Is [product] SOC 2 compliant and what does it cost for 15 seats?” Your site should provide an accurate answer or a precise path to obtain it.
Below is a worked money-page system for the demo company: the page map, one full decision-first outline, and the internal-link plan connecting them. Treat it as a reference answer. Build your own map first, then compare against this one to see what you missed.
Money page portfolio planner
Map commercial demand to product, use-case, solution, integration, comparison, and pricing pages without cannibalization.
Portfolio coverage by page type
A healthy SaaS portfolio covers distinct buying decisions, not keyword permutations.
Turn demand data into a strategy.
Traffic is an input. The decision is where evidence, commercial intent, product fit, proof, and team capacity justify action. Changes save automatically on this device.
Start with modifiers, then inspect the live SERP, ranking page types, sales calls, and the next question. A human assigns the final intent.
CRM opportunities and closed revenue outrank modeled value. Use modeled pipeline only where attribution is missing, and label it as directional.
Rank every demand family, then limit the active list to actual quarterly capacity. Everything else is validated, supported, or parked.
Modifiers suggest intent. The ranking page types and buyer evidence confirm it.
| Intent | Query clues | SERP proof | Buyer decision | Likely asset |
|---|---|---|---|---|
| Diagnose | why, problem, meaning | Guides and definitions | Understand the problem | Expert guide |
| Solution | how to, automate, improve | Processes and use cases | Choose an approach | Use-case page |
| Category | software, platform, tools | Product and category pages | Choose a solution type | Product / category |
| Compare | best, top, vs, alternatives | Lists and comparisons | Build a shortlist | Comparison / best-of |
| Vendor | brand, reviews, demo | Vendor and review pages | Evaluate a named vendor | Vendor / proof |
| Pricing | price, cost, plans, ROI | Pricing and calculators | Validate commercial fit | Pricing / ROI |
| Validate | integration, security, migration | Docs, proof, implementation | Remove purchase risk | Integration / proof |
Use the strongest evidence available and keep weaker estimates visibly separate.
| Method | Evidence | How to use it | Confidence |
|---|---|---|---|
| Sourced revenue | Landing page or content is the recorded acquisition source | Use directly | Highest |
| Influenced revenue | Asset was touched before opportunity or close | Report separately with window | High |
| Opportunity evidence | Demand family appears in calls, forms, notes, or campaigns | Opps x win rate x ACV | Medium-high |
| Paid-search evidence | CPC, conversion, and opportunity quality exist | Use as commercial validation | Medium |
| Modeled potential | No direct CRM history exists | Volume x CTR x conversion x ACV | Directional |
Use your own GSC, analytics, and CRM rates. These assumptions affect modeled potential, not observed revenue.
| Now | Demand family | Intent | SV | CRM revenue | Opps | Win % | ACV | Fit | Evidence | Gap | Sales | Effort | Page state | Opp expected revenue | Modeled pipeline | Score | Next action |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| YES | $39,440 | $13,260 | 90.5 | Refresh + prove | |||||||||||||
| YES | $45,360 | $102,600 | 89.0 | Refresh + prove | |||||||||||||
| YES | $43,560 | $31,680 | 88.0 | Refresh + prove | |||||||||||||
| YES | $61,380 | $38,880 | 87.0 | Build revenue page | |||||||||||||
| YES | $43,320 | $17,670 | 85.0 | Refresh + prove | |||||||||||||
| LATER | $49,980 | $24,570 | 84.5 | Build revenue page | |||||||||||||
| LATER | $20,800 | $18,720 | 74.0 | Fix blocker first | |||||||||||||
| LATER | $17,600 | $60,000 | 69.5 | Consolidate URLs | |||||||||||||
| LATER | $4,320 | $86,400 | 44.0 | Park | |||||||||||||
| LATER | $0 | $104,400 | 31.5 | Park |
80-100: build or refresh now. 65-79: validate and queue. 50-64: supporting backlog. Below 50: park. Overlap and technical blockers override the score.
Best: sourced or influenced CRM revenue. Next: opportunity and win evidence. Last: modeled pipeline using explicit assumptions. Never present modeled value as revenue.
Check each item only after the artifact meets the standard. Progress saves on this device; use the academy-home backup to move it elsewhere.