Acme CRM
It sits in an inbox
You paid for a click. The platform emails a notification, or drops it in a spreadsheet somebody downloads at eleven. By the time a person rings, the prospect has already spoken to whoever answered first.
Sales CRM for teams that work the phone
Every lead lands on the board. Every call lands on the lead.
Leads arrive straight from Meta and Instagram, Google Ads, your website form and your Telegram bot — seconds after someone fills in the form, not the next morning when somebody exports a spreadsheet. Every call that follows attaches itself to the right person by phone number. Nobody types anything twice.
5
lead sources wired in, with nothing to build
25
reports ready to run on day one
52
permissions, so a rep sees only their own book
661
automated tests behind every release
Why teams move
The lead is not lost. It is just nowhere useful.
Most sales teams do not have a lead problem. They have a twenty-minute problem, a phone-log problem and a Monday-morning problem — and all three cost the same thing.
The call goes unrecorded
The number was rung from a mobile, so nothing about it exists in the CRM. Was it answered? Was it the third attempt? Nobody knows, and the lead gets called twice by two people or not at all.
Monday is guesswork
Which source actually pays for itself? Who is sitting on leads they have not touched in a week? The answers are in the data and reachable only by somebody willing to spend an afternoon in a spreadsheet.
End to end
What happens between the click and the close
One path, and every step of it is already built. No integration platform in the middle, no nightly job, nobody re-keying a name.
Someone fills in your form
On Instagram, on a Google lead form, on your own site, or in a chat with your Telegram bot.
It is on the board in seconds
Named, with its campaign attached, in the first stage of your pipeline — and flagged if it looks like somebody you already know.
A rep picks it up and rings
The call comes back from your telephony provider and attaches itself to the lead and the rep, with duration, outcome and the recording.
You can see what it was worth
Won revenue by source, first-response time by rep, calls answered against calls made — all standing reports, not a data project.
Pipelines
A board that tells you what it is worth
Drag a lead across and the stage, the status, the probability and the close date all move together — because they are one action, not four fields somebody has to remember to update. Each column carries its own count and its own weighted value, so the number at the top of a stage is the number you would forecast from.
- Separate pipelines for leads and for deals, each with its own stages and win probabilities.
- Stages can rot: set a limit, and a lead sitting too long tells its owner so itself.
- Converting a lead creates the contact, reuses the company if you already have it, and opens the deal — in one step, keeping the lead so your source reporting survives.
- A rep's board shows a rep's book. The totals at the top match it.
Inbound
Five ways in, and none of them is a spreadsheet
Point a channel at your workspace's own address, paste in one secret, and leads start arriving. Meta's lead ads, Google's lead forms, the contact form you already have, a Telegram bot, and a general-purpose shape that anything else — Zapier, Make, n8n, your own script — can post to.
- Every delivery is kept exactly as it arrived, so a lead is never lost to a mapping mistake — it can be replayed once the mistake is fixed.
- A retry from the platform returns the first answer instead of creating the same person twice.
- A new lead that resembles someone you already have is created and flagged. Nothing is silently refused.
- Campaign, ad and UTM details come across with the lead, so attribution is not a separate exercise.
Inside
A complete CRM, not a lead inbox
Everything a sales team needs after the lead arrives — and nothing it does not.
Leads, contacts, companies, deals
The four records a sales team actually uses, related properly: a deal knows its company, its contact and who plays which role on it.
Calls that log themselves
Connect your telephony provider once. Direction, duration, outcome and the recording land on the lead, matched to the right rep by number.
Reports that already exist
Twenty-five of them — revenue by source, closed-won by owner, first response, calls answered, overdue tasks. Filter, and export the whole thing to CSV.
Roles that hold
Owner, admin, manager, agent, viewer — with fifty-two individual permissions behind them. An agent's list, board and reports all show their own book.
Your fields, your views
Add the fields your business actually asks about — twelve types, validated on the way in — and save the filters your team keeps re-typing.
Nothing disappears
Deletes go to a trash you can restore from. Every change is written to an audit trail that says who, when, from what to what — in names, not database ids.
Reporting
The questions you ask every month, already answered
There is no report builder to learn, because the reports a sales manager runs are the same twenty-five everywhere. Pick one, set the dates, filter by owner or source or pipeline, and export it.
- Money: won revenue by owner and by source, lost revenue by both, expected revenue by close date.
- Effort: incoming against outgoing calls, answered against unanswered, call outcomes by rep.
- Speed: first response time on a lead, measured from when it was assigned — and reset when it is reassigned, because the new owner did not cause the old silence.
- Housekeeping: open, overdue and completed tasks, per person.
₹42.6L
Weighted pipeline, this quarter
31%
Win rate, on leads that actually closed in the period
14m
Median first response, from assignment to first outgoing call
8
Tiles on the dashboard, one request, no waiting
Your data
Built to be the system of record
A CRM is only worth using if the team trusts what is in it. These are not settings you turn on — they are how the product is built.
- Your workspace is your own
- Every record belongs to a workspace and is fenced there by the database layer, not by remembering to add a filter. A workspace that needs its own database entirely can have one.
- Duplicates are surfaced, never enforced
- The same person enquiring twice is normal in a lead business, so nothing is refused. Matches are shown to you — including on the way in from an ad — and merged when you decide.
- Two people editing at once cannot overwrite each other
- A save that would clobber someone else's change is refused and shown the current version, so the conflict is resolved rather than silently lost.
- A retry is not a duplicate
- A form submitted twice on a bad connection, an app resending a queued write — the second one returns the first result instead of creating a second record.
- You are told how long things are kept
- Every retention window is written down, adjustable, and applies only to what the system generates about itself. Nothing a person created is ever removed automatically.
- Run it where you like
- Docker Compose, a single command, on your own server. MySQL, PostgreSQL, MariaDB or SQL Server. The API documents itself and every endpoint is callable from the browser.
See it running on your own numbers
Thirty minutes, your pipeline, your lead sources. If it is not obviously better than what you are doing now, we will say so.