In the world of AI, would you buy or build a CRM if you had the option to do so.

Imagine you have your startup, 6 figures ARR, 200 clients, currently need basic datapoints.

Need to keep track of the following:
- accounts
- deals
- contacts
- email
- activities
- revenue

And most likely integrate other tech stack like slack, meeting notes, etc.

Many sales teams treat call review as a compliance exercise. A manager checks whether the script was followed, whether the price was stated correctly, and whether the required questions were asked. That is useful, but it does not explain why some conversations become sales while others quietly disappear.

The real value of call review is finding the patterns that affect the customer journey.

Start by defining the decision you want the review to support. Are you trying to understand where leads lose interest, which objections repeat, why follow ups fail, or which questions help move a deal forward? A clear question is more useful than a long scorecard.

Select calls by outcome instead of listening to random recordings. A small weekly sample can include a won deal, a lost deal, a lead that stopped replying, a repeated customer, and a conversation that ended with a clear next step. Comparing these groups usually reveals more than reviewing the same type of call over and over.

The review also becomes much more useful when it is connected to the CRM record. The note should capture the main objection, the customer goal, the promised next step, and the reason the opportunity changed stage. If the recording lives in one system and the learning stays in a private spreadsheet, the team loses the connection between conversation and result.

Keep the next step mandatory. After every meaningful call, the CRM should show what happens next, who owns it, and when it is due. This simple habit often improves follow through more than adding another complex rating category.

AI can help with the first pass by transcribing conversations, locating topics, and flagging unusual moments. It is good at reducing the amount of audio a manager needs to review. It should not replace human coaching, because the same phrase can mean something different depending on the customer, the industry, and the stage of the deal.

It also helps to separate quality control from training. If every review feels like punishment, representatives learn to protect themselves instead of improving the conversation. If the team studies both strong and weak examples, call review becomes a shared learning process.

A simple weekly routine can be enough:

1. Choose three call outcomes to review.

2. Use five clear quality criteria.

3. Record the next step in the CRM.

4. Discuss a few examples with the team.

5. Track the most common reasons for lost opportunities.

The goal is not to discover who made a mistake. The goal is to understand which part of the process makes it harder for a customer to move forward.

How does your team handle call review today? Do you listen manually, use automated analysis, or connect recordings to deal outcomes in the CRM?

I’m a business owner running an A4 copier paper distribution business, and I’m not a professional software developer.

I couldn’t find a simple software that really matched the way we operate, so I started building my own system.

I used AI-assisted development, mainly Claude, to turn the problems I was facing in the business into an actual working application.

It has gradually evolved into a system for:

* Field sales and route-wise customer visits

* Customer follow-ups

* Orders by paper brand, GSM and reams

* Deliveries and pending deliveries

* Partial payments and outstanding dues

* Sales executive tracking

* Repeat orders and customer history

* Inventory and stock movement

* GST billing and delivery challans

* Sales, collection and product reports

The interesting part is that I didn’t start with the intention of building a CRM product. I was simply trying to solve problems in my own distribution business.

Now I’m wondering whether these problems are specific to my business or whether other distributors face the same thing.

For people working in distribution/wholesale in a4 paper distribution business,

And if there was a simple system designed specifically around distribution workflows, would you actually find it useful?

I’m not trying to sell anything here. I’m genuinely looking for feedback from people who run or work in distribution.

I’d especially appreciate honest criticism including why you wouldn’t use something like this.

If anyone is interested in seeing what I’ve built, I’ll share it in the comments.

For a long time, we had one lead score. It mixed engagement with fit, which sounded reasonable until we actually looked at the leads it was ranking.

Someone from a company that would never buy could score highly because they were reading everything we published. At the same time, someone from an ideal account could visit once, book a call, and end up with a surprisingly low score.

The problem wasn't the formula. We were trying to make one number answer two different questions.

So we split it.

One score tracks engagement in HubSpot. The other looks at fit: firmographics, plus whether the company is actively hiring for the function we sell to. We use Coresignal for that part, mainly because the hiring data needs to be fresh enough to use as a signal.

A low-engagement, high-fit lead now goes into a different workflow from a high-engagement, low-fit one. Before, both could land in the same middle of the score range.

The annoying part was getting everyone to accept two scores. Sales wanted one number they could sort by. Fair enough, but the second score explained why some of the leads at the top weren't actually worth pursuing.

How are others handling this? One combined score, or separate scores for fit and engagement?

I help startups, small SaaS companies, agencies etc streamline their operations, automate support pipelines and build clean Hubspot workflows.

HubSpot admin at a small shop. Leadership wants a separate branded scheduling page for every rep × brand × pipeline stage combo. For us that math works out to ~70 links per person. Per. Person.

