KESSEL & CODE

MVP development and prototyping.Something tangible in days.

Your idea becomes something you can click through and test with real users. That way you see early on whether development is worth it, before the big budget is spent.

What is the difference between a prototype and an MVP?

A prototype shows how an idea feels. It is clickable and often built only as far as the test requires. An MVP (Minimum Viable Product) is the smallest version that real users can use day to day, with real data.

AI has made the path there much shorter. What used to take months is often up within days. That changes the math, because testing an idea now costs less than debating it at length.

For us, fast doesn’t mean unchecked. As soon as real data is involved, we take a close look at security and data flows.

The idea got shelved

The development quote was too high and too uncertain. Since then, people only talk about it.

The requirements document keeps growing

Months of coordination. Nobody has held the result in their hands yet.

A quick mockup doesn’t hold up

The quickly generated version looks good but falls apart with real data. Then you start from scratch.

What our prototyping work includes.

Clickable prototypes

An interface users can click through, in the browser and on their phone.

MVP development

The first real version with login, database and the features you really need.

Technical feasibility

Can this be solved with AI at all, and how reliably? We test it with your data instead of guessing.

Real-user testing

We define what the test should answer. Then we analyze what users actually do.

App prototypes

For ideas that live on the phone. A web app is often enough for the first test. That saves time and money.

Path to development

If the idea holds up, we keep building. The version is set up so it can become the foundation.

It ends with a decision.

The prototype isn’t an end in itself. It answers whether and how to move forward. Each of the three answers saves you money.

Keep building

Users understand it and want it back. The prototype becomes the foundation of development.

Change

The idea holds up, but part of it doesn’t. We rebuild and test again before it gets expensive.

Stop

Nobody needs it. That’s a good result too, because you keep the big budget.

From idea to decision.

  1. 1

    Understand

    We clarify what problem the software should solve and how we measure success.

  2. 2

    Build

    The AI writes fast. We keep the scope small. Within days the first working version is ready.

  3. 3

    Test

    Real users try it out. We see what they understand and where they get stuck.

  4. 4

    Decide

    You get a clear assessment and decide whether to keep building, change course or stop.

The AI does the grunt work. We make the decisions.

What the AI does

  • Generate interfaces and code quickly
  • Build and compare variants of a process
  • Create test data and initial documentation
  • Evaluate feedback from tests

What our team does

  • Keep the scope small and the goal in sight
  • Check whether the technology holds up with real data too
  • Take responsibility for security and data flows
  • Say so plainly when an idea isn’t worth it

The people behind it.

More about us
Portrait of Armin Sanjari
Armin Sanjari
Managing Director, mathematics and analytics

Founded the agency IT-WINGS in 2016 and still runs it. It serves well-known clients in the automotive, consumer goods, pharma and mechanical engineering industries.

Portrait of David Otto
David Otto
Managing Director, economics and growth

Has been scaling digital businesses since 2015, first at Festool, then for six years at Mercedes-Benz. There he led projects in digital products and global performance marketing.

That’s how we built our own products too.

We built Propspector and UTM Spot ourselves and run them ourselves. That’s why we know what comes after the first clickable mockup.

See our products

Frequently asked questions about Prototyping.

What does a software prototype cost?

That depends on the scope and on whether it should only be clickable or already work with real data. Because we work with AI, the effort is well below traditional development. After a short conversation, we give you a fixed price.

How quickly can a prototype be ready?

A clickable prototype is often ready within days. An MVP with login and real data usually takes longer. After the first conversation, we tell you what to expect.

What is an MVP?

MVP stands for Minimum Viable Product. It is the smallest version of a piece of software that already delivers value to real users. It shows whether further investment is worthwhile.

Can we reuse the prototype later?

We settle that up front. A pure test can be built simply. If it’s meant to become a product, we build it from the start to serve as a foundation.

Who owns the code?

You do. You get the complete code and can take it forward yourself or hire us to do so.

What sets you apart from an AI builder?

Builders produce something visible quickly. For a first impression, that is often enough. We also check whether it runs securely with real data and can be built on.

Do we need technical knowledge?

No. We need someone on your side who knows the problem and the users. We translate that into technology.

What idea have you shelved?

Tell us what you have in mind. We will tell you honestly whether a prototype is worth it and how we would start. You’ll get a reply within 24 hours.

hello@kessel-und-code.de
Rotebühlplatz 11–15, 70178 Stuttgart