We build a marketing site, an MVP or a web platform ready to scale for your startup. First we decide which features are genuinely essential, then we launch a product people can use.
Each stage calls for something different. Building a full platform at the idea stage is premature, while a marketing site alone is not enough at the growth stage. Below are the three stages and what we do at each.
The problem, the audience and the core offer need defining. There is no product yet, but it must be clear who it is for and why.
What we do
We write the idea down in terms of the user's problem, define what the first version contains and, where useful, suggest measuring interest with a marketing site first.
The essential features users can try need building. The goal is not a complete product but testing the hypothesis.
What we do
We make one core user flow work end to end and add an admin panel and a channel for collecting feedback.
The product works and there are users. Now it needs extending, management needs simplifying and the numbers need to be visible.
What we do
We add user roles, an extended admin panel, integrations and analytics; where needed we extend to a mobile app.
These three do not replace each other — they answer different questions. Below is who each one suits and what it contains.
Who it suits
When you need to explain the idea, the team or the product to investors and early customers.
What it includes
Who it suits
When the product idea needs testing with real users.
What it includes
Who it suits
When the product is validated or a wider business process is required.
What it includes
The bigger the scope, the later the launch — and the later the hypothesis gets tested. So we split features into three groups.
Without these the user cannot try the product at all.
Useful, but must not delay the first test.
Until you can see how people actually use the product, spending time here is premature.
This list is an example — in your product the “needed now” group may look different. We define it together in the first conversation.
Six stages. At each one it is clear in advance what you approve and what you are left with.
Who you are solving a problem for, which problem it is and how that person solves it today.
Stage outcomeA written description of the problem and audience, plus the first hypothesis.
Together we decide which features go into the first version and which can wait.
Stage outcomeA feature list and a user flow diagram — which you approve.
The main screens and the transitions between them are drawn, with the mobile view handled separately.
Stage outcomeA clickable prototype — before development starts.
The product is developed and the admin panel and agreed integrations are connected.
Stage outcomeA working version on a test address — you open it yourself through a link.
The core flow is checked end to end, issues are fixed and the domain is connected.
Stage outcomeA launched product and access to the admin panel.
Analytics and user feedback are reviewed and the list for the next stage is drawn up.
Stage outcomeA prioritised list and an estimated size for the next version.
Choosing technology is not a matter of taste. Below is the business problem each one solves.
With Next.js and React we reuse ready components — the first working version arrives sooner.
A Node.js and NestJS backend is split into modules: adding a feature does not mean rewriting the product.
PostgreSQL or MongoDB, chosen to fit the task. As users and content grow, the product does not slow down.
With React Native an iOS and Android app can be added later — the backend and data stay where they are.
Where useful, an AI API is connected to the product: text analysis, recommendations or automatic replies.
Analytics show where users drop off — the next version is based on numbers rather than guesswork.
The three options below are a starting point. Each card shows the most important scope; the full list opens under “full scope”.
To validate the core idea behind your startup
Ready in 14 daysWho it suits
Teams that want to test an idea quickly and start with a minimal feature set.
A custom-built website for startups
Ready in 14 daysWho it suits
Those who need to present the product to investors and early customers and collect users.
A website covering the full functionality of your startup
Ready in 30 daysWho it suits
Projects that need user roles, extended management and an API.
The timeline shown applies to the scope in that specific card. Adding features, integrations or a mobile app changes both the timeline and the price.
Startup projects rarely fit a standard plan exactly. Once the scope is clear we send a separate quote describing the contents and timeline.
Below are product projects we have worked on. Each card opens the project page describing the task, the work delivered and the technologies used.
Answers to the questions asked most often before a project starts.
An MVP is the first working version of a product with only the essential features. Its purpose is not sales but testing a hypothesis: do people want to solve this problem in this way. If the product idea has not yet been tested with real users, building a full platform before an MVP does not add up.
None of this has to be in the first version. These are added once the product is running and the need appears.
When you need it
When a campaign or waitlist push needs a page focused on one specific offer.
When you need it
When users work with the product from a phone regularly.
When you need it
When user questions start repeating and an automatic answer is needed.
When you need it
When customers and enquiries need tracking by stage.
When you need it
When most conversation with your audience happens on Telegram.
When you need it
When you want search traffic coming to your product pages.
Before making a decision, these articles may answer your questions.
In a short conversation we define your product idea, the users, the most important features and the scope of the first version. Then we prepare a technical and commercial proposal.
