From the first message
to the store, and after.

How a project runs with KorLab: what happens at each stage, what you have in hand after it, and who you talk to along the way.

Five stages, each with
something to show.

  1. Brief

    You tell us about the product in a message or on a call. We reply with how we would build it: the platforms, the stack and what goes into the first release.

    You get A plan for the first release.

    Smart Eat went from the client’s first draft to a release on iOS and Android.

    Smart Eat
  2. Design

    We design the interface ourselves, flow by flow, before the code is written. You see the screens and change them while that is still cheap.

    You get Screens for every flow of the first release.

    Rayson’s app, backend and 1C integration were designed and built by us as one system.

    Rayson Fashion Store
  3. Build

    A first working build usually comes within a couple of days. From then on you try demos and TestFlight builds on your own phone, and changes pass automated builds and tests on the way.

    You get A build on your phone in the first days.

    1,100+automated tests

    NutriKor is our own product, from the brand to the deploy pipeline.

    NutriKor
  4. Release

    We prepare the store listings and screenshots and ship to Google Play and the App Store from one pipeline. A website goes live with every push.

    You get The app in the stores, or the site on its domain.

    4stores it prepares listings for

    Our own listings come out of Mockup Studio, the tool we built for it.

    Mockup Studio
  5. After launch

    Content, prices and promotions change from an admin panel, without a new release. Support and further work are agreed with you, and we would rather stay for the long run.

    You get An admin panel to run the product day to day.

    60 sfrom a CMS edit to the live page

    The A2 LSTK team publishes its own projects, no developer needed.

    A2 LSTK Steel Framing

Already started?
We take it from there.

These products began as something else: a no-code prototype, seven separate apps, a game from 2018. A half-built product is a starting point we know.

Questions clients ask.

How fast can you ship?

Usually in days, not months. A first working build often comes within a couple of days, and demos and test builds follow as the product grows. When the first store release lands depends on what goes into it.

How often will I see progress?

Whenever there is something new to try, not at the end of a stage. Builds come straight to your phone: TestFlight on an iPhone, a test build on Android.

Who will I talk to?

The people building your product: Ivan Taranov, the founder, or the developer you came to us through. Messages or calls, whichever suits you. There are no account managers in between.

Who owns the code and the store accounts?

We agree that at the start. We can work in your repository and publish under your developer accounts, or set everything up on our side and hand it over when you need it.

How is the work priced?

Per project, agreed with you. The price follows the scope and the way you want to work.

Do you support the product after launch?

Yes, on terms agreed with you, and we prefer to work for the long run. Rayson has been in production with us since 2024, and our own apps have been kept up and rebuilt for years.

Do you sign an NDA?

Yes, whenever a project needs one.

Bring us in at
any stage.

From an idea or from a half-built product, tell us where it stands and we will reply with how we would take it on.