Salesforce consulting · Dallas–Fort Worth, Texas
I architect and implement Salesforce — Sales Cloud, Service Cloud, and Field Service — for home services companies. I also spent years as an HVAC field technician, so I know exactly what happens to a beautiful workflow at 4pm in a 140-degree attic.
The usual situation
Service runs on dispatch. New construction runs on schedules and draws. Wholesale runs on price lists and POs. Most orgs get built for whichever one was loudest in the kickoff meeting, and the other two get bolted on with custom fields until the reports stop reconciling.
That is usually the point somebody calls me. The fix is rarely more configuration — it is deciding which objects carry which line of business, and being disciplined about where revenue is counted.
What I do
Before anything gets built: object model, record types, lines of business, and the reporting spine. Most failed implementations were lost here, not in the build.
Work Orders, Service Appointments, scheduling, mobile, and the parts-and-labor costing layer — configured for how your crews actually dispatch.
An org someone else built and nobody trusts. Jobber, ServiceTitan, or spreadsheets you have outgrown. I map what exists and get you to something maintainable.
Current engagement
Garage door manufacturer and installer · Service, New Construction, Wholesale
Doorvana came in on Salesforce Pro Suite with Jobber alongside it, running three lines of business that need three different object paths. The engagement covers the edition move to Enterprise, the Field Service foundation, the Wholesale carve-out, and a single revenue ledger that the leadership team can actually trust.
Stack
How I work
01
Opportunity is what was booked. Work Order is what was performed. They converge on Order Products. Sum both and your revenue report is fiction.
02
Field Service is not available below Enterprise, and no clever custom object gets you around it. Scope the license first or rebuild later.
03
A flow that takes eleven taps on a phone in a crawlspace is a flow nobody runs. The field is the acceptance test.
04
Clicks in production with no source of truth is how orgs rot. Every change I make is a commit you can read, review, and roll back.
Field Notes
Build logs from live engagements — the architecture decisions, the metadata, and the things that went sideways.
The single most common way a home services Salesforce org starts lying about revenue — and the object discipline that prevents it.
Next step
A 30-minute call. I will tell you whether Salesforce is the right answer for your shop — including when it is not.