EDIT: soluzione trovata con Trackords

Ciao a tutti gestisco una concessionaria di automobili e parallelamente dei noleggi auto, sono in cerca di un software/servizio web based, gratuito possibilmente, che nello specifico mi dia la possibilità di creare anagrafiche dei clienti e per ognuno di loro inserire tipo di noleggio auto, date di scadenze contratti, etc.. con una funzione di reminder per ogni scadenza che arrivi anche solo via mail al mio indirizzo aziendale. Sapreste aiutarmi?

Almost all CRMs claim some degree of Outlook integration, but the reality is that “Outlook integration” covers a broad range of connection types. At one end of this spectrum, it means a sidebar that lets you copy an email into a record by hand. At the other end, email, calendar events, and contacts move in both directions without anyone touching them.

The gap between those two typically reveals itself a few weeks after rollout. Reps who must click to log each email, stop doing it, and the CRM slowly becomes a record of whatever the most diligent person on the team remembered to enter. Managers then see a quiet pipeline while the inbox tells a different story.

An effective approach is to decide which behaviors need to be automatic before you reach the demo/trial stage. Email logging tends to come first for most teams, because it’s a repetitive action for reps. Calendar sync is next, so meetings scheduled in Outlook end up on the correct deal without the need for a second step. Contacts are important too, especially when someone updates a phone number in one system and expects it to be updated in the other system.

There's also the question of what "two-way" really means and what it covers. Some setups push data in one direction on a schedule and call it “sync.” That holds up until two people update the same record. That’s when you discover which system wins.

Teams sometimes underrate how much the integration shapes habits. If working inside Outlook is already how reps spend their day, a CRM that meets them there will typically be used. One that asks them to context-switch will likely be used during pipeline reviews and ignored the rest of the time.

For those of you running a CRM alongside Outlook right now, what's the one behavior you'd insist be fully automatic before calling it a real integration? And which manual step turned out to quietly kill adoption?

Spent the last few months watching outbound teams drown in overly complex CRMs that require a PhD just to log a call, while smaller operations default right back to messy spreadsheets that break the second things scale.
The reality is most software is built for enterprise bloat, not for people who just want to manage pipelines and actually close deals without fighting their own tools.
Got tired of the friction and started building a cleaner alternative focused purely on fast workflows and zero dashboard clutter.
Keeping it in a private waitlist right now to iron out the feedback before a wider rollout. If you are dealing with the same pipeline headache and want to take a look
Curious how everyone else here tracks their deals are you sticking to custom sheets, or have you found a setup that actually doesn't slow you down?

Consider a CSV used to update existing contacts by record ID. Some phone cells are blank because the source has no new information; others are blank because someone deliberately removed an incorrect number. Those are two different instructions, but the file looks the same.

Ignoring every blank preserves good data, yet also preserves numbers that should be cleared. Treating every blank as a deletion risks wiping fields the export simply didn't include.

I'd lean toward a separate, explicit clear-field instruction and a preview that shows additions, replacements and deletions before import. For example, a blank phone cell would leave it alone, while a clear_phone flag would remove it. That adds a little work for whoever prepares the file.

How do you make that distinction in a repeatable bulk-update process, and who reviews intentional clears? I'm interested in the import convention and review step, rather than a CRM recommendation.

a few weeks ago i ran email accuracy tests on apollo for our outbound campaigns and the results are... not great. we're seeing like 15-20% bounces on what apollo marks as "verified" emails, especially for smaller companies and startups. our deliverability is taking a hit and our domain rep is suffering.

i know apollo has a huge b2b contact database but i'm starting to think quantity doesn't mean much if the apollo data quality isn't there. we're a team of 3 SDRs doing about 500 emails/day across different industries (mainly SaaS and fintech). need something that actually verifies emails properly, not just pattern matching.

my manager is already on my case about bounce rates so i need to figure this out fast. leaning towards Prospeo because they claim really high accuracy with real-time verification, but want to hear what others think before committing. also looked at ZoomInfo briefly but the pricing is absurd for a small team like ours. has anyone done side-by-side testing of apollo accuracy vs other email verification providers? what kind of bounce rates are you seeing?

Wanted some solid, unbiased feedback from everyday businesses that actually use CRM heavily.

The CRM side is completely free. No paywalls. No per seat fees, or anything like this. Free to use the CRM. Our main product is the Voice and SMS which we do charge for. But it’s not required.

oneearlybird.ai

We finally got into demand gen at a 50-person SaaS startup and really need to level up our targeting. We're burning through budget on spray-and-pray LinkedIn ads and Google PPC, and it's getting harder to justify the spend to leadership.

The big account based marketing tools are insane - 6sense quoted us $40k minimum, Demandbase was even worse. I get it, they have fancy predictive models and whatnot, but we're not enterprise. We just need to identify and reach the right accounts without bleeding money.

Apollo is another option we're looking at but their intent data seems more limited from what I've seen in demos. Someone on our team also mentioned Prospeo as a possible fit for the contact enrichment side - pulling verified emails and mobile numbers for decision makers at target accounts. That plus some kind of intent signal would basically cover what we need.

