A man reads a stage document in Maestro, with a calendar on the wall and an alarm clock beside the computer

September 2, 2026 · 6 min read

By Thomas Cohen, founder of Maestro

How long does it take to create an application in 2026?

Hours, days or months for the same idea: the difference lies less in writing code than in the exchanges around it. Timelines, route by route.

In 2026, allow a few hours for a prototype with an AI generator, a few days for a product directed stage by stage with an agent team, and several months through an agency. Writing code, now almost instantaneous, no longer makes the difference: delays come from exchanges and approvals.

a few hoursa presentable prototype generated from a description
a few daysa directed product, including requirements and verification
several monthsthe same product through an agency, including meeting cycles

Where agency months come from

An agency does not spend months typing code. The calendar fills with other things: initial scoping and its quote, queues between projects, meeting cycles, we meet, decide and meet again in two weeks, and final acceptance with its back-and-forth. Every decision waits for the next appointment. This pace has a virtue, several people mature each stage, and a price: months accumulate while your market moves. This way of working protects both the agency and its clients; its calendar cost rarely appears in the quote.

The prototype's hours

A prompt-based generator produces a presentable application in an evening: describe, look, ask again. Those hours are real, as is the result, for what it is: a living mockup, perfect for testing the idea, insufficient for receiving real customers. Our article on the prototype/product boundary explains what is missing; remember that prototype hours prepare product days without replacing them. Also allow time to formulate: describing a precise idea often takes longer than generating it.

The directed product's days

With an agent team and human approvals, the calendar changes nature: agents work continuously, and you become the critical path. Your reading of the brief, corrections to requirements and ‘Looks good to me’ approvals set the rhythm; allow one to two hours of your time per day in the first days. Construction and verification stages follow one another between your approvals. The result: calendar days largely determined by your pace, evenings included. A product whose every document you approve advances at the speed of your decisions.

What lengthens timelines, whichever route you take

Three factors stretch timelines everywhere. Indecision first: every unresolved rule, ‘we'll see about VAT’, returns later at a higher time cost. Shifting scope next: an idea added along the way costs more than the same idea written at the start, whoever builds it. Finally, data migration: Excel history to retrieve adds its own cleaning and parallel-running stages, described in our migration guide. No tool compresses these three: they depend on you.

Estimate your case with two questions

First question: can your need be expressed in rules you know how to state? If yes, a directed product takes days; if everything remains to be discovered, add discovery time whichever route you take. Second question: who decides, and how quickly? A decision-maker available an hour a day beats a monthly committee on every route. The bottleneck has shifted from construction to decision, and that resource is in your hands.

Back to the journal

Take the baton.

Leave your email to try Maestro in the first waves.

The beta opens in waves. People on the list try it first, and Maestro stays free throughout the beta.

The beta is currently available on macOS 13 or later. Your answer helps us plan other versions.

Your email is only used to let you know when access opens. Nothing else, we promise.