r/WhichCRM

Background context: We are a printing business mainly my father dealt business since last 40 years. we mainly do wedding invitations and other custom printing for individual customers.

We are dealing in shop visiting customers and we also run ads on instagram facebook whatsapp and tiktok. the customer lands in our chat and we deal them manually through chat and they place order where maybe some advance amount is paid and we fulfill order and take remaining balance.

Now the issues i am facing are related to check which ad is working better and where i am lacking to close the deals and since mostly deals are closed on chats which CRM is better for my process.

Thanks for the guidance.

I run a sealcoating and line striping business, and I’m looking for an estimating/proposal software with package options.

What I need is one estimate/proposal for one property with three options, and each with its own editable line items, quantities, unit prices, and subtotal. I have a price book, and I can enter measurement details specific to a property manually to get the final cost. But I cannot do it for multiple package options.

I need to present all three options to my clients in ONE PDF, not just a digital version where they can click and choose the option they desire. Quote IQ has a similar option but you cannot "drag and drop" a customizable service you offer.

As every property has a different area size, I cannot enter a fixed price per option and I want to show clients what they are paying for a bit more in detail, not a single line item.

Has anyone found such software?

Hi there,

We are a small team that is looking for a CRM.

We sell consumable products to our customers that are industrial businesses like mining companies or companies that do maintenance for mining companies.

Our sales timeline can be of breakdown nature where something is needed asap or it could be a long burn where we are doing an upgrade on site where it could take 6-12 months.

Our customers are all return customers once we have trading accounts setup and we live up to our end of the bargain.

Account management is big part of our business, as our sales people meet with the same people on a plant to check in and make sure.

I've spoken to my sales guys and we came up with the following that ties in with the above:

• As the sales manager I want to be able to see what they are working on and whether they are keeping in touch with customers.
• Also keeping track of any actions required out of each meeting would be ideal.
• Log calls - in person, via phone or Teams.
• Relationship management/tracking is more important than messing around with a pipeline. Many sales are so quick it won't register on a pipeline. Other sales take forever and so it will just sit in a pipeline and not move. We want to track the relationship more than what is in the pipeline.
• We also want something that is straightforward and not too complex. I'd prefer something with less features than something that has all the bells.
• I also want something that integrates with Outlook emails and calendar.

I hope this is enough to provide me with some options.

Lately I’ve been thinking about how much ChatGPT changed user expectations around software.

You type what you want.
It understands context.
It reasons.
It takes action.

But then you open most CRM/FSM/operations software and it’s still:

• dashboards
• filters
• forms
• tabs
• manual workflows
• endless clicking

So I’m curious:

Has anyone here found software that actually feels conversational and agent-driven instead of just “AI-powered” as a feature?

Something where you can genuinely say:

• “reschedule tomorrow’s jobs”
• “follow up with overdue estimates”
• “assign the nearest available tech”
• “handle after-hours calls”

…and the system actually understands and executes it.

Feels like business software UX hasn’t caught up to where AI is heading yet.

Hi all,

I’ve been playing around with Claude Code for the past month and building whatever came to my mind. I just wanted to see how powerful it is. I haven’t tried building a CRM specific to my business needs though.

And I wanted to ask if any if you maybe created a CRM with Claude Code? If so, how did it work for you?

Thanks

We use hubspotpot but new leads come in with just name + email. SDRs waste 20min per lead digging on LinkedIn, finding company size, tech stack, and recent funding. We tried ZoomInfo Enrich but it’s $15k/year and overkill.

I need something that auto-enriches new HubSpot contacts with firmographics + intent signals, then routes hot ones to Slack.What’s the lightweight stack for this without enterprise contracts?

There's a conversation happening right now in the field service world, and most contractors aren't part of it yet — but they should be.

New CRM and field service platforms are appearing almost weekly. Many of them are being built rapidly using AI tools and sold with real enthusiasm to pressure washers, plumbers, roofers, landscapers, and HVAC techs who are just trying to run cleaner, more organized businesses. The messaging is compelling: fast, modern, affordable, built by someone who gets the trades.

And honestly? A lot of these tools look great in a demo.

The part that doesn't make it into the pitch is what happens six months in. What happens when something breaks. What happens when your crew is standing at a job site at 7am and the app won't load. What happens when an invoice disappears, an automation stops firing, or a customer never gets their follow-up because the system silently failed overnight.

That's the conversation nobody is having loudly enough.

Speed is not the same thing as reliability

Mike Vidan, co-founder of QuoteIQ, has been building in this space for years — and he's watched the AI-built SaaS wave hit the field service industry up close:

"Most discussions around 'AI-built SaaS' focus entirely on speed. Very few talk about operational responsibility. Building software with AI is pretty easy. Maintaining mission-critical software for thousands of businesses is not. Especially in field service management and CRM systems, the real challenge is not generating code. The real challenge is building the infrastructure around the code — production monitoring, database management, QA processes, deployment safeguards, support operations, and a bunch of other stuff."

His co-founder Justin Rogers puts it this way:

"The dangerous part is that AI dramatically compresses the distance between idea and production, but it doesn't compress operational maturity at the same rate. Anyone can grab a MacBook and build an app now. The real question is: who's there six months later maintaining it, supporting customers, fixing issues at scale, and keeping businesses running when something breaks?"

That's the gap. AI can accelerate the build. It cannot accelerate the years of operational experience, team infrastructure, and institutional knowledge required to run software reliably at scale.

What "vibe-coded" actually means for your business

The term "vibe coding" has taken off in developer circles. It refers to building software by prompting AI tools and assembling the output fast, often without deep technical oversight of what's actually happening under the hood. For side projects, internal tools, and prototypes — totally fine. Great, even. It's genuinely impressive what one person can build now.