Anyone here running ABM on a budget? What abm platform are you using that doesn't require a second mortgage? We're a small b2b sales team so anything with a 6-month onboarding process is basically a non-starter.

Is it too hard to look for a crm that ties a team email, whatsapp, and instagram? And then has automating sequences, pipeline mgt, contact lookup and mcp?

I feel so lost haha

We've been going through a commerce platform eval after flagging that our current setup won't hold what we're planning to scale into.

And at every turn the SI we've been working with has been steering toward Salesforce Commerce Cloud, which makes sense given we're already in the ecosystem across CRM and CPQ.

But it's starting to feel like the SI recommendation and the platform recommendation are the same conversation dressed as two different ones.

The architecture argument checks out, the ecosystem consolidation case has weight, and I don't want to dismiss it, but when we started pulling on threads ourselves we found that the SI dependency varies a lot depending on which platform you choose, and that some of the alternatives come with pre-built retail logic that shortens the implementation scope considerably.

A couple of options that have come up on Reddit alongside SFCC, Scayle and Spryker, seem to handle SI involvement very differently, and what we're seeing is that platforms built from a retailer's own operating model need less custom assembly before they function, which changes the SI equation from how long will they be here to whether we need one at all.

So if you've been through a similar eval, did your SI recommend the right platform for your setup, or did you find that evaluating platforms independently gave you a different picture?

There are so many options and I genuinely don't know where to start. Every fintech looks the same on the surface. What do people actually use, and what made you pick it over everything else?

We’ve been building RiverX, an AI platform for building and customizing web apps.

One of the templates we’ve been working on is a CRM with the basic stuff you’d expect:

- Deal board with stages you drag deals between
- Dashboard with pipeline totals and a stage chart
- Companies, contacts and deals linked together
- Sign-up and log-in already included

The idea isn’t to compete with every CRM out there.

It’s more about having a solid starting point and then being able to say things like:

“Add a separate pipeline for renewals.”

“Add lead scoring and show it on the dashboard.”

“Create an approval step before a deal can move to Closed Won.”

…and have RiverX actually modify the application.
You can also customize the template yourself, or if you have a specific CRM workflow you want to build, we’re happy to help customize it for you.

We’re trying to figure out whether there’s value in this approach, so curious:

If you could change one thing about your current CRM, what would it be?

Idea is simple. We built our company on the basis that organisations want out from HubSpot but not to a small own built vibe CRM without proper security or CRM development.

We decided for an outcome pricemodel with unlimited seats and access to the full product so the only way we grow is actually if our customers grow.

DM if you want in on it :)

When I joined an IoT company, its sales team was managing the entire process in spreadsheets. The business had been around for about six years and already had product-market fit.

I’d been building SaaS products for three years. I wanted to try working in another industry, and the founder gave me responsibility for working with the sales team.

I started building a CRM from scratch. The first version was a Kanban board for tracking leads, which gave us somewhere to put the enquiries coming through Google Ads.

As I understood the workflow, I wanted the system to help the team continue working on each lead. Someone opening a record needed to see its history and understand the next action.

Normal WorkFlow--->

Our pipeline started at “acquired.” A new enquiry needed a qualification call about the customer’s requirements. Smaller deals went to sub-dealers because we had a minimum ticket size for opportunities handled by our team.

Suitable leads moved to “verified.” We estimated device requirements and conducted a survey, then prepared a quote covering the devices, installation, and other charges.

After sending it, the lead moved to “quoted.” The team followed up, sometimes every 10 to 15 days, until the customer sent a purchase order and we closed the deal.

That could take three to six months altogether.

Building around those stages brought up more work than I’d originally pictured. We needed to track the activities completed for a lead, understand why deals hadn’t closed, and see how many deals each salesperson had closed. I also added duplicate-lead prevention.

Then I added My Sauce --->

For initial qualification, I built an AI voice agent that called new enquiries and asked the qualification questions. An Decision Model to evaluate the answers and scored the lead.

We then assigned leads using deal value and the number each salesperson already had, with higher-ticket deals going to more senior people.

I connected the WhatsApp API so quotes could be sent from the CRM. We also added offline conversion imports, sending lead progress and closed-deal events back to Google Ads.

I enjoyed seeing the system grow around the team’s process. Each addition had a place in the journey from enquiry to purchase order, and I could understand why the team needed it.

I handled everything from design to deployment, with plenty of bug fixes and sleepless nights along the way. After the product had been stable for about a month, I couldn’t think of any new features to build.

So I started using the CRM as a member of the sales team. I handled acquisition and lead verification myself, doing the work the application was supposed to support.

I found 30 features we didn’t need. I removed them and added features people actually wanted. Using the pipeline myself helped me understand needs I hadn’t picked up while building it.

That was one of my biggest reflections from the project. The team couldn’t always put what they wanted into words. Sometimes you have to get involved in their day-to-day work to understand what should be added and what can be removed.

Does anyone use incentives to drive CRM user engagement (besides the obvious threat of getting fired if they don’t 😅)?

