CRM for sales teams of 5–30 people

A CRM where you see every deal, every client and every next step

Roll out a clear sales system in 1 day or migrate your database from AmoCRM / Bitrix24.
A free audit will show exactly where your deals are leaking.

Trial migration before paymentSoftphone included in the plan$10 per seat, no extra fees
View the product

The audit comes with no obligation to buy. We'll simply look at how to improve your sales.

In production

A&W Studio runs its own sales in LidaCRM

Data migration with a dry run

Report first, payment second

Softphone at no extra cost

Calls, recordings, missed calls — no separate widget to buy

Permissions that actually work

Managers see only their own deals; you see everything

One price for everything

$10 per seat. No hidden fees, no paid add-ons

Sound familiar?

Sound like your sales team? We'll show you how to fix it in 15 minutes.

This is what a team looks like once it has outgrown its CRM.

  • Leads wait too long for a response

    A form lands in someone's inbox, a call goes unanswered — and an hour later the client is talking to your competitors. Nobody's to blame: there's simply no queue of unhandled inquiries.

  • Half of all deals have no next step

    On paper, work is happening: cards are created, statuses are set. In reality, the deal is forgotten until the next review — and reviews happen once a month.

  • Managers prepare reports by hand

    Export to a spreadsheet, roll up by rep, recalculate conversion. By the time the picture is ready, it describes last week.

  • Half the essentials are paid widgets

    Softphone, custom fields, lead distribution and proper permissions are sold as extras. Your final bill no longer matches the price on the website.

The product, live

Five screens that keep every customer in view

From the board to access rights, every screen has one job: making sure no deal slips past the team.

A board that updates itself

  • Drag between stages without reloading the page
  • Teammates' changes show up for everyone instantly
  • Every pipeline has a spam stage — junk stays out of the way
lidacrm · board
Lead sources

Inquiries land in the CRM automatically

A call, a website form or a colleague's invite creates a record with no manual entry. Below is the honest status of each channel: what already works and what's in development.

Calls

Novofon: call log, recordings, softphone

Working

Website forms

Lead capture from landing pages

Working

E-mail

Invitations and notifications

Working

Messengers

Telegram and VK as inbound channels

In development

What happens to a call

No missed call gets lost

A missed call creates a deal and a “call back” task, and the owner gets notified. No more combing through PBX logs by hand.

Call recording in the deal card

Call logs and recordings are linked to the contact and deal — listen right in the CRM, no need to open the provider's dashboard.

Geo-based dialing rules

Outgoing calls to a blocked destination are rejected before they reach the provider; incoming calls from it create no lead and no task. By default, +7 is allowed and +76 and +77 are blocked.

Spam stays quiet

Marking a contact as spam moves their open deals to the spam stage with a single summary notification, and their future calls no longer pop up as toasts.

An unnamed contact stays unnamed. The caller's number isn't put into the “name” field — otherwise the phone number leaks into deal titles, search and notification texts, and “no name yet” turns into a fake name.

The choice

How we differ from the usual options

Three ways sales teams usually handle this today — and where each one hits its ceiling.

AlternativeThe LidaCRM difference
amoCRM

Tired of $10 per seat turning into $33 once you pay for add-on widgets?

The LidaCRM differenceEverything included in the base price: softphone, permissions and import
Bitrix24

Need a CRM for sales, not an all-in-one bundle of portal, chats and tasks?

The LidaCRM differenceLidaCRM is built for sales only. Nothing extra to slow you down
Tables and task tracker

Ten deals in a spreadsheet is manageable. What about 100? Want to lose a client because someone forgot to call?

The LidaCRM differenceLidaCRM reminds, shows, suggests
Proof

We sell our own products through LidaCRM

Before offering the CRM to others, we moved our own sales team onto it. Studio clients and our three products run in separate pipelines within one workspace — with the same permissions, calls and notifications our clients get.

20+active studio clients
3in-house products, each in its own pipeline
1one workspace for every line of business

Readiness map — no promises in advance

Honest status for every block. Items marked “in development” aren't part of the core plan's promises and don't affect its price — you pay for what already works.

Working8
  • Pipelines, deals, tasks
  • Contacts and organizations
  • Custom fields
  • Comments and mentions
  • Inbox and Web Push
  • Roles and permissions
  • Data import
  • Softphone
