[ Removed by Reddit on account of violating the content policy. ]

Recently heard about a salesperson who had to fill in two additional fields just to get a deal amount to appear in a report.

I'm building a lightweight CRM for small B2B teams and trying to keep things simple.

What's one thing you wish your current CRM did differently?

[ Removed by Reddit on account of violating the content policy. ]

Hi everyone,
I work as a Marketing Manager At The Facilitators, for FixPRO CRM. It is a repair shop CRM. I want to tell you this first, so you know I am not a normal user.

I am asking because many shop owners tell me the same thing. They do not want to pay every month. They want self-hosted repair shop software. They want one-time purchase repair shop management, pay once and done.

Some people also search for open-source workshop management software. FixPro is not open source. It is a paid script. But you get the full source code, and you keep it on your own server.

It is a Laravel repair shop CRM script. It is made with Laravel 11 and PHP 8.2. Many PHP repair management scripts are old, so I think this is a good point. The installer is easy. It makes the database for you in a few steps.

If you are looking for a repair shop management system PHP or a repair CRM PHP script, please tell me what you found. One bad thing is that you need your own hosting. So it is not for everyone.

I have two questions:

1. Do you like to pay one time and host it yourself? Or pay every month?

2. What do you use now in your shop? Paper, Excel, or software?

I will answer any question. I will also tell you what FixPro cannot do yet.

Thanks!

[ Removed by Reddit on account of violating the content policy. ]

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!

At what point does WhatsApp stop being “just where customers message us” and quietly become a business's actual sales system?

I've noticed this pattern with growing businesses.

At first, WhatsApp is simple. A customer messages, someone replies, and the conversation ends.

Then things start changing.

More enquiries come in. Different people handle sales. Customers return weeks later. Someone asks for a quote and disappears. Another salesperson needs the previous conversation. Follow-ups depend on someone remembering them.

Suddenly, important business activity is happening inside hundreds of chat threads.

And that's where the interesting question starts:

Are you still using WhatsApp as a messaging app, or has it already become your CRM without you intentionally designing it that way?

The problem is that chat history isn't really a sales process.

You can have every conversation saved and still not know:

• Which leads are waiting for follow-up
• Who owns a particular conversation
• Which enquiries are genuinely sales-ready
• How many opportunities went cold
• Which conversations actually turned into customers

That seems to be the point where a WhatsApp CRM starts making more sense than simply adding another shared phone or asking the team to “follow up properly.”

I'm curious how businesses here handle this once WhatsApp becomes a serious source of leads and sales conversations.

What was the first sign that your WhatsApp process was no longer scaling?

For context, tools such as Replai are built around this shift from unmanaged conversations toward more structured WhatsApp customer workflows.

Would genuinely like to know what other teams use before reaching that point.

Not gonna lie ive been bouncing between a few diffrent strategies for b2b saas leads and curious whats working for others right now.

We're at 18k MRR selling to mid-market teams. Cold email used to be our bread and butter but response rates tanked hard this year. Now doing a mix of LinkedIn outbound (manual not automated), some content marketing thats starting to pick up, and testing paid search but the CAC is brutal honestly.

For cold outreach we pull contacts from Apollo and a couple other databases then personalize based on thier tech stack. Getting maybe 8-10% reply rates which feels low. My cofounder keeps saying we should try Prospeo becuase someone in his network swears by it but havent pulled the trigger yet.

What channels are driving most of your pipeline? And if your doing outbound, what kind of response rates are you seeing lately? Trying to figure out if we need to completely pivot our saas lead gen approach or just optimize what we have.

Loss reason, next step, close date, lead source — pick your poison.

Every CRM has at least one field everyone pretends is clean because the dashboard depends on it. Reps fill it because it is required. Managers read the chart because it is there. Then the business makes decisions off a value nobody would defend in a one-on-one conversation.

The weird part is that making the field mandatory often makes the report look better before the data gets better.

For teams that actually fixed this: what changed?

