Pavel Kroupa Home Portfolio Services About Contact
CS

All services

Decision Prototype · A decision you can click through

A working prototype in a few days.

I sit down with the person who has the requirements in their head and ask questions until it's clear how the service should work. Then I turn that into a working prototype on the web. Your team clicks through it, comments, and moves forward.

Starting point

2 weeks of meetings. Nothing to click or test.

Everyone agrees in the meeting. Engineering still waits, because the decision lives in people's heads and slide decks.

How it works

Every round starts
with an iteration

The team discusses a working prototype, not slides or another meeting.

STARTWORKWHAT YOU GETManaged rounds of changesbusiness + engineering · changesExisting productrepository · designsNew ideano product yet1Talk itthroughfacilitated discussionWho decidesQuestions, not slidesThe process, live2Mapthe servicenavigation mapScreens and rolesWhat's in scope3Buildthe screensoutputsService logicUser flowsScreens and statesDocumentation4Shareone linkdeployed prototypeDeployed prototypeCommentsVersionsBuilt from your real components and tokens.It's not production code. Engineering builds from it once decisions are made.Decidedscopefirst version · flowsdecision logHandofffor engineeringnavigation mapstates · tokens

What you get

3 things you keep.

A decided scope

What goes into the first version, which flows matter, and why you decided that way.

One link for everyone

A password-protected prototype on the web. Anyone can open it in a browser and comment on any screen.

A handoff that engineering builds from

A screen map, every state, and your real colors and components.

Duration and price

1 day, 2 days, or a week.

1 dayFrom CZK 49,000

1 question. A workshop and a clickable first version.

2 daysFrom CZK 125,000

1 open question. A workshop, a prototype, and a decision log. Resolved end to end.

1 weekFrom CZK 220,000

An entire product area. More interviews, workshops, and screens. Same process.

Included in every option

  • The problem, the people, and the goal, written up in advance
  • A workshop with your decision-makers
  • A working prototype on the web, password-protected, with comments
  • A decision log: what we decided and why

What affects the price

  • Scope
  • Complexity
  • Product size

You pay per project, not per hour. I'll send a final quote after our first meeting.

For CTOs and architects

Questions you'll ask.

Does it touch our production code?

No. It uses your components, but it isn't production code. Engineering builds from it only after decisions are made.

Where does it run?

On GitHub, behind a password-protected link.

Who owns it afterward?

You do. If I created the repository under my account, I'll transfer it to you.

What do you need from us?

Mainly time with your decision-maker. Access to your repository or design system helps, if your security policies allow it.

Next step

Where are you stuck?

Write to me. In a 30-minute call, I'll tell you whether I can help. No slide deck and no complicated proposals.