Product studio vs traditional agency: why it changes everything

Let's be blunt. Many digital projects go off track. Not because the ideas are bad, not because the market doesn't exist, but because execution is broken. An MVP that takes six months to ship. A product that looks nothing like the original vision. A budget that explodes while nobody raises the alarm.

If you've ever worked with an agency, you probably know the script: a polished pitch, ambitious promises, then a very different reality once the project kicks off. Developers rotate mid-project. The project manager juggles 8 clients simultaneously. Your project becomes a number in a pipeline.

Source: McKinsey, "Delivering large-scale IT projects on time, on budget, and on value", 2012.

That figure covers large projects, but the mechanism holds at any scale. The same study shows that every extra year of duration adds about 15% to the cost overrun: the longer and more rigid a project, the more it slips. The business model weighs in too. When a vendor bills by time spent, nothing pushes it to go faster. When it staffs juniors on your project, it protects its margin, not your outcome.

The problem isn't the talent of the individuals. There are brilliant people in agencies. The problem is the system. And that's exactly why a different model has been emerging over the past few years: the product studio.

To understand why the product studio model works better, you first need to understand where the traditional agency model runs into trouble. And it starts with a simple observation: an agency is a services business. Its business model depends on volume. More clients, more revenue.

There's nothing inherently wrong with that. But the consequences for your project are real. When an agency manages 15, 20, sometimes 30 projects in parallel, resources are stretched thin. Your project is never anyone's number one priority. The senior dev who did the pitch isn't the one writing the code. The designer who made the mockups moves to another client the following week.

Then there's the hourly billing problem. When an agency sells 200 man-days, their incentive is for the project to take... 200 days. Not 120. Not 80. There's no reward for being more efficient. In fact, efficiency reduces revenue.

And then there's the skin in the game question. When your project fails, the agency moves on to the next one. They've already cashed in. Your failure doesn't penalise them. They have no reason to fight for your product to succeed in the market. Their job ends at delivery, not at success.

This isn't a criticism of the people who work at agencies. Many are talented and driven. But the system they operate in doesn't incentivise them to give their best for your specific project. It's structural, not personal.

A product studio is fundamentally different. It's not an agency that changed its name. It's an organisational model built around one conviction: you build better when the people building have already launched their own products, and when they stay after delivery.

In practice, the people who build stay involved in every project, the studio also builds its own products, and the work is organised so that every request is reviewed by someone who understands your business. At Figue, that organisation is called a queue: a team shared across clients, one active request at a time per slot, a point of contact who knows your product. It is not a dedicated team, and that is precisely what makes the price sustainable.

The studio model isn't new. Teams like Thoughtbot, ustwo or Hanno have worked this way for years: the people who build stay close to the client, and the studio runs its own products. In France, the model is now emerging seriously, and that is exactly what we do at Figue.

“We don't build products for clients. We build products with founders.”

That semantic difference is huge. 'For' implies a transactional relationship. 'With' implies a partnership. And that's precisely what makes the difference between a mediocre product and one that actually works.

Theory is nice, but what does it look like in practice? Here's what changes when you work with a product studio instead of a traditional agency.

Take a concrete example. You want to launch a B2B SaaS. With a traditional agency, you'll spend 2 months on a detailed spec, 4 to 6 months in development, then delivery. The agency leaves, you receive a finished product that's never been tested by the market. You discover that half the features aren't used. Too late, the budget is spent.

With a product studio, the approach changes. You start with a lean MVP in a few weeks. You put it in front of real users. You iterate based on data, not opinions. The scope evolves naturally. And the studio stays involved because it has a direct interest in the product finding its market.

Source: CB Insights, "The top 9 reasons startups fail", 2026.

This isn't just about methodology. It's about mindset. An agency thinks in terms of delivery. A studio thinks in terms of outcomes. Delivering a product is easy. Delivering a product that works is a completely different game.

Not all studios are created equal. And calling yourself a 'product studio' isn't enough, the model has to be real. Here are 5 concrete signals to distinguish a genuine product studio from an agency that rebranded.

At Figue, we tick these boxes. We build our own SaaS products. The people who build your product are in every request. Work is organised as a queue, one active request at a time per slot, reviewed before every delivery. And we stay after launch, with no commitment, because that is where the real work begins.

For a long time, product studios sold projects: a scoping, an MVP, a launch. Today, they also sell a subscription: unlimited development. The studio no longer sells a project that ends, but a queue of requests that never ends: a new feature, an integration, an AI agent, a fix, in the order you choose, for a fixed monthly price.

It is the most complete version of "with" rather than "for". The studio stays involved every month because it is its model, not because it promised. And you keep what you were looking for in a product studio: engineers in the code, people who launched their own products, and a review on every delivery. At Figue, it is called Figue Unlimited: €1,990 per month ex VAT, no commitment.

The full workings, the slot, the prices and the limits are on the unlimited development page. For a whole product built from scratch, the fixed-price project remains the right answer.

The digital world is full of vendors. People who take a brief, execute, invoice, and move on. That's not necessarily bad, but it's not what you need when you're launching a product that matters.

A digital product isn't a brochure website. It's a living thing that evolves, pivots, and must adapt to its market in real time. That demands a partner who understands this. Who lives it. Who builds their own products and knows how deeply every technical decision has business consequences.

“The difference between a good product and a mediocre one is rarely the technology. It's always the team and the alignment of incentives.”

If you have a project in mind, whether it's a SaaS, an app, an AI agent or a platform, don't look for the cheapest vendor or the biggest one. Look for the one who has the most to lose if your project fails. The one who builds as if it were their own product. Because in a product studio, that's exactly how we think.

The agency model still has its place, especially for a fixed, well-defined scope. But when a product has to live and evolve every month, a partner who stays and builds with you changes a lot.

Going further: the full definition of a product studio and the fractional CTO.