Did you remove fields, audit them against calls/emails, change who enters them, or just stop pretending some values belonged in the CRM at all?

I look after CRM reporting for a B2B SaaS team and I’m putting together our quarterly churn review. CS logs a cancellation reason for every account and there are notes from renewal calls and save attempts. That’s what we use to group the losses and explain them to leadership

For accounts marked low usage, I still want to know what changed in their day to day work and where that work went.

The notes don’t always get that far. We rarely speak to customers again after cancellation so the explanation entered at the time carries straight into the review. Some have been gone for a few months now and I’m struggling to tell how much of the story we ever got

I’m looking for GTM and growth roles where I can own the strategy, run the experiments and build the systems behind them.

I’ve worked with teams from EF and YC, alongside other funded startups. At Pavo, I was the sole engineer building the GTM platform used by a 14-person revenue team, with systems supporting a $660K+ sales pipeline.

Here’s some of the work I’ve built and run:

A Slack agent for messy CRM and pipeline operations. Sales context was scattered across conversations, calls and CRM records. I built an agent that reads those conversations, extracts deal information, updates Attio and assesses deals against a 13-signal health checklist. It also prepares meeting briefs, drafts follow-ups and surfaces stalled deals. The team could work from Slack while the system handled much of the CRM upkeep.

A D2C acquisition motion built around a brand audit tool. Built a research tool that analysed brands through their product catalogue, ads, reviews and technology signals. Used the audit as the entry point for a PLG-style acquisition motion at a major trade show. 70% of booth visitors booked a discovery call. The work covered the research, the offer and the path into a sales conversation.

ICP refinement and outbound across 129 campaigns. Worked on targeting, enrichment and personalised outreach across 12,800+ prospects. Used hiring activity and company signals to identify relevant accounts, then built messaging around a specific reason to reach out.

Campaign analysis that changed where we focused. Found a segment with an 8.3% reply rate against a 4.4% overall baseline and used that finding to refine targeting. The roughly 2× difference was between segments; it helped us decide where to concentrate the next round of outreach.

The infrastructure to keep learning. Built and live-tested a Botdog → Postgres → Attio pipeline to connect outreach activity, messages and replies to company records. That made campaign performance and follow-up easier to inspect.

I make build-versus-buy decisions around the workflow. Sometimes an existing tool is enough; sometimes a small custom integration saves the team hours. I want the team to understand and operate what I hand over.

What I can own

• ICP research, positioning and acquisition strategy.
• Outbound campaigns, messaging, follow-up and partnership experiments.
• PLG and audit-led acquisition motions.
• Funnel analysis, onboarding and conversion improvements.
• CRM operations, deal visibility and GTM automation.

Stack: Attio, Apollo, Clearbit, Sumble, Smartlead, Botdog, Fathom, Slack, Google Workspace, Meta Ad Library, Python, SQL/Postgres, APIs, Claude/Gemini, Docker and GCP.

Available immediately for remote GTM/growth roles, contracts or retainers. Based in India and available for US or EU business hours.

Agencies: open to white-label work and overflow execution, including research, outreach operations, growth experiments and client systems.

Happy to share my background and relevant walkthroughs over DM. Tell me what you sell and where the customer journey gets stuck.

Never dealt with business banking before and just realized we're leaving cash sitting in a checking account doing nothing. What should I even be looking for in a small business savings account to make sure we're not wasting runway?

I’ve been comparing plumbing software for my site, Tools In The Wild, and I’m sharing the main takeaways from each comparison here. This one covers plumbing CRM software. I used our desktop and iPhone testing notes, plus vendor documentation, to compare seven options. I focused on customer records, properties, and communication. I’d love to hear from people using these systems day to day, especially if there’s something I missed or alternatives you love.

One thing I paid particular attention to was managed properties. The tenant who needs an arrival update, the owner approving a repair, and the property manager handling the invoice may all be different people. Saving their contact details is only part of the job. The software also needs to make it clear who gets each message and where unfinished follow-up belongs.

Main things I cared about:

