# Decision Memo: AI scope-of-work reviewer for agency selection Full report: https://ideanavigatorai.com/ideas/marketing-scope-of-work-reviewer/ Recorded: Not recorded ## Decision - Team verdict: Park - Validation verdict: Research (56/100) - Confidence: 45% - Recommendation: Keep this parked until the team has evidence for the next validation step: Review twenty live agency selections, track which flagged clauses caused real disputes within six months, and measure buyer willingness to pay for the next selection. ## Team rationale No team rationale recorded yet. ## Reviewers - No named reviewers recorded. ## Source anchors - Buyer: SMB or mid-market company comparing marketing agency proposals - Market: Marketing procurement tools - Problem: Companies picking an agency compare proposals they can't evaluate: vague deliverables, unbenchmarked pricing, and scope language written to permit under-delivery - and they discover the gaps quarters into the retainer. - Thesis: AI scope-of-work reviewer for agency selection should be tested as a narrow first-win workflow for one buyer: SMB or mid-market company comparing marketing agency proposals. - Source: https://www.hubspot.com/ - Source: https://en.wikipedia.org/wiki/Statement_of_work ## Validation rubric Rubric version: INAV-VALIDATION-2026-06-04 ### Demand signal - 4.7/10 (24% weight) Demand looks weak because the report has 2 source-backed signal(s), an editorial confidence of 45/100, and a defined buyer in Marketing procurement tools. - Agency-client disputes overwhelmingly trace to scope ambiguity present in the original SOW. - Target buyer: SMB or mid-market company comparing marketing agency proposals ### Problem severity - 5/10 (22% weight) Problem severity is weak when the buyer pain, customer value, and dream-outcome scores are combined. - Companies picking an agency compare proposals they can't evaluate: vague deliverables, unbenchmarked pricing, and scope language written to permit under-delivery - and they discover the gaps quarters into the retainer. - Agency-client disputes overwhelmingly trace to scope ambiguity present in the original SOW. ### Willingness to pay - 5.5/10 (20% weight) Willingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections. - Per-review pricing with a subscription for companies running ongoing agency relationships. - Review twenty live agency selections, track which flagged clauses caused real disputes within six months, and measure buyer willingness to pay for the next selection. ### Competitive saturation - 5.7/10 (18% weight) No source-backed direct match is recorded yet, so saturation risk is treated as unknown rather than proof of novelty. - Existing-product check has no named direct match. - Competitive score rewards a narrow wedge, not absence of research. ### Feasibility - 7.8/10 (16% weight) Feasibility is strong for a low build if the MVP is limited to the first measurable workflow. - Review twenty live agency selections, track which flagged clauses caused real disputes within six months, and measure buyer willingness to pay for the next selection. - Episodic usage - companies pick agencies rarely, so the durable buyer may be procurement consultants. ## Market gap Underserved segments: - SMB or mid-market company comparing marketing agency proposals who still run the workflow in spreadsheets, generic docs, email, or chat threads. - Small teams in Marketing procurement tools that feel the pain weekly but are too narrow for broad incumbents. - New adopters who need guided proof before committing to a larger platform. Feature gaps: - A narrow workflow that reaches value without configuration-heavy onboarding. - A buyer-facing proof artifact that shows time saved, risk reduced, or communication improved. - A handoff path from manual concierge service to repeatable software. Differentiation levers: - Use specificity as the wedge: one buyer, one workflow, one measurable result. - Show proof earlier than broad competitors with before-and-after examples and small pilot data. - Keep implementation lighter than incumbent suites or generic AI assistants. ## Roast and risks Interesting hypothesis, but it needs sharper demand evidence before build time. Blind spots: - Episodic usage - companies pick agencies rarely, so the durable buyer may be procurement consultants. - A broad AI assistant can flatten differentiation unless the wedge is painfully specific. - The first release can become a generic dashboard if the job is not named tightly. Hard questions: - Who wakes up already trying to solve this? - What do they stop paying for or stop doing when this works? - What proof would make a skeptical buyer trust it in one screen? - What is the smallest paid version of this idea? ## Kill criteria - Fewer than five qualified buyers agree to discuss the workflow after targeted outreach. - No buyer can name a current cost in time, money, risk, or reputation. - The first demo does not produce a clear next step, paid pilot, or specific objection. ## Offer ladder - **Lead magnet (Free)**: Ai Scope-of-work Reviewer For Agency Selection checklist Goal: Capture qualified leads and learn the buyer's exact language. Value: Helps SMB or mid-market company comparing marketing agency proposals audit the painful workflow before buying software. - **Frontend offer ($19-$99)**: Concierge review or paid template Goal: Validate urgency, workflow fit, and willingness to pay. Value: Delivers the first useful output manually before automation is trusted. - **Core offer ($49-$499/month)**: AI scope-of-work reviewer for agency selection focused SaaS Goal: Create the recurring revenue product after the narrow wedge survives tests. Value: Turns the recurring manual workflow into a repeatable product loop. - **Continuity ($99-$1,000/year add-on)**: Monitoring, benchmarks, and monthly reporting Goal: Increase retention and make the product part of a routine. Value: Keeps the buyer engaged with ongoing proof, saved time, or reduced risk. - **Backend offer (Custom)**: Done-with-you setup, agency, or team rollout Goal: Capture higher-value accounts once the productized wedge is proven. Value: Adds implementation help, integrations, and workflow migration.