Web application
User registration and roles, a database, a personal account area, an admin panel and a REST API. The full spine of a product — including the parts other software will need to talk to.
Custom development for software with real users, real money and real data behind it. Four to six weeks of engineering for a fixed €2 500, finished with deployment on your own infrastructure, written documentation and 90 days of warranty support.
One Pro project is one of the five variants below, described in writing before anything is paid. If your problem sits between two of them, we say which one it belongs to and why.
User registration and roles, a database, a personal account area, an admin panel and a REST API. The full spine of a product — including the parts other software will need to talk to.
Catalogue, cart and payments through Stripe, Montonio or bank links. Stock levels, delivery integration with Omniva and DPD, and automatic invoices for every order.
Subscriptions, billing, multi-tenancy and basic analytics — enough product to charge money for it and to learn something real from the first paying accounts.
Process survey, design, rollout and staff training. We map how the work is done today, then build the system that takes over the repetitive half of it.
Moving an old system onto a current stack with the data preserved: schema mapping, a rehearsed migration run, a switch-over plan and a documented way back.
Tell us what the business needs to stop doing by hand. We will say which variant covers it, or tell you plainly that Pro is not the right size yet.
Send the detailsThese are part of the €2 500, not an upsell at the end. They are the difference between software that was delivered and software your team can actually operate.
Anything outside the written scope is quoted before work starts. The €2 500 does not move on its own halfway through a sprint.
A Pro project is long enough that "we'll see how it goes" is not a plan. Each step has an output you can read, and a staging link exists from the first build sprint.
Two or three working sessions on users, roles, data and the money path. Output: a written scope with the variant, the deliverables, the exclusions and the delivery date.
Data model, API surface, third-party services, environments and access. Output: a short architecture note you can hand to any other engineer, plus the migration plan when an old system is involved.
Work lands on a staging link you can open any day. Written updates twice a week, a place to leave comments on what you see, and revision rounds agreed per milestone rather than saved to the end.
The six checks below are worked through, then the system is deployed to your own infrastructure with backups, monitoring and a documented rollback in place.
A one-hour session for your team, recorded so new colleagues can watch it later. Then 90 days in which defects in the agreed scope are fixed at no cost.
The parts nobody demos, and the parts that decide whether the system survives its first bad day. Every Pro project goes through the same six checks.
Hashed passwords, sane session and token handling, and permission checks enforced on the server — not only hidden in the interface.
Automated database backups, plus one restore actually performed before hand-over — so recovery is a rehearsed step and not a theory.
Structured application logs, error reporting and an uptime check, so a failure is noticed by the system before it is reported by a customer.
Server-side validation on every write path, parameterised queries, upload limits and output escaping. The boring defence that stops the common attacks.
Every schema change is a versioned migration that runs identically on a laptop, on staging and in production. No manual edits to a live database.
A run against the traffic you actually expect, to find the slow query or the missing index before your users find it for you.
A complete small product rather than a platform: corporate site with a CMS, a bot, an integration, a dashboard or a clickable prototype. 30 days of warranty support.
What follows the 90 days: hosting, updates, backups and monitoring, plus an optional pool of development hours every month for the small changes that keep arriving.
Send the shape of the problem — users, roles, data, the thing that has to stop being manual. You will get a human answer within one business day, including an honest note if Pro is more package than you need right now.