CRM, ERP and SaaS Development in Lutsk, Ukraine
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.
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
Business Process Analysis
I deeply study your workflows, user roles, pain points, and system requirements. I build a process map.
Information Architecture
I design system structure, navigation, data hierarchy, and access roles. I define key usage scenarios.
Wireframes & Prototype
I create schematic layouts of main screens and an interactive prototype for testing with real users.
UI Design & Design System
I develop the visual style, component library, and detailed mockups for all system screens.
Testing & Handoff
I conduct usability testing, make adjustments, and prepare complete documentation for the development team.
Pricing
Choose the optimal package for your project
CRM Start
Basic CRM system
$3000$4000What's included:
- Customer management module
- Sales funnel
- Tasks and reminders
- Basic analytics
- Responsive interface
- Team training
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
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
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
Portfolio
Examples of completed projects
Frequently Asked Questions
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:
- MVP CRM for a sales team (lead cards, pipeline, Binotel/Phonet telephony integration, basic reporting) — 3–5 months of development.
- Industry ERP for manufacturing, logistics or agriculture (warehouse, document flow, 1C/BAS and M.E.Doc integration, roles, branches) — 6–10 months.
- SaaS product with multi-tenancy, billing, customer portal, analytics — 8–14 months, with ongoing development afterwards.
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:
- Processes. In a boxed system you're limited to built-in pipelines and fields. In custom — any logic, including non-standard stages for agricultural seasonality or customs clearance.
- Integrations. 1C/BAS, M.E.Doc, PrivatBank, Monobank for Business, PUMB, Binotel, NovaPoshta API — all connected directly, without tier limits.
- Data. Your server, your DB (PostgreSQL), full export anytime. In a boxed system, data lives in the vendor's cloud, export is restricted.
- Pricing. Boxed systems charge per user (for a team of 30 in Lutsk that's $300–600/month forever). Custom — fixed development cost + cheap hosting.
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:
- Frontend: Next.js 15, React 18, TypeScript, Tailwind CSS — fast rendering, SEO for public SaaS pages, excellent support.
- Backend: Node.js (NestJS or Express), TypeScript — one language across front and back, easier to scale the team.
- Database: PostgreSQL — reliable relational DB for CRM/ERP. For specific tasks — Redis (cache, queues), MongoDB (logs).
- Infrastructure: Docker + Docker Compose or Kubernetes (for large SaaS), nginx, CI/CD on GitHub Actions or GitLab CI.
- Hosting: your server (Hetzner, OVH, a local data centre in Lutsk or Lviv) or cloud (AWS, GCP, DigitalOcean).
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:
- 1C/BAS Accounting, BAS ERP. Two-way sync: counterparties, items, invoices, acts, delivery notes. Through 1C web services or ready-made connectors.
- M.E.Doc / Sonata. Automatic generation and dispatch of tax invoices, EDI exchange with counterparties.
- Bitrix24. If you're keeping it partially — sync of leads, deals, contacts via REST API.
- Banks: PrivatBank, Monobank for Business, PUMB, Raiffeisen — statement import, payment generation, receivables control.
- Telephony: Binotel, Phonet, UniTalk, Asterisk — call recording, attachment to client cards, WhatsApp/Telegram monitoring.
- Logistics: NovaPoshta API, Ukrposhta, for export — DPD, GLS, Schenker.
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:
- Schema-per-tenant in PostgreSQL. Each client gets its own schema in one DB. Scales to hundreds of tenants, with cheap backups.
- Database-per-tenant. Separate DB for large enterprise clients — full isolation and the ability to physically host in a specific jurisdiction (e.g., on servers in Poland).
- Row-level security. A single tenant_id in every table — the simplest and fastest option for SaaS with thousands of small clients.
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:
- Agro monitoring. Field cartography (integrations with Cropio, Soft.Farm, eFarmer), crop rotation tracking, fertiliser logs, yield forecasts, fuel control.
- Warehouse and WMS. Lot tracking, FEFO/FIFO, barcoding and data terminals, inventory, expiry control for food production.
- HACCP compliance. Critical control point logs, temperature logs from IoT sensors, audit reports for EU certification.
- Logistics and export. Routing, NovaPoshta and DPD integration, customs declarations, document flow with Polish and German counterparties.
- Production accounting. Technological cards, norms, cost accounting, MRP planning.
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:
- Encryption. TLS 1.3 for all connections, AES-256 for data at rest, separate encryption for PII (phone numbers, emails, passport data).
- Audit log. Every user action logged with timestamp, IP, user-agent. Available to admin and exportable for audit.
- Backups. Automatic daily backups with 30-day retention, point-in-time recovery for the last 7 days. Stored in a separate geographic zone.
- Right to be forgotten. A tool to anonymise or delete user data on request — as required by GDPR Article 17.
- 2FA, SSO. Two-factor authentication mandatory for admins, optional for the rest. SSO via Google Workspace, Microsoft, or corporate SAML.
- Pen-test. Before launching large SaaS products I recommend a basic pen-test — included in the project budget.
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:
- Phase 1 (3–4 months): the system core — authentication, roles, main entities (clients, deals, products), telephony integration and basic reports.
- Phase 2 (2–3 months): integrations with 1C/BAS, M.E.Doc, banks. Document flow.
- Phase 3 (2–4 months): analytics, dashboards, BI reports. Mobile apps for field staff.
- Phase 4: AI features (sales forecasting, lead scoring), additional modules.
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:
- Access to a private Git repository (GitHub/GitLab) with the full commit history.
- Architecture, API and database documentation — in Notion or Confluence.
- Figma with the UI kit and prototypes.
- Deployment and infrastructure setup instructions.
- Contacts of the development team — so you can continue with them or with any other team without vendor lock-in.
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:
- Day 1–2: kick-off in Lutsk (or online), meeting key stakeholders — owner, department heads, IT lead.
- Day 3–5: user interviews — sales, accounting, warehouse, production. 45–60 minutes each. I record pains, workarounds, wishes.
- Day 6–8: analysis of current systems (1C, Bitrix, Excel, paper logs), as-is process map, bottleneck identification.
- Day 9–10: defining MVP scope, roles, integrations, non-functional requirements (load, security, localisation).
- Day 11–14: a low-fidelity Figma prototype, technical architecture, estimate and roadmap.
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:
- BMW Service CRM — a system for an official dealer: client booking, service history, integration with the manufacturer's ERP.
- Alt Mobile CRM — a mobile 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, prices, ERP integration.
- Cyty App / High-Level Remodeling — SaaS platforms for project and team management.
- Solars Power Systems — an accounting and monitoring system for an energy company.
- Fundly Hub — a fintech platform for investment management.
- Best365Care — a medical SaaS platform for clinics.
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.
Why choose me?
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 |
CRM/ERP/SaaS Dev in Lutsk — Alex Filiuk
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:
- 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.
- UX design (3–6 weeks). Screen prototypes in Figma, design system, interactive demos. Here we validate the logic before committing to code.
- Architecture and infrastructure (1–2 weeks). ER diagrams, API contracts, dev/staging/prod environment setup, CI/CD.
- Sprint development (2 weeks each). Every sprint — a demo meeting on Zoom, where I show finished features. Backend, frontend, integrations, tests.
- Testing and UAT (2–4 weeks). Unit tests, e2e on Playwright or Cypress, load tests, manual testing with your team.
- Launch and training (1–2 weeks). Production deploy, data migration, user training, documentation.
- 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.