Custom software
for your business
- CRM, ERP and mobile.

Custom CRM, ERP and business automation for small and mid-sized companies - software you own outright. No subscription for every additional user, and no modules nobody at your company will ever open. The code goes to your repository from day one of the rollout, and the data stays with you. No vendor lock-in.

from 2 wks
from idea to a working system
free quote
tailored, no strings attached
4 in 5 clients
come back to us with the next job
web + mobile
panel and app, one team

Custom software for your company - our services.

We build systems around the way a business actually runs, so what you get is genuinely tailor-made. Sometimes that turns out to be a classic CRM or ERP, sometimes a system that fits no category at all. Here is what we do for small and mid-sized companies.

Custom CRM system

Sales run the way you run them - your pipeline stages, your rules for assigning clients. Accounts, quotes, contact history and permissions per role.

Custom ERP system

Orders, stock, production and documents in one place - built to exactly the scope you need and no further.

Warehouse system (WMS)

Picking and stock-taking on a scanner instead of on paper. Locations, quantities and stock movements written to the database in real time.

Mobile app for the field

A sales rep, technician, driver or warehouse worker gets exactly what they need on the phone, where they are. Integrated with the rest of your systems, and it works with no signal.

Portal for your clients

Catalogue, orders, statuses and documents available to your end client. They stop calling the office because they can see it all themselves - and what they enter lands straight in your system.

Integration with your ERP

We connect to the systems you already run and make sure the data matches everywhere. New capabilities added, nothing that works replaced.

Projects start at €2,250 net; the full ranges and delivery times are in the pricing section below.

Which system for
a small or mid-sized company?

The best place to start is wherever it hurts most today - in sales, in the warehouse, in service, on the production floor, or in the back office and customer support. We build the one piece that closes a specific problem first, and add the rest later. Six examples:

Mobile CRM for field sales

The rep takes the order on the spot at the client’s premises - they can see that client’s prices, credit limit and stock availability, and the order goes straight into the system. No more typing it up from a notebook in the evening.

Sales

Warehouse system (WMS) on a phone

The warehouse worker scans barcodes with a phone instead of writing everything down, and the app suggests locations and keeps quantities in check. Stock-taking runs on the same tool: the count is compared against the system immediately and the differences show up on the spot.

Warehouse

Service job system for technicians

The technician or driver gets the day’s job list, ticks off a checklist, takes photos and collects a signature on site. The service report, the parts used and the proof of delivery land in the system there and then, with no paper forms.

Service and deliveries

B2B portal for your clients

Catalogue, online ordering, statuses and documents available to the end client, along with notifications when something changes. A B2B platform like this collects enquiries in one panel instead of an inbox - the client stops calling because they can see everything themselves.

Customer service

Production system (MES) with reporting from the floor

The foreman reports completed operations and flags shortages straight from the floor, without walking to the office. Production and quality-control data reaches the system as it happens, so the planner schedules against real progress rather than against last shift’s state.

Production

Custom ERP panel for the office and the board

Every order, status and document flow in a single browser panel - the office distributes work and closes cases without chasing people by phone. Management gets the same reports on the phone, current to the minute, instead of waiting for month end.

Office and management

Why do companies pick
custom software over an off-the-shelf package?

An off-the-shelf CRM or ERP starts from the question “how do we fit the company to the system”. A custom one starts from the opposite - and you can see the difference in every week of work after go-live. Here is what it actually comes down to:

  1. Data entered once, with no spreadsheet alongside

    An order entered at the source is immediately in the warehouse, in accounting and in the report - no typos, no duplicate lines. An off-the-shelf system does that too, right up until it meets an exception nobody planned for. That is when a spreadsheet starts living next to the system, and the data is in two places again.

  2. The system fits your process, not the other way round

    We start with how you actually work - your naming, your exceptions and that one client who always does it differently. The screens come afterwards, and the fields in them are the ones you use rather than the ones prescribed for an entire industry.

  3. Paid once, with no subscription

    You pay for the build once and know the figure up front. The bill does not grow with every new person you hire - adding a fifth warehouse worker costs nothing. Your invoice does not scale with your headcount.

ERP integration or a build from scratch? We do both.

Most companies already run something - an off-the-shelf package, or something written to order a long time ago. Others have nothing beyond Excel and an inbox. Both are good places to start; they just lead down different roads:

Integration with your existing ERP

The problem is rarely that the system is bad - it is that it does not reach where it needs to: the field, the client, the shop floor. We connect through its API (or another route) and add the missing layer: an app for people in the field, or a portal for your clients. Data flows both ways, and you throw nothing away.

Your first system, built from scratch

Having no old system is an advantage, not a problem - there is nothing to work around and nothing to repair after someone else. We start with the one thing that hurts most: orders, the warehouse or field work. You get a working tool, and the system grows piece by piece at your company’s pace.

