I've been building and sharing a Notion CRM template for solo business owners.

But I'm still struggling with the part that actually matters: getting the first sale.

For those of you who have sold software, templates, digital products, or services:

What was the thing that finally got someone to buy?

Was it more traffic? Better positioning? Social proof? Better targeting? Something else entirely?

I'd genuinely appreciate any advice.

I work for a local humane society and we’re looking for a new donor management system. We currently have Network for Good and we’ve way outgrown it.

Looking for recommendations. Who do you use and what do you like about it? So far we’ve done a lot of research with Bloomerang and EveryAction. Personally, I’m hard leaning towards Bloomerang.

A big thing for us is the automated communication workflows and the ability to easily import bulk data from our animal management system. Currently we have about 11k constituent profiles and we’re growing everyday.

My team just finished a project that ate our whole quarter but honestly it's one we're proud of merging two companies' CRMs into one system after an acquisition, without losing historical data, breaking active pipelines, or making the sales team relearn everything from scratch. Duplicate records, conflicting automations, two totally different tagging philosophies, the works.

It's done now and it's clean. Which means we've got bandwidth opening up and are looking for the next thing that's actually hard. We are US based with excellent customer service.

To be clear about who we are , we're not prompt-and-pray vibe coders. We're developers who've been doing CRM/automation work for years, and we like the projects most agencies won't touch because they require actually understanding the business logic first.

If you are dealing with a mess, reach out, happy to help

Hello

I built lead operating system for *REAL ESTATE* that asks the question to the lead qualify them, and also follow up them, and update the dashboard.

*Why should I pay for it, what's unique in this? :*

- so it has the each user memory

- Automated follow-ups using the user's current_state

*For example:*

_if the user gave the answers of only 2 Questions out of 5, then this system knows the progress of the lead. whenever the user will come 1 Month, 2 Months, even 2 years the agent have the memory of each of your leads and ask them a next questions no previous one that already asked. And if user Dissapeared after giving the answer of 2( Out of 5) questions then we sends him/her the follow up msg according to the lead current state_

- Lead qualification agent `(Hot, Warm,Cold Leads)` based on your rules like if you want only those lead whose timeline is within 1 Month (`Bcz timeline is more important than a budget`)

- And everything is on the dashboard

If anyone wants to see a demo please DM

Hello, we are selling Wi-FI networks in big scale buildibgs, which we as sales work 3 to 5 months to sign the contracts.

iam looking for the tool that suits my need of managing the tenders and sales activities such as:

1. Reminding us with RFP date submission.

2. Status and updates records.

3. Generate reports like total pipeline, team work load .. etc.

4. Reminding us for O&M or subscription renewals.

What is your recommendation?

Most small businesses don't fail because of one big mistake — it's usually a handful of small, overlooked ones that compound over months. Here's what I keep seeing:

1. AI-drafted emails miss context. A lot of businesses now use AI to draft sales emails, but without real context from the actual conversation, the output feels generic — no warmth, no direction, nothing that shows you were actually listening. Clients can tell, and it hurts response rates.
2. Post-call context evaporates. Promises made, objections raised, budget mentioned — all of it lives in someone's memory for maybe 48 hours before it's gone. Nobody writes it down consistently, and it's rarely thought of as an actual problem until a deal falls through because you forgot what you agreed to.
3. Fading interest goes unnoticed. A lead goes quiet, replies get shorter, follow-ups get pushed back — and there's usually no system flagging any of it until the lead's already gone cold.
4. CRM data turns to mush. Contact info comes in through email, calls, forms, LinkedIn, random Slack messages — and someone has to manually gather all of it from scattered platforms and compile it into the CRM by hand. That step alone is where most of the mess starts: fields get filled in inconsistently, half-updated, or skipped entirely because reconciling five different sources for one contact is tedious and easy to half-do. Six months in, your CRM is more noise than signal..

I ended up building a tool that tackles all four of these directly:

For #1, it pulls context, sentiment, and prior history into every drafted follow-up, so it's grounded in what actually happened, not a generic template.

For #2, you drop in notes after a call and it saves a structured summary, objections, and next steps straight to that contact — nothing gets lost.

For #3, it classifies lead temperature on every interaction and flags in a daily briefing when a deal's gone quiet or a lead's cooling off.

For #4, every field it extracts comes with the source it pulled from and a confidence score, and you approve or reject before anything touches your CRM — no more guessing what's accurate.

