CRM · sales · automation

Custom CRM for your business process

I design and build CRM end to end — sales pipeline, roles, reports, and integrations with 1C, your website, and Telegram on your domain. Not a Bitrix24 or amoCRM box, but software shaped to your playbook: stages, fields, KPIs, and automations from your real process. Fullstack developer Vladislav Kompaniec — Royal Rental, DryRent, and 130+ projects.

from 200,000 ₽ / project

Usually 15–25 days from brief to MVP. Fixed estimate after pipeline, roles, integrations, and data migration scope.

Get in touch

Why custom CRM

Bitrix24, amoCRM, and Salesforce cover typical flows but rarely match your process end to end. Custom CRM means control over data, logic, and TCO without per-seat subscription fees.

Pipeline from your playbook

Stages, fields, KPIs, and auto-tasks match your sales playbook — no SaaS bloat. Reps see only what they need to close; leadership sees pipeline, forecast, and bottlenecks. Process changes don't wait on someone else's roadmap.

Single customer database

Deals, calls, emails, documents, and touch history live in one system — not Excel, messengers, and five tools. Open a record and see full context: who called, which proposals went out, payment status. Leadership gets reliable analytics without blind spots.

Integrations for your stack

1C, website, Telegram bot, telephony, email, partner APIs — data syncs on your rules. Site leads land in CRM instantly; 1C invoices attach to deals. Royal Rental and DryRent experience for complex B2B and rental flows.

Roles and permissions

Rep, head of sales, finance, logistics — each sees and edits only their scope. Audit trail on records; block bulk export for regular users. Flexible RBAC without buying SaaS enterprise tiers.

No per-seat subscription

Pay for build and maintenance — not per manager every month. Over 2–3 years TCO of own CRM is often below Bitrix24 for teams of 5–10+. Code and database are your asset, not rent.

130+ projects experience

Vladislav Kompaniec — fullstack CRM, B2B portals, rental (Royal Rental, DryRent), and 1C integrations. I know where boxed CRM breaks and design workarounds for your niche.

How custom CRM development works in practice

From first call to a working pipeline — without a year of development.

When a company outgrows Excel and Telegram threads, boxed CRM is the obvious first step. For typical sales it works. Rental/event gear, long B2B cycles, or tight 1C coupling hit SaaS ceilings fast: custom fields become a zoo, integrations become paid marketplace apps, every new rep adds a monthly seat.

Custom CRM is not «rewrite Bitrix» — it encodes your playbook: deal stages, required fields, automated tasks, director reports, and 1C exchange exactly as your business runs. On Royal Rental and DryRent a deal is a project with gear kits, rigging, quotes, and returns — not a generic funnel.

CRM MVP is usually 15–25 days: brief, pipeline schema, admin UI, roles, priority integrations, staging, training. Vladislav Kompaniec is fullstack — backend, frontend, API, deploy — one contractor. Post-launch changes ship in iterations, not half-year vendor tickets.

On the first call we review team size, current pain, day-one integrations. If SaaS is enough — I'll say so. If custom CRM fits — fixed estimate, timeline, source on your server.

What's in the CRM

I assemble MVP for your scenario — from a simple pipeline to 1C, telephony, and mobile access for field reps.

Leads & deals

Customer card, pipeline stages, amount, probability, source, full touch history. Drag between stages, auto-tasks on status change, rep reminders. Bulk ops and filters for sales leadership.

Tasks & calendar

Deadlines, owners, link to deal or account. Auto-tasks: call back in 3 days, send proposal after meeting. Rep calendar and overdue task report.

Documents & proposals

Generate quotes, invoices, contracts from the record — branded templates. Document versions, PDF, send to client from CRM. 1C link for finance.

Telephony & comms

Inbound/outbound call log, recording, deal link. Email threads on record; Telegram for rep alerts. Less «what did we promise them?»

Reports & analytics

Stage conversion, revenue, rep load, average deal, cycle time. Dashboards for leadership — no weekly Excel exports. CSV export when needed.

1C integration

Counterparties, orders, invoices, payment status — two-way sync without double entry. CommerceML or HTTP API for your 1C setup. Exchange errors logged with alerts.

API & webhooks

Events: new lead, stage change, payment — for site, ads, partners. REST for mobile or internal systems. Docs for your team.

Mobile web

