❌

Normal view

I think business software got the implementation model backwards

I've spent quite a few years working with CRM and business software, and one thing keeps bothering me.

The software itself is often not even the expensive part.

It's everything around it.

Consultants. Implementation projects. Workshops. Custom configuration. Data migration. Training. Then months later you're still adapting your company to the software you bought.

I always wanted something much simpler:

sign up, bring the data you already have, answer a few questions about how your company works, review what the system proposes, and start.

No consultancy just to get started.
No custom code for every company.
No €50k implementation before you know whether the product even helps you.

And I also don't really want 15 separate SaaS tools anymore.

My ideal model is one platform with a small number of apps, like Sales, Support and Operations, sharing the same customers, work, automation and context underneath.

AI should mostly remove setup and admin friction. Not be another chatbot bolted onto the side.

So I've been building around a few principles:

  • onboarding should take minutes, not weeks
  • importing existing data should be normal
  • software should adapt to the company
  • configuration should replace customer-specific code
  • you should be able to start small and add more later
  • AI should prepare and configure work, while people stay in control

I'm not really looking for feedback on a feature list. More interested in whether this underlying idea matches how other people experience business software.

If you could replace your CRM / business software tomorrow, what would stop you?

The price?
Migration?
Implementation effort?
Losing your current processes?
Getting the team to adopt another system?

Curious which one is actually the biggest blocker.

submitted by /u/Efficient-Accident96
[link] [comments]

What would it actually take for you to switch CRM? I'm testing a different approach to migration and configuration.

I've worked with enterprise CRM systems for years and keep seeing the same trade-off: simple systems eventually become limiting, while powerful systems become expensive and complicated to configure.

I'm exploring a different architecture.

Instead of building another fixed CRM, the underlying platform consists of configurable objects, fields, relationships, pages, permissions, automations and reports.

Sales would just be the first module. Support, Projects, Planning, etc. can extend the same underlying customer and business data.

The AI doesn't generate software or arbitrary code. It can only configure capabilities that already exist in the platform.

So you could say:

"Add contract value to companies, put it next to ARR, and create a follow-up when an opportunity stays in Proposal for 7 days."

The system creates a plan → shows exactly what will change → validates it → you approve it.

The part I'm most interested in is migration. Rather than asking a company to make a big-bang switch, the idea is to analyze the existing CRM, map its objects/fields/processes, preview the new setup and eventually allow teams/modules to migrate progressively.

I've attached a visual explaining the concept.

I'm specifically NOT looking for "cool idea" feedback. I'd like to know: what would make you refuse to switch to something like this? What would I have to prove before you'd trust it with your real business data? And which part of this sounds less useful than I think it is?

submitted by /u/Efficient-Accident96
[link] [comments]
❌