Prototype in a day Validate your use case One Day Build

Prototype in a day: from idea to working app

A digital use case often exists only in slides and discussions, until someone puts code behind it. With One Day Build, Appfront creates a real working prototype of your idea in a single working day. No Figma click-through, no specification document: a live application that your colleagues, users or management can open and test straight away.

DAY 1 09:00 Kick-off 17:00 Live URL

What exactly is a one-day prototype?

A one-day prototype is a working first version of a digital idea, built in a single working day by a small team. Not a design that still needs to be built out, not a demo on localhost, but an application running on a real URL, with real interaction, ready to show to stakeholders or to let end users try out.

The idea is not new: Google Ventures' design sprints apply a similar acceleration to design challenges. What makes One Day Build different is that the end result is not a clickable sketch but actual code. An interactive customer portal, a planning tool with real logic, a dashboard that loads data from a test file: whatever your use case is.

The proposition fits a broader trend: AI-assisted development has dramatically increased the speed at which applications can be built, and that changes when "quickly trying something out" is realistic. Appfront combines that speed with ten years of experience in custom software development, so the prototype not only works but also provides a foundation for any follow-up.

Working code, not a mockup

The difference from a clickable Figma file is fundamental: a prototype has real logic, can process data and behaves like a live application. The difference between an MVP and a prototype: a prototype validates the idea, while an MVP goes to the first users.

At the table, not via tickets

A one day prototype is a joint working session. You sit in, help decide on scope and see choices take shape. No lengthy briefings, no radio silence between delivery and feedback.

A real URL at the end

At the end of the day you get a live link you can share with colleagues, customers or investors. No "we'll send it over soon", no demo environment that only runs on a laptop.

When is a one day prototype right for your situation?

Not every software challenge calls for a prototype in a day. For a complex platform with multiple user roles, sensitive integrations and compliance requirements, you're better off starting with a thorough consultancy engagement. But for the stage where an idea has no support yet, no concrete form and no price tag, a working one-day prototype is often the fastest way forward.

Good moments for a One Day Build

  • A board member has an idea that is hard to explain in text or slides
  • There is an investment proposal that needs something concrete added to it
  • An internal department wants to show that a process can be digitised before IT commits capacity
  • A product team wants to compare three different solution directions
  • A sales or customer success team wants to show a prospect something tangible
  • A founder wants a working example on the table ahead of an investment round

When a different approach is better

  • The use case is well defined and you already know you want to go to production — start directly with a more extensive prototype engagement
  • Complex integrations with multiple existing systems are needed
  • The application must meet strict compliance requirements (medical, financial supervision)
  • Users are already waiting for a working version — then a custom development engagement is a better fit
  • The ambition is a full product, not an experiment — start with scoping

Which use cases fit into a working day?

A good One Day Build has a sharp scope: one core flow, one clear user, one question to prove. That sounds limiting, but within those boundaries a lot is possible, because modern frameworks and libraries make building interactive interfaces faster than ever. Examples of what is achievable in a single day, described generically because every use case is different:

Self-service customer portal

An interface where customers log in, view their details, submit a request and track its status. A working first version of a portal application as proof of concept for your internal discussion.

Operational dashboard

An interface that pulls in data from a spreadsheet or API and visualises it in charts, tables and filters. Similar to a custom KPI dashboard, but in one-day form to prove the concept first.

Planning or registration tool

An interface where a team plans tasks, logs hours, tracks stock or records another operational process. A first sketch of a workflow application that you can put in front of the end users.

Internal registration app

A form-driven tool that collects data and passes it on to a database or existing system. For example an intake app, a reporting system or a simple intranet web app.

AI-driven feature

An interface on top of a large language model that performs a specific task: summarising documents, answering questions, generating content. A first prototype for an AI application to test whether the output is usable.

Mobile app sketch

A prototype that also works on smartphones, such as a field-work app or a membership app. Often built as a responsive web app that can later be developed further as a native or hybrid app.

How does a typical working day go?

A One Day Build is deliberately tightly structured. A working day is short, so every phase has a fixed purpose. The full story — including what you send in beforehand, who's at the table and what you take away afterwards — is on the OneDayBuild page, onedaybuild.nl. In broad strokes, a day looks like this:

1
Preparation

Before the day, you share the use case and a few references. We choose the right stack, set up the project environment and make sure we can start building straight away on the day itself — rather than installing tooling first.

2
Pinning down the scope

In the morning, we define a sharp scope together. Which core flow has to work? Which screens are essential? What do we explicitly leave out of this prototype? A good scope is the difference between a finished prototype and a half-delivered one.

3
Building and adjusting

We spend most of the day building, with you at the table. We regularly show what works and adjust based on your feedback. Decisions that would normally play out in tickets and emails happen on the spot.

4
Going live and handing over

By the end of the day, the prototype is running on a real URL. You get access to the code, a short written summary of the choices we made and — if you want it — a roadmap for a possible follow-up project.

What do you get at the end of the day?

A working prototype is the visible result, but the most important thing is that you can move forward. The prototype is meant to support decisions — not to be a product in itself. We make sure you can use it straight away, whether the outcome is "we're going ahead" or "we're stopping here".

The working prototype

  • A live application on its own URL, shareable with your team or stakeholders
  • A working core flow with realistic data — no lorem ipsum, no empty screens
  • A responsive interface that works on laptop, tablet and phone
  • Access to the source code, in a Git repository in your name

The foundation underneath

  • A tech stack choice that fits where this idea could eventually grow
  • A written summary of the choices made and why
  • A rough roadmap sketch of what a follow-up project would involve
  • Honest advice on whether a follow-up makes sense at all — and if so, in what form

Why does prototyping in a day actually work?

Building a prototype in a day would have been unthinkable ten years ago. Three developments have made it feasible, and all three have accelerated sharply in recent years:

Mature frameworks

Tools like Next.js, React and Tailwind handle the tedious work — routing, styling, forms — out of the box. What remains is the logic that makes your use case unique.

Database-as-a-service

With cloud Postgres providers, Firebase and similar services, you have a working database and authentication within minutes. No configuring servers on the day itself.

AI-assisted development

Code assistants like Cursor and Claude speed up writing standard code. The developer stays in the driving seat — but spends less time on boilerplate and more on the choices that matter.

It isn't "magic" and it doesn't solve every problem. Production software has different requirements — testing, security, performance, compliance — and we take plenty of time for those. But to answer the question "is this actually possible?", a working day is often more than enough. Read in the knowledge base on software costs how a one-day prototype compares to larger development budgets.

Which technology do we use as standard?

The choice always depends on the use case, but there is a commonly used foundation we can start any One Day Build with. The stack is deliberately mainstream — no exotic experiments — so that a possible follow-up project doesn't get stuck on odd choices made on the day itself.

Frontend

Next.js React TypeScript Tailwind CSS shadcn/ui Astro

For the interface, we usually choose Next.js or Astro with React components. Both frameworks are well documented and widely adopted, so any developer team can pick them up later. We test mobile interaction through responsive design — for truly native behaviour, we sometimes use Flutter.

Data, AI and hosting

PostgreSQL Supabase Prisma OpenAI / Anthropic Vercel Cloudflare

For data, we use Postgres via a managed provider, so we don't lose any time on database administration on the day itself. We connect AI features to established models via standard APIs. Hosting is cloud-managed by default, with your own domain name if you want one.

Why a One Day Build at Appfront?

Building a prototype quickly is possible with countless tools these days. The difference isn't the speed itself, but what you get out of it and what you can do with it afterwards. Three reasons why organisations do their One Day Build with Appfront rather than with a pure productising agency:

Consultancy in the same seat

The developer building your prototype helps you think through the scope. What is the core question we want to answer? Which assumption is the riskiest? It is similar to our custom consultancy, but at a different pace.

UX thinking from the start

A prototype that looks messy won't get serious responses from stakeholders. Our designers help shape the structure and feel — not as a separate design phase, but in parallel with the build.

Real engineering, not vibe coding

The prototype is built so that a follow-up project can build on it. Standard project structure, readable code, no loose hacks that have to be redone later. See our work for the software projects that grew out of starts like these.

What happens after the One Day Build?

A prototype isn't an end point. It's a decision point. Based on what's on the table at the end of the day, you choose how to proceed — and you make that choice yourself, not under pressure. We see roughly four follow-ups:

Build straight on to production

You're convinced, the stakeholders are convinced, and you want to press ahead. We turn the project into a regular custom software project with sprint planning, a fixed developer team and concrete deliverables.

Develop further into an MVP

The prototype has proven the core, but user roles, integrations and production requirements still need to be added. A web application project or a broader AI application can then be a logical next step.

Take it in-house, with occasional help

Sometimes an organisation has its own developer team and wants to handle further development internally. In that case, we hand over the code cleanly and remain available on call for sparring or small pieces of outsourced work.

Not pursuing the idea

That's a legitimate outcome too. Sometimes the result is that the idea doesn't work in this form — and then the day has saved you far more than it cost. No long-running project that falls apart halfway through.

Does this sound like what you need?

Start with a short description of the idea and what you want to prove with it. We'll let you know whether a One Day Build is a good fit, or whether a different approach makes more sense. For the full proposition, availability and what to send in beforehand, see the OneDayBuild page.

Frequently asked questions about prototyping in a day

The questions we get most often from organisations considering a One Day Build or wanting to validate a use case this way.

A prototype proves an idea — can this work, will people use it, is this the right direction. An MVP (minimum viable product) is a first production version that goes to real users and can generate revenue. A prototype comes before the MVP, not after. You can read more in our knowledge base article on MVP versus prototype.

The current price, availability and what is included are listed on the OneDayBuild page, onedaybuild.nl. It also explains how the price relates to any follow-on project. We deliberately don't publish a price list on this page, because the terms are adjusted from time to time.

For a tightly scoped use case, yes. That doesn't mean a production app doesn't take months of build work, but for the question "does this core flow work the way we think it does?", one working day with an experienced team at the table is often enough. The crucial word is scope: a One Day Build that tries to cover too much won't deliver a working prototype. That's why we keep the scope tightly controlled.

You do. At the end of the day you get access to the Git repository, and you can host the code yourself or have your own team develop it further. No vendor lock-in. Even if you decide not to continue with Appfront, the code remains yours.

A short description of the idea, the user it is intended for, and the central question the prototype needs to answer. Optionally, a few examples or references of similar interfaces. No technical specs needed; we work those out together. The OneDayBuild page, onedaybuild.nl, describes the preparation process in more detail.

In most cases, yes, provided it is data that isn't subject to strict compliance requirements. An Excel file with test data, a CSV export from an existing system or a few sample records is usually enough. For production data from sensitive systems, we ask in advance about any data processing agreements or restrictions.

Then we turn it into a follow-on project. Depending on what the idea requires, that could be a custom software project, an MVP build or a feature built into an existing system. In that case, we create a roadmap together with a sprint plan and targeted deliverables.

Yes, and that is often where the most value lies. For organisations without their own developer team, a working prototype is the moment to build internal support for a digital initiative. We are used to working with management teams, innovation managers and operational teams who don't write code themselves.

One Day Build within our wider services

A One Day Build is an entry-level product, not a standalone activity. It fits into an ecosystem of services in which we guide organisations from first idea to live software. For those looking beyond the prototype, these are the logical next steps or alternatives within our services portfolio:

Custom software development

Custom software development is the natural follow-up to a successful prototype. Full sprint-based projects with UX, development and delivery.

Web application development

Building a web application suits prototypes that are growing towards a real user base, with authentication, roles and integrations.

Building AI applications

For prototypes with an AI component, we use an AI application project, including evaluation of model output and cost structure.

Software consultancy

Not a One Day Build, but a project lasting weeks? Our software consultancy supports you with architecture and stack choices.

Prototype projects

Something a bit more extensive than a day? An app prototype project covers several sprints with deeper development and user testing.

See our previous work

Curious which projects have grown out of similar questions? Our work features examples of software projects in healthcare, transport and the public sector.

A prototype is faster than an explanation

Whether or not the idea goes ahead, a working prototype sharpens the conversation, makes the decision easier and makes the next step more concrete. Tell us in a few sentences what you have in mind, and we'll see whether a One Day Build is the right format. For the full explanation of the approach, availability and terms, see the OneDayBuild page.

Edit content