# Execution Scorecard: Backyard home reports Score: 40/100 Tier: Research first Backyard home reports scores 40/100 for execution readiness. The recommended next step is 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. ## Bottlenecks - 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. - Established competitors (ADU Pilot, Site Plan Creator, ADUscale, Haven) already cover homeowner and builder segments, so differentiation and customer acquisition will be hard. - Build-cost and rental-income projections depend on local data that is noisy; inaccurate ROI estimates erode trust and can mislead homeowners' financial decisions. - Homeowner reports are a one-time low-value purchase, so unit economics likely depend on the harder-to-win builder/lender lead-gen channel. - 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. - Needs real buyer access, not only desk research. ## Accelerators - Can talk to the buyer before writing much code. - Can ship a narrow first-win demo quickly. - Can use local-first research artifacts to keep validation moving without a large team. - 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. - Concierge review or paid template ## Dated Launch Plan - **2026-07-16 / Frame the wedge**: Write the one-sentence promise and test it in the strongest channel. Proof: 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. - **2026-07-19 / Interview 10 people who match the buyer persona.**: Create the lead magnet and use it to recruit interviews. Proof: Problem resonance: 5+ calls or 10+ detailed replies. - **2026-07-23 / Ship a clickable demo or concierge workflow that produces the first useful artifact.**: Build the smallest demo that proves the first win. Proof: Activation: 25% of demo visitors complete the first-win path. - **2026-07-30 / Run one paid pilot or collect explicit pricing objections before automating the rest.**: Delete any report section that feels generic before building. Proof: Commercial pull: 3 paid pilots, LOIs, or concrete procurement next steps. - **2026-08-06 / Promote to a deeper build plan only after the wedge survives validation.**: Run the lead magnet and first-win demo tests. Proof: Fewer than five qualified buyers agree to discuss the workflow after targeted outreach. - **2026-08-15 / Execution checkpoint 6**: Promote to deeper implementation only once the wedge survives interviews or paid-pilot outreach. Proof: Promote to a deeper build plan only after the wedge survives validation. ## Builder Prompt Create a dated execution plan for "Backyard home reports". Keep the first milestone tied to 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.. Use these bottlenecks: 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.; Established competitors (ADU Pilot, Site Plan Creator, ADUscale, Haven) already cover homeowner and builder segments, so differentiation and customer acquisition will be hard.; Build-cost and rental-income projections depend on local data that is noisy; inaccurate ROI estimates erode trust and can mislead homeowners' financial decisions.; Homeowner reports are a one-time low-value purchase, so unit economics likely depend on the harder-to-win builder/lender lead-gen channel.; 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.; Needs real buyer access, not only desk research.. Use these accelerators: Can talk to the buyer before writing much code.; Can ship a narrow first-win demo quickly.; Can use local-first research artifacts to keep validation moving without a large team.; 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.; Concierge review or paid template. Link the output to the Idea Builder prompt and do not expand beyond the first validated workflow.