Buyer's guideNo named competitors

What to look for in a CRM for a small sales team

The feature list on a CRM's homepage is never the reason a required field gets skipped six months in. Six questions about what actually holds under an import, a bulk edit, or a rushed Friday afternoon — plus Automix's own honest answers.

See what Jeet already does Read the technical docs

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

Before you buy

The homepage feature list is not where a CRM actually fails.

Almost every CRM on the market advertises a pipeline, lead scoring, and reporting — the feature names converge because the job converges. What does not converge, and what a demo rarely shows you, is whether the rules a CRM enforces on its main entry-field screen still hold when a lead arrives through a CSV import, a bulk stage move, an API call from another tool, or an automation nobody is watching in real time. That gap — a rule that exists on paper but has a way round it — is where a 'required field' quietly stops being required.

This page will not put a vendor name next to a checkmark, ours or anyone else's — that table is easy to rig and stale within a quarter. Instead, six questions worth asking of any CRM you evaluate, and an honest answer to each about how Jeet, Automix's sales pipeline agent, actually behaves.

Ask what it refuses to do

A tool with no refusals has not thought about the edges of your business.

These are specific refusals in Automix's own code, named so you can ask the same question of anything else you evaluate.

It will not let a bulk stage move or an import skip a stage's required fields

Single moves and bulk moves are routed through the same gate, so there is no faster, less-checked path for moving fifty deals at once than for moving one.

It will not close a deal lost with no reason on record

The lost transition itself is refused until a reason is supplied — the field is not optional the way it is on most pipelines, so the win-loss report is built on data that actually exists.

It will not open a second live opportunity for a contact who already has one open

One open lead per contact is a schema-level constraint, not a soft warning a rep can click through — the same customer cannot become two pipelines running in parallel.

Evaluation criteria

7 questions to ask any vendor in this category.

Ask these of Automix and of anything else on your shortlist. The status pill is how the honest answer scores today, not a claim of perfection.

Does a required field on a pipeline stage apply on every path a deal can move — not just the manual screen?

Why it matters. A CRM that enforces 'you cannot mark this stage won without a close date' on the screen a rep clicks through, but not on a CSV import, a bulk stage move, or the API another tool calls, has not actually enforced the rule — it has enforced the appearance of the rule for the one path that is easiest to demo. Ask specifically about import, bulk edit, API and automations, because those are documented, by more than one established CRM, as the paths where their own required-field rules are not enforced.

How Automix answers it. Single and bulk stage moves in Jeet go through one gate, so a required field has no separate, unenforced path for a bulk operation to slip through. Seven-stage pipeline, per-stage rot days, and stage moves recorded as append-only history so a change is never silently overwritten.

Works today

Can you see why a lead scored the way it did, or is the score a black box you have to trust?

Why it matters. A 0-100 lead score is only actionable if a rep can explain, in one sentence, why it moved. A score with no visible components trains a team to either ignore it or trust it blindly — both of which defeat the point of scoring at all.

How Automix answers it. Every score carries a written reason per component, computed from what the customer actually did. Rules are written by the workspace itself in three fixed weight buckets, with a preview that runs a candidate rule set against a real lead and shows each contribution before it goes live. Decay is a rolling window, not an exponential curve, so a rep who disagrees can follow the arithmetic rather than take it on faith.

Works today

Can a deal close as lost with no reason recorded at all?

Why it matters. Win-loss reporting is only as good as the data feeding it, and in most CRMs the loss-reason field is an optional dropdown a busy rep skips. A report built on a mostly-empty field is not a report, it is a rounding error dressed up as insight.

How Automix answers it. A lost transition is refused without a stated reason. Loss reasons are grouped and counted, and win rate is reported by source, owner and stage of exit over a chosen window — a report most CRMs cannot honestly produce, because the underlying field is optional everywhere else.

Works today

Do stage rules actually move a deal on their own, or only flag what a human already knows?

Why it matters. 'Automation' on a pipeline can mean two very different things: rules that catch and enforce entry requirements, and rules that trigger an action — send a notification, reassign an owner, move a stage — with no person involved. Both are useful, but only one of them is actually automated, and a vendor demo can blur the two.

