Custom CRM, ERP and SaaS in Mykolaiv
I design custom business systems for Mykolaiv companies — CRMs for grain exporters and agro-traders, ERPs for port logistics and shipbuilding subcontractors, SaaS products. Stack Next.js, Node.js, PostgreSQL with 1C/BAS, telephony and bank integrations.
30+CRM/ERP projects delivered
15+Years of experience
40%Time saved on routine tasks
100+Satisfied clients worldwide
Leave a request
Describe your business processes and the problems that need to be solved through automation.
Free audit
I'll analyze your processes and propose the optimal CRM/ERP system architecture.
Get your system
A ready CRM/ERP with configured workflows, dashboards, and integrations tailored to your business.
Types of CRM/ERP Systems
I develop business systems for your company's specific needs
💰
Sales CRM
Customer and deal management system: sales funnel, tasks, analytics, telephony integration.
🔧
Service company CRM
CRM with ticket system, SLA control, knowledge base and customer portal.
🏭
ERP system
Comprehensive enterprise management: finance, warehouse, production, HR, procurement.
📋
Project management system
Project management platform with kanban boards, Gantt charts and reporting.
👥
HR system
Human resource management: recruiting, onboarding, time tracking, vacations.
📊
Analytics platform
Dashboards and reports for business analytics with real-time data visualization.
Work Process
1
Business Process Analysis
I deeply study your workflows, user roles, pain points, and system requirements. I build a process map.
2
Information Architecture
I design system structure, navigation, data hierarchy, and access roles. I define key usage scenarios.
3
Wireframes & Prototype
I create schematic layouts of main screens and an interactive prototype for testing with real users.
4
UI Design & Design System
I develop the visual style, component library, and detailed mockups for all system screens.
5
Testing & Handoff
I conduct usability testing, make adjustments, and prepare complete documentation for the development team.
Pricing
Choose the optimal package for your project
Basic
CRM Start
Basic CRM system
$3000$4000What's included:
- Customer management module
- Sales funnel
- Tasks and reminders
- Basic analytics
- Responsive interface
- Team training
Ready in 1 month
Business
CRM Business
Extended CRM with integrations
$6000$8000What's included:
- Everything from «CRM Start»
- Telephony integration
- Email integration
- Process automation
- Roles and access rights
- API for external systems
- Advanced analytics
Ready in 2 months
Premium
ERP Complex
Full business system
$12000$15000What's included:
- Everything from «CRM Business»
- Project management module
- Financial module
- Warehouse management
- HR module
- Real-time dashboards
- Custom reports
- Priority support 6 months
Ready in 3-4 months
Maximum
SaaS Platform
Cloud product turnkey
$20000$28000What's included:
- Everything from ERP Complex
- Multi-tenant architecture
- Billing & subscription management
- Onboarding & tooltip system
- Public API for integrations
- Multi-language support
- CI/CD, auto-tests, monitoring
- 6-month support & maintenance
For product companies
Frequently Asked Questions
Answers to the most popular questions
The price depends on the scope of functionality, number of roles, integrations and business-logic complexity. Approximate ranges:
- MVP CRM for a small business (up to 5 roles, 3-5 integrations, basic analytics) — entry package, 6-10 weeks of development.
- Full-fledged CRM/ERP for a mid-size manufacturer, agro-trader or chain (up to 15 roles, integrations with 1C/BAS, telephony, warehouse, analytics, dashboards) — mid-tier package, 3-5 months.
- SaaS product with multi-tenant architecture, billing, customer portal — premium package, 5+ months.
Exact figures come after a discovery session, once we've fixed the processes, roles and integrations. Mykolaiv, Ochakiv or Voznesensk businesses can opt for phased delivery — ship an MVP first, then iteratively grow the feature set.
Boxed solutions handle 60-70% of tasks — that's fine for small business. But once a company develops unique business logic (e.g. a specific grain-export funnel through Mykolaiv port with 8 approval stages, or a complex pricing matrix for B2B clients in EU markets), the box starts losing.
- Flexibility. In a custom CRM you build any process without template limits.
- Data ownership. The DB lives on your server, not in California or Moscow.
- Cost at scale. 50 users on Bitrix24 means a permanent monthly fee. Custom only requires support.
- Integrations. With your 1C, weighbridge at the elevator, IP telephony, mail — without API restrictions.
If you have 5 sales reps and simple pipelines — stay on the box. If you're a manufacturer, wholesaler, agro-trader or chain with non-standard logic — custom pays for itself within 1-2 years. Pick a route on contacts.
The standard cycle is 3-6 months, depending on scope:
- Discovery (2-4 weeks). Deep interviews with key roles, as-is and to-be process maps, BPMN diagrams, requirements baseline.
- UX/UI design (3-5 weeks). Information architecture, wireframes, interactive Figma prototypes, testing with future users.
- Architecture (1-2 weeks). DB schema, API contracts, integrations diagram, infrastructure (Docker, CI/CD).
- Development (10-20 weeks). Two-week sprints with demos. Frontend (Next.js), backend (Node.js), DB (PostgreSQL), cache (Redis).
- Integrations (in parallel). 1C/BAS, telephony, mail, banking, marketplaces.
- Testing (2-3 weeks). QA, load tests, security audit.
- Launch and training (1-2 weeks). Data migration, online training with regular synchronous sessions, documentation handover.
If the CRM goes alongside a website or mobile app, cycles are coordinated in a single roadmap.
Standard set for the Ukrainian market, especially relevant for the agro and port sectors of Mykolaiv region:
- 1C/BAS: two-way sync of inventory, stock, prices, documents. Real-time via webhooks or scheduled.
- IP telephony: Binotel, Phonet, Asterisk — click-to-call, call recording, automatic lead creation from port or elevator inquiries.
- Messengers and email: Telegram Bot API, Viber Business, SendPulse, eSputnik, MailChimp.
- Logistics: Nova Poshta API (waybill creation, tracking), Justin, Meest, integration with weighbridge complexes at elevators.
- Payment systems: PrivatBank (LiqPay), Monobank Acquiring, Wayforpay, Fondy.
- Marketplaces and e-commerce: Prom.ua, Rozetka, OLX, integration with your online store via REST API.
- Accounting: M.E.Doc, FREDO, SOTA — document import/export.
If you need integration with a non-standard service (equipment at a shipyard subcontractor or a grain terminal in the port) — I write a custom connector. Details on contacts.
Yes — 1C/BAS integration is one of the most frequent tasks specifically for Mykolaiv region, where grain exporters (Nibulon-style traders), food processors (Sandora-style), and shipbuilding subcontractors keep accounting in 1C, while wanting day-to-day operations in a comfortable web CRM/ERP. Architecturally:
- REST/SOAP bridge over 1C HTTP services — JSON or XML exchange.
- Two-way exchange: contractor cards, items, balances at elevators and warehouses, documents (invoices, waybills, acts, TTN), prices, contracts.
- Real-time or scheduled. Critical data (stock, prices) — instantly via webhooks. Non-critical (historical docs) — hourly or nightly.
- Conflict resolution. If a document changed in both systems — rules for which side is master per field.
- Logs and monitoring. Every exchange recorded, errors pushed to Telegram or Slack.
I work with UT, UPP, BAS Accounting, BAS KUP — each has nuances. Cases on projects.
Core stack:
- Frontend: Next.js (React) — SSR, high performance, SEO-friendly. TypeScript for type safety.
- Backend: Node.js (NestJS / Express) — shared language with the frontend, large ecosystem, high performance on I/O tasks.
- Database: PostgreSQL — relational, reliable, with JSON-field support for flexible schemas.
- Cache and queues: Redis — high-throughput, BullMQ for background jobs.
- Infrastructure: Docker + Docker Compose / Kubernetes, GitLab CI/CD or GitHub Actions.
- Hosting: AWS, GCP, Hetzner, or Ukrainian Cityhost / FastVPS — at the client's choice.
This stack is the 2024-2026 industry standard, and it's easy to find developers in Ukraine and globally. Alternatives (Python/Django, PHP/Laravel, .NET) are also used when objectively justified — ML tasks (Python) or legacy integration. Selection happens during discovery.
Yes, the role model (RBAC — Role-Based Access Control) is a baseline part of any CRM/ERP I build. Especially important for businesses with branches in Ochakiv, Voznesensk, Pervomaisk or Snihurivka:
- Roles: owner, director, department head, manager, accountant, warehouse, production, observer — each with its own rights set.
- Branch separation. A manager from the Mykolaiv branch sees only their clients, the Ochakiv branch sees only theirs. The director sees everything.
- Granular rights. Not just "see/don't see", but also "edit field X", "see margin", "export data", "change tariff".
- Audit logs. Who, when and what changed — to detect abuse and for compliance.
- 2FA for critical roles. Two-factor authentication for admins, accountants, managers.
If you have 5+ branches across Mykolaiv region and 10+ roles — I additionally design ABAC. Examples on projects.
Discovery is the most important stage of a CRM/ERP project. A mistake here costs tens of thousands of dollars later. So I dedicate 2-4 weeks to:
- Interviews with key roles — owner, director, department heads, key executors. Online work with regular synchronous sessions over Google Meet or Zoom.
- Process observation. A series of online sessions where users demonstrate a real working day in the sales department, warehouse or elevator — not how it's described on paper.
- As-is process map. BPMN diagrams, swimlanes, list of all stages and exceptions.
- Pain-point detection. What's redundant, what's duplicated, where time is lost, where errors happen.
- To-be process design. How work should look after the system goes live.
- Roadmap and prioritisation. What's MVP, what's phase 2, what's phase 3.
Without this stage any CRM becomes an expensive feature warehouse. I run discovery as a standalone business-consulting audit.
Launch isn't the end, it's the beginning. I offer three support formats to choose from:
- Basic SLA. Warranty period 60-90 days — bug fixes, user questions, small adjustments free of charge.
- Standard contract. Monthly fixed hour budget (20-40 h/month) for small features, optimisations, updates. Critical-bug response — 4 hours.
- Extended SLA. 24/7 monitoring, guaranteed 99.5%+ uptime, dedicated team, regular infrastructure and security updates.
For most Mykolaiv-region businesses the standard contract is optimal. It lets the system evolve with the company: new integrations (e.g. with a new grain terminal in the port), dashboards, roles, features. Much cheaper than throwing a new SoW to a new contractor every six months. Reach me via contacts.
Security is an integral part of the architecture, not a "finishing touch". Defaults include:
- Encryption in transit. HTTPS everywhere (Let's Encrypt or your SSL), TLS 1.3 for APIs.
- Encryption at rest. AES-256 for critical fields (passport data, banking information).
- Password hashing. bcrypt / argon2.
- SQL-injection protection. Parameterised queries, ORM (Prisma, TypeORM).
- XSS / CSRF protection. CSP headers, CSRF tokens, sanitisation.
- Rate limiting and DDoS protection. Cloudflare, fail2ban on servers.
- Audit logs. All critical actions recorded (login, data export, rights change).
- GDPR readiness. Personal data export, right to erasure, consent log.
- Backups. Daily automatic, encrypted, in two geographically separate locations.
For Mykolaiv agro-exporters working with the EU I specifically address GDPR; for medical or financial — HIPAA / PCI-DSS. Details on consulting.
Yes — multi-tenant SaaS is one of the formats I build for Mykolaiv startups and IT teams near MNU and Admiral Makarov NUK. Architecturally:
- Multi-tenancy. One codebase, one DB (with row-level security) or a separate DB per client — depending on requirements.
- Billing. Integration with Stripe, Paddle, Wayforpay, LiqPay — subscriptions, trial periods, upgrades, invoices.
- Admin panel for the product owner. All tenants, metrics, churn, MRR, ARPU.
- Tenant client cabinet. Self-registration, settings, payment, data export.
- API and webhooks. So clients can integrate the product with their own systems.
- Multi-language. Ukrainian, English, others — with redux-i18n or next-i18next.
If you plan to enter EU or US markets — I additionally prepare the SaaS for compliance (GDPR, SOC2). See cases.
Yes — that's the recommended approach for most projects. Instead of building a "big system" for 6 months, we split it into phases:
- Phase 1 — MVP (6-10 weeks). Core funnel, customer cards, basic analytics, 2-3 key integrations. Ship to production with real users.
- Phase 2 (3-4 months). User feedback → optimisations, expanded funnels, additional integrations, mobile version.
- Phase 3 (4-6 months). ERP modules — warehouse, production, finance. Or SaaS features, if going to market.
Benefits of phased delivery: faster time-to-result, faster ROI, requirements adjusted based on real usage. Especially relevant for manufacturing and agro-B2B businesses in Mykolaiv region, where not every export-chain scenario can be predicted upfront. Details on projects and contacts.
Why choose me?
Comparison with other options
| Alex Filiuk | Boxed solution (amoCRM / Bitrix24) | |
|---|---|---|
| Adaptation to your processes | ✅ Systems designed around the process | 📋 You adapt to the template |
| Meetings in Rivne | ✅ In person at discovery and launch | ❌ Support via tickets |
| 1C/BAS integration | ✅ Two-way, real-time or scheduled | ⚠️ Via third-party modules, often limited |
| Code and data ownership | ✅ Source code and DB are yours | ❌ Data on vendor servers, lock-in |
| Cost at scale (10+ users) | 💰 One-off CAPEX, no monthly per-user fees | 💰 Subscription grows linearly with users |
| Custom reports and dashboards | ✅ Any logic, any slice | 📋 Templates only, complex extra |
| Multi-tenant / SaaS model | ✅ We can build your own SaaS product | ❌ Not supported |
| Performance on large datasets | ✅ PostgreSQL + Redis, tuned to your queries | ⚠️ Lag on 100k+ records |
| Support and evolution | ✅ SLA contract with a fixed team | 🔄 Generic support desk |
CRM, ERP and SaaS Development in Mykolaiv — Custom Business Systems | Alex Filiuk
Custom CRM, ERP and SaaS development in Mykolaiv
Mykolaiv is a southern industrial and logistics hub of Ukraine, where the routes of grain export, port trade and a revived shipbuilding industry intersect. Local businesses rarely fit into boxed templates: an agro-trader shipping sunflower oil to Turkey through Mykolaiv port, a parts manufacturer for the Chornomorsk shipbuilding yard, a hospitality chain on Soborna and Admiralska streets, a food processor in the Korabelnyi district — each has its own logic of lead generation, document flow and settlements. I design and build custom CRM, ERP and SaaS systems for Mykolaiv and the surrounding region that close exactly these processes, instead of forcing a business to adapt to a template.
Unlike Bitrix24, amoCRM, KeyCRM or Pipedrive, a custom system lives on your server, with your integrations (1C/BAS, weighbridge at the elevator, bank, IP telephony, Nova Poshta, marketplaces) and your business logic — without API limitations and monthly subscriptions that grow linearly with the number of users. Over a 2-3 year horizon the investment pays back for manufacturing, agro and B2B companies with 10+ users, complex pricing matrices or non-standard funnels.
Who this fits in Mykolaiv and the region
I work with several typical Mykolaiv-region business profiles:
- Agro-traders and grain exporters. Companies dealing with sunflower, wheat, soy, rapeseed — purchase from farmers in Mykolaiv, Kherson, Odesa regions, shipping through Mykolaiv port or Ochakiv. Needs: lot tracking, quality control, integration with elevators and weighbridges, document flow (contracts, waybills, invoices, customs declarations), currency analytics.
- Manufacturers and food processors. Complex production with planning, recipes, raw and finished goods warehouses. Needs: MRP, batch control, traceability, 1C/BAS and marketplace integrations.
- Shipbuilding and port-infrastructure subcontractors. Parts manufacturers, engineering companies, installers — complex B2B funnels with tenders, technical specs, specifications, completion acts.
- Logistics operators. Companies combining maritime, rail and road transport — dispatching, tariff management, integration with Nova Poshta, Justin, shipping lines.
- Regional chains. Cafes, restaurants, stores, pharmacies on Soborna, Admiralska, in the Zavodskyi or Inhulskyi districts and branches in Ochakiv, Voznesensk, Pervomaisk — POS integrations, loyalty programs, multi-branch accounting.
- IT startups around NUK and MNU. Teams building their own SaaS product — needing multi-tenant architecture, billing, admin panel, client cabinet, multilingual support.
Tech stack and why
I use a modern industry stack that is the standard for Ukrainian and international teams in 2024-2026:
- Frontend: Next.js 14+ (React 18+), TypeScript, TailwindCSS, shadcn/ui or a custom design system. SSR and ISR provide performance even on large data volumes.
- Backend: Node.js on NestJS or Express, with optional Python mix (ML tasks, e.g. grain price forecasting or counterparty scoring).
- Database: PostgreSQL 15+ as the main relational DB, with JSON-field support for flexible schemas. For document-heavy data — MongoDB or built-in JSONB.
- Cache and queues: Redis for cache and pub/sub, BullMQ for background jobs (reports, 1C sync, notifications).
- Infrastructure: Docker + Docker Compose for smaller systems, Kubernetes for serious SaaS. CI/CD via GitLab CI or GitHub Actions.
- Hosting: AWS, Google Cloud, Hetzner (Europe), or Ukrainian Cityhost / FastVPS — at the client's choice depending on data-locality and budget.
- Monitoring: Grafana + Prometheus, Sentry for errors, Datadog or New Relic when required.
With this stack it's easy to find developers in Ukraine, the EU and the US — which reduces the risk of vendor lock on the development team itself. If you already have a legacy system in PHP or .NET — I integrate with it through APIs instead of rewriting from scratch.
Integrations with Ukrainian services for Mykolaiv region
Standard set I work with in almost every project:
- 1C/BAS: two-way sync of items, balances, prices, documents. I work with UT, UPP, BAS Accounting, BAS KUP, BAS Trade Management.
- IP telephony: Binotel, Phonet, Asterisk, UniTalk — click-to-call, call recording, automatic lead creation from incoming calls from the port or elevator.
- Messengers and email: Telegram Bot API, Viber Business, WhatsApp Business, SendPulse, eSputnik, MailChimp.
- Logistics: Nova Poshta API (waybills, tracking, branches), Justin, Meest, integration with weighbridge complexes at elevators.
- Payment systems: PrivatBank (LiqPay), Monobank Acquiring, Wayforpay, Fondy — for the Ukrainian market. Stripe, Paddle, PayPal — for international SaaS projects.
- Marketplaces: Prom.ua, Rozetka, OLX, Allo — integration through official APIs.
- Accounting and document flow: M.E.Doc, FREDO, SOTA — import/export of primary documents and digital-signature exchange.
- Mykolaiv-specific: integration with weighbridge complexes at elevators, with cargo-tracking systems in ports, with equipment at shipbuilding subcontractors.
Discovery — the most important stage
A misunderstanding of processes costs tens of thousands of dollars later. So I dedicate 2-4 weeks at the start specifically to research:
- Interviews with key roles. Owner, director, department heads, key executors — separately with each. Online work with regular synchronous sessions over Google Meet or Zoom, with screen sharing, joint Miro editing and recordings for documentation.
- Observation of a real working day. I organise a series of 2-4 hour online sessions where a manager shows a real day in the sales department, warehouse accounting at the elevator or shipment at the port — to see how people actually work, not how it's described in manuals.
- As-is process map. BPMN diagrams, swimlanes, list of all stages, forms, documents, exceptions. Foundation for designing the new system.
- Pain-point identification. What's duplicated, where time is lost, where errors happen, where risks live. Often 30-40% of "client requirements" turn out unnecessary after discovery — saving budget.
- To-be process design. How work should look after the system is implemented — given budget and time constraints.
- Roadmap and prioritisation. What goes into MVP (6-10 weeks), what into phase 2, what into phase 3. Principle: each phase has standalone business value.
I can run discovery as a standalone business-consulting audit — even if you later choose another vendor for development itself. Honest approach: you get professional BPMN documentation and a roadmap, then you're free to choose.
Development stages and typical timelines
- Discovery (2-4 weeks). Interviews, process maps, requirements baseline.
- UX/UI design (3-5 weeks). Information architecture, wireframes, interactive Figma prototypes. I test with real future users — managers, accountants, warehouse staff.
- Architecture (1-2 weeks). DB schema, API contracts, integrations diagram, infrastructure plan.
- Development (10-20 weeks). Two-week sprints with demos. Each sprint — closed business value.
- Integrations (in parallel). 1C/BAS, telephony, mail, banking, marketplaces.
- Testing (2-3 weeks). Unit, integration, E2E (Playwright or Cypress), load tests (k6), security audit (OWASP Top 10).
- Launch and training (1-2 weeks). Data migration from legacy, online user training with regular synchronous sessions, documentation handover.
Custom CRM/ERP vs Bitrix24, amoCRM, KeyCRM
Boxed solutions cover 60-70% of tasks — enough for small business and typical funnels. But once a company has unique logic, the box starts squeezing. Custom is justified when:
- 5+ roles and complex org structure. Branches in Mykolaiv, Ochakiv, Voznesensk, each with its own rights and dashboards.
- Non-standard funnels. Grain export with 8-12 confirmation stages from contract to customs clearance. In Bitrix24 this either doesn't unfold or breaks at any process change.
- Integrations the box doesn't support. Weighbridges at the elevator, equipment at shipbuilding subcontractors, specific bank or customs integration.
- Analytics and reports of any cut. The owner wants to see margin by lot, by client, by manager, by region, by product, by payment term — all at once and in real time.
- Your own SaaS product. If you want to sell the CRM rather than just use it — multi-tenant architecture, billing, admin panel.
If you have 5 sales reps and simple pipelines — stay on Bitrix24. Savings from custom only kick in beyond 10 users and complex logic. I'm honest about this at discovery — and turn down a project if a boxed solution is cheaper and more effective.
Security and compliance
Security is built into the architecture, not "added at the end":
- HTTPS and TLS 1.3 for all API calls.
- AES-256 for critical fields (passport data, banking info, export contracts).
- bcrypt / argon2 for passwords, no decryption.
- Parameterised queries, ORM (Prisma, TypeORM) — SQL-injection protection.
- CSP headers, CSRF tokens, sanitisation — XSS and CSRF protection.
- Rate limiting via Cloudflare, fail2ban on servers.
- Audit logs of all critical actions — login, export, rights change, deletion.
- 2FA for admins, accountants, branch managers.
- GDPR readiness for working with the EU: personal data export, right to erasure, consent log. Especially important for Mykolaiv-region agro-exporters dealing with counterparties in Poland, Germany, Turkey, Italy.
- Backups: daily automatic, encrypted, in two geographically separate locations.
Post-launch support and system evolution
Launch is not the end, but the start of a new life cycle. I offer three support formats:
- Basic SLA. Warranty 60-90 days — bug fixes, user questions, small adjustments free of charge.
- Standard contract. 20-40 hours per month for new features, optimisations, updates. Critical-bug response — 4 hours during business hours.
- Extended SLA. 24/7 monitoring, guaranteed 99.5%+ uptime, dedicated team, regular infrastructure and security updates.
For most Mykolaiv-region businesses the optimal format is the standard contract. It lets the system evolve with the business: you add a new grain terminal in Ochakiv — we wire it into accounting in 2 weeks; a new settlement currency appears — we add it without rewriting; you need to open a Voznesensk branch — we set up roles and access separation in an evening. Much cheaper than throwing a new SoW to a new contractor every six months and paying again for full discovery.
How to start and related services
The starting format is a 2-4 week discovery session, where we fix processes, roles, integrations and a roadmap. After that you get a clear estimate and work plan. If the CRM/ERP starts alongside a website or mobile app, I synchronise the cycles into a single roadmap and run discovery separately as business-consulting. See examples of delivered systems on the projects page, write via contacts. I work with companies from Mykolaiv, Ochakiv, Voznesensk, Pervomaisk, Snihurivka, Bashtanka and the entire Mykolaiv region.