No surprises.
A partnership you can count on.

We break building a system into stages, and each one ends with something you can see and test - not a promise, but something concrete. We set the final scope together at the first, free meeting.

STAGE 0free

Let’s get to know your problem

  • Workshop: how you work today, who will use the system and what data is involved
  • Map: what the system should show and what it has to connect to
  • Scope of the first version + a joint decision: do we start or not
Stage outcomea written scope + a map of screens and connections
STAGE 1

Plan and system skeleton

  • We turn the workshop findings into a concrete build plan
  • We stand up the skeleton: login, access and a place for the data
  • We settle what the system connects to and what it stores
Stage outcomea finished foundation for the screens to stand on
STAGE 2

Design and main screens

  • Look and layout of the key screens - in the browser and/or on the phone
  • A clickable prototype: login, list, main action
  • Screens, errors and loading states thought through up front
Stage outcomea clickable prototype for sign-off
STAGE 3

A working system

  • Every screen wired to real data, live
  • Notifications and data kept current
  • A walkthrough of what the system does
Stage outcomea genuinely working system
STAGE 4

Testing with your team

  • Your team uses the system on real work and flags what to improve
  • We check the awkward cases against your company’s real data
  • We tune speed, stability and the small fixes that come out of your feedback
Stage outcomea system proven on real work, ready to launch
STAGE 5

Launch and support

  • We switch the system on live and stand by you on launch day - you are not left alone with the first real cases
  • The browser panel and the phone app ready to work (published to the stores if needed)
  • Documentation, code handover and a roadmap for the features that come next
Stage outcomea working system, your code and our support at launch

A small team. No subcontractors.

The same team that designs your system at the first meeting delivers it to the end - for desktop and for mobile. No project managers and no rounds of clarification with people who have never built a system. You deal directly with the team shaping your company’s technical future.

Adam Dziuk
Adam Dziuk
Foundation, data and logic
Radosław Draguć
Radosław Draguć
Mobile and web apps

What does custom software cost?
2026 pricing.

Not every project can be priced in a sentence, but every one falls into one of three ranges. Below we say plainly who each is for - so you know where you stand before you get in touch.

One process

€2,250 - €4,250

2-6 wks

Who it’s for

A company that wants to sort out one place - the one that hurts most. Orders lost in email, jobs written on paper, a warehouse run in Excel, or data retyped by hand between two programs. We close one thing and leave you a system that can be built on.

Enterprise-scale system

from €17,000

from 12 wks

Who it’s for

Rollouts where the system serves several departments at once, works on large volumes of data and has to tie into what already runs at your company - most often an ERP such as SAP, Dynamics, Comarch or Subiekt. On top of that come permissions across the whole organisation, a staging environment, monitoring and an agreed response time.

Net figures. Where a project lands inside its range comes down mainly to how many processes are in the first version, whether there is a mobile app, and how many systems it has to integrate with. You get a firm quote with a delivery date after the free first meeting, broken down by stage - so you can see what is genuinely needed now and what we would put off until later.

The questions we hear most often.

The five things you ask most before deciding: what if the budget does not stretch, how long a rollout takes, what happens to the system you already have, and what follows go-live. Short answers here - the rest we are happy to cover on a call or by email.

We will say it straight: below that figure we cannot build something you would be happy with, and we would rather not sell what ends in disappointment on both sides. That said, it is usually possible to narrow the scope to the one thing that hurts most and come back to the rest in a few months - we build systems so they can be extended, so this is not a dead end. If even that does not work, we will tell you honestly at the first meeting that at this stage you are better off on an off-the-shelf tool with a subscription. That conversation costs you nothing either way.

The first working version - the one that closes a single process and that people can already work on - takes from 2 weeks. A full CRM or ERP is usually a few months, but you are not waiting on it blind: we hand the system over in stages, and after each one there is something you can see and test. You get a firm date together with the quote, after the first meeting.

Yes. If your system exposes an API, we connect to it - which is what lets data flow both ways. If there is no API (normal enough on older rollouts) there are other routes, and integration stays possible. We do not replace what works; we add the layer that is missing: an app for people in the field, or a portal for your clients.

Yes, data migration is part of the rollout, not a separate project. We take what you have - spreadsheets, exports from the old program, sometimes the database itself - and run a trial migration before go-live, so you see the result on your own data. Duplicates and mismatches between files are usually what surface at that point. Your old system stays untouched.

You pay no subscription for the system itself - it is yours. What remains is the cost of a server and a domain, somewhere between €10 and €200 a month depending on scale, paid directly to the hosting provider rather than to us. The code goes to your repository as we work, together with the documentation, so you can develop the system yourselves or with someone else - it runs on Laravel and Flutter, and there is no shortage of specialists in either. If you would rather stay with us, we agree a support model: hours, a package or ongoing care.