The problem surfaces when vibe-coded software becomes someone else's business-critical system.

Because here's what's actually at stake when a field service CRM goes down:

• Estimates and quotes — gone or inaccessible
• Invoice records — corrupted or lost
• Customer communication history — wiped
• Payment workflows — broken
• Recurring job schedules — failed silently
• Operational visibility — completely dark

That's not a software inconvenience. That's revenue. That's customer relationships. That's your reputation on the line with people who trusted you to show up.

And it's not hypothetical. These failures happen. They happen to established platforms with full engineering teams. The question is what happens next — how fast it gets resolved, who owns it, and whether anyone is even awake when the alert fires.

The solo operator problem

Here's where it gets real.

Imagine a CRM platform being maintained by a single person. Maybe they're a contractor themselves — pressure washing on weekdays, pushing code on weekends. Maybe they built the tool to scratch their own itch and started selling it to their community because why not, it works for them.

That's a cool story. Genuinely. But now imagine that person's platform is running the operations of 500 or 1,000 service businesses. And something breaks on a Tuesday morning.

Who handles the urgent production issue? Who manages the infrastructure when traffic spikes unexpectedly? Who responds when automations start silently failing across the board? Who troubleshoots email deliverability when invoices stop reaching customers? Who monitors uptime around the clock — and what's the actual response time when it drops? Who maintains and evolves the database architecture as the product grows over time? Who's on the phone when a contractor calls in a panic because they can't access three months of customer records?

These aren't edge case questions. These are table stakes for any software platform serving businesses that depend on it to operate. And they require people — not just code.

As Vidan puts it: "Those operational layers are what separate a real software platform from a quickly assembled application."

AI changes what makes engineers valuable — it doesn't eliminate the need for them

To be clear: this isn't an anti-AI argument. AI-assisted development is real, powerful, and genuinely changing what's possible. Nobody serious is arguing otherwise.

The argument is about what AI does and doesn't change.

It doesn't change the fact that software operating at scale always — always — encounters edge cases, regressions, unexpected dependencies, and operational failures over time. Not because the developers were careless. Not because the AI generated bad code. But because that's what complex systems do when they interact with the real world at scale.

Vidan again: "I don't believe AI replaces software engineers. I believe it changes what makes an engineer valuable. The strongest developers will likely be the ones who combine AI-assisted speed with a deep technical understanding."

The analogy for contractors is pretty direct. Better equipment didn't eliminate the need for skilled tradespeople — it raised the floor and changed what mastery looks like. A pressure washer with a brand new rig and no experience is still going to strip paint or blow out a window seal. The machine doesn't know what it's about to ruin. That judgment still lives with the operator.

Same thing here. AI lowers the barrier to building software. That means comprehension of the system — its failure modes, dependencies, and operational demands — becomes the differentiator. Not the speed of initial assembly.

What to actually look for before you commit

When you're evaluating a CRM or field service management platform — especially a newer one — go beyond the feature list. Go beyond the demo. Go beyond the founder's follower count or how relatable their content is.

Ask real questions:

• How many people are on the engineering and support team?
• What does your uptime history look like, and where can I see it?
• What's your incident response process when something breaks at 2am?
• How long has the platform been running in production at scale?
• What's your data backup policy and recovery time if something goes wrong?
• Is there a dedicated support team, or is support handled by the person also writing the code?

None of this is meant to scare you away from newer tools. Innovation is good. Competition in this space is good. Contractors deserve better software than what the legacy platforms have offered for years.

But you also deserve to know what you're actually signing up for. Your estimates, your invoices, your customer relationships, your payment workflows — that's your business. That data represents years of work. It deserves to live on infrastructure that was built to handle it, maintained by a team whose full-time job is keeping it running, and supported by people who are there when things go sideways.

"AI can absolutely accelerate execution. But it still can't replace ownership of the system itself. The code is only one piece of the system. Be careful what you trust with your business." — Mike Vidan, co-founder of QuoteIQ

If you've had an experience — good or bad — with a field service CRM going down at a critical moment, drop it in the comments. Contractors need to hear these stories from each other. That's how this community actually protects itself.

Mike Vidan - QuoteIQ Co-Founder

I’m running a 4-man crew doing resi and light commercial, and I’m hitting a wall with software. Everything I find is either a massive system designed for a 50-truck fleet or a glorified calendar that doesn’t help with the actual workflow. A customer (rightfully) called me out for slow estimates, and I realized it's because I'm re-keying data three times between the field and the invoice. Anyone found a "middle ground" app that actually connects estimates, field updates, and billing without the massive overhead?

Why is every field service app so complicated? I need a dead-simple way to handle scheduling and billing for my 4-person crew. No bloat, just the essentials.

Small business owners: What are you using that actually saves you time instead of wasting it?

Hey guys!

I've worked in b2b sales since over 10+ years, we're building a CRM tool for founders (just like myself) with a small team. This one is a mobile app, with a built in AI agent. We're still in the beta test phase, might be rolling out the app pretty soon.

But im posting here for the first time to know if anybody would like to try it out. I need some honest feedback from actual b2b sales managers/reps/founders who're struggling with current sytems. If you're using google sheets and want to upgrade, or if you're using heavy tools, with no context, maybe this one is for you. Our main goal was to unify all the msgs- linkedin DMs, whatsapp chats, etc into one mail box, and then we added more features, like a outbound lead management tool.

Ugh, hopefully this doesn't sound like a promotion. But hit me up/comment if someone's interested. Thanks a bunch!

I’ve built https://leavy.io/ - a simple leave management tool for SMEs.

It came from a common issue I kept seeing: managing time off in Excel works early, but breaks once you hit ~15–20 people (overlaps, no visibility, messy approvals).

I have a couple of teams are using it.

I’m keeping it simple and focused (not another bloated HR tool).