The content bottleneck nobody plans for.

Process · 5 min read

There's a moment in every content-heavy app project where everything stalls. The design is done. The developer is ready. The timeline is set. And then everyone realises that the app can't be built without the content. And the content hasn't been written yet.

I've seen this happen with apps that need structured data: categories, entries, descriptions, questions, template text. The founder has the knowledge in their head. They know the domain cold. But getting that knowledge out of their head and into a format a developer can use turns out to be a much bigger job than anyone expected.

Why content becomes the critical path

In app development, the critical path is the sequence of tasks that determines the minimum timeline. If any task on the critical path is delayed, the whole project is delayed. Developers can build the interface without content by using placeholder text. But at some point, real content has to go in. And if it isn't ready, the developer is either waiting or building things that will need to be rebuilt when the real content arrives.

The issue is that content preparation is work. Real work. It's not something you can knock out in an afternoon. If your app has a hundred entries that each need a title, a description, a category, and three supporting details, that's five hundred individual pieces of content. Someone has to write them, organise them, check them for accuracy, and format them so the developer can import them.

That someone is usually the founder. Because the founder is the subject matter expert. The designer can't write it because they don't know the domain. The developer can't write it because they don't know the domain either. AI can generate placeholder content, but it lacks the accuracy and nuance that domain expertise provides. The content has to come from the person who knows the space.

How to prevent the stall

Start the content work during the design phase, not after it. As soon as you know what the app will contain, start organising your content. If you need categories, write them. If you need descriptions, draft them. If you need structured data, put it in a spreadsheet. Don't wait for the design to be finished. The two can run in parallel.

Give the content a format. The developer doesn't want a Word document with paragraphs. They want structured data. Rows and columns. A spreadsheet where each row is an entry and each column is a field. That format makes it importable. It makes it checkable. And it forces you to be specific about what each piece of content actually is, rather than leaving it vague.

Set a deadline for the content that's ahead of the development start date. Not the same day. Ahead of it. Because content always takes longer than you think, and if it's not ready when the developer starts, you're paying for idle time or rework.

The founder's hidden job

Nobody tells first-time founders that a big part of their job is content creation. They think they're hiring someone to build an app. They are. But the app is a container. And they're the ones who have to fill it. The homework doesn't stop when the design is approved. It intensifies.

The upside is that this work makes the product better. When you sit down and write out every category, every description, every piece of content your app needs, you discover gaps. You find things that don't make sense. You realise that two categories should be one, or that a description needs to be rewritten because the original wording doesn't work for the user. That discovery is valuable. It just takes time.

Plan for it. Budget time for it. And start early. The content bottleneck catches everyone off guard, but only because nobody warns them. Consider yourself warned.

Sources
Content-First Design (Nielsen Norman Group) - Why content should drive design decisions, not follow them.
Designing Inside Out (A List Apart) - Content as the core of product design.

Related blog posts:

Don't forget to do your homework →

Your timeline is wrong →

What is an MVP? →