Custom software

Custom software when a boxed tool forces workarounds

This page is the wide custom-software hub: operational panels, client portals, workflows and the integrations that glue them together. A first scope is PLN 25,000-60,000 net; a wider platform is PLN 80,000-200,000 net, same bands as the SaaS systems price list. We write the piece that sits between the tools you already pay for, not a full CRM or ERP from scratch. Own CRM or ERP from scratch lives on custom CRM and ERP. A shop with couriers and payments lives on the online shop page.

TL;DR: A first custom-software scope is PLN 25,000-60,000 net; a wider platform is PLN 80,000-200,000 net.

Who it is for

Panels, workflows and the glue between tools

For teams that need an operational panel, a client portal or a workflow boxed SaaS will not stretch to, without replacing the whole stack.

Scope

Process analysis, UX, web application, backend, database, API integrations, admin panel, monitoring and post-launch development.

Outcomes

What remains after the first scope

We do not start with a huge specification. First we build a small working scope that can be shown to the team and customers.

System matched to company processes

Client portal or operational panel

Glue to the CRM, ERP, payments and APIs you already run

Codebase ready to evolve after the MVP

Process

How we work

MVP scope

We define the smallest system that solves a real problem and can be deployed quickly.

Design and development

We build frontend, backend, database and integrations in short iterations.

Maintenance

After launch we provide monitoring, fixes, development and technical support.

Search intent

The wide custom-software hub

Greenfield CRM or ERP around orders, customers and warehouse goes to custom CRM and ERP. Retail checkout with couriers and payments goes to the online shop. Stay here for the panel, the workflow and the integrations between tools you already have.

Next step

We do not start with a huge specification. First we build a small working scope that can be shown to the team and customers.

The first slice is a screen the team can click: an ops panel, a dealer portal or a document flow. That is how Lugomat (B2B orders and the ops panel) and RehaTop (admin, checkout, feeds) actually started - not with a year-long specification.

A panel for a process, not a new ERP

When we write software instead of stacking another SaaS

This hub is the custom piece between tools you already pay for. A full CRM or ERP from scratch is a different page. A shop with couriers and payments is a different page.

The trigger is a process a boxed product will not hold

A contractor portal, a document circuit, an offer calculator, a service panel, a dealer price list that ERP cannot show. Teams usually arrive here after sheets, exports and three subscriptions start costing more than the work itself.

We do not copy the old chaos into a new UI. The first workshop cuts steps. The first delivery is the smallest screen that removes the worst workaround. More roles and integrations come after that screen is in daily use.

What we have already built in this shape

Lugomat is a B2B building-materials platform we took over: Phoenix and Nuxt, MeiliSearch, media, orders and an ops panel, after a PATHFINDER audit and a move to a dedicated host. RehaTop is a medical shop we moved off Shoper into our own monorepo - SSR storefront, API, admin, payments, couriers, feeds and CRM - with the catalog kept intact.

The electrical-equipment B2B platform is a 3000+ SKU dealer catalog with wholesale orders and ERP glue. CoreTSL is the other end of the spectrum: a full TMS, which belongs on the CRM/ERP page when the core objects are orders, fleet and invoices. This page stays on the piece that is not the whole system of record.

AI sits inside the screen

If the user is building an offer, the model drafts variants and checks completeness. If the screen is a document queue, it extracts fields. The result lands on the record, not in a side chat. A write still needs a role when the field is dangerous.

After go-live we keep monitoring, backups and a backlog. The product does not end on the launch day. Greenfield CRM or ERP still goes to custom CRM and ERP. Checkout with carriers still goes to the online shop.

Custom software

FAQ

Common questions about custom software development for companies - scope, deployment, data, cost and security.

01 When is custom software worth building? +

When a panel, a workflow or an integration is cheaper than stretching a boxed tool. If the real job is a full CRM or ERP from scratch, use the custom CRM and ERP page instead.

02 How much does custom software cost? +

A small MVP usually starts from several or tens of thousands of PLN. The final cost depends on integrations, roles, data and scope.

03 Do you maintain systems after launch? +

Yes. We implement monitoring, backups, updates and further development after launch.

From the old web apps page

B2B platforms and the SaaS card

The B2B section absorbed from the retired web apps URL: a contractor catalogue, accounts and browser orders. Login, database and integrations.

B2B platform

Catalogue, contractor accounts and orders in the browser. The panel, roles and integrations follow your process, not a shop template.

SaaS card

A platform with customer accounts, roles and payments (billing, subscriptions) lives on SaaS systems.