--- title: "Salesforce that survives contact with the truck." description: "Nocona Consulting architects and implements Salesforce Field Service for home services companies — HVAC, plumbing, electrical, garage door and roofing." source: "https://noconaconsulting.com/" --- # Salesforce that survives contact with the truck. Nocona Consulting is a Salesforce practice in Dallas–Fort Worth that architects and implements Sales Cloud, Service Cloud, and Field Service for home services companies — HVAC, plumbing, electrical, garage door, and roofing. 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. [Book a call](https://noconaconsulting.com/contact) [See the Doorvana build](https://noconaconsulting.com/work) - **Focus** — Home services — HVAC, plumbing, electrical, garage door, roofing - **Depth** — Field Service, multi-line-of-business orgs, source-controlled metadata - **Background** — Field technician before consultant — Trane, Carrier, Daikin ## You have three businesses sharing one CRM, and none of them fit. 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. ## Three ways engagements usually start ### Architecture & discovery 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. - Discovery workshops - Object & data model design - Edition and license scoping ### Field Service implementation Work Orders, Service Appointments, scheduling, mobile, and the parts-and-labor costing layer — configured for how your crews actually dispatch. - FSL object chain - Scheduling & dispatch policies - Mobile app rollout ### Rescue & re-platform 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. - Org audits - Migration planning - Metadata in source control [Full scope of services →](https://noconaconsulting.com/services) ## Doorvana Garage door manufacturer and installer · Service, New Construction, Wholesale Doorvana's owner is also a co-owner of Nocona Consulting — [not an arm's-length engagement](https://noconaconsulting.com/work). 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. - **Pro Suite → Enterprise** to unblock Field Service and Apex - **FSL object chain** — Work Order → Line Items → Service Appointment → Assigned Resource - **Wholesale carve-out** so it never touches Field Service objects - **SFDX + git** — every metadata change reviewable in source [Read the build log](https://noconaconsulting.com/work) - Sales Cloud - Service Cloud - Salesforce Field Service - Experience Cloud (partner portal) - SFDX · VS Code · git ## Four things I will not negotiate on 01 ### One revenue ledger, always 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 ### The edition decides the architecture As of 2026, Salesforce Field Service is not available below Enterprise Edition, and no clever custom object gets you around it. Scope the license first or rebuild later. 03 ### If the tech will not use it, it does not exist A flow that takes eleven taps on a phone in a crawlspace is a flow nobody runs. The field is the acceptance test. 04 ### Metadata belongs in git 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. ## What I am building, written down Build logs from live engagements — the architecture decisions, the metadata, and the things that went sideways. Build log Doorvana Sep 22, 2026 ### [I built four Account record types yesterday and deleted them this morning](https://noconaconsulting.com/blog/record-types-vs-picklists) Record types are for process. Customer kind is an attribute. The test that sent four Account record types to the bin while three on Opportunity stayed — and the two deploy errors either choice hands you. - Record types - Object model - Picklists - Lead conversion Build log Doorvana Sep 22, 2026 ### [Day one on a greenfield Salesforce org: standing up Field Service without building on sand](https://noconaconsulting.com/blog/greenfield-field-service-setup) The order I set up Doorvana's Salesforce org — CLI, SFDX project, baseline retrieve, Field Service enablement, the FSL managed package — and what bit me on each. - Field Service - SFDX - Greenfield - Managed packages Architecture Doorvana Sep 21, 2026 ### [Opportunity is what you booked. Work Order is what you did. Never add them.](https://noconaconsulting.com/blog/one-revenue-ledger) The single most common way a home services Salesforce org starts lying about revenue — and the object discipline that prevents it. - Field Service - Revenue reporting - Object model - Order Products [All field notes →](https://noconaconsulting.com/blog) ## Common questions ### What does Nocona Consulting do? Nocona Consulting is an independent Salesforce consultancy for home services companies — HVAC, plumbing, electrical, garage door, and roofing contractors. The work covers three things: discovery and architecture before anything is built, Salesforce Field Service implementation, and rescuing orgs that were built badly or have been outgrown. ### Do I need Salesforce Enterprise Edition to use Field Service? Yes. Salesforce Field Service requires Enterprise Edition or above, and there is no way around it with configuration. The Field Service managed package is hardwired to specific standard objects — Work Order, Work Order Line Item, Service Appointment, Assigned Resource — and cannot be remapped onto custom objects you build on a lower edition. Editions below Enterprise also block Apex, sandboxes, and most managed AppExchange packages, so the edition decision constrains the architecture before design starts. ### Should a home services company use Salesforce instead of Jobber or ServiceTitan? Not always. Jobber and ServiceTitan are purpose-built for field service and a well-run instance of either is the right tool for many contractors. Salesforce becomes the better answer when a business runs several lines of business that need genuinely different object paths, needs reporting the purpose-built tools cannot produce, or needs to integrate deeply with systems outside field service. Nocona Consulting will say plainly on the first call when Salesforce is not the right move. ### What does a Salesforce implementation for a home services company cost? Cost is driven by four things rather than a headline number: how many lines of business share the org, whether Field Service is in scope, the Salesforce edition and license mix required, and how much existing data has to be migrated and cleaned. Licenses are a separate ongoing cost paid to Salesforce, not to the consultancy. Scope and a real number come out of the discovery engagement, which is deliberately sold separately so the build is quoted against a written architecture rather than a guess. ### Does Nocona Consulting work outside Texas? Yes. Nocona Consulting is based in the Dallas–Fort Worth area of Texas and works with home services companies nationwide. Discovery interviews, design review, and build work are all done remotely.