Your Org Is Full of Unbuilt Apps: Introducing the Latent Demand Audit

Most companies think they have an AI problem.

In reality, they have a visibility problem.

The tools are now strong enough that a single person, working with an AI coding agent, can build solid internal tools in days or even hours. What is missing is not code. It is clarity about what should exist.

The Invisible Backlog Of "Wouldn't It Be Nice If..."

Every organisation has a silent backlog of unbuilt software:

The spreadsheet that runs half a process.
The recurring task everyone copies from the last email.
The "quick check" someone does in three different systems before approving something.
The weekly report that eats up half a day in copy-and-paste work.
The Notion or Word template that someone hacked together to keep things on track.

These are not logged as tickets. They don't show up in official roadmaps. They live in the heads and hard drives of people who have given up on anyone ever fixing them.

Now that agents and AI coding tools can build small, local, messy software quickly, this hidden layer of work is the biggest opportunity space in most enterprises.

The problem is simple: leaders can't manage what they can't see.

Moving From IT-Led To Employee-Led Demand

Traditional software demand is IT-led and project-driven:

Someone writes a business case.
It gets prioritised against everything else.
Months later, if it survives, it becomes a project.

That model cannot handle hundreds of tiny, high-value micro-apps.

These micro-apps might:

Auto-assemble a weekly client status report.
Clean and structure inbound data from a partner.
Prepare a first draft of a board pack from live metrics.
Reconcile transactions between two systems with slightly different schemas.
Organise a folder of messy documents into something searchable and sane.

Each one on its own may not seem "strategic" enough for a formal project. Together, they can reshape productivity, reduce errors, and unlock capacity for more meaningful work.

To get there, you need to flip the model:

IT focuses on guardrails, platforms, and security.
Employees and local leaders surface what actually needs building.
Agents and digital employees handle most of the glue code and workflow logic.

What A Latent Demand Audit Does

A Latent Demand Audit is a structured way to ask:

"Where in your day do you quietly fix things that software should already handle?"

Instead of asking people "What AI use cases do you want?" (which they often cannot answer), the audit looks for signals:

Where do you repeat the same steps every week?
Where do you have to jump between systems for one task?
Where do you rely on one person who "knows how to do it"?
Where are you maintaining your own spreadsheet, template, or script?
Where do you say "I could do my job in half the time if only..."?

The output is not a vague "ideas list". It is a portfolio of concrete opportunities for:

Micro-apps.
Digital employees.
Agent-assisted workflows.

Each opportunity can be scored on impact, feasibility, and risk so leaders can see where to start.

Why This Matters Now

The timing is important.

Coding agents and tools like Claude Code, Cursor, Replit, and others have changed what one motivated person can do. You no longer need a full product team to prototype internal tools.

That means two things:

1. The cost of building internal software has collapsed. Small, local apps are now economically viable.

2. The bottleneck has moved to discovery. The hard part is no longer building the app, but knowing which apps to build.

A Latent Demand Audit plugs directly into this new reality. It helps you:

Turn vague frustration into specific, solvable problems.
Prioritise where digital employees or micro-apps should appear first.
Give your AI champions a clear backlog to work from.

From Audit To Action

On its own, a survey is just data. The power of a Latent Demand Audit lies in what happens next.

A typical flow looks like this:

Run the audit across selected teams or the whole organisation.
Cluster responses into themes: reporting, approvals, client onboarding, reconciliations, etc.
Score opportunities on impact, feasibility, and risk.
Select a starter set of 3-5 micro-apps or digital employees to build.
Assign AI champions or a small build squad to each opportunity.
Launch, learn, and loop. Use early results to refine the next wave.

The result is a rolling, evidence-based pipeline of internal tools and digital employees that reflect how work actually happens, not how it looks on a process chart.

Where The Digital Employee Fits In

The Latent Demand Audit is not just about one-off tools.

Many of the opportunities it surfaces are not "apps" in the traditional sense. They are roles that a digital employee can fill:

"Reporting Analyst" who prepares dashboards and summaries.
"Deal Desk Assistant" who prepares quotes and checks edge cases.
"Onboarding Coordinator" who guides new clients or staff through steps.
"Research Associate" who assembles background briefs and comparisons.

Once you see these as roles, you can:

Define responsibilities and guardrails.
Measure performance.
Hand them over, like you would with a new team member.

The audit helps you find where those roles are needed before you start building them.

Closing Thought

Most organisations do not suffer from a lack of AI ideas. They suffer from a lack of structure to turn everyday friction into buildable, testable, measurable digital employees and micro-apps.

A Latent Demand Audit is a simple, practical way to:

Listen to the organisation at scale.
Turn invisible workarounds into a visible opportunity map.
Focus your agents and builders on what matters most.

If your teams are already saying "I could do this so much faster if...", then the opportunities are there. You just need a way to see them.