• organizing customers, properties, and the different people attached to a job
• finding previous work when a call starts with an address or phone number
• choosing service-update, estimate, and invoice recipients
• keeping follow-up visible and checking which plans include the required tools

Here’s my breakdown:

FieldPulse

FieldPulse was my overall pick for growing residential and light-commercial plumbing businesses. Multiple contacts, locations, related customer accounts, and custom fields give the office room to organize more than a homeowner’s name and one service address.

For example, you can designate the tenant as the job contact, then choose the owner for an estimate and the property manager for an invoice in the Email To field. Automated job messages follow the designated job contact.

The important catch is that Bill to Parent saves the billing party, with overrides on individual documents. It doesn’t save separate email-routing rules. The office still needs to select the correct document recipients before sending.

Custom fields can hold account references or property instructions, with visibility controlled by staff role. Mentions in job and estimate comments also support team communication. Pricing is a custom quote based on seats and configured products, and the flexibility works best when the office agrees on how to organize the records.

Housecall Pro

Housecall Pro has a more prescribed residential setup. With parent/child billing, a tenant saved as a sub-customer receives visit-status updates, while estimates, invoices, and receipts go to the billing parent by default. That can be convenient when the parent is also the person approving the work. If the owner is different from the billing parent, the office still needs to add the owner to the estimate email.

The linked tasks were useful for follow-up. From an estimate, you could create a task, assign it to a teammate, and mark it complete. That gives an outstanding call or return-visit follow-up a named owner instead of leaving it in a note that someone has to remember to check.

Jobber

Jobber is a good starting point for solo plumbers and smaller teams that want clients, properties, and previous work kept in a fairly simple structure. A landlord can remain the client while each rental house has its own property record.

Additional contacts can identify a tenant or the office administrator handling billing. However, marking someone as a billing contact adds their email alongside the main client’s email when sending quotes or invoices. It doesn’t replace the main recipient.

There’s also an access detail worth checking: additional client contacts get access to that client’s Client Hub. Adding a person for communication is therefore also an access decision. Custom fields are available on select plans, and pricing depends on the plan, team size, and billing commitment.

ServiceTitan

ServiceTitan makes the most sense when a larger plumbing company needs the paying account and physical service locations separated formally. A property management company can be the customer, with each building stored as a service location. A water-heater repair then belongs to the relevant building, while the customer record represents the billing relationship. Location-level installed-equipment records add context when someone returns to work on the same heater or pump.

The trade-off is administration. Records, permissions, and office procedures need consistent setup. A small shop mainly serving homeowners at a single address may have little use for that added structure. Pricing is quoted per technician, with the package and additional products determining the configured cost.

BuildOps

BuildOps is the stronger commercial option when customer relationships extend across properties, contacts, installed assets, and continuing service work. The property context stays connected when a service visit leads to a repair or replacement opportunity.

Its CRM+ module uses the same customer, property, and asset data as the operating platform. That keeps the building contact and service context available when following up on something like a pump replacement.

CRM+ is an add-on, so include it when pricing the relationship and opportunity tools. Pricing depends on crew size, trades, modules, and integrations. I’d look at it for a commercial plumbing operation rather than a residential owner mainly handling straightforward service calls.

QuoteIQ

QuoteIQ offers additional contacts on every plan, with a shared recipient picker for jobs, estimates, and invoices. An auto-add setting can attach a saved contact to new documents and jobs, which is useful when the same manager needs to stay involved.

Contacts, tasks, and sales opportunities have different plan requirements. Reminders & Tasks starts on Beginner, while deals and pipelines require Elite or Max. A follow-up task can have an assignee and reminder, so check the tier against the actual work your office needs to manage.

Equipment history is a separate limitation. Detailed heater or pump records rely on notes and forms, so a company organizing ongoing equipment service has different needs from one mainly organizing callbacks. Pricing is published by plan, with included user allowances and charges for extra users.

FieldEdge

