Print-ready memo
Decision Memo: Backyard home reports
- Team verdict
- Park
- Validation verdict
- Rethink / 47/100
- Confidence
- 52%
- Recorded
- Not recorded
Recommendation
Keep this parked until the team has evidence for the next validation step: Pick one ADU-friendly metro (e.g. a Los Angeles or Bay Area county) and build a manual concierge MVP: a simple landing page offering an 'instant backyard home feasibility + ROI report' for a fixed price. Drive traffic via local search and ADU community groups, and fulfill the first 25 paid orders by hand-researching each parcel. Measure conversion to paid, willingness to pay, and how many buyers click through to request a builder introduction, then approach 3-5 local ADU builders to confirm they will pay for those qualified leads.
Team rationale
No team rationale recorded yet.
Reviewers
- No named reviewers recorded.
Source anchors
- Buyer: Homeowners exploring a backyard ADU (primary buyers of one-off reports) and ADU design-build firms, modular ADU companies, and renovation lenders who buy reports or pay for qualified leads
- Market: US residential proptech / ADU (accessory dwelling unit) construction and home improvement
- Problem: Before committing to a backyard home, a homeowner has no fast way to know whether their specific lot can legally support an ADU and whether the numbers work. Answering 'can I build, how big, where, what will it cost, and what rent will it return?' currently requires reading dense municipal zoning code, interpreting setback and lot-coverage rules, and getting a builder out for a site visit. This research takes days or weeks and gates the whole decision, so most curious homeowners stall and builders waste time qualifying leads that were never feasible.
- Thesis: Backyard home reports should be tested as a narrow first-win workflow for Homeowners exploring a backyard ADU (primary buyers of one-off reports) and ADU design-build firms, modular ADU companies, and renovation lenders who buy reports or pay for qualified leads.
Validation rubric
Demand signal
24% weightDemand looks weak because the report has 5 source-backed signal(s), an editorial confidence of 52/100, and a defined buyer in US residential proptech / ADU (accessory dwelling unit) construction and home improvement.
Problem severity
22% weightProblem severity is thin when the buyer pain, customer value, and dream-outcome scores are combined.
Willingness to pay
20% weightWillingness to pay is weak; the model has a monetization hypothesis, but it must still be proven through paid pilots or explicit pricing objections.
Competitive saturation
18% weightCompetitive room is reduced by 3 recorded alternative(s); the wedge must stay narrow and differentiated.
Feasibility
16% weightFeasibility is weak for a high build if the MVP is limited to the first measurable workflow.
Market gap
Underserved segments
- Homeowners exploring a backyard ADU (primary buyers of one-off reports) and ADU design-build firms, modular ADU companies, and renovation lenders who buy reports or pay for qualified leads who still run the workflow in spreadsheets, generic docs, email, or chat threads.
- Small teams in US residential proptech / ADU (accessory dwelling unit) construction and home improvement 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
- Zoning and ADU rules vary by jurisdiction and change frequently; keeping per-city rule sets accurate is costly and a wrong feasibility call carries reputational and possibly liability risk.
- 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
Backyard Home Reports checklist
FreeHelps Homeowners exploring a backyard ADU (primary buyers of one-off reports) and ADU design-build firms, modular ADU companies, and renovation lenders who buy reports or pay for qualified leads audit the painful workflow before buying software.
Concierge review or paid template
$19-$99Delivers the first useful output manually before automation is trusted.
Backyard home reports focused SaaS
$49-$499/monthTurns the recurring manual workflow into a repeatable product loop.
Monitoring, benchmarks, and monthly reporting
$99-$1,000/year add-onKeeps the buyer engaged with ongoing proof, saved time, or reduced risk.
Done-with-you setup, agency, or team rollout
CustomAdds implementation help, integrations, and workflow migration.