The stated justification is “measuring each link and how often they’re used” which, correct me if I’m wrong, is just… meeting outcomes and deal stage reporting? Things that already exist?

I proposed ~5 purpose-based links per rep (intro, review, follow-up, reschedule) with brand handled by a token. Apparently this is not how it was done at [prestigious former employer], where the 70-link matrix was allegedly “standard.”

So I’m taking it to the people. Has ANYONE here ever seen a real org maintain 50-70+ scheduling pages per user? What reporting does it unlock that outcomes/stages/properties don’t? And who was the poor soul maintaining it
?
Genuinely open to being wrong, but before I build the links and create the extra thousand workflow branches… help

I’ve been trying to find recs to try and convince my bosses to get us to switch CRMS because we use Method and it sucks soooo bad. It’s so clunky and really annoying to navigate for no reason, but as I’ve tried to find recs I’ve just found people also complaining about hating theirs lmao.

I recently transitioned my own business from HubSpot to GoHighLevel, largely because HubSpot gets expensive very quickly once you need the marketing features. The cost is also difficult to justify for many of the small-business clients I work with.

Financially, GHL makes much more sense, and I know it has a ton of capabilities. But compared with HubSpot, I’m finding it less polished, less intuitive, and not nearly as pleasant to work in.

So, help a girl out! For those who have made the switch:

• How long did it take you to get comfortable with GHL?
• What did you customize to make it feel cleaner and more organized?
• Are there any templates, snapshots, integrations, or setup tips that made the transition easier?
• What HubSpot features do you still miss or haven’t found a good replacement for?

I know aesthetics aren’t the most important CRM feature, but usability matters when you’re working inside it every day. What helped make GHL feel less clunky and more intuitive?

Can someone tell me why a company would choose to use HubSpot over GHL (HighLevel)? I've used both and cannot figure out why anyone would use HubSpot. It's not at all intuitive, and I haven't identified any feature that's better than GHL. I hate HubSpot, and when I have a client who has it, I dread working with whatever jerry-rigged system they've set up. Don't even get me started on websites built in HubSpot.

What am I missing?

For smaller events, we can usually get by with a laptop and printed attendee list. But once the numbers start climbing, the bottlenecks become pretty obvious, especially when badges have to be printed on site.

Last year, scanning wasn’t really the issue for us. The bigger problem was the manual badge process, which created a second queue at check in.

Curious to hear from others, at what point did you feel dedicated check in software became necessary? And did having on site badge printing actually make much of a difference?

I've built up an AI centric 100% free CRM and I am looking for feedback from users.

I built it after experiencing the difficulty of promoting B2B software without a large sales team. Lists are easy to obtain; understanding why a specific person should care is not. Presage connects recipient context, company signals, campaign intent and the sender’s value proposition to create relevant, human-approved outreach.

You can create your account and start using it without any credit card.

This is a weekly post for you to let out about something which happened this week for you in CRM that mattered: features, client requests that were either great or awful this week, and just generally chat CRM / CRM consulting chatter.

No self promo, just a place to share tales from the front-line of CRM!

We are currently scaling our B2B team and hitting a massive wall with our current setup. Up until now, we have relied on an all in one CRM platform to handle our CRM, email campaigns, landing pages and basic form tracking. On paper, having everything in one place sounded like the dream. In reality as our marketing campaigns have gotten more complex, the native marketing features inside our CRM feel clunky and limited. The landing page builder is frustratingly rigid, attribution reporting is a black box and advanced email workflows require awkward workarounds. We are considering moving toward a modern marketing stack by decoupling our marketing execution tools (using dedicated best of breed software for email, landing pages, and analytics) and feeding all that enriched data back into a core CRM. For those who switched from an all-in-one CRM to a modular modern marketing stack, was the extra flexibility worth the technical overhead?

The biggest mistake in the “SaaSpocalypse” thesis is treating all SaaS companies as if they have the same exposure to AI.

Salesforce’s latest earnings make me think that argument might be too simple.

Agentforce ARR is already above $1.5B and growing 240% YoY, while Salesforce itself is still growing revenue around 11%. So AI doesn’t seem to be replacing the platform. It’s becoming another thing the platform can charge for.

The part I find most interesting is the pricing shift.

Traditional SaaS basically charges for how many people use the software. But if AI agents are doing more of the work, companies can start charging based on usage or work completed instead.

So maybe the real divide isn’t AI vs SaaS. It’s platforms with deep customer data, workflows and integrations vs smaller tools that mostly sell a narrow feature.

The second group seems much easier for AI to commoditize.