FieldEdge suits established plumbing teams that want customer history connected to call booking, dispatch, equipment, and QuickBooks. Customer history and management are available across Select, Premier, and Elite, so basic record access isn’t limited to the highest tier. The package differences show up elsewhere. Select includes two mobile licenses, Premier four, and Elite six. The Consumer Management Portal is included with Elite and costs extra on lower plans.

I’d count the technicians who need mobile access and price the portal separately before comparing quotes. FieldEdge uses custom pricing, so the tier, mobile requirements, and additional products all affect the total.

I put the full comparison on my website if you want the detailed contact workflows, recipient rules, and plan differences.

I'm curious, I work in sales in the hospitality world. I would say 89% of my communication comes through email. If you work in sales or any sort of project management role. What is the breakdown one your day to day communication volume?

I'm working on a CRM/outreach product for small teams, and this is a step I'm trying to get right. This is research for the build, not a request for software recommendations.

Someone replies 'sounds interesting, send me some details.' You send the information. Now there's a positive reply in the inbox, but that doesn't necessarily mean there's a real opportunity yet.

What do you actually record at that point? Do you create a deal immediately, keep it as a conversation with a next task, or wait until you've confirmed something specific?

I'm especially interested in teams where the person handling the reply isn't always the person who follows up. What has to be written down so the next person can pick it up without rereading the entire thread? And what tends to get missed?

A recent example would help, with names and private details left out. I'd rather hear what you really do on a busy day than the ideal process in a CRM training guide.

CRM cleanup usually becomes a priority only when reports start showing inconsistent numbers, duplicates pile up, or outdated records affect campaigns. How can I maintain data quality throughout the year?

Do you rely on regular checks, automation, or quarterly cleanup projects? Who owns it in your team?

I've designed software to protect you from dialing or texting people outside of the tcpa calling hours. I'm really trying to show some comparisons between it and any other programs or crms that have similar features. Usually that's a dialer. If any of you are curious and willing to try the experiment, then the tests are simple:

Make a test lead and use a dummy phone number like (areacode) 555 0157. That range of numbers are not given to real people so they can be used in movies etc.... The area code you choose shouldn't matter since the service should go by state/zip with people moving around.

Set the state for RI zip code 02901 and try to call it after 6 pm EST. Your system should block you.

Set the state for FL zip code 32003 during the day and try to call it 4 times. It should block you on the 4th try.

Set the state for AL zip code 35004 and try to call it on Sunday. Your system should block you.

If any one of those goes through, then your system isn't blocking correctly. If all of them go through, then your system probably doesn't block calls based on state rules at all. 23 states are more restrictive than the federal guidelines. If you can call or text earlier than 8 am or later than 9 pm, then your system doesn't block Federal law either.

Please post the results here or send me a DM. I'll give you a free subscription to my software for a year for testing, but I don't need too many people to test each one so first come first served.

I'm throwing this out there as my team uses GHL but I hate the CRM and its clunky to use.

So I went down the path of using API's from it to custom build a layer that allows me to send notes back to GHL, search, and create daily call lists so much faster than GHL.

All of this was done with Claude Code.

If you're CRM has API's just build something custom that is tailored to your workflow and setup.

I am frustrated with every CRM marketing to me that they will save me time and increase productivity but as soon as I sign up I have to relearn their whole system and create workflows by their rules. What CRM frustrations do you have?

I can't be the only one who is fed up. Am I crazy?

Bill McDermott was pretty blunt on ServiceNow's results call. His pitch is that the old CRM was built for sales teams, and that service is where the customer relationship actually lives. He's openly talking about rip and replace, and says deployment times are now 30 or 60 days for a serious company at serious scale.

There are some numbers behind it. CRM showed up in 13 of ServiceNow's top 20 deals last quarter and CRM AI net new ACV tripled. HPE signed up for its Cloud and AI support services, and Stagwell is consolidating four legacy service desks across more than 70 agencies.

I'm sceptical of the 30 day bit. Data migration and integrations are what kill CRM projects, not the software.

Has anyone here moved service off Salesforce or Dynamics onto ServiceNow? How long did it really take?