Looking for genuine opinions here.

How much do these type of features matter to you as a sales rep or a sales manager, or do they matter at all? How have these features impacted your overall performance and productivity?

Also, do you wish there was a crm feature that existed?

• Meeting transcriptions(multilingual), summaries and recommended next actions
• Automated meeting follow-ups
• Buyer intent signals
• Deal health and risk alerts
• Email tracking
• CRM updates suggestions
• Multichannel messaging/mail/call tracking

(given that all these features are ai based)

We spend a lot of time looking at how sales and revenue teams actually work day to day, and one thing shows up again and again: account plans get built with real care at the start of a relationship, then rarely get touched again once the deal is in motion.

It's an interesting pattern because it's not really a discipline issue on the surface. Most teams have a template, most reps do fill one out. The gap seems to be in what happens after, whether the plan actually gets revisited as priorities shift, new stakeholders show up, or the account grows.

We've talked to a fair number of teams about this, and the reasons vary. Some say updating the plan feels like overhead with no immediate payoff. Some say ownership is unclear once a deal moves from sales to CS. Some say the plan was never built to be a living document in the first place.

Curious how this actually plays out for people here. Does your team keep account plans updated in real time, or does it mostly get rebuilt from scratch at each review cycle? And if you've seen a team do this well, what made it stick?

A HubSpot workflow tip that isn't in any documentation, but should be:

The built-in "Test" button lies to you sometimes — not on purpose, but in a way that can send you chasing the wrong bug for hours.

Here's what happened: I was debugging a workflow that was only supposed to run for a specific set of accounts (a segment membership condition, nested inside an associated company record). I ran it through Test on a record that shouldn't have qualified.

Test said: success, would have enrolled.

Real enrollment history said: never enrolled, correctly excluded.

Same record. Same workflow. Opposite answers.

The pattern: Test tools that simulate a run are built to check straightforward field conditions well. Nested conditions — anything checking a property on an *associated* record, not the enrolled record itself — are where the simulation and the real trigger logic can quietly diverge.

The fix wasn't clever, just annoying: stop trusting the Test panel for anything involving associated objects, and instead pull a real record through the actual workflow and read the enrollment history logs directly. Slower, but it's ground truth — the Test tool is a prediction, the logs are what actually happened.

Small thing. But it's the difference between debugging the workflow and debugging a tool that's telling you the workflow works when it doesn't.

If you're deep in HubSpot workflows with any cross-object logic, worth checking which one you're?

I am thinking of making a web application for cafes and restaurants but my app will not have hundreds of features.

Instead, I'll just build those very important features that almost everyone needs, even small cafes.

And obviously the cost will be lower than the big giants.

So should i actually get into it?

Disclosure: I work on CRM/GEO research, not as a software buyer for my own company.

I am trying to understand how CRM admins, revenue ops, and channel ops people in Malaysia evaluate a legacy CRM replacement in larger organizations.

When the CRM touches customer-facing sales, service, and partner teams, what usually blocks the switch: data model cleanup, user adoption, reporting definitions, partner workflows, integrations, support coverage, or trust in AI-agent workflows?

I am especially interested in what you would ask vendors to prove before taking them seriously. No vendor links needed.

Lately i have been seeing everybody and their mom talk about MCP integration in their CRMs and genuinely want to know if they have been any useful other than gaining context

Also if this is a feature that would make you consider replacing your current CRM with a new mcp one.

Twenty eight days ago my cto pinged me on slack with a one liner that basically changed my job we are going all in on mcp for internal tools just imagine what this means for sales and marketing

I run go to market ops at a bootstrapped saas small team decent revenue nothing crazy. Up until this point my world was all quotas forecasts reports for the board plugging in yet another tool sales swore they needed and then abandoned

When we started playing with mcp internally it felt easy at first. We wired up our crm, support tool and product database so an internal agent could answer questions like show me all accounts where product usage spiked this month but nobody has talked to them yet

We already have a sort of gtm intelligence light setup cobbled together from call recordings plus basic ai summaries website intent data product usage pings crm fields nobody fills in

It works in the sense that everyone complains about it equally.

I am stuck now in this weird in between state. mcp is clearly going to be our internal wiring for anything new we build. At the same time, every vendor in the gtm intelligence space is pitching me a full replacement for what we already hacked together.