Run the 90-day execution cadence

You are assisting a human B2B SaaS SEO and AEO operator with Module 10: Run the 90-day execution cadence.

Current lesson: Set one 90-day objective
Objective: The objective should describe a buyer-visible change, not an activity count.
Required artifact: 90-day execution board

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
- Operating backlog exported from Linear / Asana / ClickUp
- Performance inputs exported from GSC + audit + citation tools
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Choose the segment and demand area from Module 01.
2. Name the visibility and pipeline outcomes you expect to influence.
3. Add guardrails: what this cycle will not attempt.
4. Choose outcome: Set one commercial objective, one priority segment, and explicit constraints for the quarter.
5. Sequence: Schedule foundational fixes and evidence before dependent pages and promotion.

REQUIRED OUTPUT
Return a table using these exact columns: Commercial outcome | Segment | Baseline | Target | Constraint | Executive owner | Decision date.
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: “Become a credible shortlist option for agency reporting buyers,” measured across 30 prompts, 12 queries, and qualified demos.

You are assisting a human B2B SaaS SEO and AEO operator with Module 10: Run the 90-day execution cadence.

Current lesson: Sequence dependencies
Objective: Technical access and evidence often need to precede content volume.
Required artifact: 90-day execution board

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
- Performance inputs exported from GSC + audit + citation tools
- System of record exported from Docs / Sheets
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Put blocking technical fixes and measurement setup in Weeks 1-2.
2. Sequence money pages and answer passages before supporting content and source promotion.
3. Start relationship-driven source work early because response and publication times vary.
4. Baseline: Complete the demand, technical, page, prompt, source, and measurement artifacts needed for decisions.

REQUIRED OUTPUT
Return a table using these exact columns: Work item | Impact | Confidence | Effort | Dependency | Pass condition | Priority.
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: Fix indexation -> ship comparison -> publish supporting test -> pitch benchmark -> retest prompts.

You are assisting a human B2B SaaS SEO and AEO operator with Module 10: Run the 90-day execution cadence.

Current lesson: Plan against real capacity
Objective: A smaller finished plan beats an overloaded backlog.
Required artifact: 90-day execution board

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
- System of record exported from Docs / Sheets
- Weekly commitments exported from Slack / meeting cadence
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. List weekly capacity for SEO, engineering, product experts, writing, design, customer marketing, and analytics.
2. Estimate work in reviewable units and expose external dependencies.
3. Reserve 20% of capacity for discoveries, fixes, and revisions.
4. Build backlog: Convert findings into outcome-sized work with impact, confidence, effort, dependency, and pass condition.
5. Operate weekly: Review shipped work, blocked dependencies, quality failures, and next seven-day commitments.
6. Measure monthly: Read leading and lagging indicators with context and document decisions.

REQUIRED OUTPUT
Return a table using these exact columns: Week | Workstream | Owner | Capacity hrs | Dependency | Blocker | Escalation.
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: One expert article requiring product review may consume more constrained capacity than three page refreshes.

You are assisting a human B2B SaaS SEO and AEO operator with Module 10: Run the 90-day execution cadence.

Current lesson: Run the operating rhythm
Objective: Use a short cadence that keeps quality and learning visible.
Required artifact: 90-day execution board

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
- Weekly commitments exported from Slack / meeting cadence
- Operating backlog exported from Linear / Asana / ClickUp
- Definitions for any internal fields, stages, scores, and abbreviations

TASK
1. Weekly: review shipped work, blockers, next queue, and evidence needed.
2. Monthly: rerun prompts, inspect cohorts, review influential sources, and update priorities.
3. Day 90: document results, misses, lessons, and the next compounding bet.
4. Load capacity: Reserve named engineering, design, expert, legal, content, and distribution time.
5. Close quarter: Audit every artifact, preserve learnings, reprioritize the backlog, and set the next outcome.

REQUIRED OUTPUT
Return a table using these exact columns: Artifact | Expected | Actual | Evidence | Learning | Carry forward | 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: A 30-minute weekly review uses one board: Done, Evidence/QA, This week, Blocked, Next.