Calls
Novofon: call log, recordings, softphone
Working
Digital studio
A&W
CRM for sales teams of 5–30 people
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.
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 LidaCRMData 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
This is what a team looks like once it has outgrown its CRM.
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.
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.
Export to a spreadsheet, roll up by rep, recalculate conversion. By the time the picture is ready, it describes last week.
Softphone, custom fields, lead distribution and proper permissions are sold as extras. Your final bill no longer matches the price on the website.
From the board to access rights, every screen has one job: making sure no deal slips past the team.
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.
Novofon: call log, recordings, softphone
WorkingLead capture from landing pages
WorkingInvitations and notifications
WorkingTelegram and VK as inbound channels
In developmentA missed call creates a deal and a “call back” task, and the owner gets notified. No more combing through PBX logs by hand.
Call logs and recordings are linked to the contact and deal — listen right in the CRM, no need to open the provider's dashboard.
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.
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.
Three ways sales teams usually handle this today — and where each one hits its ceiling.
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 importNeed 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 downTen deals in a spreadsheet is manageable. What about 100? Want to lose a client because someone forgot to call?
The LidaCRM differenceLidaCRM reminds, shows, suggestsBefore 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.
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.
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.
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.
The first two steps cost nothing and commit you to nothing.
You tell us how many sales reps you have and what you need to get done.
We create your workspace and set up pipelines and roles for your team.
Your sales reps log in and start working deals on day one.
We discuss your current CRM, database size and your team's needs.
You export deals and contacts from your current CRM.
We run a dry-run import and send you a report. Nothing is written to the live database.
We agree on the migration timeline. You pay only after you approve.
We migrate your data, train the team and get your sales department running on LidaCRM.
A stack built for multi-user CRM: data isolation, live updates and predictable load from background jobs.
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.
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.
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.
The standard export is parsed as is: deals, contacts and companies. No need to prepare or reformat the file by hand.
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.
Before the live run, you map the managers in your export to workspace users. Deals land with their owners right away.
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.
One database, one set of permissions and one API. Not a set of modules an integrator has to stitch together.
Multiple pipelines: a deal can live in several at once, with one primary placement. Private pipelines with explicit membership, tags, watchers and attachments.
Call log and recordings, a softphone right in the browser, threaded comments with reactions and @mentions of colleagues.
Thirteen event types with per-pipeline filters, Web Push and live boards. Mentions reach you even if you weren't following that deal.
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.
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.
250+ projects built by A&W since 2009
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.