Web application
Registration and login, user roles and permissions, a relational database, a personal account area, a full admin panel and a documented REST API for whatever needs to connect later.
Package 03 — Pro
Custom systems, built to last.
Four to six weeks of engineering for the software your business will still depend on in three years: an application with real users and roles, a store that takes money and ships parcels, or a SaaS product with subscriptions and tenants.
€2500 fixed
4–6 weeks
90 days support
Training session
Who this is for
When the software
is the business.
Pro is for systems that carry money, customer data or daily operations. That changes how we work: proper data modelling, access control, error handling, backups and a deployment you can roll back. It is slower on purpose.
Real users log in and see different things by role
Money moves through it, or stock does
Another system will need to talk to it via an API
An old system holds data you cannot afford to lose
Choose exactly one
Five builds.
All production-grade.
Larger scopes are quoted individually — Pro is the baseline for custom engineering, not a ceiling.
Online store
Catalogue, cart and checkout, payments through Stripe, Montonio or Estonian bank links, stock tracking, shipping integration with Omniva or DPD, and automatic invoices sent to the customer.
SaaS MVP
Subscription plans and billing, multi-tenancy so each customer's data stays separated, trial handling, a usage-limit system and the basic analytics you need to know whether anyone is actually using it.
Turnkey process automation
We start by mapping how the work actually happens today, design the target process, build the software that runs it, then train your staff to use it. Ends with people working differently, not just a new tool.
Legacy migration
Moving an old system onto a current stack without losing history. Data is mapped field by field, migrated in dry runs first, verified against the original, and only then switched over — with a rollback path ready.
Always included
90 days of post-launch support, deployment onto infrastructure you own and control, complete technical documentation, and a one-hour training session recorded so new staff can watch it later.
Engineering standards
What "production-grade" means here.
Access control by design
Permissions are modelled at the data layer, not hidden by the interface. A user who should not see a record cannot fetch it through the API either.
Backups and rollback
Automated database backups with a tested restore, and deployments that can be reverted to the previous version in minutes rather than hours.
Observability
Structured logging and error reporting from day one, so when something breaks at 23:00 the cause is in a log, not in a guess.
Tests where they pay off
Automated tests on money, permissions and data integrity. Not 100% coverage theatre — coverage on the parts that hurt when they break.
Documentation that survives you
Architecture notes, environment setup, deployment steps and known trade-offs — written for the next developer, whoever that turns out to be.
No lock-in
Standard frameworks, standard databases, your own cloud accounts. Nothing in the build requires us to stay involved after handover.
Timeline
Six weeks,
five milestones.
WEEK 1
Specification & data model
User roles, entities, relationships and the main flows written down and agreed. Cheap to change now, expensive to change in week five.
WEEK 2–3
Core & API
Database, authentication, permissions and the API. The admin panel comes online so you can see and edit real records early.
WEEK 3–4
Interface & integrations
User-facing screens, plus payment, shipping or third-party connections wired to their sandbox environments and tested end to end.
WEEK 5
Hardening
Load, permission and failure testing. Backups configured and a restore actually performed. Monitoring and error alerts switched on.
WEEK 6
Launch, training, handover
Production deployment on your infrastructure, a one-hour training session, documentation and source transfer. 90 days of support begins.
Pro — FAQ
Before we start
something this size.
For projects at this level we would rather spend an extra hour on the specification than an extra week on a rebuild.
For a well-defined first version, yes — that is exactly what the fixed scope is for. It is not enough for an open-ended product with a moving feature list. If your idea is bigger than the package, you get an honest hourly estimate instead of a false promise.
Stripe and Montonio most often, plus direct Estonian bank links. Others are possible if they publish a documented API. Provider fees, contracts and KYC are between you and the provider — we build and test the integration.
Deployment goes onto infrastructure you own — your cloud account, your domain, your database. We configure it and hand over the keys. If you would rather not manage it, a care plan covers that separately.
Defect fixes, help with questions about how the system works, and assistance with configuration issues after launch. It does not include new features or content work — those are quoted separately or covered by a care plan.
Yes. We can work in your repository, follow your code standards and hand over via pull requests. It usually adds a little time for coordination, and that is reflected in the offer.
Nothing is destroyed. Migrations run as dry runs against a copy first, results are verified record by record against the original, and the old system stays available read-only until you confirm the new one is correct.
Custom engineering
Bring the hard one.
Send the requirements, the old system or just the problem. You get a specification proposal and a fixed date back.
Start small
Start — €500
Audit the existing system first, then decide whether to fix, rebuild or migrate.
Open
Middle ground
Business — €1200
A CMS site, a bot, an integration or a dashboard in two to three weeks.
Open
Bigger than Pro?
Custom quote
Multi-month projects are estimated individually, in phases with fixed prices each.
Talk to us