1 working day Clickable prototype Go/no-go advice

App in a day: from idea to clickable prototype in one working day

One working day for your product team, founder or management team member with an app idea you want to test seriously before investing tens or hundreds of thousands, or more, in development. No sticky-note brainstorm and no no-code demo. In one structured day, we take you from an idea in your head to a clickable prototype on your screen, plus an honest roadmap with phasing and an order-of-magnitude cost estimate. By the end of the day, you know whether the idea is worth pursuing and what the next step involves.

Plan a working day View the programme

What we aim to deliver on the day

Clickable prototypeFigma + UI flow
Technical roadmapStack and phasing
Cost estimateMVP and V1 estimate
Honest adviceBuild, refine or don't
FormatIntensive working day

When a working day shows whether your app idea is worth pursuing

Most app ideas don't fail because they are technically unfeasible, but because the scope, the user problem and the business model weren't sharp enough when developer days were bought. A structured working day brings that discussion forward, before you commit to a project lasting months.

You're considering a serious investment and want certainty about scope

For concepts where the scale of the build is substantial. A working day costs a fraction of that, and filters out the cases where it later turns out the real use case was somewhere other than you thought. Investors and boards appreciate it when you have a prototype ready before you ask for budget.

Your team is divided about what the app should actually do

The founder sees feature A as the core, marketing wants feature B up front, developers ask for feature C for scalability. A joint working day with outside-in facilitation brings three versions together into one clickable prototype that everyone agrees on.

You want to know whether integrations are realistic for your budget

Half the time in a serious app project goes on integrations, not on new screens. CRM, ERP, payments, identity, GDPR compliance. Mapping out in a single working day which integrations your idea really requires prevents surprises worth tens of thousands later on.

You want a quick, honest go/no-go decision with an outside perspective

Not every app should be built. A day with people who have seen hundreds of apps up close gives you arguments to press on, pivot the idea or deliberately stop. The advice is put in writing, even if the advice is that you're better off not building.

What you take away at the end of the day

A handful of tangible deliverables, not a management summary of a whiteboard session. Material you can present straight away to stakeholders, co-investors or a future development team.

1

A clickable prototype in Figma plus working UI screens

A series of connected core screens that you can demonstrate on your laptop. We work AI-assisted with v0 and Cursor, but every screen choice goes past an experienced product designer before it ends up in the prototype. Not a throwaway mock-up: the file can be built out directly by another dev team.

2

A technical roadmap with architecture, stack choice and phasing

Which stack fits, which integrations are needed, how to build it in a GDPR-compliant way, and in which phases it can go into production. Concrete enough to take to a development partner, or as a starting point for your own team. Including realistic sequencing, so you can validate step by step instead of building everything at once.

3

An order-of-magnitude cost estimate for MVP and V1

Not an exact quote, but a substantiated range. We work with ranges that match what the market typically charges for this type of work, so you can judge whether it fits your budget and business case. The figures are based on concrete sprint estimates, not guesswork.

4

Written advice: build, refine or don't build

A written recommendation, drafted after the workday and sent to you shortly afterwards. We give a well-founded verdict: the idea is strong enough to pursue, it is strong but the scope needs to change, or it is not strong enough and you are better off not building it. Honest and reasoned, because a workday that honestly talks you out of something costs far less than a months-long project in which you discover that yourself.

The four phases that make up the day

We agree the exact timings and length of each phase based on your team and the complexity of the idea. What is fixed is the order, because each phase builds on the previous one. We build in breaks and buffer, because a group of people cannot think well about their own product for hours on end.

Phase 1: discovery

Who the user is, what the problem is, what the desired outcome is

We start with the person on the other side. Not with features, but with who is struggling with something and what change they want. Stakeholders who suspected they were talking about different things often discover the first scope corrections right here.

Phase 2: screens and flow

Core screens and user journey on the whiteboard, before we open any tools

