Corporate website
Five to eight pages with a CMS your team edits without calling us, a blog, working forms and a multilingual structure — Estonian, English and Russian, for example.
The package for a first real product. A corporate site your team edits itself, a bot that answers enquiries, two systems that finally exchange data, a dashboard someone opens every morning — or a clickable prototype to put in front of an investor. Interface design, documentation and 30 days of warranty support are part of the price, not an extra line.
Fixed scope · Fixed price · Source code yours
The price and the timeline are the same whichever variant you pick. What changes is where the two to three weeks go. Pick one — mixing halves of two variants turns the estimate into guesswork.
Five to eight pages with a CMS your team edits without calling us, a blog, working forms and a multilingual structure — Estonian, English and Russian, for example.
A bot that handles incoming enquiries by a scenario you approve, with its own database and an admin panel where your staff read, answer and export the conversations.
Site, CRM, accounting and payment gateway wired together through their APIs, with data kept in sync, retries on failure and a log you can read when something looks wrong.
Numbers from several sources pulled into one screen: charts, filters, export to Excel or CSV, and login-protected access so only your people see it.
Real interfaces and real logic without a backend behind them — enough to show an investor how the product behaves, or to test the flow with users before anyone pays for a database.
If your idea sits between Business and Pro, we will tell you which one it belongs to before you pay anything — including when the honest answer is the smaller package.
For thirty days after hand-over, anything that does not match the agreed scope is fixed free of charge. You write to the same address you already use; no ticket system to learn.
How it is built, where it runs, how to deploy it again, what every environment variable does, and a short editor guide for whoever updates the content.
The full repository with its history, in your organisation's account. Economic rights to the custom code pass to you on the final payment — nothing stays hostage on our side.
The last two belong elsewhere on purpose: billing and multi-tenancy are Pro, and ongoing maintenance is a care plan.
You see a staging link from the first day of the build, not a demo at the end. Written updates arrive twice a week, and every step finishes with something you can look at and comment on.
One call, then a written document: the list of pages or screens, the data that moves between them, the integrations involved, and everything deliberately left out. You approve it before the first line of code.
Layouts for every screen type — desktop and mobile — with the real navigation and real content blocks. Comments go straight onto the design; nothing is built from a guess.
Front end, CMS or admin panel, forms, the API work and the data sync. Staging link live from day one of this step, updated as the work lands.
Cross-browser and mobile testing, load and form checks, deployment to your hosting, then the documentation, the repository, the credentials and a walkthrough call. The 30-day warranty starts the day you accept.
If two or more of these are true, say so in the first message. Pro or a scoped discovery is usually the cheaper answer.
One focused task: a landing page, a technical audit, an automation script or ten hours of improvements on something that already exists.
A system the business runs on: roles and accounts, payments, subscriptions or a legacy migration — with 90 days of support and deployment on your infrastructure.
After the warranty month, a monthly care plan keeps hosting, updates, backups and monitoring in place from €150.
Two or three paragraphs about the product is enough to start. You get a written scope with the price, the exclusions and a delivery date — and an honest note if Start or Pro suits you better.