Estimatein 1 hourEstimate a projectreply within 1 hour

Home / Our work / Why the development does not stop after the first version of the software project is released

Approach · product

Why the development does not stop after the first version of the software project is released

An innovative IT product is not something you complete and forget about. It needs to be continually enhanced, upgraded to versions 2.0, 3.0, and

Timelineongoing

Development costUndisclosed

FormatApproach · product

StatusCase essay

Challenge

Move a fintech product beyond a one-off 1.0 release

Solution

T&M delivery, Scrum, microservices and open task tracking

Result

In 18 months: MAU up 410%, average ticket up 70%

Why development does not stop at version 1.0

A fintech startup came to us with a private-investment platform. Founders planned a classic fixed-budget 1.0, launch, then occasional maintenance — treating engineering as finished after acceptance, like a factory line that never upgrades and with no budget for version 2.0.

During MVP acceptance, focus groups asked for new flows, broker integrations and better analytics. The market shifted toward open APIs and instant payments. A fixed spec went stale every week — “ship and forget” stopped working and delayed breakeven.

We reframed the engagement as iterative partnership instead of a one-time release. The goal was to show that a successful launch is a starting point; years of revenue come from continuous evolution driven by feedback, regulation and competitive pressure.

Key capabilities

Time & Materials

Moving from a rigid spec to T&M with sprint reports removed dozens of change orders and sped up reaction to market shifts.

Scrum delivery

Two-week sprints, demos and mandatory product analytics before planning turn each iteration into a tested hypothesis, not a wish list.

Microservice architecture

Gradual extraction from the monolith lets broker, billing and reporting modules evolve independently without freezing the whole platform.

Transparent tracker

The client sees task progress, sprint completion and budget forecast — trust is backed by numbers, not vague “in progress” statuses.

CI/CD and quality

GitLab CI, automated tests and canary releases keep SLA above 99.95% while load grew fivefold after the 1.0 launch.

Discovery and roadmap

Workshops with product owners and a shared roadmap align business goals with the queue for versions 2.0, 3.0 and beyond.

How it works

Stack tuned for iteration: Node.js and TypeScript, React and Next.js, PostgreSQL and Redis, RabbitMQ between services, Kubernetes and AWS Lambda for peak microservices, GitLab CI with Jest and Cypress on every release.

Version 1.0 shipped in four months; then sprints followed a “major capability + metrics” rhythm. Strangler migration off the monolith cut downtime risk while adding brokers, push alerts, multi-currency ledger and a payment gateway.

Burn-down and budget forecast in Jira eased founders’ fear of runaway spend. Over eighteen months the product moved from pilot to a visible player with subscription tiers, PWA and a partner API while holding SLA above 99.95%.

How the work went

01Discovery and a new engagement model

02MVP launch and product analytics

03Microservices, integrations and 2.x

04Scale-up and the 3.0 roadmap

Technologies

Node.jsTypeScriptReactNext.jsPostgreSQLKubernetesGitLab CIScrum delivery

Want a similar product approach? A project like this starts from 1–3 months at a fixed price, or 0 for development with support from 45,000 ₽ / month.

What we delivered

The client dropped the “done and forgotten” mindset. Development runs on a continuous improvement spiral: version 3.0 is in progress, the backlog is metric-backed with in-app and cohort signals and budget is planned as investment in a living product.

In eighteen months active users grew 410% versus the first three months after pilot. Average ticket rose 70% thanks to subscriptions with advanced analytics, personal recommendations and paid alerts on portfolio limits.

Time-to-breakeven shortened from a planned 14 months to 11 through fast monetized features and transparent T&M. The ESK team and client specialists work as one unit — the case became a reference for continuous delivery among ESK product clients.