I work for a fun-loving company that wants to make CRM adoption more fun and engaging, rather than just another task on everyone’s to-do list.

Aside from cash bonuses, do you offer incentives or prizes to recognize your most engaged CRM users? Think company swag, gift cards, fun perks, or other creative rewards.

I’d love to hear what’s worked for your team

decided to try prospeo about 2 months ago for our outbound campaigns. we're a series A startup doing ~5k cold emails/week.

the good: their email finder is accurate. we went from like 18% bounce rate with our old setup (mixing LeadIQ + Hunter) down to maybe 3-4% with prospeo's data. the direct dials are real too - people actually answer their phones now which is wild. the weekly data refresh is nice since we target fast-growing companies where people change roles constantly.

the meh: their chrome extension is pretty basic compared to something like LeadIQ. works fine for grabbing emails from linkedin but thats about it. also wish they had more integrations - we use outreach and had to jerry-rig it through zapier which was annoying.

pricing is reasonable, way cheaper than what we were paying for credits before. we burn through about 4k lookups monthly between email verification and enrichment. main thing is you only pay for verified contacts which saves money compared to tools where you burn credits on everything whether the data is good or not.

overall its become our primary b2b data provider. not perfect but the data quality is noticeably better than the bigger players we tried. curious if anyone else has a prospeo opinion or experience worth sharing

If your team wants a new CRM because nobody trusts the pipeline, give it a month first. In close to twenty years of sales and ops, I’ve watched teams switch and end up with the same complaints in a new tool. The bad habits get exported along with the contacts.

Here’s what I’d do instead. Check ten deals. Pick ten open ones at random and ask each owner: is the stage right, and will the next step actually happen? Write down how many are wrong.

Hide the junk fields. If half the entries say “tbd”, “n/a”, or just a period, reps are filling it in to get past the save button. Take it off the layout, but don’t delete it.

Define each stage in one sentence, like “Proposal: they have our pricing and confirmed they got it.” Right now every rep probably has their own definition.

Ask reps what they type twice. Email and calendar sync plus a simple Zapier or Make automation usually covers it.

Give each rep one saved view of deals with no next step or an overdue one. Their day starts there, and so does your pipeline meeting. Updates in side spreadsheets don’t count anymore (people will push back on this one).

After a month, check ten deals again. If it’s better, keep going. If not, and the tool really is the blocker, like it won’t connect to your phone system or billing, then switch. You’ll go into the demos knowing what you need.

Disclosure: my team builds CRM automations and integrations, so weigh that in.

I’ll be around in the comments. If you’ve cleaned up a CRM before, what made the biggest difference?

tl;dr: before switching, spend a month fixing fields, stages, and data entry. Check ten deals before and after.

Hi everyone,

We're the team behind LeadMino, a sales CRM we're building for growing teams.

We're interested in learning how small businesses and sales teams actually manage their pipelines day to day.

A few areas we're curious about:

• Keeping track of leads across different channels
• Remembering follow-ups and daily activities
• Managing deals through different sales stages
• Getting a clear view of pipeline progress

For those working in small sales teams, which of these is the biggest challenge? Or is there something else that takes up more of your time?

We'd love to hear how you're handling it today, whether that's with spreadsheets, an existing CRM, or another workflow.

Not looking to promote anything here, just interested in learning from real experiences.

we run a small outbound sales team, about 12 agents. most of the day is spent dialing lists manually and a lot of time gets wasted on no-answers and busy signals. the managers keep pushing for higher connect rates but the agents are already burned out from constant redialing.

we recently started testing an auto dialer to cut down the dead time between calls. it’s helped a bit with volume but now the complaints are about the pace feeling too fast and some leads getting dropped mid-transfer.

how do you guys handle the balance between higher dial rates and agent burnout? and for teams that switched to predictive or power dialing, did talk time actually go up or did quality drop?

I work at a property management company. We handle about 30 buildings and around 4,000 tenants.

Tenants keep calling to ask about repair requests and lease documents. Our front desk spends hours on this every day.

A portal where each tenant sees their own requests and files would save us hours.

That’s why I’m thinking about CRM portals and app builders like Softr. Maybe it’s not meant for a company our size, so I’m asking for your opinions.

IT also wants single sign-on for staff and a record of who accessed what.

But before I pick one, how should I set up the data and access rules?

I run Axenda, a small HubSpot and RevOps consultancy. Here’s the checklist I use when reviewing an existing automation setup.

Before building anything new, I check:

- Can two workflows update the same property? If so, which one should control it?
- Does every lead have an owner and a next action?
- Do pipeline stages have clear entry and exit criteria?
- Can someone explain why a contact enrolled in a workflow?
- When replacing an old workflow, which dependencies need to be checked before switching it off?

A useful starting point is a simple inventory: workflow name, trigger, properties it changes, dependencies and person responsible.

That makes it easier to spot conflicts before adding more automation. Workflow count alone doesn’t tell you whether the system works.

How do you document dependencies in your portal? A spreadsheet, naming conventions, or something else?