CRM, ERP and SaaS Development in Lutsk, Ukraine

CRM, ERP and SaaS Development in Lutsk — custom systems for Volyn businesses

Businesses in Lutsk and the Volyn region operate every day at the intersection of three markets — Ukrainian, Polish, and the wider European one. Export-oriented agriculture ships grain and rapeseed through the customs post in Yagodyn. Food producers (Lutsk Dairy, Volynsky Kolos, Svityaz, dozens of craft apiaries and farms) go through HACCP audits to enter German retail chains. Customs brokers process hundreds of declarations daily. Hotels next to Lubart's Castle host tourists from Poland and the EU during peak season. Each of these businesses has long outgrown Excel and paper logs — but "boxed" CRMs like amoCRM or Bitrix24 don't fit them either. I'm Alex Filiuk, Senior UI/UX and product designer with 15 years of experience, designing and leading the development of custom CRM, ERP and SaaS systems for Lutsk businesses since the 2010s. My portfolio includes 30+ launched systems for clients in Ukraine, the US, the UK, Poland and Germany.

This page brings together everything an owner or IT lead needs to know before commissioning CRM, ERP or SaaS development in Lutsk: when boxed software still works and when it doesn't; what the technical stack looks like; which integrations matter specifically on the Volyn market; how much time and budget to plan for; how to avoid the typical traps.

Why a custom CRM/ERP matters for Volyn businesses

Lutsk is a special city. Proximity to the Polish border (~70 km to Yagodyn) shapes the local business profile: a significant share of companies export to the EU or import from Poland and Germany. That means multi-currency accounting, document workflows in several languages (UA/EN/PL), specific customs procedures, integrations with European logistics operators (DPD, GLS, Schenker), and strict transparency and audit requirements from EU partners.

Boxed CRMs don't cover these needs for three reasons:

• Rigid constructor. amoCRM, Bitrix24, Pipedrive are built around "classic" B2C/B2B sales. Agricultural seasonality, lot-based warehouse accounting, export document flow — outside their logic.
• Expensive integrations. Off-the-shelf modules for 1C/BAS, M.E.Doc and banks cost extra and are often shallow (one-way sync, limited fields).
• Vendor lock-in. Your data lives in the vendor's cloud, export is restricted, the subscription price grows with every new employee.

A custom system removes these limits once and for all. Yes, it's more expensive at the start — but by month 18–24 it pays back through the absence of per-user fees and the flexibility of processes. If you're hesitating — start with a business consultation or a UX audit of your existing systems.

What systems I build — CRM, ERP, SaaS

These are three different products with different architectures and business logic. Here's how to tell them apart for your business:

• CRM (Customer Relationship Management). Managing customers and sales: leads, deals, pipeline, telephony, email marketing, reports. A custom CRM makes sense when your sales cycle is non-standard — for example, B2B with a 6-month cycle, public-sector tenders, or export deals with Polish distributors.
• ERP (Enterprise Resource Planning). Managing all company resources: finance, warehouse, manufacturing, HR, logistics, document flow. ERP is needed when the business goes beyond a single function — a manufacturer with its own distribution, an agricultural holding with fields and processing, a retail chain with multiple points in Lutsk, Kovel, Volodymyr-Volynskyi.
• SaaS (Software as a Service). Your own product that you sell to other companies. This is a separate category: it requires multi-tenancy (one codebase serving many clients), billing, a marketing site, documentation, support. SaaS is the format Lutsk IT startups choose when targeting Poland, Czechia or Germany — or established Ukrainian companies turning their internal tools into a product.

These categories often overlap. For example, a manufacturer can launch an ERP for itself and later turn part of the functionality into a SaaS for partner-competitors. Or a CRM gradually accumulates warehouse and accounting modules and evolves into an ERP. I help draw these lines during discovery — so you don't pay for unnecessary complexity, but also don't hit a ceiling in two years.

Technical stack: Next.js, Node.js, PostgreSQL, Redis, Docker

The stack must be modern, but not "trendy." Choosing technology is an investment for the next 5–10 years: you need to easily find developers, update dependencies, and not get stuck with outdated solutions. My base stack:

• Frontend: Next.js 15 on React 18, TypeScript, Tailwind CSS. SSR/SSG for public SaaS pages (important for SEO), client components for the dynamic CRM/ERP interfaces.
• Backend: Node.js on NestJS — a structured DI framework that scales well. Alternative — Fastify/Express for simpler services. TypeScript on the backend too — one language across the team.
• Database: PostgreSQL — the gold standard for CRM/ERP. Transactional integrity, JSONB for flexible fields, strong full-text indexing, reliable backups.
• Cache and queues: Redis — for sessions, caching heavy reports, background job queues (BullMQ).
• Containerisation: Docker + docker-compose for smaller systems, Kubernetes for large SaaS with autoscaling.
• Infrastructure: CI/CD on GitHub Actions or GitLab CI, monitoring via Prometheus + Grafana, logs in Loki or ELK, error tracking in Sentry.
• Hosting: Hetzner (cheap, reliable, server nodes in Germany and Finland), OVH (Poland, France), AWS/GCP for complex SaaS, local data centres in Lutsk or Lviv if regulations demand it.

