Current path is mapped
Using your public form, written description, and approved field list.
Mapping + tested local prototype. No production integration.
Test a clearer HVAC intake path before changing your live systems.
A fixed-price discovery sprint for independent HVAC companies. We map one current enquiry path, configure a local browser prototype, and run five synthetic cases through explicit rules. No customer records, credentials, external messages, or production accounts are used.
- Synthetic data only
- No autonomous sending
- One bounded prototype
The workflow
From a synthetic enquiry to a dispatcher-view queue in four controlled steps.
Local form is configured
Required fields and client-approved wording are represented in a browser prototype.
Rules route test cases
Five invented enquiries exercise normal, hazard-word, and incomplete-input behavior.
You review the result
The local queue, test report, rules, and source files are handed over for a fit decision.
Important: this sprint does not connect to a live inbox, form, CRM, spreadsheet, dispatcher, phone, text, or email system. Production integration, if technically suitable, requires a separate scope after prototype acceptance.
Not an emergency or life-safety system: the prototype cannot receive or act on live requests and is not a diagnostic tool or substitute for calling emergency services, a utility, or the HVAC company's direct dispatch channel.
Who this is for
A practical fit check before either side wastes time.
This sprint is a low-access way to decide whether one HVAC enquiry path deserves a later production integration.
Good fit- Your company publicly offers emergency, same-day, or rapid-response HVAC service.
- You can describe the current input, desired dispatcher view, and exact rules.
- You can review five invented cases without supplying customer records.
- You need a production integration, phone agent, CRM migration, or customer-facing chatbot now.
- The workflow handles regulated health, legal, or highly sensitive data.
- You want replies sent autonomously without human approval.
What you receive
A mapped intake path
One-page diagram of the current public input, desired fields, explicit rules, local queue, and human decision point.
A local browser prototype
A source-code demonstration using a structured form, deterministic rules, and in-session owner queue. No external connectors are included.
Five synthetic cases
Invented examples cover normal requests, hazard words, and missing required information. Expected and observed outputs are recorded.
Implementation-options memo
A short factual note identifies what a later production build would require, including unresolved APIs, access, privacy, monitoring, and cost dependencies.
Handoff package
Prototype source files, configuration, test report, plain-English runbook, and seven calendar days for defects in the agreed prototype.
Plain terms
Price, timing, data, revisions, and support—agreed before payment.
Confirmed after fit review
The written schedule is set only after the public path, field list, rules, synthetic cases, and reviewer availability are confirmed.
$750 fixed
This is an unvalidated launch-price test: $375 after a signed scope and $375 after acceptance testing, before handoff. No third-party spend is included.
One revision round
Includes one consolidated round on field mapping, deterministic rules, queue labels, and synthetic cases before handoff.
Prototype stays offline
No production accounts, customer records, outbound messages, diagnosis, estimates, arrival promises, or dispatch actions are part of the sprint.
Seven-day fix window
Defects against the agreed prototype tests are fixed for seven calendar days. Production sources, destinations, or new branches are outside this offer.
No outcome guarantee
The sprint evaluates a proposed intake design. It does not guarantee production feasibility, labor savings, response time, leads, sales, or revenue.
FAQ
Questions before access changes hands.
What do you need from me?
Your public intake URL, a written workflow description, approved fields and rules, and review of five invented cases. Do not send credentials, customer records, or private system access for this sprint.
Does this connect to our live tools?
No. The deliverable is a local browser prototype and implementation-options memo. Any live form, inbox, spreadsheet, database, CRM, phone, text, or email connection requires separate technical, privacy, access, and price review.
What happens when information is missing?
The local prototype validates required structured fields and records the observed test result. It does not use a confidence model or infer missing facts. Production failure handling is outside this sprint.
Can you add a source or CRM later?
Possibly, but no integration is promised here. It may be scoped separately only after the prototype, platform documentation, permissions, data controls, monitoring, and operating costs are reviewed.
What does the fit check cover?
We confirm the public intake path, local prototype fields, explicit rules, five synthetic cases, acceptance test, schedule, and who gives approval. A signed scope comes before any invoice.
What counts as complete, and what do we receive?
Completion means the five agreed synthetic cases produce the recorded expected outputs or an explicit validation error. After final payment, you receive the project-specific source, configuration, map, test report, implementation-options memo, and runbook. Pre-existing components and third-party code remain subject to their original licenses and the signed scope.
See whether one intake path is worth a production build—without touching live systems.
Request a fit check
Next step: a written fit review. No invoice until scope, schedule, seller details, and acceptance terms are agreed.