Category guide
CRM software
The five questions every team asks before buying a CRM, answered — without needing to want our product first.
Start here
The five questions that come up before buying
Roughly in the order people ask them.
What is a CRM?
The definition, the parts, what it actually does — and what it doesn't.
What is a CRM?CRM buyer's guide
Seven criteria, and the questions to put to any vendor — including us.
CRM buyer's guideFree CRM
How far a free plan gets you, and where paying actually starts.
Free CRMPersian CRM
RTL, Jalali dates and Persian documents — translated interface versus built Persian.
Persian CRMCloud or on-premises?
Hosted versus your own servers, and a simple test for which you need.
Cloud or on-premises?
The arguments
Why we think about it this way
The four situations this product came out of. Each is an argument, not an introduction.
The account that went quiet
An absence is not an event, so no system raises it on its own.
The account that went quietWhen someone leaves
The account knowledge goes with them — unless it was attached to the account.
When someone leavesThe attachment nobody can find
Having a document is not the same as being able to use it.
The attachment nobody can findThe pipeline is a view
A pipeline filled in by hand reports optimism, not reality.
The pipeline is a view
And then, the difference we argue for
Everything above is about the category, not about us. Here is PulseUp's claim: most CRMs are a customer database and a pipeline, and both work on one condition — that somebody keeps entering things. In practice, that condition is the one that fails.
Our premise is that teams don't lose deals because they lack a pipeline; they lose them because the organisation forgets. So instead of asking for more input, we put the memory somewhere else:
- A feed on every contact and engagement
- Documents read and indexed
- Tasks that come out of a note or a voice memo
- Pulse, which brings a quiet engagement back on its own
42 days since anyone recorded anything
Kavir Steel
Stage 4 of 9 — Fieldwork
Common questions about CRM
What's the difference between a CRM and an ERP?
A CRM looks outward — customers, sales, follow-ups, service. An ERP looks inward — finance, inventory, production, HR. Plenty of organisations run both and integrate them. If your question is “who is looking after this client?”, the answer belongs in a CRM, not an ERP.Does a four-person team need a CRM?
It depends on cycle length, not headcount. If weeks or months pass between first contact and outcome, and several people talk to the same client in between, you need a shared memory. A four-person team on a six-month cycle needs one more than a twenty-person team selling on the spot.How long does a CRM implementation take?
It depends how much of the work you insist on defining on day one. A heavy rollout with custom processes takes months. Our approach inverts that: import contacts, start leaving notes that week, and let the pipeline and structure emerge from real work rather than being specified ahead of it.Where is our data kept?
Your choice. The hosted version runs on infrastructure inside Iran, and self-hosting is a first-class option rather than an expensive exception. Self-hosted, the licence verifies offline and the language model can sit inside your own network.What if we genuinely keep our current CRM current?
Then you do not have the problem we solve. We say that plainly, because the opposite claim collapses in the first demo.
Try it on your real contacts
The free plan has no time limit. Import your contacts and see when the first thing you'd forgotten comes back.