Custom CRM development and ERP systems

One system instead of Excel, chats and manual re-entry into 1C

We build CRM and ERP modules around your processes: pipeline, roles, stock, orders and data exchange with 1C. We start with the most painful area and add modules one by one, with no big-bang switch. Pricing is per task, with an estimate in 1–2 days after the brief.

What we build

A familiar picture: deals live in chats and Excel, statuses drift apart, stock reaches 1C late, and the boxed CRM needs a workaround for every step you take. We build custom CRM and ERP modules that mirror how your departments actually work. 1C stays the accounting system: we do not break it, we set up an exchange of orders, counterparties, stock and payments. We start with a process map and one module running alongside the old spreadsheets, then bring departments on board one at a time.

  • A CRM built around your sales process

    For a sales team whose deal does not fit the amoCRM or Bitrix24 template. Your own stages, tasks, permissions and exports: managers do not lose deals, heads see the pipeline.

  • ERP module and 1C exchange

    For companies that run orders and stock in Excel while 1C finds out last. We build an operations module — orders, stock, approvals — and connect it to 1C without double entry.

  • Internal systems and admin panels

    For teams that manage a catalog, content or a store network by hand. One panel with roles, change history and two-factor sign-in, including on your own servers.

  • Client cabinet tied to accounting

    For B2B and B2C companies whose managers spend the day answering “where is my order”. Clients see statuses, documents and invoices; the data comes from your CRM and 1C, not from copy-paste.

What the work includes

We price by task: an estimate in 1–2 days after the brief.

  • As-is audit: spreadsheets, current CRM, roles, statuses and team bottlenecks
  • System boundaries: what stays in 1C and what moves to the new system
  • Data model and screen prototype agreed before coding
  • Role model, change history and Excel export
  • Integrations: 1C, banks, marketplaces, telephony, messengers, website
  • Data migration and a parallel period reconciled against the old setup
  • Staff training, guides and sprint-based improvements after launch

How we work

  1. 01

    Scoping

    A call about goals, audience, processes and constraints. We review what you already have if needed.

  2. 02

    Estimate and plan

    Stages, timelines and the cost of each stage. Estimate in 1–2 days.

  3. 03

    Prototype and design

    Structure and user flows first, then design. Agreed before we write code.

  4. 04

    Development

    Sprints with demos: you see a working version, not just reports.

  5. 05

    Launch and support

    We move it to production, connect analytics and integrations, then keep improving under contract.

Questions

Why not use amoCRM or Bitrix24 off the shelf?

If the boxed product covers your process, we keep it and extend it. Custom CRM development makes sense when the template breaks your sales: your own stages, a complex client cabinet, reports, a tight link with 1C. A common setup is a boxed CRM for sales plus a custom module next to it.

How do we move off Excel without stopping work?

In stages. First a new setup for one or two roles while Excel keeps running. We migrate statuses and reference data, reconcile, train people — and only then switch the spreadsheets off.

Will you rework our 1C configuration?

No. By default we build an external API exchange with an error log and mismatch checks — not “manual exports once a week”. Changes inside a standard 1C configuration happen only under a separate spec, together with your 1C partner if needed.

Who owns the code, and what if our processes change?

The code and infrastructure stay with you. New processes come in as modules: each is estimated separately, with acceptance criteria agreed before coding.

How much does it cost, and who supports the system after launch?

We price per task, with an estimate in 1–2 days after the brief, refined after the process map: roles, integrations, data migration volume. After launch we keep improving the system in sprints or hand it over to your team.

We stay after launch

Support, improvements and monitoring under contract, with a 24/7 SLA if needed. You can also hand over a project built by another team.

Support and SLA →

A quote in 1–2 days

Name the process that eats time. You get a pilot range, not a 40-slide deck.

Or message us