Web app and MVP development

We build web apps, client dashboards, platforms, Telegram Mini Apps and mobile apps, often with AI inside. We start with a narrow first version real users can have in 4–8 weeks and keep building from there.

What people come to us with

Products usually get stuck before the code or right after it, not in it.

  • We have the idea but no team

    Hiring a designer, a backend developer and a mobile developer separately is slow and expensive, and the idea needs testing now.

  • A vendor built it, but it does not work

    The code was delivered, users cannot finish the main flow, and nobody knows what to fix first.

  • A hundred-page spec and launch a year away

    The feature list grows faster than the confidence that anyone wants the product.

From idea to first users

Every week you see a working version, not a progress report. We decide what comes next from live data.

  1. 2–3 days

    Discovery

    Who the first user is, which single flow they must complete, and how we will know the product is wanted.

  2. week 1–2

    Prototype

    Clickable screens of the main flow. Something to show users and investors before any code.

  3. weeks 2–6

    Working version

    Sign-in, the main flow, payment, an admin panel and AI inside the product. A demo every week.

  4. week 4–8

    Launch

    First users, analytics on key actions, support through the first days.

  5. after launch

    Next release

    We look at where people get stuck and what they ask for, then choose the next step.

Timings for a narrow first release. We fix the exact plan after discovery.

What goes into the first release

Every product’s idea list is longer than the time to launch. The first release gets only what a user needs to finish the main flow.

First release 5

  • Sign-in with a phone number or Telegram
  • The main flow from start to finish
  • One convenient payment method
  • An admin panel for the team
  • Analytics on key actions

After launch 5

  • Native apps in the App Store and Google Play
  • Recommendations and personalisation
  • Every payment method and instalments
  • Integrations with every company system
  • Three interface languages

A typical split. We build your own list together in discovery.

Products we have launched

Different markets, similar work: narrow the first release, get it to people and improve it from real use.

  1. Forecast map and a chart for selected cities in jua.ai
    Weather forecast web product · jua.ai

    jua.ai

    The first working web version for a Swiss startup: area selection on a map, forecasts, charts, alerts, sign-in and client access.

    • ~$2.5M round the early version supported
    • Built directly with the founder
    Read the case
  2. The LiftEd teacher dashboard: create a lesson in a minute
    Platform for schools · LiftEd

    LiftEd

    A platform for teachers, students and parents: AI grades written work, maps knowledge gaps and picks practice.

    • ~500 paying teachers
    • ~20k active students
    Read the case
  3. The home screen of the Kaizen Club summit Mini App
    Telegram Mini App for a summit · Kaizen Club

    Kaizen Club · TheNext

    One product for a business summit attendee’s whole journey: tickets and payment, QR entry, the programme, AI avatars and a business diagnostic with a report.

    • 7 weeks from kick-off to the summit
    • 226 attendees went through the whole journey in one product
    Read the case
  4. Balance and challenges in Kaizen Coin
    Business club gamification · Kaizen Club

    Kaizen Coin

    The club’s own currency in Telegram: challenges with photo reports, a leaderboard, a rewards catalogue and an admin panel where every transaction has a reason.

    • ~2 weeks to a working version
    Read the case

One team instead of five vendors

We take the product from the first screen to release and beyond. You do not have to hire specialists separately and stitch their work together.

  • Product and flows

    With separate vendors Everyone reads the task differently and the flows live in chat threads

    With us The first user, the main flow and the success criterion on one page

  • Design

    With separate vendors Mockups are drawn separately and development simplifies them later

    With us A prototype in your brand you can show before development

  • Engineering

    With separate vendors Frontend, backend and the mobile app sit with different people

    With us Web, Telegram Mini App or a mobile app, sign-in, payments and admin in one team

  • AI inside the product

    With separate vendors AI is bolted on at the end and nobody checks its quality

    With us Grading, recommendations, an assistant, with quality checked on real examples

  • Launch and support

    With separate vendors The vendor disappears after hand-over

    With us Analytics from day one, hosting, error monitoring and fixes after release

How we work

A small team of senior engineers and designers. The founder takes part in the key decisions.

  • A demo of the working version every week, not progress reports
  • We tell you what to cut, even when it shrinks our own scope
  • All code, access and rights are handed over to you
  • We start one to two weeks after discovery

Frequently asked questions

Usually 4–8 weeks including discovery and a prototype, if the first release is narrow and decisions are quick. Kaizen Coin was working in about two weeks; the Kaizen Club summit Mini App took seven.

A first working version starts at $6,000. We fix the scope and price before we start; payment is by milestone, part at the start and the rest on acceptance.

Yes. If the main risk is the flow, sales story, or clarity of the idea, a prototype may be the honest first step.

The problem, first users or a path to them, real examples of the current work, and someone who can make decisions.

No. We run the whole product: flows, design, engineering, AI inside the product, analytics and launch.

Yes, when the site is part of the product or the launch: a landing page for the first users, a site with a client dashboard, a catalogue with leads going to the CRM.

A studio usually builds to a finished spec. We start by asking what to test first, cut the scope down to the first release and answer for users getting through the main flow. The founder takes part in key decisions, and AI inside the product is checked on real examples.

You do. All code, access and rights are handed over on acceptance, so your own team can keep building.

We review real user actions, questions, errors, and drop-off points. Then we choose the next release or change the bet.

Reading before the call

Let’s talk

Send the idea, first user, and what you have already tried. We will help find the first release people can use.

Azamat Galimzhanov
I read every request myself.
Azamat Galimzhanov Founder and tech lead Meet the rest of the team
Brief (optional)