From Brief to Clickable Prototype in 48 Hours

The standard way of buying a system goes like this: an intro call, then a second call, then a thirty-page PDF whose most interesting sentence is "final quote after analysis". Three weeks pass and you still have not seen a single screen.

We do it the other way round. You leave a brief, and within 48 hours you get a link to a clickable prototype of your booking flow, plus a quote.

What actually lands in your inbox

The prototype is a visual preview of your system, built from what you wrote in the brief. It is not a template with your logo dropped on top.

• Your services and your steps. If booking with you takes four steps, a specialist choice and a consent form, that is exactly what you click through.
• Your data in the content. Real service names, real team names, prices, currency, language. That specificity is the whole point, because it is what lets you spot in the first minute what fits and what does not.
• Your branding. Colors, typography, the general feel of the interface.
• A quote and an architecture direction. What it costs and how we want to build it, in a form you can put in front of your board.

The link is private and tied to your brief. It does not sit on the open internet and it does not end up in search engines.

What it is not

We would rather say this plainly, because the word "prototype" gets stretched a lot.

The prototype runs entirely in the browser. There is no database underneath, it does not talk to any API, it does not take payments and it will not email anyone. The data inside is prepared for your case, but it is demo data.

It is not a trial of the production system and not a staging environment. It is a mockup that behaves like the product: you click through it the way your customer would, and you see whether that flow makes sense.

That sounds like a limitation, and it is exactly why it is ready in two days instead of two months.

Why a prototype beats a proposal

The decision stops being abstract. It is hard to judge the sentence "we will build a flexible availability configurator". It is easy to judge a screen where you try to book an appointment and notice there is no location picker.

Misunderstandings surface in 48 hours, not in week six. Every brief leaves something unsaid, that is normal. A prototype turns the unsaid into concrete notes: "this step is unnecessary", "the customer has to pick a room here", "our prices depend on duration". At this stage a fix costs one sentence in an email.

Your whole company sees the same thing. Operations, marketing and management read a specification in three different ways. A clickable prototype looks identical on every desk, which usually cuts weeks off internal alignment.

The quote is anchored to something concrete. The number under the prototype refers to the things you have just seen, not to a bag labelled "booking system". Easier to verify, and easier to compare with other offers.

You also get to test us. You see how we read a brief, how we think about your process and what our work looks like, before you sign anything. Two days of output is a fairer sample than the best-written case study.

How this fits into 48 hours

There is no magic here, just a different order of work.

The prototype is a static front-end layer, so we skip everything that normally eats the most time: the data model, integrations, payments, permissions. AI takes us from brief to finished screens in hours rather than days, and the team spends the rest of the time where a machine does not help, which is the logic of your process.

Then there is the less glamorous but equally important part: we run only a few projects at a time. There is no queue in which your brief waits for a free slot.

We wrote more about the way we work in How we build.

The part we consider fair

The prototype is free and comes with no commitment. You do not have to sit through a sales call first: you fill in the brief yourself, in an AI-guided conversation, in about fifteen minutes, at any hour.

Everything created from your brief, the prototype included, is 100% your IP. Only our project team sees the brief, we process it on secure infrastructure, and the conversations are not used to train models.

If you look at the prototype and say "thanks, but no", that is the end of it. No seven-email follow-up sequence starts afterwards.

When those 48 hours can shift

One case: the brief leaves questions open that would turn the prototype into guesswork. Then we come back with those questions first, and the clock starts from your answer. We would rather ask than deliver on time something that misses how you actually work.

What happens next

That last stage runs on a fixed price agreed upfront, 0% commission on your bookings, and a full handover of the code and infrastructure to you. Why we think this is how booking systems should be bought is the subject of The Anti-SaaS Manifesto.

Start with the brief

The hardest moment in a project like this is usually the first concrete question: "how is this supposed to work, exactly?". The prototype answers it in 48 hours, on your own data, for free.

Leave a brief and see your system before you make any decision.