Self-building CRM — "self build" feature concept
A friend dropped an idea that stuck with us — a CRM that builds itself
through prompts instead of manual configuration.
Concept
User describes what they want, CRM builds it:
- "Add a Probability field to the pipeline"
- "Create a view of leads with no activity this week"
- "If a lead doesn't reply in 3 days → flag for follow-up"
What we already have
- Plugin system (NestJS dynamic modules) ✅
- MCP server (CRM tools exposed to external AI agents) ✅
- AI Compose (email drafts enriched with Pokelo RAG context) ✅
- `metadata: jsonb` on leads/contacts = custom fields without migrations ✅
What's missing
- An agent that modifies the CRM via prompts (fields, views, automations)
- A2A endpoint for crm-agent
Reference
bb IDE (getbb.app) — an IDE that builds itself through prompts.
Same concept, applied to CRM.
Open questions
- Should MVP be prompt-based view/config only (no code generation)?
- MCP server → Hermes skill → A2A — which order?

p/aperture-7
p/runevr
p/producthunt
p/google-cloud-platform
p/raycast
p/kuc-kuc
p/offiai
p/lasso-11
p/kodlo
p/ai-context-flow
p/many-displays
p/reso
p/dino-kids
p/dex-by-exmergo
p/htmldrag
p/jev
p/supabase
p/murror
p/nexupira
p/jot-2-0
Replies
Be the first to reply
Have a question or a thought to share? Add a comment above to start the conversation.