Web application development: MVPs and client portals
A web app your clients work in, not just read
We build cabinets, web services and SaaS MVPs: roles, data, payments and integrations with your CRM and 1C. We start with a prototype, ship the first working version and grow it in stages. Pricing is per task, with an estimate in 1–2 days after the brief.
What we build
A web app is a product in the browser: users, roles, data and a real job to do — sign in, place an order, approve a document, pay a subscription. You need one when clients keep asking “where is my order” in messengers, partners get documents by email, or your SaaS idea has hit the ceiling of a no-code builder. We develop web apps in iterations: a prototype of the key screens, an MVP for the first users, then stages from the backlog. Each stage has its own estimate, acceptance and release. A site that only collects leads is a separate category.
Client or partner cabinet
For companies whose managers spend the day answering status questions. Clients see their orders, documents and invoices; partners see only their own prices and deals.
Web service
For a team whose idea already works in a Telegram bot or a spreadsheet. We move it to the browser: sign-up, balance, checkout and each user’s history.
SaaS MVP
For a founder who needs the first paying users. We build the minimum: the core scenario, roles, plans and subscriptions. SaaS development then continues in stages, guided by what early clients do.
Platform or marketplace
For businesses where several sides meet: sellers and buyers, contractors and customers. Catalog, listings, moderation, cabinets for each side and a publishing admin.
What the work includes
We price by task: an estimate in 1–2 days after the brief.
- Discovery: roles, scenarios, what goes into v1 and what goes to the backlog
- A clickable prototype of the key screens before development starts
- Roles and permissions: who sees what and who can change it
- The integrations the stage depends on: CRM, 1C, payments, your own APIs
- An admin panel for your team: users, content, orders, exports
- Testing against acceptance criteria and every task deployed to staging
- Production launch, access handover and project documentation for your team
How we work
- 01
Scoping
A call about goals, audience, processes and constraints. We review what you already have if needed.
- 02
Estimate and plan
Stages, timelines and the cost of each stage. Estimate in 1–2 days.
- 03
Prototype and design
Structure and user flows first, then design. Agreed before we write code.
- 04
Development
Sprints with demos: you see a working version, not just reports.
- 05
Launch and support
We move it to production, connect analytics and integrations, then keep improving under contract.
Questions
Why not build it on a no-code platform?
For testing a hypothesis over a couple of months, a builder is fine. Custom code pays off once you hit limits on permissions, integrations, speed or plan quotas. A common path: prototype on a builder, then an MVP on your own code with the data migrated.
How much does it cost and how do I pay?
We price per task, with an estimate in 1–2 days after the brief. It depends on the roles, screens and integrations in the release. You pay per iteration — prototype, MVP, next stage — on acceptance, not the whole budget upfront.
Who owns the code?
You do. The code and infrastructure stay with your company, so you can switch teams without rewriting the product.
What if the requirements change along the way?
Before coding we agree what goes into v1 and what goes to the backlog. New ideas do not break the current stage: we estimate them separately and plan them for the next one. Every finished task goes to staging, so you see the product instead of waiting for the end.
Who supports the app after launch?
We can: releases, monitoring, roadmap and support under a maintenance agreement. If you have your own team, we hand the project over to them.
We stay after launch
Support, improvements and monitoring under contract, with a 24/7 SLA if needed. You can also hand over a project built by another team.
Other development areas
- WebsitesAn ad landing page, a corporate site or a property catalog — with forms, CMS and analytics.
- Online storesCatalog, product page, cart and orders in the admin. Payments, delivery and CRM as needed.
- CRM, ERP and 1C integrationA CRM built around your sales process, an ERP module with 1C exchange, internal systems and admin panels.
- Mobile appsiOS and Android apps: native or a single codebase, with a backend, admin panel and store release.
- Telegram bots and Mini AppsBots for leads, bookings and payments, plus Mini Apps with a store, voting or a game, connected to your CRM and systems.