Visible project route
Coordinate the entire remodel
Bring layout, systems, finishes, and sequencing into one scope before work starts.
Plan · build · hand over
A conversion-first template for contractors who need to explain scope, decisions, and next steps before asking a homeowner to commit.
Local template only · No quote or appointment is created
Conceptual interface · No project result shown
Start with the decision
Each route changes the visible project map and prepares a non-binding brief. It does not estimate cost or claim site conditions.
Visible project route
Bring layout, systems, finishes, and sequencing into one scope before work starts.
The operating layer
These are documentation outputs a contractor may provide. This preview does not claim that a specific company already provides them.
A visible boundary between included work, assumptions, options, and exclusions.
A sequence for selections and approvals before they become field delays.
A documented path for pricing and approving discoveries before execution.
A closeout view for documentation, walkthroughs, and open items.
A reusable delivery story
Understand goals, constraints, existing information, and unknowns.
Checkpoint · fit and next evidenceTranslate priorities into scope, dependencies, options, and decisions.
Checkpoint · scope alignmentConfirm documentation, selections, access, sequence, and responsibilities.
Checkpoint · readinessTrack progress, changes, quality checks, and handover without hiding open items.
Checkpoint · documented completionLocal project brief
Choose three non-personal project signals. The result stays in this browser and can be handed to an approved chatbot or scheduling adapter later.
Prepared in this browser
This is a local summary, not a quote, lead submission, availability check, or appointment.
Questions the template should answer
No. It organizes the project context and makes assumptions visible. Any real estimate requires the contractor’s approved process and project evidence.
No. The integration slot is intentionally unconnected. A calendar can only be added through an approved adapter with real availability and confirmation states.
Yes. Brand tokens, copy, modules, interaction emphasis, and assets are configuration. The underlying accessibility and integration contracts remain stable.
Yes, after their source and permission are recorded. The base template uses no third-party project imagery or implied portfolio results.
Integration host · v1
Template mode. No chatbot, calendar, lead capture, or booking service is connected.
An approved Chat Bots adapter can mount here later. This host never claims that a lead was sent or an appointment was confirmed.