In short
Web and mobile apps, online stores and internal systems — built from scratch around your process.
A simple website in as little as 7 days. A first working MVP usually within a month.
Smaller project — fixed price. Larger — time and materials, without a fictional budget agreed up front.
Warranty and post-launch support are included in the project price.
We take over projects from previous suppliers, including unfinished ones.
Poland-based, one hour ahead of London and in the same time zone as Berlin.
What we build
Web applications
Systems people use every day at work — dashboards, platforms and tools that carry your process end to end. This is most of what we do.
Online stores
E-commerce built around a specific sales model rather than bolted onto a template, with an admin panel your team can actually work in.
Mobile applications
Android and iOS in React Native or Flutter — one codebase for both platforms, from first release to the App Store and Google Play.
Internal systems
Custom tooling for your team: document flows, registries, operational dashboards — everything that currently lives in spreadsheets.
When custom software is worth it
Not always. If an off-the-shelf tool does what you need, custom software will be slower and more expensive — and we will say so.
It is worth it when:
- your process is your advantage, and bending it to fit somebody else's template erases that advantage,
- you pay subscriptions for features you barely use while the one you actually need is missing,
- data lives in several places at once and somebody retypes it by hand between a spreadsheet and a system,
- the off-the-shelf tool caps your growth — it cannot be extended in the direction the business is going.
How long it takes
Real timelines from our projects, not brackets from a price list.
How we run a project
Short iterations instead of one big hand-over at the end — by then it is too late to correct course.
Scoping conversation
We establish the business goal and the shortest path to it. You leave with a concrete scope and an estimate.
Design and architecture
We decide what goes into the first version and what we deliberately postpone. That first scope is always smaller than it looks at the start.
Iterations
We work in short cycles and show working versions as we go. You can change direction during the project rather than after it.
Release
The first version goes to production early — real feedback from users is worth more than another month of adding features.
Warranty and growth
After launch you are covered by warranty and support. Further development and infrastructure upkeep are billed separately.
Fixed price or time and materials
A smaller, well-defined project — fixed price. We know what is being built, so we know what it costs. No hours added after the fact.
A larger project — time and materials. On a multi-month system a fixed price is a fiction: either we add a thick risk buffer you pay for whether or not the risk materialises, or the first scope change breaks the contract. Time and materials is fairer to both sides and lets priorities change mid-project.
Which model fits your project is something we settle on the first call, together with the scope that can realistically ship in a first version.
Examples
Bezuma — an online store in 3 weeks. From zero to a version where the client adds products and runs sales themselves. Design, delivery, content and search optimisation on our side.
LGD Gorce-Pieniny — a site in 2 weeks. Our fastest full delivery: from design to a live site in a fortnight.
Bus-Koncert. A platform designed, built and delivered end to end by our team.
The common thread: a first working version reaches users quickly, and development continues based on what they actually do rather than what we assumed at the start.
What you get
Code that is yours
The repository and the IP transfer to you. No lock-in written into the contract.
An admin panel
You change content and data yourselves, without filing a ticket for every typo.
Working versions as we go
Progress is visible in your environment, not in a status report.
Post-launch warranty
Defects within the agreed scope are fixed under warranty, without a separate invoice.
Support after go-live
We stay reachable after launch. Further development and upkeep are quoted separately, but we do not disappear.
What we build with, and why
In roughly 90% of projects we work on a JavaScript and TypeScript stack: Next.js, React, NestJS and Fastify. Mobile applications are built in React Native or Flutter, depending on what the project needs. Less often, when there is a reason, we reach for Python or Ruby.
This is not fashion. One language across front end, back end and mobile means the same team works across the whole project, and you do not pay for translation between two worlds. Hiring another developer into that stack is also realistic — and that is your risk, not ours, if you ever bring the project in-house.
We take over projects from other suppliers
It happens that a project stalls: the supplier stops responding, the code is in a state nobody understands, or the application runs but cannot be developed further.
That is not a problem for us. We start with an inventory — what exists, what the access looks like, what is missing — and get the project to a state where it can be rebuilt from scratch. Only then do we talk about new features.
After that review we say plainly what is worth saving and what is cheaper to rewrite. Including when the answer is inconvenient.
Working with a team in Poland
We are based in Dąbrówka near Poznań, Poland. For clients in Western Europe that means an almost complete working-day overlap — questions get answered the same afternoon, not the next morning.
Just Site sp. z o.o. is a registered EU company, so contracts, IP assignment and GDPR sit inside one legal framework.
More on how we work: software house in Poznań and our office and company details.
Get your project estimated
Tell us what you want to build. We reply within 24 hours and help you define the scope of a first version — including when our answer is that an off-the-shelf tool would do.
