Service
Web service MVP development
A first working version of your web service with its key flows: users sign up and do the main thing the service exists for, while you see how they use it and decide what to build next. The architecture is designed for the product to grow from day one.
Who it is for
- You have an idea for a service and need to test it on real users before investing in the full version.
- Your company wants to turn an internal tool into a product for other companies.
- A prototype built on a no-code tool or in spreadsheets can no longer cope with the number of users and data.
- You need to show partners a service they can actually use, not just screen mock-ups.
What is included
- Working through the idea: which flows go into the first version and which come later
- Screen prototypes for approval before development
- Sign-up, login and user roles
- The product's key flows on a PostgreSQL database
- An admin panel for managing users and data
- Automated tests of the main flows and launch in Docker
- A plan for the next stages based on the launch
Billed separately
- A custom interface design
- Payments and pricing plans
- A Telegram bot for the service's users
- Integrations with external services via an API
- Server rental in your name, paid by you
Price and timing
Estimated timing
8–12 weeks
What affects the price
- The number of key flows in the first version
- How many user types and roles there are
- Whether payments, plans and subscriptions are needed
- A custom design or a ready-made UI library
- Integrations with external services
| Service | Price |
|---|---|
| Web service MVPA first working version of the product with its key flows. | from 6,000 BYN≈ $2,000 |
How we work
Discussion: who the users are, what problem they solve and what will show the idea works
The scope of the first version, screen prototypes and a stage plan
Development in 2–4 week stages with a working version after each
Launch for the first users, changes based on their feedback and a plan for the next steps
Example
A demo on fictional data and a real project from my portfolio with a similar task.
Demo
CRM and user portals
I show how a small CRM is organised using a fictional appliance repair service: requests, statuses, technicians, timesheets, and client and employee portals.
Open the demoFlagship case
Fleet management system: from a Telegram bot to an ERP
- Task
- A company with its own vehicle fleet needed shift check-ins, the daily plan, fuel accounting and vehicle maintenance in one system.
- Solution
- Started with a Telegram bot for START and FINISH check-ins and grew it into two services: the management system (bot and web admin) and a driver portal. Integrated with two GPS telematics systems and fuel cards.
- Result
- The system runs every day in a real company and keeps growing: about 620 commits since January 2026.
- FastAPI
- python-telegram-bot
- PostgreSQL
- SQLAlchemy 2
- Alembic
- Docker
FAQ
How much does an MVP cost?
From 6,000 BYN for a first version with key flows, sign-up, roles and an admin panel. The price depends above all on how many flows go into the first version. I give an exact price once we have discussed the task.
What goes into the first version?
Only what the service cannot solve the user's main problem without. Other ideas go into the plan for later stages. The narrower the first version, the sooner you find out whether users need the product.
How long does MVP development take?
The estimate is 8–12 weeks. The timing depends most on the number of flows: if you need to launch sooner, some features move to the next stage.
Will everything have to be rewritten later?
From the start I set up the data model, migrations and a split into modules so that new features are added to the running version. My main project began with a single function and grew into a system of two services: about 620 commits since January 2026, and it keeps growing.
How do I protect my idea before we start?
I sign an NDA at your request, before you share the details. The source code and access pass to you after the final payment, and I publish a case study only anonymised and with your consent.
What happens after the MVP launch?
You watch how the service is used and decide what to build next. I estimate the next stages separately. The first version has a 3-month warranty: I fix errors in the code and settings I made at no extra charge, if the work deviates from the agreed specification.
Contact
Tell me about your task — I'll reply with possible solutions. Or message me directly in the messenger you prefer.
Related services
- Custom CRM and internal system development
When records live in spreadsheets and chats, and an off-the-shelf CRM keeps getting in the way.
from 4,500 BYN
- Client portal
When customers call and message you to check an order status, get a document or repeat a request.
from 4,500 BYN
- Telegram bot with a web admin panel and database
When a lot of data flows through the bot and it has to be managed: searched, checked, exported and reported on.
from 3,000 BYN