We sketch by hand. The core screens and how a user moves through them. Decisions about which information goes where, which actions are prominent and what error paths look like. Deliberately analogue, so that AI or tooling doesn't make early choices for the people involved.

Phase 3: AI-assisted prototyping

Whiteboard sketches become clickable UI on your laptop

The team works in parallel on flows in Figma and on working UI components using tools such as v0 and Cursor. The whole team regularly looks on and you steer as we go. By the end the screens are there, they click through, and they behave realistically. Every design decision stays with people; AI speeds up the execution.

Phase 4: roadmap and go/no-go

What exists, what the next step is, and whether it is worth building

We put together the roadmap direction: architecture, phasing and order-of-magnitude costs. Then we look back on the day with the group: is there a product here worth pursuing, or do we see reasons to stop? This conversation sometimes runs counter to the enthusiasm of that morning, and that is exactly why we do it.

Who this day is for, and who it isn't

Not every team gets value from a single day. The list below makes clear up front where you belong, before you invest time and money in a workday.

A good fit

  • Founder, product owner or management team member with a serious app idea that hasn't been built yet
  • Team considering a substantial investment in development that wants certainty before committing
  • Company considering an internal tool that wants to know whether building, buying or doing nothing is the sensible choice
  • Investor or board that wants an independent opinion on an idea they are putting money into
  • Founding team that is divided over scope and needs an external facilitator
  • Organisation with an idea where the users, the problem and the desired outcome are already roughly clear

Not a good fit

  • A completely vague idea such as "we want to do something with AI", with no concrete use case or target group
  • Team that only wants to brainstorm without an outcome; a free intake call is enough for that
  • An idea that already has a production app that you want to build on; a product audit is more suitable for that
  • Organisations looking for validated no-code, as we design for custom builds
  • Teams expecting a fixed-price quote at the end, as we deliver ranges and honest advice, not a contract
  • Strategic research into market size or competition; other agencies are better at that than we are

The method: AI-assisted prototyping with human review

A workday in 2026 is not the same as a workday in 2022. AI tooling speeds up the development of screens considerably. But without an experienced designer and developer reviewing the work, AI produces inconsistent flows and screens that look plausible but are unusable. Our method combines both.

Tools we use

Figma for screens and the design system. v0 and Cursor for generating working UI components. Claude for copy suggestions and flow validation. Astro or Next.js for the prototype build, with Tailwind for styling. Everything is open source or widely available.

Figmav0CursorClaudeAstroNext.jsTailwind

Why AI-assisted

AI tooling speeds up the design of screens considerably. The difference from sketching by hand lies in the turnaround time, not in the quality of the thinking. The decisions remain human.

Why human review remains essential

AI hallucinates UX. Screens look good at first glance but contain patterns that break in production. An AI-generated form doesn't know the specific validation requirements of your industry. The designer and developer review every screen before it enters the flow, and throw away whatever doesn't work.

Why Appfront, and not a no-code agency or a freelancer

Building a prototype in a single day has become a market in its own right. There are no-code agencies, freelance product designers, and agencies that run "design sprints". They can all deliver a prototype. Our added value lies in what can be made of it afterwards.

We also handle the phase that comes next

A no-code prototype is great until you want to scale, integrate with your ERP or comply with the GDPR. We design in a single day, in a stack we run in production ourselves for healthcare, transport and finance clients. No prototype that has to be rebuilt for production.

An honest go/no-go, even when it costs us business

An agency that also wants to sell the build has a conflict of interest during the workday. We often end up giving a team a no-go recommendation, because an idea that looks strong on paper won't survive in practice. We write that down, even if it costs us a future project. Our reputation weighs more heavily.

Experience with production apps in healthcare, transport and finance

Our designers and developers have conducted hundreds of user interviews, have seen apps in production fall apart on integrations, and know which assumptions in a prototype usually turn out to be naïve. That experience is in the room on the day, and it shapes the screen choices and the phasing of the roadmap.

