Custom CRM, ERP and SaaS development for businesses in Lutsk — from CRMs for furniture manufacturers to ERPs for agri-holdings and billing for hotels near Lubart Castle. Stack: Next.js, Node.js, PostgreSQL, Redis. Integrations with 1C/BAS, Bitrix24, Nova Poshta, Liqpay.
Describe your business processes and the problems that need to be solved through automation.
I'll analyze your processes and propose the optimal CRM/ERP system architecture.
A ready CRM/ERP with configured workflows, dashboards, and integrations tailored to your business.
I develop business systems for your company's specific needs
Customer and deal management system: sales funnel, tasks, analytics, telephony integration.
CRM with ticket system, SLA control, knowledge base and customer portal.
Comprehensive enterprise management: finance, warehouse, production, HR, procurement.
Project management platform with kanban boards, Gantt charts and reporting.
Human resource management: recruiting, onboarding, time tracking, vacations.
Dashboards and reports for business analytics with real-time data visualization.
I deeply study your workflows, user roles, pain points, and system requirements. I build a process map.
I design system structure, navigation, data hierarchy, and access roles. I define key usage scenarios.
I create schematic layouts of main screens and an interactive prototype for testing with real users.
I develop the visual style, component library, and detailed mockups for all system screens.
I conduct usability testing, make adjustments, and prepare complete documentation for the development team.
Choose the optimal package for your project
Basic CRM system
$3000$4000What's included:
Extended CRM with integrations
$6000$8000What's included:
Full business system
$12000$15000What's included:
Cloud product turnkey
$20000$28000What's included:
Examples of completed projects
Answers to the most popular questions
The cost depends on the scope and complexity of the system. Approximate ranges I see on projects for Lutsk and Volyn businesses:
Exact figures come after discovery (1–2 weeks). I don't sell hours — for each project the scope, deadlines and cost are fixed in the contract. If you also need UI/UX design or branding for the SaaS product — we calculate it as a combined package, cheaper than separate services.
Boxed systems are a constructor where you adapt your business to the platform's logic. A custom CRM is the opposite: the platform adapts to your business. Key differences:
Boxed systems make sense at the start, when processes are not yet formed. Once you know exactly what works — custom pays off in 18–24 months. The decision logic is detailed in my business consulting.
I work with a team on a modern, proven stack that's easy to find and maintain in Ukraine and the EU:
For UX I use Figma — all documentation, prototypes and guides in one place. The development team comes online after the architecture is agreed: I bring in engineers from a network of trusted contractors I've worked with for years. For Europe-focused launches I factor in SEO and GDPR requirements.
Yes — this is part of a typical scenario for businesses in Lutsk and Volyn. The integrations I most often build:
If you have a specific system (agricultural field monitoring, warehouse SCADA, customs broker software) — we integrate via REST/SOAP/MQTT. At discovery I always ask for the full list of systems we need to connect to.
Yes. For businesses in Lutsk and the Volyn region I make time for in-person meetings — especially during discovery, when we need to quickly understand your processes, talk to department heads, see the warehouse or factory floor first-hand. Lutsk is just next to Rivne, and travel is part of my standard working format.
Meetings are held at your office or, if more convenient, on neutral ground — the Yevropeiskyi business centre on Hrushevskoho, coworking spaces on Lesi Ukrainky street, cafés in the centre near Theatre Square. Further work is hybrid: weekly online standups via Zoom or Google Meet, demos in Figma and Loom, communication in Telegram or Slack. If the project runs alongside main website development or a mobile app, the meeting cadence is synchronised.
Multi-tenancy means a single codebase serves many clients (tenants), and one client's data is fully isolated from another's. For SaaS products in Lutsk targeting Polish, Czech or German markets, this is critical for GDPR compliance and customer trust.
I apply different approaches depending on load:
Roles are flexible, down to field and action level. Owner, branch manager, sales rep, accountant, guest, API user — each sees only what's theirs. RBAC + ABAC, audit log of all actions, 2FA, SSO via Google Workspace or Microsoft Entra ID. The role architecture is designed during discovery and locked in documentation before code starts.
Volyn is a strong agricultural region and a hub of food production (Lutsk Dairy, Volynsky Kolos, Svityaz, Carpathian Apiaries, dozens of farming enterprises). For them I build modular ERPs that close specific tasks:
For small and mid-sized operations a modular approach is often optimal: launch the ERP core in 4–5 months, add modules incrementally. The business sees ROI immediately and doesn't pay for unused functionality. Other locations for similar projects — Lviv and Rivne.
Data security is the foundation of CRM/ERP/SaaS. For a Lutsk business working with Polish or German partners, GDPR is a mandatory minimum. What I build in by default:
I document data processing policy, the DPA, Privacy Policy and Terms in Ukrainian, English and Polish — so you can sign with EU partners without external legal help.
This is my favourite format, especially for Lutsk businesses commissioning a custom system for the first time. The logic is simple: first we launch an MVP — a minimum viable product solving one key task and delivering quick ROI. Then, based on real usage, we add modules.
A typical CRM/ERP roadmap looks like this:
Between phases — 1–2 month pauses for team adaptation and feedback collection. It's cheaper, safer and more productive than a single 12-month launch of a large system. If a mobile app is needed in parallel — we slot it into phase 3.
You do. 100%. The contract clearly states: exclusive proprietary rights to the code, design and documentation transfer to you after full payment. You receive:
Data lives on your infrastructure from day one: your server in Hetzner, OVH, a local data centre in Lutsk or Lviv, or your own AWS/GCP account. I don't store client data on my resources. If you ever decide to part ways — everything stays with you, no strings attached. This is a matter of principle: I build products, I don't build vendor lock-in.
Discovery is 1–2 weeks of work before development starts. Without it you can't accurately estimate a project, but you can guarantee blown deadlines. What we do:
The discovery output is a package of documents you can either start with me on, or take to the market to compare proposals. Discovery is a separate deliverable with a fixed price; it doesn't oblige you to continue. This stage is critical — and shouldn't be skipped, even when someone promises a "quick start." More on my approach — in product strategy.
My portfolio includes 30+ launched CRM, ERP and SaaS products. Among the cases relevant to Lutsk businesses:
Among the clients — companies from Ukraine, the US, the UK, Germany, Poland. This gives me a clear view of how a local Lutsk business can compete effectively in the international market — and how a custom system becomes the engine of that expansion.
Comparison with other options
| Alex Filiuk | Boxed CRM (amoCRM / Bitrix24) | |
|---|---|---|
| Adaptation to your processes | ✅ Built from scratch for your Lutsk business | 📋 Only within constructor limits |
| Integration with 1C/BAS and M.E.Doc | ✅ Two-way via official APIs | 💰 Paid modules with limited scope |
| Telephony Binotel/Phonet | ✅ Recording, analytics, scripts | ✅ Basic, no custom logic |
| Multi-tenant and roles | ✅ Flexible roles, branches, field-level access | ⚠️ Standard roles only |
| Code and data ownership | ✅ Your code, your server, your data | ❌ Data hosted in vendor cloud |
| Monthly fees | ✅ Only hosting + support | 💰 Per-user subscription |
| Meetings in Lutsk | ✅ In person at discovery | ❌ Chat-bot or call centre only |
| UX and product design | ✅ Figma prototype before code | 📋 "As-is" interface |
| Expansion to EU markets | ✅ EN/PL localisation out of the box | ⚠️ Partial localisation |
| Scaling under growth | ✅ Architecture for 100k+ records | 🔄 Plan tier rises with team size |
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.
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:
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.
These are three different products with different architectures and business logic. Here's how to tell them apart for your business:
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.
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:
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.
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:
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.
Transparency is the foundation of long projects. I work in a clear cycle where you see intermediate results every week:
Between phases — short 1–2 week pauses to gather feedback. This lets us course-correct without reworking large blocks.
If your Lutsk business works with Polish, German or other EU partners — GDPR is mandatory. I bake security requirements in at the architecture stage:
For mission-critical SaaS products I recommend a basic pen-test before public release — and budget for it inside the project.
Over 15 years in product development I've seen Lutsk companies lose serious money to typical traps. The most common:
CRM/ERP/SaaS development evolves fast. Trends I keep in mind for projects in Lutsk and the region:
My portfolio includes 130+ projects, of which 30+ are CRM, ERP or SaaS. Most relevant for Lutsk businesses:
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.
CRM/ERP/SaaS is part of an ecosystem. Often the system needs other components alongside it:
Beyond Lutsk, I actively work with companies from other regions:
Full list of locations — on the "Service Areas" page.
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.