MVP Development: A First Version Someone Outside Slack Can Use

An MVP is a slice a user can finish: one loop, a store listing or a URL, enough backend to be true. Six roles and a TAM slide is a cathedral with a smaller invoice. If nobody outside Slack can use it, it is a prototype.

CodeLoop Studio in Sarajevo freezes that cut on purpose. The commercial page is MVP development. Founders who still need a page, not tenants, should read web agency for startups. Multi-tenant billing is SaaS development agency.

Products that started as a sharp job

cijene.me compares prices in a market. Koliko counts stock on a shift. seeQRmenu publishes a menu. None of those were “the platform” in month one. Typical studio work sits in a 3–9 month band; MVPs sit toward the short end when the cut is real.

What we freeze

• The cut is a deliverable. We write down what is out of v0. That document is the MVP.

• Stack after the slice. Flutter, React Native, native, or Next.js — picked for the frozen features, not a favourite talk.

• Store or URL. Review and listings sit in the plan — shipping from Sarajevo.

• Stay for v1.1. We can remain. Handover is not a vanishing act. Events you will actually read are event tracking plans.

What we will not call an MVP

A redesign of email. A marketplace with no second tenant. A blockchain because the deck asked — when not blockchain. Cost without a poster number is app cost in Bosnia.

Send the loop, not the platform

Who finishes the job in week one, and what is explicitly out. Reply in 24 hours — online estimate or contact.