Our own development team, no subcontracting

Appfront operates from Westerdoksdijk 599 in Amsterdam with a permanent team. The same designer and developer who work with you on the day are available if you decide to build afterwards, or they will give you a well-founded referral to a specialised team if your use case is a better fit there.

Practical details

The practical details of the workday, as far as it makes sense to fix them in advance. We settle the rest in a thirty-minute intake call a week before the day itself.

  • Location At your office or at ours in Amsterdam. We agree where it takes place for each engagement, depending on what works best for your team.
  • Duration One intensive workday. We agree the exact start and finish times in the intake, so that they suit your team.
  • Participants A small team on your side, ideally including the founder or product owner, someone with budget authority and someone with domain knowledge. On our side, there is a mix of product designer and developer.
  • Preparation A short intake call before the day in which we align on the goal, participants and any materials needed in advance. No homework required.
  • What you bring A laptop per person, and optionally a short document with your current thinking on the idea. No presentation needed. It helps if you have access to the internal systems the idea would need to integrate with.
  • Price indication We don't list exact prices on the site, because the price scales with scope, number of participants and location. Request a quote via the contact form and you'll quickly receive a price and a proposed schedule.
  • Next steps No obligation. We'd love to keep building, but we won't be offended if, after the day, you decide another agency is a better fit or that you'd like to pause. You keep the written advice either way.

Frequently asked questions about App in a day

The most common questions we hear before planning the working day, with honest answers.

Will I really have a working app on the App Store after this day?

No. We are deliberately honest about this: building a working production app takes weeks to months, not a single day. What you will have after this day is a clickable prototype that behaves like the real app, plus a roadmap to production. Companies that promise you a working app on the App Store after one working day either deliver a no-code shell you'll never be able to build on, or they stretch the meaning of "working" into something it isn't.

How does this day compare to an AI Design Sprint?

The AI Design Sprint is a five-day programme for products where AI functionality is the core. This App in a day is a single day, for general app ideas where AI may be part of the product but not the whole of it. For general app validation, this one working day is enough. For an AI product that requires research into models, datasets and LLM orchestration, it takes longer.

What happens to the prototype, can we delete it?

The prototype is yours. We deliver the Figma file and, if it also has a working front end, the accompanying code in a repository in your name. You can keep it, delete it or continue building it yourself. There is no lock-in on tooling that only we can open.

Who comes from Appfront, and are they experienced?

A product designer and a senior developer. Both have experience with production apps, not just prototypes. We don't send a junior with a template. For the intake call, you will try to meet as many as possible of the same people who will facilitate the day, so you can judge in advance whether it clicks.

Can we do the day at our office?

Yes, that's actually common. A working day at your office has the advantage that colleagues can join between sessions to give specific input, and that the team works in a familiar environment. What we need is a room with a large whiteboard or flip chart, and power sockets. We also have a comparable space available at our Amsterdam office.

What if our idea turns out to be too complex for one day?

That happens. Sometimes we discover in the first session that there are actually three products in one idea, or that the real use case hasn't yet crystallised. In that case, we use the working day to narrow the scope to what is feasible for a prototype, and save the rest for a follow-up conversation. The roadmap you take away then honestly states which part has been prototyped here and which part needs further research.

What if we drop the idea after the day?

Then that is the outcome. As far as we're concerned, a working day that ends with "we're not building this" is just as valuable as one that ends with "we're going to build". In fact, it is cheaper and more honest than a six-month project in which that decision is made anyway. The written advice stays with you, so if you want to come back to it in a year, you still have the documents.

How far ahead do we need to plan?

The team works on production projects in parallel, so we schedule working days in fixed slots. Request a quote and we'll quickly get back to you with suitable calendar options.

Planning a working day for your app idea?

Send us a short description of what you have in mind. We'll quickly come back with calendar options, a price indication and who from our side would join. No sales pitch beforehand, no obligation.

Request a working day

Edit content