Ignis Design
All insights
Product··5 min read

AI can build the app. So why do companies still pay for one?

Lovable, Bolt and Cursor made building an app cheap. Owning one did not get cheaper. What companies actually pay for, and when building it yourself is the better call.

A question we hear more and more, from founders, from business owners and on X: if Lovable, Bolt or Cursor can build an app in an afternoon, why would anyone still pay a team to build one?

It is a fair question, and we build with AI ourselves every day. The tools really have made the first version cheap. But the first version was never where most of the cost of an app sat. People pay for what happens after the build: keeping the app running, current, safe and supported, and having someone who answers for it.

The build is the visible part

When you generate an app, you see screens, a login and a database that works. What you do not see is everything a product needs once other people depend on it. That work does not show up in a demo, so it is easy to assume it does not exist. It shows up later, usually on a busy day, usually in front of a customer.

Here is what that work consists of.

1. Keeping it running

A live app needs hosting that holds up when more people arrive, backups that are actually tested, error logging and alerts, and someone who looks at those alerts. If the app stops working on a Saturday morning, the question is not whether AI could have written the code. The question is who notices, who fixes it and how fast.

None of this is difficult on its own. It is just work that never ends, and it has to be someone's job.

2. Keeping it current

Software ages even when nobody touches it. Every app depends on dozens of packages that get security fixes, and the platforms move on every year.

Since 28 April 2026, Apple only accepts uploads to App Store Connect that are built with Xcode 26 and the iOS 26 SDK. Google Play requires new apps and updates to target a recent Android API level and raises that bar every year; apps that fall behind stop being offered to new users on newer devices. So even an app that works perfectly today has to be rebuilt, tested and resubmitted regularly to stay in the stores.

On the web it is the same story with frameworks and server software. The PHP2Shell vulnerability showed how quickly an outdated stack becomes a risk. If updates depend on someone remembering, they do not happen.

3. Keeping data safe

The most common gap we find in AI-built apps is data access: the interface hides other users' records, but the database or API behind it hands them out to anyone who asks. We described how to test for it in what a Lovable prototype needs before real users.

Once real people use the app, this stops being a technical detail. Under the GDPR, a personal data breach generally has to be reported to the supervisory authority within 72 hours of becoming aware of it (Article 33). That assumes you notice the breach, know what was affected and know who to call. Paying for an app is partly paying for someone to have thought about this before it happens.

4. Supporting the people who use it

Users forget passwords, get stuck in onboarding, pay twice, want their account deleted or find a bug on a phone nobody tested. Each of those needs an answer, and most need a tool: an admin or support portal where your team can see what happened and fix it without touching code.

These portals rarely appear in a generated prototype, because a prototype has one user: the person building it. In real products they are often as much work as the app itself.

5. Someone who is accountable

This is the part people underestimate most. When something goes wrong, a business needs a person or a team who knows the code, owns the decision and can explain what happened to a customer, a partner or an investor. An AI tool will happily write a fix. It will not sit in the meeting.

AI made building cheap. It did not make owning software cheap.

When building it yourself is the right call

None of this means you should pay a team for everything. There are plenty of cases where building it yourself with AI is the smarter choice:

  • Testing an idea. If the goal is to learn whether anyone wants the product, a prototype you built in a week is exactly right. We argue for it in AI made building cheap.
  • Internal tools for a small team. If five colleagues use it, nobody pays and the data is not sensitive, the bar is much lower.
  • Short-lived projects. A landing page for an event or a one-off calculator does not need a maintenance plan.

The line usually sits where other people start to rely on the product: customers sign up, money changes hands or personal data is stored. From that point on, the work after the build is the larger part of the job.

Questions to ask before you decide

  • Who will notice when the app is down, and how?
  • Who updates dependencies and resubmits the app when Apple or Google change their rules?
  • Who can see which data, and has that been tested with more than one account?
  • Where does your team go when a user writes in with a problem?
  • If something goes badly wrong, who explains it to your customers?

If you have good answers to all five, you may not need an agency. If you do not, that is what you would be paying for. Our app development page explains how we design, build and launch apps with one senior team, and our page for founders covers taking an existing prototype to production.

Fredrik Christensen
Fredrik Christensen
Co-founder · Product & Technology

Fredrik brings more than 18 years of experience in product and design, including leading large design teams inside technology companies such as Pennylane. He has also founded and sold businesses, giving him a practical understanding of the decisions, constraints and responsibilities on the other side of the table.

LinkedIn
Where to go next
App development
Learn more
Contact

Tell us what you’re working on.

Bring an idea, an existing product or a launch you’re preparing for. We’ll discuss what you need, where we can contribute and what a sensible first step looks like.

hello@ignisdesign.agency