Warranty, Past Clients & The Referral Channel
A continuous system that handles warranty properly, maintains past clients, and works the architect and designer relationships that produce most of the business.
- Tier
- Flagship
- Build order
- 6th of 7 for custom builders
- Shape of it
- 9 steps
- At launch
- Built against your stages, then proven before it runs alone
The problem this solves
Custom building is referral-driven and the referral channel is maintained by memory.
Warranty. Requests arrive by text to the principal or the project manager, months after handover, into nothing. There is no record, no triage, no distinction between a genuine defect, a subcontractor callback, and normal settlement the client misunderstands. So they are handled inconsistently, and the client's last experience of the firm is worse than the build was.
Past clients. Contact stops at handover. A custom home client is a high-value advocate for a decade and hears nothing after month one.
Architects and designers. These relationships produce most of the pipeline and are maintained by running into each other. When a designer refers three projects in a year and the builder never acknowledges the pattern, the fourth goes elsewhere.
The eleven-month inspection. Most warranties run twelve months. A visit at eleven months catches issues inside the period, demonstrates care, and is the single best referral-generating touch in the trade. Almost nobody does it systematically.
How it works, step by step
Every wait, threshold and branch below is a value we set with you during the build, against your stages and your language. None of it is a default we impose.
- What starts it
Step 1Trigger
Every completed project enters a warranty record with the start date, duration, subcontractor warranty terms, and the handover documentation attached.
Step 2
Warranty requests arrive on a real channel and become tickets with the project history attached.
Step 3
Triage separates a genuine defect, a subcontractor callback under their own warranty, normal building movement, and a client maintenance question.
Step 4
Subcontractor warranty callbacks are routed to the subcontractor with the documentation, rather than absorbed by the builder.
Step 5
An eleven-month inspection is scheduled automatically, before the warranty expires, as a service and as a referral moment.
Step 6
Past clients enter a long cadence: seasonal maintenance guidance relevant to their specific house, the build anniversary, and a genuine check-in.
Step 7
Architects, designers and referral partners are a tracked segment with referrals attributed, acknowledged, and reciprocated where appropriate.
Step 8
Photography and case-study permission is requested at the right moment, which is shortly after handover while the client is delighted, and recorded so nobody asks twice.
Step 9
Review requests go only to projects that completed cleanly.
How it gets built
Built inside what you already run
- Buildertrend
- CoConstruct
- JobTread
- Houzz Pro
- Procore
- or whatever your office already runs on
Nothing to log into and nothing to license. If a system needs a record your platform does not hold, we add the field to your platform rather than starting a second one beside it.
This is the actual build order, in the phases its own steps fall into. It runs in supervised mode first, with you approving what goes out, until you are happy with the tone.
- 1
Build
Build the warranty record from System 5's handover data.
Built inside the software you already run, against your stages and your language.
- 2
Build
Move warranty requests onto a real channel. Expect the principal to be the hardest person to move off personal text messages.
- 3
Build
Build triage with the project manager, including subcontractor routing.
- 4
Build
Schedule the eleven-month inspection automatically. Highest-value single element of this system.
- 5
Build
Build the past-client cadence with house-specific content.
- 6
Build
Build the referral partner segment with attribution.
- 7
Build
Build the photography permission request at handover.
- 8
Build
Connect review requests to project outcome with exclusions.
What changes after it goes live
How it runs today
Custom building is referral-driven and the referral channel is maintained by memory.
After this one is live
Warranty stops arriving on the principal's phone and disappearing. Subcontractor callbacks go to the subcontractor. The eleven-month inspection catches issues inside the period and generates referrals. And the architects who refer see that it is noticed.
How to measure whether it worked
Your arithmeticRun with your numbers, not ours
Four numbers: warranty work absorbed that was a subcontractor's obligation, projects traceable to a referral partner, past clients who built again or referred, and case-study photography never obtained because nobody asked in time. The first is direct cost; the last quietly limits marketing for years.
We agree the baseline before anything is built, and we do not take credit for things that were going to happen anyway. There is no figure on this page claiming what we have produced for somebody else, because there is no verified figure to publish.
What we will not do
This is from the same delivery document as everything above it. It is on the page because a supplier who has not thought about it will not tell you, and you would find out later.
Client privacy is the primary exposure. Custom building clients are frequently wealthy and deliberately private.
- Never expose a client name, address, project value, floor plan or photographs of their home in any demonstration, template or marketing asset.
- Photography and case-study permission is obtained explicitly, in writing, and recorded. A permission granted for one use is not a permission for all uses.
- Several clients will have a confidentiality expectation even where no NDA exists, and some will have an actual NDA.
Contract and lien law.
- Draw requests, lien waivers and retainage are governed by state statute, and the requirements differ materially between states. Any automation touching draw documentation must be built to the specific state's requirements and reviewed by the builder's counsel.
- Change orders are contract amendments. An automated approval flow must produce something that satisfies the contract's own requirements for a valid change order, which frequently means a signature rather than a click.
- Nothing in these systems constitutes legal advice about lien rights or notice deadlines, and no automation should be relied upon for statutory notice timing.
Messaging.
- TCPA and CAN-SPAM apply. Consent per number, quiet hours in local time, immediate opt-out honoured across every system.
- Subcontractors and suppliers are businesses, but the same consent and opt-out discipline applies.
Subcontractors are not employees. Any system that assumes subcontractor adoption will fail. Systems must work with the trades as they are, and where a system genuinely needs subcontractor participation, that must be flagged to the builder as a commercial negotiation rather than a configuration step.
Nothing here is legal advice. State contractor licensing, lien statutes, building codes, contract law and consumer protection rules can each add requirements.
Nothing here is legal advice. Rules in this area have moved more than once recently, and every template that states a commercial term or a guarantee goes to your own counsel before it goes live.
Seven systems forcustom builders.
We build one at a time and prove it moved before starting the next. The tiers are the dependency order, not a price list.
Tier 1Foundational
Nothing arrives late or unowned. These come first because everything above them assumes they are true.
- 1Enquiry Capture & Qualification Before Design HoursProtects design hours, which is the scarcest resource, and captures the architect introductions that currently live in email threads.
- 2Consultation & Site Visit PreparationProtects the most expensive hour in the sales process and calibrates cost before the meeting.
Tier 2Growth
The recoverable money. These work the pools the foundational systems have made visible for the first time.
Tier 3Flagship
One connected system end to end, plus what the owner reads on a Monday. Only once the pieces are proven individually.
- 5The Complete Build SystemThe flagship, once the pieces are proven.
- 6Warranty, Past Clients & The Referral Channelyou are hereCompounds everything, and depends on System 5's handover data.
- 7The Principal's Morning BriefOnly meaningful once there are systems to report on.
The tiers are the dependency order for custom builders, not a price list. Most firms do not start at the first one, because the order is a default and the call is where it gets changed.
A note on sequencing this trade
Sequencing note specific to this trade. The build cycle is six to eighteen months, so System 5 cannot be proven inside a normal engagement window. Prove Systems 1 through 4 on live projects, and implement System 5 on projects starting during the engagement with the understanding that its results arrive after it. Say this at the start rather than being asked about it later.
Back to the custom builders overview for the stage map and where these fit.
Is this the oneyou need first?
Often it is not. On the call we look at what is actually costing you most right now, which is frequently a different system from the one that brought you to this page. If there is nothing worth building yet, we will say so.