How Automix answers it. Both halves are built now. The entry-gate half: mandatory fields enforced on every write path, and per-stage rot days that surface what has gone stale, ignoring a future next-activity date and counting weekends the same way the one CRM whose behaviour users have already learned does. And a trigger evaluator that moves a deal on its own: task-completed and inbound-reply rules fire inline, in the same transaction as the event that could trigger them, while stage-entered-days, score-at-least and quiet-days-at-least rules are picked up by an on-demand scan rather than a cron job, because the scheduler file they'd need is being edited by other agents this wave. Conflict handling: rules are evaluated in creation order and at most one moves a lead per pass — every other rule that also matched is recorded as skipped, not silently ignored. Loop handling: a rule cannot refire on the same lead within its own cooldown window, checked against that lead's history rather than a counter. A rule can never target 'lost', because that transition still requires a human-supplied reason no trigger can invent.

Works today

When a task comes due, does the rep actually get notified, or does it sit in a table until they check?

Why it matters. A task list is not a reminder system. The difference matters the day a rep does not open the CRM until after a callback deadline has passed — a task 'assigned' with nothing pushing it to the person is a task that was never really delivered.

How Automix answers it. Tasks are created against a lead, assigned to a person in the workspace, listed by today, overdue and open with unassigned counted separately, and logged to the lead's history on completion. Actually notifying the rep now works too: a dispatch route raises an in-app bell notification for every open task past its due time, tracked per task so calling it twice never double-notifies. A separate route escalates a task overdue by more than a day to the assignee's team manager, looked up from real team membership; a rep on no team is named as not escalated rather than silently skipped. Both routes run on demand rather than a schedule, since the shared job scheduler they would need is being edited by other agents this wave.

Works today

If the same customer contacts you twice, do you get two open opportunities or one?

Why it matters. Duplicate leads inflate a pipeline's apparent size and split a customer's history across two records nobody reconciles. The question worth asking is specifically where the dedup happens — at the deal level, the contact level, or not at all.

How Automix answers it. One open lead per contact is enforced by the schema itself, so the same customer cannot become two live opportunities in Jeet. Contact-level deduplication now reaches into Jeet's own pipeline too: a scan finds duplicate contact groups, and merging one moves the losing contact's leads onto the survivor — closed ones unconditionally, but the whole merge is refused, naming both lead ids, if both sides already have an open lead, rather than silently combining two live opportunities. A dismissed match does not resurface on the next scan unless the group's membership actually changes, and every completed merge is kept in a permanent log after the losing contact row is gone.

Works today

If you send a templated email from the CRM, does open and click tracking actually work — and can it send at all?

Why it matters. Open and click tracking is only worth trusting if it runs regardless of who eventually delivers the message, and a tool that quietly drops an unsubscribe on the floor while still logging opens is worse than not tracking at all — the two features have to be built together, not one hiding the other's gap.

How Automix answers it. Templates, the consent gate, the self-hosted open-tracking pixel and click-redirect all run locally with no provider: a lead who opted out through the same consent record Wavy's WhatsApp broadcasts use gets a send blocked before anything goes out, and an unsubscribe link here writes back to that same record rather than a separate one. Actual delivery is a different matter — this deployment has no ZeptoMail key configured, so POST /emails/send records the message as blocked for a missing provider instead of pretending to send. Connect ZeptoMail and delivery starts working with the tracking already wired to it.

Needs your setup

Where we do not measure up yet

In one place: which of the answers above is not a green light.

Pulled straight from the criteria above, not a separate list — a guide that scores itself full marks on every criterion is not one you should believe, ours included.

If you send a templated email from the CRM, does open and click tracking actually work — and can it send at all?

Templates, the consent gate, the self-hosted open-tracking pixel and click-redirect all run locally with no provider: a lead who opted out through the same consent record Wavy's WhatsApp broadcasts use gets a send blocked before anything goes out, and an unsubscribe link here writes back to that same record rather than a separate one. Actual delivery is a different matter — this deployment has no ZeptoMail key configured, so POST /emails/send records the message as blocked for a missing provider instead of pretending to send. Connect ZeptoMail and delivery starts working with the tracking already wired to it.

Needs your setup

Questions

Common questions.

Why does 'gate enforcement on every path' matter more than the number of fields a CRM lets you require?

Because the number of required fields you can configure is meaningless if a bulk edit, an import or an API call can bypass them. Ask any CRM you evaluate to demonstrate a required-field rule surviving a bulk operation, not just a single manual entry.

Is Jeet's lead score a machine-learning model?

No — it is arithmetic over rules the workspace writes itself, in fixed weight buckets, with every component's contribution shown. That is a deliberate choice: a score a rep cannot follow is a score most teams eventually stop trusting.

What happens today if a task comes due and nobody checks the CRM?

