Custom software

A tool built around the way you work

When off-the-shelf software forces your team into awkward workarounds, a tool built around how you actually operate usually works out cheaper.

  • Priced after a conversation
  • You own the code
  • Delivered in stages

When it pays off

Signs it's time for your own tool

If at least two of these sound familiar, a conversation is probably worth your time.

A spreadsheet has outgrown itself

Several people edit the same file, nobody is sure which version is current, and one mistake can cost a day of work.

Someone retypes data between systems

Every day a person moves the same information from one system into another. That work can happen on its own.

You pay for features nobody uses

The subscription grows with every user added, while the team uses a small fraction of what the tool can do.

Your process doesn't fit the software

The business bends around the program instead of the other way round, and every exception is handled by hand.

Scope

What I can build for you

I work in web technologies, so the tool runs in a browser — on a desktop and on a phone alike.

Internal dashboards and apps

One place where the team runs orders, bookings or records, with permissions matched to each role.

Integrations between systems

Connecting your shop, warehouse, accounting and other tools so data moves without anybody retyping it.

Automation of repetitive work

Reports, notifications and documents generated without a person involved, on a schedule or triggered by an event.

Extending what you already have

Adding the missing pieces to a system you already run, instead of replacing everything from scratch.

Ground rules

How I run these projects

Custom software has a habit of getting out of hand. Three rules keep it under control.

01

Smallest working version first

We start with the feature that solves the main problem. You use it in practice, and only then do we decide what comes next.

02

Priced stage by stage

Every stage has its own price and deadline. You can stop after any of them holding a working tool, not half a project.

03

The code and data are yours

The repository and database belong to you. You can hand them to another developer at any point — we don't build a dependency on me.

Questions

Worth settling upfront

What does custom software cost?

It depends entirely on scope, so I won't quote a range out of thin air. After we talk through the process you get a price and deadline for the first stage — and only then do you decide.

How long does a project take?

The first working version is usually a few weeks. I deliberately keep it small so you see the tool at work quickly, instead of waiting months for a complete feature set.

What if the requirements change along the way?

That's normal, which is why I work in stages. The scope of the next stage is agreed after you've used the previous one — changing direction doesn't mean throwing away the budget.

Who maintains the tool afterwards?

I can look after it on an ongoing basis, or hand the documentation to your team. There's no lock-in — the code is yours and whoever you choose can work on it.

Contact

Let's talk about your project

Write a few sentences about what you need. I reply within one business day, usually sooner.

Phone
790 542 202
Where I work
Remotely, with clients across Poland and beyond

The person replying is Sebastian Rykowski — not a consultant and not a ticketing system.