In development4
  • Management reports
  • Email and calendar
  • Messaging apps as a channel
  • AI call monitoring
Pricing

One price for the whole CRM

No artificially stripped-down base plan: import, permissions, API and reporting are all included. Only services with their own running costs — telephony and AI minutes — are billed separately.

Basic

$10per user per month
  • Pipelines, deals, contacts, companies
  • Comments (reactions and threads), history
  • 5 custom fields
  • Forms and widgets
  • Inbox, import and export
  • Softphone
  • Duplicate detection and merging

Professional

$21per user per month
  • Everything in Advanced
  • End-to-end analytics
  • AI agent and custom analytics
  • Flexible access rights: roles, “own deals only,” stage- and field-level access
  • Advanced search and history
  • Task tracker included free

More than 30 employees or need special terms? Let's discuss custom terms: a dedicated environment, integration with your IT infrastructure, higher reliability and an SLA. Just write to us and we'll find the right setup for your company.

How to get started

How the switch works

The first two steps cost nothing and commit you to nothing.

I want to start from scratch

  1. You send a request

    You tell us how many sales reps you have and what you need to get done.

  2. We set up the CRM

    We create your workspace and set up pipelines and roles for your team.

  3. The team is working

    Your sales reps log in and start working deals on day one.

I want to migrate

  1. We get on a call

    We discuss your current CRM, database size and your team's needs.

  2. You send us an export

    You export deals and contacts from your current CRM.

  3. Dry-run import

    We run a dry-run import and send you a report. Nothing is written to the live database.

  4. We agree on a plan

    We agree on the migration timeline. You pay only after you approve.

  5. Live migration

    We migrate your data, train the team and get your sales department running on LidaCRM.

Technology and approach

A stack built for multi-user CRM: data isolation, live updates and predictable load from background jobs.

  • Vue.js
  • Nuxt 4
  • TypeScript
  • Pinia
  • Vite
  • Laravel 12
  • PHP 8.3
  • GraphQL
  • PostgreSQL
  • Redis
  • Docker
  • Nginx
  • GitLab CI/CD
  • Sentry

The core runs on Laravel 12 + GraphQL + PostgreSQL with Redis queues. Every CRM table carries a workspace ID, and permissions are checked by operation name in the schema — so data isolation and access control are built into the architecture, not a checkbox in settings.

Migrating from amoCRM and Bitrix24

“Will we lose our data in the move?”

It's the main — and entirely rational — question for a team that has lived in its CRM for years. We answer with a process, not a promise: first a dry run with a report on every row, and only then a write to the production database.

0duplicate records on re-import: each “source + row key” pair is unique, so you can rerun the import as many times as you like

Two-pass import, not “upload and hope”

The live run references its dry run, so you compare two reports instead of taking our word for it. Every row has its own status and the original payload saved.

What happened to the rowStatusWhat this means for you
Nothing written to the databaseStatuscreated- createdWhat this means for you a deal, contact or organization was created in the CRM
This record has already been importedStatusmatched- matchedWhat this means for you re-running doesn't create a duplicate — it finds the existing record
Row skipped by decisionStatusskipped- missedWhat this means for you you can see exactly what failed and which rule caused it
Row couldn't be parsedStatusfailed- errorWhat this means for you the source row and error text are kept in the log — fix it and rerun

What the migration includes

amoCRM deals CSV export

The standard export is parsed as is: deals, contacts and companies. No need to prepare or reformat the file by hand.

Contacts from vCard

A company phone book is imported as a separate source type: phone numbers, emails and messenger handles are sorted into the contact's communication channels.

Responsibility map

Before the live run, you map the managers in your export to workspace users. Deals land with their owners right away.

Quiet during import

During the import run, automations and watcher notifications are muted. Your team won't get a thousand emails about “new” deals that are actually two years old.

What we need from you to start: a deal export from your current CRM and, if you have them, vCard contacts. We do the dry run — you review the report and only then decide whether to start the live run.

What's inside

One product, four channels

One database, one set of permissions and one API. Not a set of modules an integrator has to stitch together.

Platform core

Laravel 12 · GraphQL · PostgreSQL · Horizon
  • Multi-tenancy: each company's data is isolated
  • Permission = operation name; everything is denied by default
  • Live board updates and Web Push
  • Self-hosted deployment in your own infrastructure

