Your best closer, in the room, with the whole office behind them.

07:40 · The office

The lead lands, and the system already knows what it is.

A call on your RingCentral line, a Meta lead form, a contact in JobTread, a canvasser at a door — all of it arrives in one pipeline. Before a human touches it, RenoFlow normalizes the phone to E.164, checks it against every lead you have ever had, and decides on its own whether this is a new opportunity, the same homeowner calling back, or junk. Then it scores it.

• Phone-level dedup with rules you set per company
• 0–100 quality score from six fields you define
• Source and sub-source captured at the moment of intake
• Closed deals re-open as new opportunities, not duplicates

09:05 · Dispatch board

Assign the appointment to the rep who actually closes it.

The board shows today by salesperson, with an unassigned column you cannot quietly ignore. Each rep carries their 30-day close rate and their current load in the column header, so assignment becomes a decision instead of a habit. Open the map and every appointment is geocoded, pinned in its rep’s color, with real drive times between them.

• 30-day close rate per rep, computed server-side
• Mapbox geocoding and drive times between stops
• Confirm, invalidate, cancel or reassign in one click
• Rate the caller’s work 1–5 stars on the same screen

13:52 · In the driveway

The rep’s phone shows one thing: today, confirmed.

Installed to the home screen like an app, because a field tool that lives in a browser tab does not get used. The rep sees only their own confirmed appointments — and if their role is not cleared for it, the homeowner’s phone number never leaves the server. Status moves from pending to en route to in meeting, and the dispatch board moves with it.

• Installable PWA on iOS and Android
• Phone numbers withheld server-side by role, not hidden in the UI
• Web push when an appointment is assigned or changes
• The dispatcher’s note travels with the appointment

14:31 · The objection

Randy answers from your playbook. Not from the internet.

"We’re getting three more quotes." Every rep has lost that one. Randy searches your own training documents — the ones your best closer wrote — using contextualized embeddings, pre-filtered to this customer’s profile and this moment in the conversation. And if your playbook does not cover it, he says so, rather than inventing something you would never have said.

• Retrieval over your own PDFs and Word documents
• Pre-filtered by customer profile and conversation scenario
• No retrieval hits means he declines — he never improvises
• Managers can read every thread a rep ever had

14:58 · The kitchen, as it will be

Photograph the room. Hand them the result.

The rep taps the camera inside the homeowner’s record, picks Kitchen, and describes the work in a sentence. The model composes their actual photograph with up to eight style references your manager curated — your finishes, your cabinetry, your standard of work — so what the homeowner falls in love with is a job you can actually deliver. It arrives on an expiring signed link, captioned for illustration only.

• Their real photo, composed with your curated style library
• Six categories: roof, kitchen, bath, exterior, interior, landscaping
• Private storage, links that expire in minutes
• Watermarked and labelled — never presented as a guarantee

15:20 · The number

Cost and minimum sell, straight out of your pricebook.

Randy does not do arithmetic on a price. He reads it. Your catalog supports eight pricing models — unit, unit with minimum, flat, size bracket, range, composite, manual and size matrix — and every row stores your real cost, with minimum sell either set explicitly or derived from it. He returns both, plus a flag when the job is unusually large, unusually small, under your minimum square footage, or priced by hand.

• Eight pricing models, one catalog per company
• Your cost and your minimum sell — never an estimate of them
• Flags for large deal, complexity, and below-minimum jobs
• One tap creates the account, location and job in JobTread

↳Proposals and e-sign live in JobTread. RenoFlow hands off; it does not duplicate them.

15:44 · Financing

Finance is a stage in your pipeline, not a dead end.

Whether the homeowner is open to financing is one of the six fields that score the lead on day one. A declined deal gets its own result and its own stage rather than quietly becoming a loss, and it stays eligible for a second rep to rehash until it has been declined twice. Randy will discuss financing only from your approved playbook, and is explicitly forbidden from quoting a rate, a monthly payment, or an approval.

• Finance-declined tracked as its own stage and its own result
• Rehash-eligible until a second decline
• Randy quotes no rates, no payments and no approvals

↳Lender matching and in-app offer comparison are on the Enterprise roadmap and are not in the product today.

18:15 · Back at the office

The close writes itself back into the business.

When the proposal is approved in JobTread, the webhook sets the deal sold and carries the revenue back with it — which is the only reason the reporting can be trusted. Ninety days of performance by source and sub-source. Close rate per rep with a minimum sample before anyone gets judged. Commission periods with carry-over balances that actually reconcile. And five detectors that read your data without a language model anywhere near them.

• Sold is set by the webhook, never typed in by hand
• 90-day attribution by source and sub-source
• Commission periods with balances carried across periods
• Five deterministic detectors, plus a brief each office day