01 — The problem
Where off-the-shelf CRM software stops fitting your sales process
Most teams don't lack a CRM. They lack one that matches how they qualify and close. Stages don't reflect your exit criteria, custom fields pile up, and what matters lives in a spreadsheet next to the CRM: renewal dates, partner-sourced deals, territory rules and discount approvals.
The result is double entry between the CRM, the quote sheet and finance. Exceptions, like a parent account with several buying entities, get handled in email threads nobody can report on.
02 — What to build
What your CRM app should track
Accounts and contacts with your fields: segment, territory, parent company, buying role.
Opportunities with your own stages, exit criteria, value and close date.
Activities and next steps, each with a named owner.
Deal desk approvals that route discounts above your limit to a sales manager.
Sales-to-success handoff with a checklist completed before an account changes owner.
Roles
reps see their own book, managers see their team, finance reads closed-won deals only.
Pipeline views by stage, owner and quarter (see our sales pipeline app guide).
03 — How to build it
How to build a CRM with Henosia
Create a private project
It's a sandbox; nothing goes live until you publish.
Add representative mock data
CSV exports of accounts, contacts and deals with your real column structure.
Connect a database so the app works against structured tables, not loose files.
Describe the CRM in Plan mode
The agent asks clarifying questions and proposes a plan. Nothing is built until you choose to build.
Build a first version and test it with a few reps
Fix stage logic and edge cases with new prompts.
Publish with access control tied to your company email domain and app-level roles.
An example Plan-mode prompt for a CRM builder session:
Plan a CRM for our B2B sales team using the attached accounts, contacts and deals CSVs.
Stages: Qualified, Discovery, Proposal, Negotiation, Closed Won, Closed Lost.
Reps edit only their own deals; managers see their team; finance sees Closed Won read-only.
Discounts above the limit in pricing_rules.csv need manager approval before Proposal.
On Closed Won, create a handoff checklist for customer success.Paste it into a private Henosia project in Plan mode. The agent asks questions and proposes a plan first.
04 — Before you go live
Decisions to make before real customer data goes in
A first version can come fast, but production use needs clear answers. Who owns the customer data and the app? Which roles edit deals, and which only read? Who approves publishing and later changes?
Scope integrations with email, quoting or finance per system, data direction and access level. Henosia can work with data connections and API-based data, and more point-and-click connector interfaces are on its roadmap. You own what you build.
Start a private project in Henosia, load a sample of your pipeline, and plan your first CRM version with your sales team in the room.
Start a private project05 — FAQ
Frequently asked questions
How much does a custom CRM cost?
It depends on scope: how many objects and roles you need, which systems it must integrate with, and how much testing real data requires. Henosia shortens the build part, because a domain expert can plan and iterate on the app directly. Integration work, testing and ownership still need time and budget.
Do I need developers to build a CRM app?
Not for the first version. A sales ops lead can describe stages, fields and roles in Plan mode and build without writing code. For integrations with core systems, write access to other tools or complex security requirements, involve IT or a technical builder before you publish.
Is customer data safe in a CRM built with Henosia?
Projects start as private sandboxes, and published apps use Henosia Authentication, with access based on your company email domain, app-level permissions and optional IP restrictions. Your IT team gets an overview of apps, builders and integrations. Confirm data handling and security requirements for your specific setup before loading real customer records.
What is the difference between an AI CRM and a custom CRM built with AI?
An AI CRM is usually an off-the-shelf product with AI features added. A custom CRM built with AI is your own app, where AI helps you plan and generate it around your stages, fields and approvals. You decide what it does, and you own what is built.