One calm page captures the context needed for founder/admin review.
Supporting lane for the flagship Moat 1 bundle
Before You Hire: Property Check Support
A supporting property-context intake for the Before You Hire bundle. It helps the founder organize concerns, source needs, and evidence gaps before drafting questions, without becoming an inspection, safety, legal, insurance, tax, or compliance product.
SurfaceManual intake
ProductionLive
DeliveryHuman reviewed
BillingPackets + watch
Start The Report Request
The product surface leads with the information DoorFrame needs to prepare a founder-reviewed clarity packet.
Sandbox Intake FormProperty context that makes quote questions sharper
This grouped intake saves through the sandbox service layer. The default save path is browser localStorage; Quote Check can only attempt the local disposable database path when the quote-specific server flag and disposable target assertions are set.
Founder pilot note: use this as a manual revenue-learning intake, then review source context, evidence gaps, action cards, follow-up outcome, and data-quality issues outside production behavior.
LocalStorage stays the default and fallback unless a guarded local disposable path is enabled.
The submitted shape can become source checks, missing-data notes, and action cards.
No payment, dispatch, provider recommendation, public report, or unsafe conclusion starts here.
Clarity Package At A Glance
A plain-language read of what this lane sells, what it captures, and what it never promises.
Best forProperty context that makes quote questions sharper
Capture the property concern, seasonal context, and manual source-snapshot needs that help the founder prepare a sharper Quote + Property Check packet.
Data captured
ZIP + neighborhood, property type, seasonal concern, manual source snapshot need
LocalStorage defaultmanual review
Customer-safe output
- Property concern summary and neighborhood/ZIP context.
- Manual source links and checked-at notes when available.
- Questions the customer should ask before committing to work.
- Evidence gaps such as photos, scope details, materials, dates, or access notes.
Not included
- No inspection, engineering, legal, tax, insurance, appraisal, or compliance advice.
- No claim that the property is safe, unsafe, compliant, or violation-free.
- No provider contact, dispatch, recommendation, assignment, or customer/provider commitment.
- No payment execution, production database behavior, customer-facing AI conclusion, private beta, or launch behavior.
Moat 1 Revenue Readiness Snapshot
A faster founder-facing read of the sellable clarity lane before the detailed safety boundary.
Customer valueProperty context that makes quote questions sharper
Capture the property concern, seasonal context, and manual source-snapshot needs that help the founder prepare a sharper Quote + Property Check packet.
manual founder reviewsource-labeledaction cards
Founder learns
- Use this as support for Quote + Property Check, not as a standalone inspection product.
- Track property concerns, ZIP/neighborhood context, source gaps, evidence gaps, and action-card questions.
- Keep every output source-labeled, uncertainty-aware, and human-reviewed before any customer-safe packet.
Still blocked
- No inspection, engineering, legal, tax, insurance, appraisal, or compliance advice.
- No claim that the property is safe, unsafe, compliant, or violation-free.
- No provider contact, dispatch, recommendation, assignment, or customer/provider commitment.
- No payment, dispatch, provider recommendation, legal conclusion, or production behavior.
Founder Pilot Targets
The operating scoreboard for selling clarity manually while each row becomes structured Moat 1 learning.
Support roleBehind flagship
Feeds the Quote + Property Check packet with property context, not a standalone inspection offer.
Source workManual snapshots
Parcel, permit, code, rental, weather, 311, and customer-submitted context remain source-labeled and human-reviewed.
Evidence queueGaps first
Capture missing photos, dates, access notes, materials, visible concerns, and prior-work context as questions.
Hard boundaryNo condition call
No inspection, safety, compliance, insurance, tax, legal, appraisal, or violation-free conclusion.
Founder Ops Reference
Internal posture, package-readiness, and blocked-scope details stay available without burying the customer intake.
Moat 1 No-Evidence Continuation PostureFounder-run evidence is not required right now for bounded non-production Home Readiness support polish on this existing browser-local intake surface.
Allowed right nowContinue improving property-context prompts, source-label language, evidence-gap copy, action-card framing, and localStorage fallback clarity without waiting for returned founder-run evidence.
Still gatedEvidence is still required before revenue proof, evidence/source acceptance, inspection or engineering conclusions, legal/tax/insurance advice, provider contact, dispatch, persistence, launch/private beta, marketplace behavior, or production claims.
Moat 1 Property Check Support CockpitRead-only support-lane boundary review for property context, seasonal concern capture, manual source snapshots, evidence gaps, action cards, and localStorage-only intake posture.
Support laneHome Readiness supports the flagship Quote + Property Check bundle; it is not a standalone inspection, engineering, legal, tax, insurance, appraisal, compliance, or safety product.
Property contextProperty type, ZIP, neighborhood, seasonal concern, and customer-submitted notes can sharpen quote questions without creating safe, unsafe, compliant, or violation-free conclusions.
Source postureManual source snapshot needs can be labeled for founder review, but no live public-record ingestion, browser-direct lookup, public-record scoring, or legal conclusion is authorized.
Evidence gapsPhotos, dates, access notes, material details, visible issue descriptions, and prior work notes can become evidence-gap prompts, not professional inspection findings.
Action cardsDoorFrame Action Cards can turn property concerns into questions to ask before hiring; they do not recommend providers, assign contractors, authorize dispatch, or create customer/provider commitments.
Runtime postureBrowser localStorage remains the only default save path for this route. No database contact, SQL, runtime database wiring, new UI write control, or expanded browser-local write behavior is added here.
Founder Property Check Review QueueWhat the founder can review before deciding whether a quote-support report, source snapshot, action-card packet, or later persistence sprint deserves narrower approval.
Intake CompletenessReview name, contact placeholder, ZIP, neighborhood, property type, service interest, urgency, readiness, property concern summary, seasonal concern, and source snapshot need.
Manual Source NeedsReview whether parcel, permit, code, rental, weather, 311, customer-submitted, or provider-submitted context is needed, always as manual and human-reviewed context.
Report InputsReview property concern, source labels, evidence gaps, customer questions, fulfillment minutes, report status, action cards, follow-up outcome, and repeat-interest signal.
Blocked ConclusionsKeep no inspection conclusion, no engineering advice, no legal/tax/insurance advice, no safe/unsafe claim, no compliance claim, and no customer-facing requirement explicit.
Provider BoundaryPreserve no provider contact, no recommendation, no ranking, no assignment, no customer/provider commitment, no dispatch authorization, and no marketplace behavior.
Persistence BoundaryVerify localStorage fallback, no runtime database wiring, no database contact, no SQL, no production Supabase/auth/RLS, no payments, and no Phase 13 behavior.
Static Property Check Package Readiness MapHow property-context labels can help Moat 1 sell clearer Before You Hire reports without becoming inspection execution, legal/compliance advice, live public-record ingestion, or production persistence.
Customer Package FitThe route supports manual property-context intake for Buffalo/Erie customers who need better questions before hiring, not a professional inspection or provider-matching workflow.
Data Package FitThe route can create structured property concern, source-need, evidence-gap, action-card, follow-up, and data-quality learning signals while public data remains source-labeled, uncertain, and human-reviewed.
Blocked Property Check RuntimeNo new route, route handler, server action, UI write control, expanded browser-local write behavior, payment execution, provider recommendation, provider matching, dispatch, legal/compliance/safety conclusion, production AI, live ingestion, SQL apply, production Supabase/auth/RLS, private beta, public launch, marketplace behavior, or production behavior is authorized here.
Founder Package Readiness HandoffThe simple founder review lens for deciding whether property context is ready to support the flagship clarity package, needs more source snapshots, or should stay blocked.
Sellable package signalReady means the row has a property concern, ZIP/neighborhood context, service category, evidence gaps, and customer questions that can strengthen a Before You Hire: Quote + Property Check packet.
Data moat signalCapture property concern patterns, source-snapshot needs, seasonal context, missing photos/dates/materials, action cards, follow-up outcome, and data-quality gaps for the Revenue Data OS.
Founder next actionIf property context is useful, attach it to a Quote + Property Check packet; if source-thin, add manual source labels; if evidence-thin, ask for photos or dates; if unsafe, archive with a blocked-conclusion reason.
Runtime locksThe handoff is browser-local/manual only: no inspection execution, provider contact, dispatch, payment execution, live public-record ingestion, legal/compliance/safety conclusion, customer-facing AI, database contact, SQL apply, launch, marketplace, or production behavior.