Reading view

I built a crm spending months on it I need feedback to continue

Hi everyone

I have spent months to build crm for small agencies and real estate now I need few people to test my crm and give a feedback or opinions and say what is broken in the crm or what is missing in the crm

It is very simple to use and simple ui to understand and free to use not credited card or payment required to use it

Test it and give a feedback and opinions

Crm.hero-industries.in

Feedback and opinions is must

submitted by /u/Exciting_Initial_362
[link] [comments]
  •  

What I learned building a CRM for field-sales SMBs (and where the big CRMs miss)

I spent the last few months building Griddus CRM — a CRM made for small and medium businesses anywhere in the world, with a visual pipeline, accounts, contacts, tasks, field visits, geolocation check-ins, and a layer of AI (lead scoring, sentiment analysis, and follow-up email drafting).

I set up a free demo environment — no account, no strings attached:

Griddus CRM

Accessing the main website, click the DEMO button.

All data is fictitious and is periodically updated. I am open to honest feedback (praise and, especially, criticism) — the goal is to make it truly useful for sales teams in their daily work.

What do you think? What's missing for a CRM for SMEs to be worthwhile?

submitted by /u/ar_silva
[link] [comments]
  •  

I’m building a CRM specifically for home-service businesses — Pobalt

I’ve been building Pobalt around a problem I kept seeing with home-service businesses: their customer management and their actual day-to-day operations often live in completely different systems.

Pobalt is designed to bring both sides together:

• CRM & customer management
• Jobs & work orders
• Scheduling
• Invoicing
• Team management & permissions
• Automations
• Business dashboard

The workflow I'm aiming for is simple:

Customer → Job → Schedule → Team → Invoice

All connected in one system.

I’m the founder, so I want to be transparent that this is my own product.

For people who work with CRM systems: what's one feature you think most CRMs still get wrong?

submitted by /u/kinfemichael_tilahun
[link] [comments]
  •  

True question: what is it about your CRM system that gets your staff really frustrated?

I'm a developer in the initial stage of building a CRM — before writing any code, I'm trying to find the users of these solutions for now.

No intentions to make a pitch here. I really need to know what is wrong.

Here are a few issues I've heard from people that I talked to:

- Pay-per-seat pricing that causes headaches in scaling

- Manual logging of the activities feels like doing the second job

- Documentation and email correspondence exists everywhere but not in the CRM

- Artificial intelligence is useless or demands transferring your data to some third-party

However, I want to hear your opinion:

What does your CRM fail completely? What is that issue you hear from your team during every stand-up?

Additional question: did data privacy or "Where is our client data actually stored?" become an issue ever? Or, probably, this is a non-issue in reality?

Every comment helps. Even the single one liner will be good.

submitted by /u/devttp
[link] [comments]
  •  

For those who build/implement CRMs for clients: do you see real estate (or other niche) owners leaning custom or off the shelf?

For the devs/consultants here who've actually built these for clients: in your experience, do real estate owners (or whatever niche you work in) usually end up wanting something custom, or do they just take GHL/Zoho/HubSpot and configure it?

What tips them one way or the other, budget, missing features, or just not wanting to deal with a dev long term?

And if you've built custom for a client, did it actually hold up, or did they end up wishing they'd just used an off the shelf tool?

submitted by /u/vexabots
[link] [comments]
  •  

I built a CRM specifically for relationships that start on Reddit

I’ve been using Reddit for customer acquisition, feedback, and talking to founders for a while, and one problem kept coming up:

Reddit is great for starting conversations, but terrible for remembering and organizing all the people behind them.

You talk to someone today, they comment again next week, you DM them later, and eventually you have dozens of usernames with no idea who was who or what you talked about.

I used to manage all of this in spreadsheets.

So I built Bantico, basically a CRM around Reddit relationships.

It helps you:

  • Find potential customers already talking about problems your product solves, asking for recommendations, or looking for alternatives.
  • Keep people and conversation context together, so you know who someone is, what you’ve talked about, and why they might matter.
  • Organize potential customers and relationships instead of keeping Reddit usernames scattered across spreadsheets.
  • Track your interaction history so you can see previous conversations and know where you left off.
  • Use Watchlists for people who look interesting but aren’t ready right now, so you can keep track of them instead of forgetting them.
  • Know who to follow up with as relationships develop over time.
  • Keep beta testers, potential customers, community members, feedback conversations, and eventually paying customers in one place.

The basic idea is that a Reddit post or comment might be the first interaction, but the person behind it can turn into a much longer relationship.

So instead of treating every Reddit conversation as an isolated interaction, Bantico helps you build context around the person over time.

Would love to know if anyone here is currently using a traditional CRM for Reddit-sourced relationships, or if you’re still handling this manually with notes/spreadsheets.

submitted by /u/No-Entertainer8410
[link] [comments]
  •  

Is "easiest to use" really about the software, or about how disciplined you are in month one?

Every few weeks, we see a post in this (or a similar) subreddit asking which CRM is the easiest to learn. Why people ask this is understandable. Nobody wants to sink a whole week into onboarding just to abandon the software later. But after seeing many teams go through the onboarding process, we believe that "easiest" might apply to more than just the tool’s interface.

The teams that struggle with the implementation and onboarding process almost always try to import their entire contact history on day one, build a pipeline with nine stages (because that's how their process "really" works), and turn on every notification and automation they can find before anyone has even touched a single deal. Then, two weeks later, the system feels like a second job, and they blame the tool.

The teams that stick with it and succeed actually do the opposite. They start by importing only a small portion of contacts they currently work with, keep the first pipeline to just a few stages, and don’t add any automations until the team has understood exactly which repetitive tasks are worth automating. Those teams may not necessarily describe the software as simple, but they'd likely describe their own approach as restrained.

This could be why CRM adoption stats are typically so low. It's not that the tools are secretly all terrible. It's just that the task of setting it up properly is treated as a weekend project instead of a month-long process. By the time teams are frustrated, they assume it's a product problem instead of a pacing problem.

Has anyone else seen the same pattern? Did switching to an “easier” tool actually fix adoption for your team, or did it just delay the same mistakes by a few weeks?

submitted by /u/nutshell_crm
[link] [comments]
  •  
❌