Where an estimate request starts
A busy phone line is not an organized estimate pipeline. Many HVAC, roofing, plumbing, electrical, landscaping, and cleaning companies answer calls, texts, and website forms—then still lose job details in a group chat, site photos in one tech’s camera roll, and follow-up with whoever called back. The form is not the workflow. The workflow is the path from the first request to a scheduled visit and a clear next step.
This map is for trade and home-service teams that share estimate and appointment work across phone, text, email, and the website. A new marketing page alone does not stop a lead from falling between the cracks. TwoQM develops custom software, automation, CRM workflows, portals, and connected systems when your current tools do not hand the work to the right person. Hosting, domains, and email can sit beside that work. They are not the whole job.
Here is an original example, not a TwoQM client and not a measured result. A four-truck HVAC company gets a Saturday-evening text with three photos of a condenser and a question about “how soon someone can look.” The owner sees it Sunday night. On Monday a dispatcher books a different address from a website estimate form that never attached those photos. The homeowner’s spouse left a voicemail on the shop line that nobody logged. Three channels, three partial stories, one frustrated callback.
The same request may start on an estimate form, in a Google Business Profile message, on the office phone, in a tech’s personal text thread, or in an email with photos buried three replies deep.
Ordinary automation covers a large share when it is on and pointed at one inbox the team opens: a confirmation that the request arrived, a reminder before the inspection window, and a status the office can update without rewriting the address. Scheduling and CRM tools can hold a customer record and a job note. They do not merge a photo text with the website lead or tell a junior dispatcher which jobs they may quote.
Write the staff path first
One intake shape. Every new estimate collects the same facts: service type, address or service area, timing window, access notes, and approved photos. A form can require some of that. A text cannot, unless someone copies it into the shared job record the same day.
One owner for unscheduled channels. Name who checks the shop text line, Google messages, after-hours voicemail, and the estimate inbox—and by what time. “Whoever is free” means Saturday waits until Tuesday.
Photos that travel with the job. Site photos belong on the shared record the estimator and the tech both open, not only in one phone. If a photo is not on that record, the next person does not have it.
Appointment windows that match the trade. A quick filter change and a first-time roof inspection do not share a length, a buffer, or the same crew. Travel time should be a schedule rule, not a memory trick.
A status the customer and the office can both understand. New request, waiting on photos, inspection booked, quote sent, waiting on decision, scheduled for work. Pick names the team will actually use.
One follow-up owner. After the quote goes out, name who calls or texts—and when. Two people chasing the same lead is as bad as nobody chasing it.
Automation, then a draft a person sends
Use ordinary automation when the answer is already in the record: confirmations, reminder timing, a short note that photos arrived, and an alert when a quote sits untouched past your deadline. Those steps should not wait on a language model, and they should not invent crew availability the calendar does not have.
AI fits when the message is messy and a person still decides. A note like “AC not cooling, upstairs warm, unit outside looking dirty, can someone come Thursday” can become a short brief: likely service category, missing facts, and whether photos are attached. A draft reply can ask for access notes and a preferred window using language you already approve. It must not invent a price, promise a same-day tech, or send itself. AI and automation (https://twoqmllc.com/ai-automation) at TwoQM starts with the task, the information it may use, and who reviews the result. Model usage is an operating cost, separate from the build.
A CRM workflow (https://twoqmllc.com/crm) helps when stages—new estimate, waiting on photos, quote sent, scheduled—need a clear owner. If your field or scheduling tool already holds the job the team opens, connect that system (https://twoqmllc.com/connected-systems) instead of starting a second database.
When a custom piece is justified
Custom software fits when the same handoff breaks every week and no form setting fixes it: bilingual intake, photo sets that must stay with the address, crews that must not see one another’s open quotes, or an estimate that must land on one board with the original channel preserved. Agree on permissions, and on what happens if a vendor connection fails, before anyone builds it.
Software and websites for contractors (https://twoqmllc.com/industries/contractors) are planned around estimate requests, service areas, proof of work, and how an inquiry meets the schedule. That is not a generic template, and it is not “you need a website” as the fix for lost follow-up. If the site hides the estimate path, fix the path. If the path works but the office still loses photos and callbacks, fix the workflow.
Describe a workflow
Write down the path you are losing: Saturday texts with photos, forms without attachments, or quotes nobody follows. Describe that workflow (https://twoqmllc.com/business-automation) to TwoQM. We are based in Brownsville, Texas, and we deliver nationwide, in English and Spanish. We will say whether your current tools, a connection between systems, or a small custom piece fits—and what it will not do. An inquiry is not a quote, and it is not a claim that a system is already built.