It stays visible in the overdue list, and an in-app bell notification is raised for the assigned rep once a dispatch pass runs. That pass is an on-demand route today rather than a fixed schedule, so it only fires when something calls it.

Does Jeet merge duplicate contacts automatically?

Contact-level merge is Wavy's responsibility, not Jeet's — Jeet's own guarantee is narrower and schema-enforced: one open lead per contact, so a duplicate cannot become a second live deal even before any merge happens.

Is Jeet available to buy today?

Not yet — Jeet is in build, the same honest status shown next to every agent on this site rather than marketed as live before it is. Wavy, the WhatsApp engagement agent, is the one Automix product available today.

Can I apply these six questions to a CRM I already use?

Yes — that is the point of writing them as questions rather than a scorecard. Try a bulk edit against a required field, close a deal lost with no reason, and see what your current CRM actually does in each case.

Apply it

Apply these six questions to Jeet, and to whatever you use today.

Jeet is still in build, so there is no live pipeline to click through yet — but every claim above is checked against the same backend status table this whole site is built on, not written for this page.

See what Jeet already does Read the technical docs

Jeet's own status today:Coming soon

More buyer's guides

Buyer's guide

How to choose a WhatsApp business tool

Six questions that matter more than the feature list any vendor hands you — plus the one constraint every tool built on Meta's Cloud API shares, whether its marketing page mentions it or not.

Read the guide

Buyer's guide

Choosing a social media scheduling tool

The word 'scheduled' hides more than it reveals. Six questions about approvals, invented engagement data, and what actually happens when a post's date arrives — with Automix's own honest answer, including the one place nothing actually publishes yet.

Read the guide

Buyer's guide

Choosing bookkeeping software you can hand to a CA

The books your accountant actually trusts are the ones where nothing can be quietly edited after the fact. Six questions about append-only entries, honest reconciliation, and what a tool should never claim to do on your behalf — with Automix's own answer to each.

Read the guide

What to look for in a CRM for a small sales team

What this guide will not do

No named or characterised competitorNo invented statistic or ratingHonest where our own answer is a limit

What to look for in a CRM for a small sales team

The homepage feature list is not where a CRM actually fails.

A tool with no refusals has not thought about the edges of your business.

It will not let a bulk stage move or an import skip a stage's required fields

It will not close a deal lost with no reason on record

It will not open a second live opportunity for a contact who already has one open

7 questions to ask any vendor in this category.

Does a required field on a pipeline stage apply on every path a deal can move — not just the manual screen?

Can you see why a lead scored the way it did, or is the score a black box you have to trust?

Can a deal close as lost with no reason recorded at all?

Do stage rules actually move a deal on their own, or only flag what a human already knows?

When a task comes due, does the rep actually get notified, or does it sit in a table until they check?

If the same customer contacts you twice, do you get two open opportunities or one?

If you send a templated email from the CRM, does open and click tracking actually work — and can it send at all?

In one place: which of the answers above is not a green light.

If you send a templated email from the CRM, does open and click tracking actually work — and can it send at all?

Common questions.

Apply these six questions to Jeet, and to whatever you use today.

Evaluate the rest of your stack.

How to choose a WhatsApp business tool

Choosing a social media scheduling tool

Choosing bookkeeping software you can hand to a CA

What to look for in a CRM for a small sales team

The homepage feature list is not where a CRM actually fails.

A tool with no refusals has not thought about the edges of your business.

It will not let a bulk stage move or an import skip a stage's required fields

It will not close a deal lost with no reason on record

It will not open a second live opportunity for a contact who already has one open

7 questions to ask any vendor in this category.

Does a required field on a pipeline stage apply on every path a deal can move — not just the manual screen?

Can you see why a lead scored the way it did, or is the score a black box you have to trust?

Can a deal close as lost with no reason recorded at all?

Do stage rules actually move a deal on their own, or only flag what a human already knows?

When a task comes due, does the rep actually get notified, or does it sit in a table until they check?

If the same customer contacts you twice, do you get two open opportunities or one?

If you send a templated email from the CRM, does open and click tracking actually work — and can it send at all?

In one place: which of the answers above is not a green light.

If you send a templated email from the CRM, does open and click tracking actually work — and can it send at all?

Common questions.

Apply these six questions to Jeet, and to whatever you use today.

Evaluate the rest of your stack.

How to choose a WhatsApp business tool

Choosing a social media scheduling tool

Choosing bookkeeping software you can hand to a CA