Corporate website
Five to eight pages with a CMS you actually understand, a blog, working forms and multilingual content — typically ET / EN / RU. Editable text, images, pages and menus without touching code.
Package 02 — Business
Two to three weeks of focused work that ends with something your team actually operates: a multilingual site you can edit yourself, a bot that handles enquiries, an integration that stops the copy-paste, or a dashboard that answers a question every morning.
Who this is for
Business is the package for companies that already work — orders arrive, clients call, invoices go out — but the process leaks through spreadsheets, WhatsApp threads and manual re-typing. We build the one product that plugs the biggest leak.
Choose exactly one
Each is a finished, documented system handed over with its source code. Scope is agreed in writing before the first commit.
Five to eight pages with a CMS you actually understand, a blog, working forms and multilingual content — typically ET / EN / RU. Editable text, images, pages and menus without touching code.
A bot with a real database behind it and an admin panel in front: scripted conversation flows, enquiry capture, statuses, notifications to your staff and an exportable log of everything that happened.
Your website, CRM, accounting software and payment provider talking to each other over APIs. Orders create invoices, invoices update statuses, statuses reach the customer — without a human retyping anything.
One screen that pulls numbers from several sources — database, spreadsheets, an external API — and shows them as charts with filters, date ranges, CSV export and login-protected access per user.
Every screen and every interaction, wired together and clickable in a browser — without a backend. The cheapest way to test an idea on real users, or to show an investor what you mean.
Whichever option you pick: 30 days of warranty support after delivery, technical documentation written for a developer who has never seen the project, and a full handover of the source code and infrastructure access.
Included
Not included
Timeline
WEEK 0
We map the pages, entities or conversation flows on one page of text. You approve it. That document becomes the definition of "finished".
WEEK 1
Data model, admin area and the main screens. By the end of the week you can log in to a staging environment and click through the skeleton.
WEEK 2
Your content goes in, translations are wired, edge cases are handled, and the whole thing is tested on phones, tablets and old laptops.
WEEK 3
Production deployment, documentation, source transfer and a walkthrough call. The 30-day warranty starts the day you go live.
Business — FAQ
If your case is close to the edge of this package, say so early. Moving between packages before the offer is signed costs nothing.
Depends on the site. For content-heavy marketing sites we usually use WordPress or Strapi; for structured catalogues, a small custom admin panel is often simpler and faster for your staff. You see the choice, and the reasoning, in the offer.
Three language versions are included in the price — typically Estonian, English and Russian, but any combination works. We build the language switching, URL structure and admin fields; you supply the translated text.
If your CRM has a documented API, yes — one integration is normally within scope. Several integrations at once are closer to the "System integration" option, or to the Pro package if they come with business logic attached.
Anything inside the approved scope is free to refine. Genuinely new features get a small written quote — you decide whether to add them now or park them for a second phase. The delivery date moves only with your explicit agreement.
Your choice. We can deploy to infrastructure you already own, or set up hosting in your name — you keep the accounts and pay the provider directly. We never hold your domain or servers hostage.
Anything that does not behave the way the approved scope says it should. Defects are fixed free of charge. New requirements, third-party outages and changes you make yourself are not defects — those are handled as new work or under a care plan.
Two to three weeks from now
Tell us what your team does by hand today. That is almost always where the first version should start.
Smaller
A landing page, a technical audit, an automation script or ten hours of fixes.
Open
Bigger
Web apps with roles and APIs, e-commerce with payments, SaaS MVPs, migrations.
Open
After launch
Keep it patched, backed up, monitored — and keep development hours on tap.
Open