Paper Boat Media / Buying decisions that hold up
How to Choose a CRMFrom contractors to enterprise sales teams.
Use cases, specific tools, true costs and the work between the first inquiry and the final payment.
Understand the handoffs before you choose the software.
The first question is “What are you trying to do?”
Before I want to know which CRM you are considering, I want to know what you are trying to accomplish. Are good leads disappearing? Are estimates sitting unanswered? Are technicians arriving without the right parts? Is marketing celebrating inquiries that sales considers worthless? Does your leadership team spend the first half of every meeting arguing about whose numbers are correct?
Those are different problems. Buying the same software to solve all of them can become an expensive way to discover that.
A contractor with two trucks might need a dependable path from phone call to estimate to payment. A regional distributor may need salespeople to see stock availability and customer-specific pricing. A Fortune 500 organization may need account relationships, territories, permissions, forecasting and customer history to work across divisions, countries and acquired companies. Each deserves a serious system. Serious does not always mean large.
My recommendation is to choose the smallest sustainable combination of tools that handles the work, preserves the information you need and supports the next credible stage of growth. That might be Jobber. It might be HubSpot. It might be Salesforce connected to several other systems. It might be a better configuration of software you already pay for.
What it should never be is an expensive answer to a question nobody asked.
Start with the job you need the system to do
“We need a CRM” is a purchasing statement. “We need every qualified estimate followed up before the customer hires someone else” is a useful business objective.
Write one sentence before you watch a demo:
We need [person or team] to [perform an action] when [something happens], using [specific information], so we can improve [a measurable result].
For a painting contractor: “We need our estimator to receive a follow-up task after each proposal, see the customer's questions and record the next step, so qualified estimates stop disappearing.” For a commercial service company: “We need dispatch to know the equipment, required skill and available parts before assigning the visit, so fewer jobs require a second trip.”
For a national manufacturer: “We need account teams to see the customer's buying entities, installed equipment, open service issues and renewal dates, so different divisions stop approaching the same customer as strangers.”
Then identify the constraint. If estimates take two weeks because nobody has time to prepare them, better reminders will only remind you that you are late. If salespeople cannot promise a delivery date because inventory is inaccurate, a more attractive sales dashboard will not locate the missing pallet.
Agree on the workflow, the person responsible and the measure of success. Only then turn those requirements into a software shortlist.
What needs to
work better?
Choose the main constraint. Start with the matching shortlist, then test your actual workflow.
A connected service workflow from the first inquiry through quotes, scheduling, invoicing and payment.
Move an unanswered estimate into follow-up, accept it, schedule the work and record payment without entering the customer twice.
A starting point, not an automatic purchase decision. Inventory or warehouse requirements may add an ERP or WMS to any shortlist. Product editions and integrations still need checking.
CRM, field service, project management and ERP are different purchases
CRM stands for customer relationship management. In practical terms, CRM software helps a business organize customers, contacts, sales opportunities, communication and follow-up. Some products extend much further. The label alone tells you very little about whether they can run your operation.
| System | The work it should own | A concrete example |
|---|---|---|
| CRM | Relationships, lead ownership, opportunities, next actions and sales history | Who follows up on the commercial roofing proposal Friday? |
| Field-service management | Work orders, scheduling, dispatch, technicians and service history | Which qualified technician can handle this repair with the required part? |
| Construction project management | Project schedules, budgets, documents, changes and production coordination | Has the customer approved the change, and what does it do to cost and schedule? |
| ERP, or enterprise resource planning | Financial and operational records such as orders, purchasing, inventory and accounting | What has been ordered, received, invoiced and paid? |
| WMS, or warehouse management | Receiving, storage locations, picking, packing and stock movement | Which bin contains the item, and has it been allocated to another order? |
| Marketing automation | Campaigns, segmentation, nurturing and communication preferences | Which prospects should receive the maintenance-plan reminder? |
| Business intelligence | Combined reporting across the systems that hold the evidence | Which lead sources produce profitable completed work? |
One product can cover several of these jobs. A broader suite can also contain separately licensed applications. Do not assume a CRM subscription includes warehouse operations, advanced routing, marketing automation or sophisticated quoting because the vendor sells those things somewhere else in its catalog.
The useful question is: Where should this information be maintained, and who else needs to see it? A salesperson may need to see an unpaid invoice without becoming responsible for the accounting ledger. A dispatcher may need parts availability without editing warehouse quantities.
Few users. Clear handoffs. Minimal administration.
Sales, materials, dispatch and finance agree.
Account hierarchies, permissions, regions and integration ownership.
My tool recommendations, based on the actual use case
These are starting shortlists based on product scope and the workflow described, not claims that I have independently benchmarked every product. Capabilities, integrations and prices vary by edition. Require a demonstration of your specific process before buying.
01A solo contractor or small service crewJobber / Housecall Pro
I would start by comparing Jobber and Housecall Pro when the business needs customer records, quotes, scheduling, invoices and payments in a connected service workflow. Both publish plans for service businesses. Compare the exact tier that includes your required functions, not the lowest number in the advertisement. Jobber · Housecall Pro
Consider a pressure-washing business whose owner answers calls between jobs. The useful system captures the inquiry, records the property and requested work, produces the quote, schedules the accepted job and keeps payment status visible. A simple reminder for an unanswered quote may be worth more than a sophisticated lead score.
Overkill starts when that owner needs to administer a complex sales platform, maintain multiple connectors and design a dispatch system just to accomplish those basic tasks. Conversely, if the business handles only a handful of inquiries and loses nothing, a disciplined shared tracker and calendar may be a sensible temporary choice. Set a migration trigger, such as missed follow-ups or a second person needing reliable access, rather than waiting for the spreadsheet to collapse.
02Roofing and exterior contractors with a real sales-to-production handoffJobNimbus / AccuLynx
I would compare JobNimbus and AccuLynx for a roofing-centered operation. Their product positioning is specific to roofing; evaluate how well each supports your inspection, proposal, documentation and production process. JobNimbus · AccuLynx
Imagine a roofer managing retail replacements and storm-related inquiries. The salesperson needs the property, inspection notes, measurements, photos, proposal version and next action. Production needs the accepted scope, selected materials, approvals and timing. The office needs a reliable customer record and payment status.
Ask the vendor to demonstrate what happens when the homeowner changes materials after accepting the quote. Who sees the change? Does the estimate update? Is a new approval required? What happens to the material order? A colorful pipeline is only the beginning of that test.
03Remodelers, builders and contractors managing extended projectsJobTread / Buildertrend / Procore
I would shortlist JobTread and Buildertrend when estimating, budgets, change orders and project execution dominate the problem. For organizations with more extensive construction coordination requirements, I would also evaluate Procore. These are project-oriented candidates; compare their sales capabilities and any need for a separate CRM. JobTread · Buildertrend · Procore
A kitchen remodeler does not finish the customer relationship when the contract is signed. Selections change, subcontractors need instructions, materials arrive late and an approved change can alter both margin and completion dates. The system needs to carry the agreement into the work.
I would hesitate to buy a general-purpose CRM and custom-build an entire construction management application inside it. First determine whether a product designed around that work already solves most of the problem. My broader general contractor and remodeler consulting follows the same principle: the sales promise must survive the handoff to production.
04Service companies with substantial dispatch and operating complexityServiceTitan
ServiceTitan belongs on my evaluation list when dispatch, service operations, technician workflows and management visibility have become substantial requirements. Its pricing page describes per-technician pricing and requests a quote. That calls for a scoped evaluation of the full package and rollout, not a guess based on another contractor's bill. ServiceTitan
Picture an HVAC business with multiple dispatchers, service agreements, replacement opportunities and technicians with different skills. A customer calls about equipment the company installed two years ago. The office should be able to connect the customer, location, equipment and service history. Dispatch must find an appropriate appointment. The technician needs useful information before arriving. Sales needs to know whether a replacement estimate is appropriate, and accounting needs the resulting transaction.
This complexity can justify a broader platform. It still does not excuse a poor implementation. Define who maintains the price book, membership records and operating rules before signing.
05A business whose main problem is sales follow-upPipedrive / Zoho CRM
Pipedrive would be an early choice to test when the priority is a clear sales pipeline, ownership and next actions. Zoho CRM belongs on the shortlist when the organization wants a configurable CRM and is willing to evaluate its editions and related applications carefully. Pipedrive · Zoho CRM
A commercial contractor pursuing property managers might need to track the management company, each property, decision-makers, bid opportunities and contract renewal windows. That is relationship development, not merely dispatching the next available truck. A general sales CRM can make sense while an existing operations system continues to run delivery.
Ask whether the tool supports the relationships you actually have. One person might manage twelve properties. One property might have a property manager, facilities contact and separate billing entity. Flattening all of that into “customer name” creates avoidable confusion.
06A company trying to connect marketing and salesHubSpot
I would put HubSpot high on the shortlist when website inquiries, nurturing, sales activity and customer communication need to work together. Its separate marketing and sales offerings make packaging an important part of the decision. Price the combination you need, including seats, marketing contact requirements, automation and onboarding. HubSpot Sales · HubSpot Marketing
Consider a regional equipment supplier. A buyer downloads a specification guide, attends a demonstration, requests a quote and brings purchasing into the conversation. Marketing should know when sales takes ownership. Sales should see the useful context. An existing customer with an unresolved service problem should not receive an oblivious “ready to buy?” sequence.
A connected marketing and sales environment can help. It will not automatically know which messages are appropriate. Your team must define the segments, handoffs and suppression rules.
07Complex sales organizations and Fortune 500 environmentsSalesforce / Dynamics 365 / SAP
Salesforce and Microsoft Dynamics 365 Sales are serious candidates when the requirements include complex account structures, multiple teams, configurable processes and extensive integration. SAP's customer-experience portfolio also deserves evaluation where the organization's existing SAP environment and business requirements make it a credible fit. Salesforce · Dynamics 365 Sales · SAP
I would lean toward evaluating Salesforce early when a company needs a highly configurable sales environment and has the resources to own it. I would evaluate Dynamics 365 early when Microsoft business applications and the surrounding technology strategy are central to the organization. Neither recommendation means that integration will be automatic or that every department belongs in the same application.
A Fortune 500 manufacturer may sell through distributors, direct enterprise accounts and regional subsidiaries. One global customer can have dozens of buying entities, negotiated agreements, installed equipment and local service relationships. Management needs a consolidated view without giving every salesperson unrestricted access to every record.
The buying exercise now includes identity, account hierarchies, territory rules, currencies, approval authority, data residency requirements, auditability, release management, regional exceptions and acquisitions. The project needs business owners, architecture, security, finance and operating teams involved before the software contract is finalized.
Company size alone is a poor selection rule. A large organization might use a simpler CRM for a clearly bounded division. A relatively small company might have unusually complex channel sales. Buy for the complexity of the work and the capacity to maintain the system, not the prestige of the logo.
- 01 / CRMCapture & qualify
Source, fit, owner and next action.
- 02 / ESTIMATINGQuote & approve
Scope, price, versions and approval.
- 03 / OPERATIONSCheck & allocate
Materials, capacity and commitments.
- 04 / FIELD OR PROJECTSchedule & deliver
People, skills, instructions and changes.
- 05 / FINANCEInvoice & collect
Completed work, billing and payment.
- 06 / CRM + MARKETINGRetain & learn
Service history, renewal and outcomes.
Each handoff needs an owner, a shared record identifier and a way to handle exceptions. The same product may cover several steps.
Lead tracking needs ownership, next actions and disposition
Capturing a lead is not the same as handling it. A useful record answers where it came from, what the person wants, whether the work fits, who owns the response and what should happen next.
At minimum, consider source, inquiry date, requested service or product, location, customer type, assigned owner, stage, next action, next-action date and outcome. Add fields only when they support a decision or required task. Forty mandatory fields can be an excellent way to get people to enter forty unreliable answers.
Stage tells you where an opportunity is. Disposition records what happened to an inquiry or sales attempt. An inquiry can be contacted but unqualified. An opportunity can be awaiting a proposal without being lost. “No answer,” “outside service area,” “wrong service,” “duplicate,” “future project,” “lost on price” and “lost on availability” should not all disappear into one miscellaneous bucket.
| Record | Useful treatment | Why it matters |
|---|---|---|
| Qualified project, estimate sent | Keep an owner and dated next step | The customer still has a decision to make |
| Customer wants work next spring | Record future timing and an agreed follow-up | Timing is different from rejection |
| Inquiry outside the service area | Disqualify with the geographic reason | Marketing needs to understand targeting waste |
| Prospect chose another contractor | Record the stated reason, or “unknown” | A guessed loss reason is bad evidence |
| Existing customer needs warranty help | Route to service and link the customer history | A service request is not a new sales lead |
For an illustrative example, imagine 100 inquiries: 20 outside your territory, 15 for work you do not perform, 10 duplicates and 55 legitimate opportunities. If 11 become customers, that is 11% of all inquiries and 20% of qualified opportunities. Those answer different questions. Neither number is useful without its denominator.
Good disposition data helps distinguish a marketing problem from a response problem, an estimating problem or a capacity problem. It also tells you when to stop an automated sales sequence. Someone who has already said no should not receive cheerful follow-ups forever.
Quotes should preserve the economics of the job
A quote is a commercial commitment, not just a PDF with your logo. Depending on the business, it may need labor assumptions, material quantities, subcontractor costs, allowances, freight, tax treatment, discounts, payment milestones, exclusions and an expiration date.
For contractors, test whether estimates become workable budgets and whether approved changes preserve a history of what the customer accepted. For distributors, test customer-specific pricing, quantities, freight and available-to-promise information. For manufacturers, test approved product configurations, incompatible options and discount authority.
This is where CPQ, or configure-price-quote software, can be useful. A business selling combinations of products, services and contract terms may need rules that prevent an invalid configuration or route an unusual discount for approval. Salesforce's revenue-management offering is one example to evaluate for this category; it is a separate scope decision from basic sales CRM. Salesforce revenue management
The electrician quoting three standard service options may not need enterprise CPQ. The equipment manufacturer with thousands of permitted configurations may have an expensive problem without it.
Ask the vendor to revise a quote after approval, retain the previous version and show the downstream effect. “We can email an attachment” is not a complete answer to a quoting requirement.
Materials, inventory and warehousing need their own discipline
A customer record cannot tell you whether the correct equipment is physically available unless reliable inventory information reaches it. Inventory on hand, inventory reserved and inventory available for a new promise are different quantities.
Consider an HVAC replacement. The salesperson quotes a unit, the customer approves it and a date is proposed. The operation must confirm the equipment, allocate it, identify additional materials and make sure the crew can install it. If the final unit is already committed elsewhere, the salesperson needs to know before promising Tuesday.
For businesses with meaningful purchasing, inventory and financial requirements, I would evaluate an ERP such as Microsoft Dynamics 365 Business Central or NetSuite alongside the CRM decision. That is a recommendation to investigate operational scope, not a claim that either is necessary for every contractor. Business Central
When warehousing involves receiving, bins, picking, packing, stock counts and multiple locations, evaluate WMS capability explicitly. NetSuite WMS, for example, describes those warehouse workflows and is an add-on module. NetSuite WMS
Your demonstration should include a partial delivery, a backorder, a return and a substitution. Show how warehouse stock moves to a truck, how used materials are recorded against the job and how unused items return. Test the product identifiers and units of measure. A case of twelve is a rather different promise from one item.
Choose an authoritative system for each important record. Finance owns the posted invoice. Inventory owns available stock. CRM owns the opportunity and next sales action. The other applications receive the information they need. Without ownership rules, “two-way sync” can mean two systems confidently correcting each other all afternoon.
Routing means more than drawing a shorter line on a map
There are at least two kinds of routing in this conversation. Lead routing assigns an inquiry to the correct seller or branch. Field routing assigns work to people and vehicles with the right location, time and capabilities.
Lead routing can depend on geography, product, account ownership, language, availability and response deadlines. A national account should not lose its established owner because a contact filled out a local form. An unaccepted lead needs an escalation path.
Field routing must account for more than distance. A technician may be nearby but lack the required qualification, equipment, part or time window. A short route that creates a failed visit is not efficient.
For a service company, test its field-service platform's dispatch and route functions first. For a more complex organization, Dynamics 365 Field Service and Salesforce Field Service belong on the evaluation list, with licensing and integration assessed separately from sales CRM. Dynamics 365 Field Service · Salesforce Field Service
A commercial grounds-maintenance business also needs recurring schedules, property instructions and weather-related changes. A repair network may need appointment windows and skills matching. A distributor delivering materials has different vehicle, loading and delivery constraints. Make the vendor demonstrate your type of routing.
Test mobile use in ordinary working conditions, including poor connectivity. Ask what can be viewed or edited offline, what happens during synchronization and how conflicts are resolved. “There is an app” is a very low bar.
Integration: show me the records moving
“It integrates” is the beginning of a discussion. The useful questions are what moves, in which direction, how quickly, under which subscription and what happens when it fails.
A connector might create a contact but not update it. It might send invoices without handling credits. It might recognize a standard field but ignore your custom job number. The integration you need may require a higher software tier, an outside connector or ongoing development.
For a straightforward handoff, start by evaluating a supported native connection. Zapier can be a practical candidate for bounded cross-application workflows when its available triggers, actions and operating limits match the job. Workato or MuleSoft can belong in a more extensive enterprise integration evaluation. These are options to test, not interchangeable promises of reliability. Zapier · Workato · MuleSoft
Here is a realistic integration acceptance test:
- A website inquiry enters the CRM with its source and requested service.
- The correct person receives ownership and a response task.
- An accepted proposal creates one job or order, with the approved scope and correct customer identifier.
- Operations checks capacity and materials before confirming the appointment.
- Completion and invoice status return to the customer record without changing the financial ledger incorrectly.
- Marketing receives the appropriate customer status and communication preferences.
Now repeat the test with a duplicate inquiry, a changed email address, a canceled job, a partial payment and a temporary outage. Check retries, error alerts and how staff repair a failed transaction. A successful test must not create a second invoice when someone presses the button twice.
At enterprise scale, also test account identifiers across subsidiaries, historical data, permissions, volumes and regional requirements. Someone must own monitoring after the implementation team leaves. An integration without an owner is a future support ticket with excellent timing. For the broader design of customer data, automation and connected systems, see my marketing technology and integration architecture work.
Marketing and dashboards should tell you what to do next
The CRM should help marketing learn which inquiries become worthwhile customers. Preserve source information, campaign context where available and the customer's own account of how they found you. Connect it to qualification, sales outcomes and completed work when the systems permit.
Treat attribution as evidence with limitations. A person can hear about you from a friend, read your website, see an ad and call from a search result. One recorded source does not describe every influence.
For a contractor, I would want a dashboard that connects inquiry volume to qualified opportunities, response time, estimates issued, overdue follow-ups, wins and completed-job economics. For recurring service, add renewals and cancellations. For a regional operator, compare branches while accounting for service mix and capacity.
For an enterprise sales team, account coverage, opportunity aging, stage movement, forecast changes, renewals and retention may matter. Define what counts as a qualified opportunity and what permits a stage change before treating the forecast as reliable.
| Person using the dashboard | A decision the dashboard should support |
|---|---|
| Owner | Where are profitable opportunities being lost? |
| Sales manager | Which opportunities need action, reassignment or an honest close-out? |
| Dispatcher | Where can we fit the right work without breaking existing commitments? |
| Purchasing or warehouse manager | What will prevent scheduled work from being supplied? |
| Marketing leader | Which sources produce customers the business wants? |
| Finance leader | What was booked, invoiced and collected, and where do those differ? |
| Enterprise leadership | Which business units, products or regions are growing profitably? |
Use the CRM's native reporting first if it answers the question. Evaluate a tool such as Power BI when the decision requires combining evidence from several systems. A separate reporting layer adds work and needs consistent definitions. Power BI
Bookings, revenue, invoiced amounts and cash collected are not synonyms. Neither are estimated margin and actual margin. If two departments define the same label differently, putting both numbers on a larger screen will not settle the argument. My KPI and dashboard design consulting starts with the decisions people need to make and the evidence those decisions require.
This connection between demand and delivery is also central to my growth consulting for home-service businesses. More leads are useful when the company can respond, sell and deliver the right work profitably.
The subscription
is the starting line.
Put your own numbers into a first-year planning budget. Defaults reproduce the illustrative example below; they are not vendor quotes.
Ongoing annual cost at these inputs: $8,440
- Licenses
- $3,600
- Setup + training
- $5,400
- Integration + administration
- $4,840
First year = 12 × monthly software + setup + training hours × hourly cost + 12 × monthly integration + 52 × weekly administration hours × hourly cost. Excludes taxes, payment fees, usage overages, financing, price increases and costs you have not entered. Saved time is not automatically cash savings.
What does a CRM really cost?
Price the system you will operate, not the entry plan you first clicked. Your total includes licenses, implementation, data cleanup, migration, integrations, training, internal administration, support, usage charges and the cost of running old and new systems during the transition.
The examples below are a September 26, 2026 snapshot of public U.S. pricing, not vendor quotes or equivalent packages. Confirm current editions, included users, billing commitments, taxes, add-ons and renewal terms directly. Promotions are excluded from the comparisons below.
| Published example | Price basis shown | What the number does not establish |
|---|---|---|
| Pipedrive Lite / Growth | $14 / $39 per seat per month, billed annually | Which plan supports every workflow and integration you require |
| Housecall Pro Basic / Essentials | $59 / $149 per month with annual billing; 1 / 5 users included | Your complete bill with optional services, payments and other requirements |
| Salesforce Starter / Pro | $25 / $100 per user per month; Starter monthly or annual, Pro annual | The cost of additional applications, implementation or a more complex deployment |
| Salesforce Core | $195 per user per month, billed annually | Your negotiated enterprise package or total operating cost |
| Dynamics 365 Sales Professional / Enterprise / Premium | $65 / $105 / $150 per user per month, paid yearly | Field-service, ERP, integration or other licensing requirements |
| ServiceTitan / Buildertrend | Request a scoped quote | A reliable total inferred from someone else's implementation |
Sources: Pipedrive pricing, Housecall Pro pricing, Salesforce pricing, Microsoft pricing, ServiceTitan pricing, Buildertrend pricing.
HubSpot's sales pricing page also illustrates why onboarding deserves its own line: the page lists required one-time onboarding fees of $1,500 for Professional and $3,500 for Enterprise. Those fees should not be mistaken for a complete migration and implementation quote. HubSpot pricing
Three examples of the arithmetic
Five Pipedrive Growth seats at the listed annual-billing rate equal $2,340 per year before other costs. One hundred Salesforce Core seats at the listed rate equal $234,000 per year in base licenses. Neither calculation tells you which product the organization should buy.
Here is a separate, hypothetical small-business budget, using invented inputs rather than a vendor estimate:
| First-year item | Illustrative calculation | Cost |
|---|---|---|
| Subscription | $300 × 12 months | $3,600 |
| Configuration and migration | One-time project | $4,000 |
| Internal training time | 40 total staff hours × $35 | $1,400 |
| Integration service | $100 × 12 months | $1,200 |
| Ongoing administration | 2 hours/week × 52 × $35 | $3,640 |
| Illustrative first-year total | Before taxes and other fees | $13,840 |
The subscription is only $3,600 of that example. Internal time is still a cost when nobody sends you an invoice for it. Year two would differ because some setup costs disappear while administration, subscriptions and future changes continue.
The return should also use honest arithmetic. If an illustrative system costs $600 a month and a genuinely additional completed job contributes $300 after incremental delivery costs, two such jobs cover that monthly amount. That excludes setup recovery and other benefits or costs. Do not count revenue as profit, claim every recorded sale was caused by the CRM or count the same improvement twice.
Saved hours are valuable when they reduce expense, release useful capacity or improve the working day. They do not automatically become cash savings. Enterprise business cases need the same discipline, even when the spreadsheet has more zeros.
Ask for a complete quote
Request the proposed editions and modules, named user roles, user counts, usage allowances, onboarding scope, migration scope, required integrations, support, implementation responsibilities and assumptions. Ask what changes at renewal, how additional users or contacts are charged and what it costs to export your data when you leave.
Get the software quote and the implementation statement of work. “Onboarding included” may describe training sessions while data cleanup and custom integrations remain your responsibility. Ask what is explicitly excluded and what would trigger a change order.
Implementation time is part of the buying decision
Opening an account can take minutes. Establishing dependable working habits takes longer.
As planning allowances, I would initially reserve roughly one to three weeks for a tightly scoped basic setup, four to twelve weeks for a modest rollout with migration and a few integrations, and three to nine months or more for a complex multi-team program. These are advisory starting assumptions, not vendor promises or industry benchmarks. A phased multinational transformation can take considerably longer. Scope, data quality, team availability and approval requirements determine the actual schedule.
Start with representative real records. Choose one team, service line or branch for the pilot. Include a person who does the work every day, not just the person approving the purchase.
For a contractor, test an inquiry through estimate, acceptance, scheduling, completion and payment. For an enterprise, test representative account structures, regional rules, exceptions and downstream transactions. Importing a clean sample is useful; it is not proof that a decade of duplicate records will migrate cleanly.
Define acceptance before launch: records arrive correctly, responsibilities are clear, essential reports reconcile, permissions work, staff can perform their jobs and failures have a recovery process. Keep an export and rollback plan. Decide when the old system becomes read-only and how historical records remain accessible.
Training should use actual tasks: enter an inquiry, revise a quote, record a lost opportunity, reschedule a visit, find an account's service issue. Give the system a business owner after launch. “Everyone owns it” often means nobody fixes the broken automation.
How to recognize overkill, underbuying and an AI distraction
An expensive platform is not automatically overkill. A cheap platform is not automatically sensible. The question is whether the extra capability addresses a meaningful requirement and whether your organization can operate it.
Warning signs of overkill include months of custom development for ordinary workflows, elaborate lead scoring on a tiny pipeline, several overlapping tools entering the same data and a system that requires expertise the business has no plan to retain. Buying for an acquisition that might happen five years from now is different from preparing for a signed expansion next quarter.
Underbuying has its own signs. People retype orders, dispatch lacks equipment history, the warehouse cannot reserve stock, management cannot separate branches and critical permissions are missing. Choosing the cheapest subscription can move the expense into mistakes and manual labor.
Before replacing an existing CRM, examine fields, stages, ownership, integrations and daily habits. If the product can do the work but nobody agreed on the process, a migration may simply give the same confusion a new address.
AI deserves the same scrutiny. Summaries, draft follow-ups, assistance finding records and suggested next actions can be useful. Test accuracy, access boundaries, review steps and usage cost. Begin with suggestions people can inspect before allowing an agent to change commitments, pricing, orders or customer records on its own.
If an AI feature saves three minutes drafting a message but requires five minutes checking it, you have bought a very confident delay. Judge the completed task, not the demonstration.
Make every vendor demonstrate the same work
Choose two or three credible candidates. Give each the same scenario and ask your actual users to perform the important tasks. A sales representative navigating a perfectly prepared account is not the same as your estimator working from a phone beside a jobsite.
Use a weighted scorecard tied to your priorities. One reasonable starting point is workflow fit at 30%, usability at 20%, integrations and data at 20%, total cost at 15%, and administration, security and support at 15%. Adjust those weights before seeing the demos. Treat essential requirements as pass/fail gates; a high total score should not excuse a failed requirement.
Ask each vendor to show:
- A new inquiry captured, assigned and followed up, including a duplicate and an existing customer.
- A revised quote, an approval and the accepted scope passed into delivery.
- A material shortage, schedule change or other exception relevant to your operation.
- A lost opportunity with a meaningful disposition and a future opportunity with a dated next action.
- The exact accounting or operational integration, including error handling.
- The owner's dashboard and the daily user's working screen.
- A usable export of contacts, opportunities, activities and relevant documents, with limitations identified.
- The proposed plan, full cost, implementation responsibilities and acceptance criteria in writing.
Ask who will maintain every custom feature. Ask what is available today. A roadmap item is not a demonstrated capability.
Questions worth answering before you buy
What is the best CRM for contractors?
For a small service business, I would begin with Jobber and Housecall Pro. For roofing, JobNimbus and AccuLynx deserve a look. For project-heavy construction, evaluate JobTread or Buildertrend and, where the requirements fit, Procore. The best candidate depends on whether the main problem is sales, dispatch, projects or a combination.
When does Salesforce make sense?
Salesforce deserves serious consideration when configurable sales processes, complex relationships, permissions and integrations justify the investment and the business can support ongoing administration. It should be evaluated against the actual scope, including simpler options when those can do the work.
Can a CRM handle materials and warehousing?
Some broader platforms include inventory functions or connect to operational applications. Do not assume a customer database is a warehouse system. Test purchasing, receiving, allocation, picking, returns and financial consequences in the proposed configuration.
Should marketing and sales use the same CRM?
They need consistent customer identity, handoffs and outcome information. A shared platform can help, but well-governed connected applications can also work. Buying one logo does not automatically resolve different definitions or unclear responsibilities.
Do we need to replace software that employees dislike?
Investigate why they dislike it. Too many fields, unclear stages, poor training and broken integrations may be repairable. If the product cannot support essential work without unsustainable customization, replacement becomes a more credible option.
What should I budget beyond the subscription?
Include setup, migration, integrations, training, internal staff time, administration, support, add-ons and usage-based charges. Compare first-year and ongoing costs, and ask for written assumptions. The contract and implementation scope matter more than a generic online estimate.
Bring the business problem to the conversation
I help businesses work out what needs to happen before choosing the technology that should support it. That includes customer acquisition, lead handling, sales processes, CRM requirements, marketing, reporting and the handoffs into operations.
Sometimes the answer is a better tool. Sometimes it is fewer tools. Sometimes it is deciding who is supposed to call the customer back.
Whether you run a contracting company, a regional operation or a complex enterprise team, bring the current workflow, the recurring frustrations and the outcome you want. I can help define requirements, compare credible options and identify where specialist implementation support belongs.
Discuss your CRM and business systems with Rob or explore CRM and AI-assisted sales enablement consulting.
The first question will still be: What are you trying to do?