One calm page captures the context needed for founder/admin review.
Compatibility packet intake
Before You Hire: Quote + Property Check
A Buffalo/Erie compatibility intake for quote context and public-source module selection. It helps DoorFrame turn scattered customer context into a structured data packet request while keeping subscriptions, source runs, and customer display in their guarded product loops.
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 FormQuote and property context for a data packet
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 forQuote and property context for a data packet
Capture the quote, property context, missing scope details, requested source modules, and source-labeled notes needed for a founder-reviewed data packet. The first job is to make the customer request structured enough for source review and cautious insight drafting.
Data captured
ZIP + neighborhood, property type, phase 10 report package requested, customer segment, property relationship
LocalStorage defaultmanual review
Customer-safe output
- Quote amount and work category as customer-submitted context.
- Property address, ZIP, neighborhood, and customer-submitted context.
- Requested Buffalo/Erie source modules for later reviewed source work.
- Missing scope, material, warranty, timeline, and evidence questions.
Not included
- No price promise or statement that a quote is fair, safe, or guaranteed.
- No legal, compliance, insurance, appraisal, tax, or safety conclusion.
- No contractor recommendation, ranking, referral, provider assignment, or dispatch.
- No checkout from this route, deposit, escrow, payout, notification, production database behavior, raw API customer display, or customer-facing AI conclusion.
Moat 1 Revenue Readiness Snapshot
A faster founder-facing read of the sellable clarity lane before the detailed safety boundary.
Customer valueQuote and property context for a data packet
Capture the quote, property context, missing scope details, requested source modules, and source-labeled notes needed for a founder-reviewed data packet. The first job is to make the customer request structured enough for source review and cautious insight drafting.
manual founder reviewsource-labeledaction cards
Founder learns
- Bundle quote context with property-source context so the request maps cleanly into a packet.
- Capture requested modules, source context, missing data, action cards, and follow-up questions.
- Turn every request into better source coverage and data-quality learning without promising contractor quality, fair price, or legal safety.
Still blocked
- No price promise or statement that a quote is fair, safe, or guaranteed.
- No legal, compliance, insurance, appraisal, tax, or safety conclusion.
- No contractor recommendation, ranking, referral, provider assignment, or dispatch.
- 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.
First packet target25 rows
Structured Quote Check or Property Data Packet requests with address, consent, and at least one requested source module.
Subscription path/property-watch
Stripe subscription checkout belongs to the Property Watch plan flow, not this compatibility intake.
Fulfillment target20-45 min
Founder time per reviewed packet draft, including source labels, action cards, and follow-up notes.
Learning loopEvery row
Capture requested modules, source gaps, follow-up outcome, repeat interest, and data-quality blockers.
Founder Ops Reference
Internal posture, package-readiness, and blocked-scope details stay available without burying the customer intake.
Data Packet Intake Continuation PostureFounder-run evidence is not required right now for bounded non-production Quote Check and Property Data Packet intake polish.
Allowed right nowContinue improving founder/admin review copy, localStorage fallback clarity, source-module prompts, action-card language, and packet-readiness language.
Still gatedEvidence is still required before source acceptance, hosted persistence beyond the existing guarded local/disposable path, customer-ready AI summaries, automated source runs, production claims, or treating this route as a checkout surface.
Quote Check Packet CockpitRead-only compatibility intake review for quote capture, property context, requested source modules, source snapshots, action cards, and guarded runtime persistence posture.
Compatibility intakeBefore You Hire: Quote + Property Check remains useful as a structured request format, while Property Watch is the main subscription product.
Price contextQuote amount and service category can be captured for founder review, but no price promise, fair-price conclusion, or pricing guarantee is made.
Property contextAddress, ZIP, neighborhood, and customer-submitted context can support manual review without becoming inspection, engineering, appraisal, insurance, tax, legal, compliance, or safety advice.
Source snapshotsRequested source modules, manual source labels, checked-at notes, confidence, uncertainty, and human review status can support the packet; no raw API customer display or legal conclusion is authorized.
Action cardsDoorFrame Action Cards can structure next questions before hiring; they do not recommend contractors, rank providers, authorize dispatch, or create customer/provider commitments.
Runtime postureBrowser localStorage remains default and fallback. The existing scoped runtime action can only attempt local/disposable intake_submissions writes when explicit server guardrails are enabled.
Founder Quote Check Review QueueWhat the founder can inspect before deciding whether later source snapshot, action-card, packet summary, or local/disposable persistence work deserves a narrower sprint.
Intake CompletenessReview name, contact placeholder, ZIP, neighborhood, property type, service interest, urgency, readiness, summary, notes, quote amount placeholder, and question-to-ask fields.
Packet InputsReview quote amount, work category, missing scope, materials, warranty, timeline, requested modules, source links, evidence gaps, and follow-up outcome as founder ops metadata.
Learning InputsReview product requested, subscription-path fit, acquisition source, fulfillment minutes, report status, repeat interest, requested sources, and data-quality gaps outside this intake route.
Blocked Customer ClaimsKeep no price promise, no contractor recommendation, no legal/compliance/safety conclusion, no checkout from this route, no provider contact, no dispatch, and no production database behavior explicit.
Persistence BoundaryVerify localStorage default, raw form-answer value redaction, intake_submissions-only target when explicitly enabled, companion writes deferred, and database mode default unchanged.
Ad Readiness SignalUse this route to rehearse founder-operated local pilot traffic only after blocked-scope language remains visible and manual fulfillment workflow is understood.
Static Quote Check Package Readiness MapHow Quote + Property Check labels can support the data-packet product without becoming live marketplace behavior, checkout, raw public-record display, AI conclusions, or production persistence.
Customer Package FitThe route supports structured packet intake for Buffalo/Erie customers who want questions to ask before hiring, not live contractor referral or job execution.
Data Package FitThe route can create structured source-context, action-card, follow-up, and data-quality learning signals while public data remains source-labeled, uncertain, and human-reviewed.
Blocked Quote Check RuntimeNo expanded browser-local write behavior, checkout from this route, contractor recommendation, provider matching, dispatch, legal conclusion, customer-ready 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 this row is ready to become a manual clarity package, a source-snapshot task, an action-card task, or a data-quality follow-up.
Sellable package signalReady means the request has a work category, quote amount context, property context, customer question, source-module needs, and a clear packet path for the Before You Hire: Quote + Property Check package.
Data moat signalCapture source labels, requested modules, confidence/uncertainty, action cards, follow-up outcome, repeat interest, and data-quality gaps for the Property Watch data strategy.
Founder next actionIf packet-ready, draft the reviewed packet; if source-thin, add source snapshots; if scope-thin, ask follow-up questions; if unsafe, archive the row with a blocked-scope reason.
Runtime locksThe handoff is browser-local/manual by default: no checkout from this route, provider recommendation, provider matching, dispatch, live ingestion, legal conclusion, customer-facing AI, database contact by default, SQL apply, production launch, marketplace, or production behavior.