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

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?

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?

Martin Anderson-Clutz at Acquia recently made the case that Drupal is becoming something more specific than a CMS with AI features.

A governed AI harness.

The argument is that Drupal already has most of what agents need:

• Structured content
• Granular permissions
• Editorial workflows
• Revision history
• Centralized governance
• Typed fields and entity relationships
• Canvas AI and the Context Control Center

The funny part is that many of these are the same things that historically made Drupal feel cumbersome to human editors.

The platform famous for asking people to complete seventeen fields may have accidentally spent two decades preparing for robots.

That is legitimately interesting to me.

If an agent is working across hundreds of pages, multiple brands, regulated workflows, and several languages, complexity may stop being baggage.

It may become the safety system.

I covered the argument in the latest episode of Headless:

YouTube
Spotify
Apple Podcasts

Drupal Association article for anyone who wants the source directly:

https://www.drupal.org/about/ai/initiatives/blog/from-headless-cms-to-ai-harness-what-i-took-to-decoupled-days

For people actively building with Drupal AI, does the “AI harness” framing match the reality yet?

Or is the positioning currently ahead of the product?