Custom CRM development

Salesforce, HubSpot, Pipedrive — great products. But in 30% of cases the business runs its own way and a stock CRM doesn't fit. That's when we build custom. Done for music schools, restaurant chains, B2B services.

When a custom CRM makes sense

• Pipeline with non-standard stages.
• Specific accounting: shifts, subscriptions, hourly services.
• Integrations that aren't in stock CRMs.
• 30+ user team with complex permission needs.
• Compliance requirements that need self-hosted infra.

What's included

• Brief and process mapping.
• Prototype of key screens.
• Brand-aligned design.
• Core build (4-6 weeks).
• Data migration from old system.
• Team training + video tutorials.
• Free support for the first month.

Case study: CRM for a music school — 2000 students, 14 days build.

Technical stack

• Backend — PHP 8.2 (Symfony) or Node.js (NestJS) — picked based on team and load profile.
• Database — PostgreSQL 16+ as primary. Redis for sessions, cache, job queues.
• Frontend — Vue 3 + TypeScript or React 18 + TypeScript. Vite for dev, fast iteration.
• UI components — custom design system or shadcn/ui (React) / Radix Vue (Vue) as base.
• State management — TanStack Query for server state, Pinia/Zustand for UI.
• Auth — JWT with rotation, OAuth2 for SSO, TOTP-based 2FA.
• Permissions — RBAC or ABAC depending on complexity.
• Realtime — WebSocket for collaborative editing and notifications, SSE for one-way updates.
• Queues — RabbitMQ or BullMQ for background jobs (emails, external API sync).
• Search — PostgreSQL FTS or Meilisearch for large customer bases.
• Files — S3-compatible storage (AWS S3, regional alternatives).
• Security — sensitive fields encrypted in DB (pgcrypto), TLS everywhere, daily backups with 30-day retention.
• Deploy — Docker + Compose, CI/CD via GitHub Actions or GitLab CI.
• Monitoring — Sentry for errors, Prometheus + Grafana for metrics, Telegram alerts.