Sales

Pipelines and deals

Multiple pipelines: a deal can live in several at once, with one primary placement. Private pipelines with explicit membership, tags, watchers and attachments.

Communications

Calls and discussions

Call log and recordings, a softphone right in the browser, threaded comments with reactions and @mentions of colleagues.

Attention

Inbox and notifications

Thirteen event types with per-pipeline filters, Web Push and live boards. Mentions reach you even if you weren't following that deal.

Management

Roles and permissions

Four role templates are deployed with the workspace. Permissions are checked on every operation, and a role can never grant more than its grantor has.

Fifteen custom field types — from text and currency to ratings, team votes and files. A field can be attached globally, to a pipeline, or to a single deal right from its card.

Questions people ask before switching

Import runs in two passes. First comes a dry run: the system parses your export and builds a report, but writes nothing to the database. You see how many deals and contacts will be created, which will be matched to existing records, which rows were skipped and which couldn't be parsed — with an error message for each. Only then does the live run start, and it links back to its dry run so you can compare the reports. Before running, you map the managers in your export to workspace users, so deals land with their owners right away.

No duplicates. Every imported row is tagged with a “source type + row key” pair, and that pair is unique. A re-run finds the existing record and marks it as matched instead of creating a copy. The same property lets you fix rows that failed to import and load them separately, without touching anything that has already migrated.

No, it's part of the product. Novofon is connected today: call log, call recordings, an in-browser softphone, and employee extensions synced with their profiles. A missed call automatically creates a deal and a “call back” task. You pay for call traffic directly to the carrier at its rates — we don't add a markup. A Beeline softphone is in development.

The cloud version is hosted in Russia. For companies that need full control over their data, there's a self-hosted option: the CRM is deployed in your own infrastructure, and you install updates on your own schedule. Pricing for self-hosted deployment is quoted separately.

We keep a readiness map on this page and don't hide it. Live now: pipelines and deals, tasks with overdue tracking, contacts and companies, 15 custom field types, comments with mentions, an inbox with Web Push, roles and permissions, import from amoCRM and vCard, and the Novofon softphone. In development: management reports, email and calendar, messengers as an inbound channel, and AI call monitoring. Items marked "in development" are not part of what the core plan promises.

$10 per user per month billed annually, $12 billed monthly; minimum of three seats. The price covers the whole CRM: pipelines, fields, tasks, permissions, import, forms and API. Two add-ons with their own running costs are billed separately: Communications at $28 per company per month, and AI Control at $17 per company plus AI minutes (still in development). Nothing else ever shows up on the bill.

No. When a workspace is created, it comes preloaded with role templates (owner, admin, manager, viewer) and a starter pipeline with its stages. Team members are invited by phone or email — if someone doesn't have an account yet, they get an email with a link and sign up themselves. No setup from scratch is needed before you start.

Yes. A pipeline can be made private with an explicit member list: then only its members, its creator and the workspace owner can see it. On top of that, a general rule applies: everything is denied by default, each operation requires its own permission, and a section simply disappears from the menu if you don't have access. And a role can never grant more permissions than the person configuring it has.

Mark a contact as spam and its open deals move to the spam stage (every pipeline has one), while the team gets a single summary notification instead of a dozen. The softphone also has its own blocklist: a call from a blocked number won't trigger a pop-up. Geo-based dialing rules stop outbound calls to restricted destinations before they ever reach the provider.

Yes — the whole product is built on a GraphQL API, and the interface uses exactly the same operations that are available to you. Website inquiries come in through a separate endpoint for forms. Permissions apply to the API too: each permission is named after its operation, so an integration physically can't do more than its account allows.

The product is built for sales teams of 5–12 people and runs comfortably for teams of up to 30. If you have more users or need SSO and an SLA, we'll quote that separately — get in touch and we'll discuss terms.

Client projects

Trusted by businesses across many industries

250+ projects built by A&W since 2009

Step one

Start with a free audit of your sales team

We'll walk through how you work with customers today and show you where deals slip away. If you already use a CRM, we'll run a trial import of your data and send you a report before you pay. If you're just starting out, we'll help you figure out where to begin and get you set up in 1 day.

We usually reply within one business day.