A field with few recent values may still feed an old report, integration, routing rule, permission check, or quarterly workflow. Deleting it too quickly can create a silent failure; keeping every field forever makes the schema harder to understand and maintain. What evidence do you require before retiring one? A workable process seems to need an owner, usage checks across automations and exports, a deprecation period, a replacement mapping when definitions changed, and a recoverable archive of old values. How do you handle fields that are technically populated but no longer trusted?

Looking for a reliable, US-compliant dispatch platform for 100+ roofing subcontractors (no coding/self-hosting). Per-user pricing ($30-$50/mo) is a dealbreaker. The system must support US privacy laws by hiding saved client contacts from dispatchers and region-locking local managers. Subcontractors need an app showing only job details and ZIP codes, unlocking full addresses only after clicking "Accept". It must support direct assignment, broadcast dispatching, and US-compliant Twilio/VoIP call recording without premium phone plans. Any flat-rate or low-cost recommendations?

Hi everyone,
I am scaling a roofing business in the US with about 100 subcontractors across multiple regions. I don't need a sales CRM like HubSpot. I need a straightforward dispatching platform for booking and routing.

Note: Just to clarify, I am not looking for open-source software, self-hosted platforms, or frameworks that require coding, setting up servers, or hiring a developer to customize. I simply do not have the time or interest to deal with code or technical setups. I am strictly looking for a fully finished, out-of-the-box SaaS solution where all these privacy and dispatch settings can be easily configured right through the standard admin dashboard.

Must-have features:

Hide client info from techs: Techs should only see the job details and ZIP code. Full address and phone number must be hidden.

Job Board App: Techs need an app with [Accept / Decline] buttons. The full address should unlock ONLY after they click "Accept".

Manual + Auto Dispatch: Ability to assign a job directly or blast it to a local pool (first-come, first-served).

Region lock for managers: Local managers should only see jobs and contractors in their specific area. They shouldn't see data from other cities.

Hide client data from dispatchers: Once a manager enters a lead's info and saves it, that phone number/email should become hidden from their view so they can't copy my client list.

Cheap Twilio/VoIP integration: Need cheap call recording without overpriced built-in CRM phone plans.

Affordable pricing for 100+ users: Paying $30-$50/mo per contractor is a dealbreaker. Need a flat rate or cheap per-subcontractor pricing.

Hi everyone,
I am scaling a service-based business in the US with around 100 independent contractors (subcontractors) spread across multiple locations and regions.
Please note: I am NOT looking for a generic sales CRM (like HubSpot, Salesforce, or Zoho). I need specialized On-Demand Dispatch, Uber-like, or Field Service Management (FSM) platform built natively for booking, routing, and field operations.
Here are my non-negotiable requirements:

Strict Contact Masking for Technicians: When a job is dispatched, the technician must ONLY see the job description and the general area/ZIP code. The client’s full name, exact address, and phone number must remain hidden.

Actionable Mobile App: Technicians must use a dedicated mobile app with clear buttons to [Accept] or [Decline] the job. The exact address and phone number should only reveal themselves after they click "Accept".

Flexible Dispatching: The system needs to support both Direct Assignment (manager manually picks a tech) and Automatic Dispatching (broadcast to a local pool on a first-come, first-served basis).

Regional Manager Restrictions: I have regional managers. Each manager must be locked into their specific cities/regions. They should NEVER be able to see or access leads, jobs, or contractor lists from other regions.

Manager Data Blindness (Blind Entry): When a manager or dispatcher inputs new lead data into the CRM, they should work "blind." Once they type in and save the customer's sensitive details, those fields must immediately mask or hide from their view so they cannot copy the client list.

Affordable Telephony Integration: I need VoIP/telephony integration to record calls, but it must be cheap or free (like a direct integration with Twilio at wholesale rates or an external VoIP provider) [4.3]. I do not want to be forced into expensive built-in CRM phone upsells where I pay massive markups per minute [4.2].

Flat Rate or Cheap Subcontractor Pricing: Paying $30–$50/month for every single one of my 100 independent contractors is a financial killer.

We were paying for Apollo for email and Lusha for EU mobile, and on top of that a separate verification layer because the catch-all detection on both was sending us into bounce rates that were flagging our sender domains.

We consolidated the enrichment into a single waterfall query, a few of us had been testing FullEnrich already so we kept it, with no separate API calls per provider, and that's what got rid of the per-tool credit billing we had before.

Email coverage and verification held up well on the switch, and the hit rates tracked closely to what we were pulling across providers before, so the consolidation on email wasn't a downgrade.

The one thing that varies by region is EU direct dial in DACH and Southern Europe, since some of our clients target larger manufacturing contacts there, and EU mobile coverage is where we're still running more volume through before drawing conclusions.

Whether that's a configuration thing or just a coverage ceiling for certain regions, that's what we're still weighing before deciding whether a dedicated phone tool needs to come back into the stack.