Build the SaaS money-page system

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.
4. Inventory: Export every product, feature, solution, use-case, industry, integration, comparison, pricing, and proof URL.
5. Score proof: Check every page for product evidence, quantified outcomes, customer proof, limitations, and next-step clarity.

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.

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 can stand alone in search and AI retrieval.
4. Classify: Assign each page one buyer decision, page type, funnel stage, and primary conversion.

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.

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.
4. Map demand: Merge GSC, keyword platform, paid search, CRM, and AI prompt language into canonical families.
5. Choose action: Keep, rewrite, consolidate, redirect, create, or noindex based on demand and portfolio role.
6. Sequence: Build high-pipeline gaps first, then connect supporting pages and navigation.

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.

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.
4. Detect overlap: Flag families mapped to multiple URLs and URLs mapped to incompatible decisions.

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.