For UX and design I use Figma — the design system, prototypes and screen documentation all live there. This makes it fast to hand off mockups to engineers and iterate without re-reviews. If the public marketing site of the SaaS also needs UI/UX design — it's built in the same logic as the product.

Integrations relevant for Lutsk businesses

No CRM/ERP lives in a vacuum. Especially in Lutsk, where a business often has a "zoo" of legacy systems — 1C, Bitrix, Excel sheets, paper warehouse logs. The architect's job is to pull all of this into a single source of truth without rebuilding everything from scratch. The most common integrations I implement:

• 1C/BAS Accounting, BAS ERP. Two-way sync of counterparties, items, documents via 1C web services or an intermediate layer (e.g., a REST wrapper).
• M.E.Doc / Sonata. Automatic generation of tax invoices, exchange with counterparties via EDI (SEPK).
• Bitrix24 and amoCRM. If you're keeping them partially (e.g., for marketing) — two-way sync of leads, deals, contacts via REST API.
• Ukrainian banks. PrivatBank (LiqPay, Privat24 Business), Monobank for Business, PUMB, Raiffeisen — statement import, payment generation, receivables monitoring.
• Telephony. Binotel, Phonet, UniTalk, Asterisk — call recording, attachment to client cards, AI transcription via Whisper.
• Logistics. NovaPoshta API, Ukrposhta, Meest, for export — DPD, GLS, Schenker, DHL.
• Payment systems. LiqPay, Fondy, WayForPay for Ukraine, Stripe / Adyen / PayU for the EU.
• Email and SMS. SendGrid, Mailgun, Postmark for email; TurboSMS, IntelTeleCom for SMS.
• BI and analytics. Metabase, Apache Superset, Power BI — for top-management dashboards and reports.

For specific cases — for example, integration with field monitoring (Cropio, Soft.Farm), warehouse SCADA, customs broker software — we connect via REST/SOAP/MQTT. During discovery I always map all current systems so nothing gets lost in the new design.

Working process: from discovery to launch

Transparency is the foundation of long projects. I work in a clear cycle where you see intermediate results every week:

1. Discovery (1–2 weeks). Kick-off in Lutsk, user interviews, process map, technical audit of existing systems. Output — a documents pack: scope, architecture, estimate, roadmap.
2. UX design (3–6 weeks). Screen prototypes in Figma, design system, interactive demos. Here we validate the logic before committing to code.
3. Architecture and infrastructure (1–2 weeks). ER diagrams, API contracts, dev/staging/prod environment setup, CI/CD.
4. Sprint development (2 weeks each). Every sprint — a demo meeting on Zoom, where I show finished features. Backend, frontend, integrations, tests.
5. Testing and UAT (2–4 weeks). Unit tests, e2e on Playwright or Cypress, load tests, manual testing with your team.
6. Launch and training (1–2 weeks). Production deploy, data migration, user training, documentation.
7. Maintenance (3–12+ months). Bug fixes, new features, performance monitoring, dependency updates.

Between phases — short 1–2 week pauses to gather feedback. This lets us course-correct without reworking large blocks.

Security, GDPR and EU compliance

If your Lutsk business works with Polish, German or other EU partners — GDPR is mandatory. I bake security requirements in at the architecture stage:

• Encryption. TLS 1.3 in transit, AES-256 for PII at rest (phone numbers, emails, passport data).
• Audit log. Every user action (creating/editing/deleting entities, viewing sensitive data) is logged with timestamp, user_id, IP.
• Backups. Daily automated with 30-day retention, point-in-time recovery up to 7 days, geo-distributed replication.
• Right to be forgotten. A tool to anonymise or fully delete user data per GDPR Article 17.
• 2FA, SSO, RBAC, ABAC. Multi-factor authentication, single sign-on, flexible roles and field-level access.
• DPA. A ready-to-sign Data Processing Agreement template in UA/EN/PL for partners.

For mission-critical SaaS products I recommend a basic pen-test before public release — and budget for it inside the project.

Common mistakes when ordering CRM/ERP — and how to avoid them

Over 15 years in product development I've seen Lutsk companies lose serious money to typical traps. The most common:

