Custom Software & Systems Engineering
Custom software for companies that have outgrown standard tools.
Standard tools may no longer fit the way you work, integrations may break whenever one system changes, or a legacy system may be holding back the next step. You may also have a new product to build.
We design and build web and mobile applications, B2B platforms and backend systems. Before we commit, we check that the people, the schedule and the payment stages are realistic for the scope.
An example failure plan for a checkout, written at design review before the build. If the payment provider does not answer in time, the system is designed to retry with the same idempotency key, so the customer is charged once. If an order event arrives twice, it recognises the copy and ignores it, so the order is recorded once. If orders arrive faster than they can be processed, it holds them in a queue and handles them in turn.
What we build
Products and platforms
Custom web and mobile applications, B2B platforms and software-as-a-service (SaaS) products, delivered as individual projects.
Backend, APIs and integrations
Backend and API development, integrations with CRM and ERP systems, financial and payment integrations, and billing and reconciliation workflows.
Modernisation
Moving a legacy system to an architecture your team can maintain, in stages, while the business keeps working on it.
Reliability and operations
Distributed systems, performance and scalability, observability, reliability and fault tolerance, and platform engineering.
Architecture and consulting
Architecture and technical consulting for teams deciding how to build, split or change a system.
Security-aware engineering
Access, data handling and dependencies are considered from the first design, not added at the end.
Some of this work starts as an automation that needs its own application or a deeper integration; that side is described under AI & Business Automation.
If the system already exists and reliability is the worry, start with an audit.
How delivery risk is handled
Before we commit to a project, we check that the scope, a realistic schedule, the people needed, security, the payment stages and the liabilities all fit together. That check happens during discovery, before a quote for the whole project.
There is no ready-made large team. Delivery capacity is assembled for each project once scope and schedule are agreed, and the person who scoped the work stays involved while it is done.
Work is delivered in stages, with regular demonstrations of working software, and payments are tied to those stages. Security is reviewed at each stage, as part of the design.
Who leads the work
Projects are led by the founder, Bartłomiej Różycki, a software engineer with deep experience in backend and distributed systems, gained in fintech and e-commerce, where reliability and fault tolerance are part of everyday work.
Typical projects
Example situations, not client projects
Replacing spreadsheets with an internal platform
Imagine a company that runs orders, approvals and stock through shared spreadsheets and email. The work would map the process, then replace it in stages with one internal application that keeps a single record of each order.
Connecting a shop, an ERP and a payment provider
An online shop, an ERP system and a payment provider each hold part of the picture of an order. Here the work would connect them so that payments, refunds and stock are reconciled, and mismatches are flagged instead of being found at the end of the month.
Modernising a legacy system in stages
A system the business depends on is hard to change, and few people understand it. The work would move it to a maintainable architecture one part at a time, so the business never depends on a single risky switch-over.
How a project runs
- 01
Discovery
We learn how the business works, what the system has to do and what it must never get wrong.
- 02
Scope and plan
We agree the scope, a realistic schedule and the payment stages, and confirm who will do the work.
- 03
Staged build
Software is built in stages, with regular demonstrations of working software, so you can change direction early.
- 04
Release
Finished stages are released into use, and the next stage starts from what was learned.
Questions people ask
Fixed scope or phased delivery?
Either can work. A fixed scope suits a well-defined piece of work; phased delivery suits a product whose details will change as you learn. We suggest one during discovery and explain why.
Can you work with our existing team?
Yes. We can work alongside your engineers on an agreed part of the system.
What does the system need to do?
Describe the work, the systems around it and any deadline. We'll reply by email, usually with questions or a suggestion for a call.