From 1000 zł net.
The rest depends on the product.
We don't publish a full price list — that would mean selling hours or templates. We do publish where it starts. A site for a small business begins at 1000 zł net to build and 100 zł net a month to keep running; a platform costs what a platform costs. Below is exactly how we get from one to the other.
Where it starts
That is a starting point, not a package. We work with one-person businesses and with companies that have their own IT department, and scope is agreed with each of them separately — which is why you'll get a number for your project rather than for a tier someone put you in.
How we get to a number
A call
30 min, free, no strings. You describe what you want to build. We tell you whether it makes sense, whether we're the right people for it, and what we'd be worried about. Sometimes that call ends with us saying you don't need us — that's a good outcome too.
Diagnosing the problem
Before anything gets costed we take the idea apart: who is it for, what has to be true for it to work, which part is genuinely hard. Most of what makes a project expensive is decided here, not in the code.
A prototype in a week
Something that runs, that you can click, built from the riskiest part first. It exists so you can see the thing before committing to all of it — and so our estimate is based on code we've written, not on a guess.
The actual quote
Scope, stages and a number, in writing. Split into milestones, so you are never paying far ahead of what exists.
Build, launch, iterate
The same two engineers who quoted it build it. Nothing gets handed to a junior after signing, because there is nobody to hand it to.
What moves the number
Pushes it up
- Integrations with systems we don't control — someone else's API, your ERP, a bank.
- Hardware. The moment a product touches the physical world, the unknowns multiply.
- Compliance and security: personal data, payments, anything regulated.
- Open product decisions. Every question still unanswered when we start is time spent answering it later, expensively.
Pulls it down
- A problem you can state in one sentence.
- One audience instead of three.
- Agreeing that version one doesn't have everything — the fastest projects are the ones that shipped something small first.
- Existing design, content or infrastructure we can build on.
Straight answers
Have a product in mind?
Two engineers from Poznań building web, mobile and hardware products — from a one-page site to a platform.