• "Make it like the competitor's." The competitor spent a year or two tuning their system to their specifics. Copying their functionality means copying their mistakes. Always start from your own processes.
• Cutting discovery short. "Let's save 2 weeks and start coding right away" is a guarantee that 4 months later you'll find critical gaps and rebuild half the system.
• Everything at once. Trying to ship a "perfect ERP" with all modules in a single year fails 80% of the time. Always start with an MVP and grow incrementally.
• Hourly billing without scope. If a contractor can't name a fixed price — they don't understand the project. Beware of the "let's code and see what we end up with" model.
• Vendor lock-in. Systems where the code, data or infrastructure don't belong to you are a trap. Always demand code in Git, DB access, full documentation.
• Ignoring UX. Internal systems still need a great interface. If a manager in Lutsk spends 5 minutes creating a deal instead of 30 seconds — you pay for that every day.
• No development plan. A system is a living thing. If you don't have budget for development and support — set it now, not "when we figure things out."

Trends 2025–2026: AI, edge, low-code

CRM/ERP/SaaS development evolves fast. Trends I keep in mind for projects in Lutsk and the region:

• Built-in AI features. Sales forecasting, lead scoring, AI transcription of Binotel calls, automatic document classification, support chatbots powered by GPT-4o or local LLMs.
• Edge computing. For agriculture and logistics — part of the computation runs at the edge (data terminals, IoT sensors in fields, in-vehicle computers).
• Low-code integrations. n8n, Make, Zapier — quick glue for non-standard integrations, without rewriting the core code.
• API-first. Every new system is designed as a set of APIs that can be plugged into any interface or external service.
• Real-time via WebSockets. Collaborative editing, instant notifications, live dashboards — the new standard.

Cases: CRM, ERP and SaaS in the portfolio

My portfolio includes 130+ projects, of which 30+ are CRM, ERP or SaaS. Most relevant for Lutsk businesses:

• BMW Service CRM — a customer service system for an official dealer: booking, history, integration with the manufacturer's ERP.
• Alt Mobile CRM — a CRM for field teams with offline mode and sync when connectivity returns.
• European Auto Parts CRM — a B2B portal for auto parts suppliers with catalogue, warehouse, ERP integration.
• Cyty App / High-Level Remodeling — SaaS platforms for project management in construction.
• Solars Power Systems — an accounting and monitoring system for an energy company with SCADA integration.
• Fundly Hub — a fintech SaaS for managing investment portfolios.
• Best365Care — a medical SaaS platform for private clinics.

To see screenshots, architecture diagrams and outcomes — visit the "Projects" section or write via the contact form. I'll select 5–10 cases most relevant to your niche.

What you receive after the project is complete

• Codebase in a private Git repository with full commit history, ready to be developed by any team.
• Technical documentation — architecture, ER diagrams, API reference (Swagger/OpenAPI), deployment guides.
• Design system in Figma — UI kit, prototypes, developer guides.
• Infrastructure — Terraform/Ansible scripts for deployment, CI/CD pipelines, monitoring, logging.
• Exclusive proprietary rights to the code, design and documentation — fixed in the contract.
• Team training — 4–8 hours of sessions for admins and users.
• Support — 30 days free after release, then under a separate agreement (SLA of your choice).

My other services for businesses in Lutsk

CRM/ERP/SaaS is part of an ecosystem. Often the system needs other components alongside it:

• UI/UX design — system interface in unified style with your brand.
• Web development — public marketing site of the SaaS with blog, documentation, customer portal.
• Mobile app design — for field CRM teams, agronomists, warehouse staff.
• Mobile development — iOS/Android clients to the main system.
• Branding — visual identity for a SaaS launching into Poland or the EU.
• UX audit — evaluating existing systems before redesign or migration.
• SEO — so your SaaS gets found in search in Lutsk, Kyiv and Poland.
• Google Ads and email marketing — to launch a new SaaS product.
• Conversion optimisation — increasing the sales conversion inside the CRM.
• Business consulting — digitalisation strategy before investing in development.

CRM/ERP/SaaS development in other Ukrainian cities

Beyond Lutsk, I actively work with companies from other regions:

• Kyiv — corporate CRMs for national chains, fintech SaaS, B2B portals.
• Lviv — IT startups targeting the EU, product SaaS.
• Rivne — ERPs for manufacturing and agro companies (right next to Lutsk — projects often run in parallel).
• Odesa — CRM for retail and e-commerce, logistics systems.
• Dnipro — industrial ERPs, B2B platforms.
• Kharkiv — IT, education SaaS, engineering systems.

Full list of locations — on the "Service Areas" page.

Ready to discuss CRM, ERP or SaaS for your business in Lutsk?

The first step is to fill in the contact form or write to email/Telegram (contacts in the footer). The first consultation is free, up to 60 minutes. We'll discuss your business, current systems, goals, an approximate budget and timeline. If the project looks realistic — I propose discovery as a separate phase with a fixed price. Discovery doesn't oblige you to continue: you receive a documents pack and can either start with me or take it to the market to compare proposals.

I'm ready to build for your business in Lutsk a system that actually works — not "another CRM," but a tool that saves your team hours every day and opens new markets. Looking forward to your message.