// The situation

CRM recommendations for a small service based business I am looking for CRM recommendations for a small business (3–4 employees across sales, marketing, and operations/service tickets). **Sales side:** We have one sales rep and one SDR. The SDR makes a high volume of outbound calls, so we need native calling from within the platform (not a bolt-on), with calls automatically logged against the lead and AI transcription attached. We trialed Close CRM and loved it for exactly this, it's excellent for sales and SDR workflows. Loved how you can see all the emails associated with a lead on the platform. Close is really simple and light-weight. **Post-sale side (where we're stuck):** Once a deal is won, we issue a service contract tied to a customer location. The contract captures the scope of work, contract type, and the staff assigned to it. These are living documents: staff get swapped out, one-off visits get added, materials/supplies get added. We need a full audit trail of those changes, plus the ability to upload confirmation documents to the record. We also run periodic quality inspections that need to be tracked back to the location. **Inventory and pricing:** We buy supplies from vendors against a master supply list, and we need visibility into vendor price changes so we can reflect them on customer invoices. Basic CPQ would cover this so nothing elaborate. All of this lives in Excel today and has become an administrative nightmare. We're officially ready to move it into a CRM, and Close doesn't handle the post-sale side well. **What else matters:** - **Configurability** — we need to relabel standard objects and create custom objects (if needed) as we go. - **Reporting** — should be easy to build with the ability to report on multi-nested objects as needed - **Document generation** — for contracts and related paperwork. - **Storage/record limits** — want to be confident we won't hit a ceiling on record counts. - **Marketing** — we don't run campaigns today, but I'd like the option to grow into it on the same platform. -**UI** - simple UI and nothing crazy or complex. I also want to be able to configure page layouts with clicks and not code. It should be dummy proof. I'd strongly prefer a single platform covering sales, ops, and marketing rather than stitching tools together. I don't want to manage integrations at this size. Would especially appreciate hearing from anyone running a recurring-service business with similar requirements. Thanks!

The verdict · Aug 11, 2026

Yes.

You need a CRM — but not one CRM for everything.

What's really going on

You have two different businesses under one roof. Close nailed the SDR side because outbound calling is a transactional sales problem. Your post-sale world — service contracts tied to locations, staff assignments, materials, inspections, audit trails — is field service operations. Those are different data models. Every "one platform to rule them all" pitch is going to force one side to feel bolted-on. Usually it's the ops side, which is exactly the side breaking you today.

What to do instead

  1. Jobber (check current pricing) — built for recurring-service businesses. Client → property/location → job → visits → materials → invoice is native, not a custom object you have to invent. Quality inspections and photo uploads attach to the location record out of the box.
  2. Keep Close for sales (check current pricing) — you already love it, the SDR workflow works, and swapping it out to chase "one platform" will cost you calls booked. Hand off to Jobber when the deal is won.
  3. Zapier (free tier, then check current pricing) — one automation: Close "won" → create Jobber client + location. That's the only integration you have to manage. Do it this afternoon: in Close, tag a test opportunity "Won"; in Zapier, use the Close "Opportunity Status Updated" trigger and Jobber's "Create Client" action.

What you're being oversold

The advice you're about to get is HubSpot or Salesforce with custom objects for contracts, locations, and inspections. On paper it checks every box you listed. In practice, a 3-4 person team building nested custom objects, page layouts, and CPQ logic in HubSpot spends six months configuring instead of running the business — and still ends up with a contract record that's worse than Jobber's built-in one. The "no integrations at your size" instinct is right in spirit and wrong in this case: one Zap is cheaper than one wrong platform. Staying in Excel another quarter costs you a swapped-staff dispute you can't audit, or a vendor price hike you eat instead of pass through.

When to revisit this

When marketing actually starts — real campaigns, not "someday" — reassess whether Close's built-in sequences are enough or you need a marketing tool alongside.

The part worth getting right

One judgment call decides this: how custom is your service contract, really? If your contracts fit Jobber's client → property → job → line-items shape with room for notes and attachments, you're done — buy it this week. If your contracts have structure Jobber genuinely can't hold (multi-year escalators, complex SLA tiers, parent-child location hierarchies across a customer), then Jobber will frustrate you inside 90 days and you're in HubSpot custom-object territory after all. Getting this wrong means a migration in a year. Which shape are your contracts?

Honest opinion · No affiliate links · public Get your own →

Did this actually help?

A binary signal so we know which verdicts are landing — and which ones aren't.