Field reps see tasks, records, update status from phone. Responsive UI without app install — PWA if needed. Telegram push optional.

Who it's for

When boxed CRM gets in the way — or your process is unique for rental, B2B, and manufacturing.

Long-cycle B2B

Multiple stakeholders, proposals, contract approval, payment terms — pipeline from first touch to cash. 1C and docs linked without Excel between departments.

Rental & events

Royal Rental — quotes, gear bookings, rig statuses in one CRM. Deal = project + kit + dates + logistics, not just amount.

Dealer networks

Partners, custom discounts, shipments, sell-out reports. Roles: channel manager, dealer, HQ — different portals and rights.

Manufacturing & wholesale

Order → production → shipment → payment in one chain. WMS and 1C links; margin control by project and client.

Agencies & IT services

Projects, stages, hourly or fixed billing, renewals. Timelines, team tasks, client reports from CRM.

Migration from amoCRM / Excel

Import contacts, deals, history — CSV or API. Parallel run during transition; team training on staging.

What we need

The clearer your sales process, the more accurate the 15–25 day timeline and 200,000 ₽ estimate. Minimum brief inputs:

  1. Sales pipeline

    Stages from lead to payment: names, transition rules, owner per step. Example: Qualify → Proposal → Approval → Invoice → Paid.

  2. User roles

    Rep, head of sales, finance, admin — view, edit, export rights. Branches or regional split if needed.

  3. Fields & records

    Required customer and deal data: tax ID, segment, source, service type, quote. Custom fields for rental or B2B.

  4. Integrations

    1C (which config), telephony, website, Telegram, email — MVP list. Partner APIs if any.

  5. Leadership reports

    KPIs: conversion, revenue, cycle time, rep load. Dashboards needed in v1.

  6. Data migration

    Volume: contacts, deals, history from amoCRM, Bitrix24, or Excel. Export format and cutover date.

Technical aspects

Reliability, security, and scale built in from day one.

Performance

DB indexes, cache, and queues keep the system fast as data and users grow. Load testing on staging before production.

Security

HTTPS, role-based access, audit logs, and API key protection. Personal data handled per your compliance model.

API & webhooks

REST and webhooks for website, 1C, Telegram, and partners — no manual re-entry. API docs included.

Mobile web

Responsive layout and PWA — most users work from phones. Native iOS/Android apps when needed.

Backups

Automated DB and file backups with verified restore on staging. Data loss in normal ops is unacceptable.

Staging

Test environment for team training and integration checks before release. Updates roll out without blocking core ops.

How we build it

  1. 01

    Brief & scope

    Scenarios, roles, integrations — MVP and estimate in 1–2 calls. We lock v1 priorities and what moves to phase two.

  2. 02

    Prototype

    Wireframes for key screens and admin — revisions before build. UX flows agreed so logic isn't rebuilt mid-project.

  3. 03

    MVP

    Working flow on your domain: core modules and test data. Your team walks through scenarios on staging before live integrations.

  4. 04

    Integrations

    Payments, 1C, Telegram, partner APIs — verified on staging. Test payments, doc exchange, and webhooks before go-live.

  5. 05

    Launch

    Deploy, team onboarding, monitoring first operations. Handover of access, docs, and support for first iterations.

FAQ

How much does CRM development cost?

From 200,000 ₽ per project. Simple pipeline with cards and tasks is near the minimum; 1C, telephony, migration, and complex roles add scope. After the brief you get a fixed price and timeline.

How long does development take?

Usually 15–25 days from brief to MVP on your domain. Depends on pipeline stages, integrations, and migration volume — agreed before start. Staging ready for team training in parallel.

Why custom CRM over Bitrix24 or amoCRM?

You own the product: your domain, brand, any fields and integrations without marketplace fees. No per-user subscription — better as the team grows. Boxed CRM is faster to start but limits rental, B2B, and Royal Rental / DryRent-style logic.

Can we migrate from amoCRM or Excel?

Yes. Import contacts, deals, history — CSV, API, or manual review of critical records. Parallel run during transition is possible. Volume estimated at brief and included in scope.

Who maintains CRM after launch?

You get source code, access, docs, and admin training. Updates and support by contract with Vladislav Kompaniec; typical changes (new field, report) take days, not months.

Order CRM development

Describe pipeline and integrations — I'll reply with timeline and cost. From 200,000 ₽, 15–25 days.