Excel App Builder: Should Excel Support Turning Workbooks into Standalone Low-Code Applications?

Excel has been much more than a spreadsheet application for a long time.

In many organizations, Excel is already used as an informal low-code development platform. Advanced workbooks often contain not only data and formulas, but complete domain-specific logic: calculation models, planning tools, dashboards, input forms, reports, simulations, administrative workflows, and sometimes even small internal business applications.

This is one of Excel’s greatest strengths. It allows domain experts, power users, analysts, engineers, teachers, consultants, and small businesses to build working tools without becoming full-time software developers.

However, there is a structural limitation: the final product usually remains an Excel workbook.

That creates several problems:

• the user needs a compatible Excel installation,
• macro security and Trust Center settings can block functionality,
• formulas and business logic are difficult to protect properly,
• distribution and updates are not as clean as with real applications,
• workbook-based tools often look less professional than standalone software,
• user interface, data, and logic are often mixed together in the same file.

I believe Microsoft could turn this existing reality into a major strategic opportunity.

Core proposal: Excel App Builder / Excel Runtime

My suggestion is an official Excel App Builder or Excel Runtime.

The idea would be to allow selected Excel workbooks to be packaged as protected standalone applications.

Excel would continue to serve as the calculation, data, and automation engine in the background. The end user would not necessarily see the workbook itself. Instead, they would interact with a clean application interface: input forms, buttons, dashboards, charts, reports, controlled tables, and export options.

Possible output formats could include:

• Windows apps,
• web apps,
• Teams apps,
• SharePoint apps,
• mobile-friendly internal tools,
• protected specialist applications.

This would not replace Power Apps. In my view, it could complement Power Apps very well.

Excel could remain the place where fast domain logic, calculations, prototypes, and models are created. Power Apps, Dataverse, Azure, and the wider Microsoft ecosystem could then support larger, scalable, enterprise-level workflows.

In other words:

Excel could become the natural entry point into Microsoft’s low-code ecosystem.

Why this could matter strategically

Excel already has an enormous “hidden developer base”: people who are not traditional programmers, but who build useful tools with formulas, tables, Power Query, Power Pivot, VBA, Office Scripts, and now AI assistance.

This is a unique market position.

Many of these users would not start with C#, JavaScript, Python, or a full application framework. But they already start with Excel. They already build the logic there. The missing step is a professional way to package, protect, distribute, and update those solutions.

An official App Builder could:

• strengthen Excel’s long-term relevance,
• differentiate Excel from simpler spreadsheet competitors,
• create a stronger bridge between Excel and Power Platform,
• give power users a professional deployment path,
• create new commercial licensing opportunities,
• reduce the need for fragile VBA/UI workarounds,
• make Excel-based tools more secure and maintainable.

Example use cases

A small engineering office creates a technical calculation workbook and exports it as a protected customer tool.

A school or university builds a grading, diagnostic, or planning tool with Excel logic but provides staff with a clean app interface.

A small business turns an Excel-based quotation calculator into an internal sales app.

A finance department packages a planning model as a controlled scenario tool for managers.

A consultant builds specialized calculation tools and distributes them professionally without exposing the workbook structure.

These are not exotic scenarios. Many people already build this kind of logic in Excel today. The difference would be that Microsoft could provide an official, safe, and professional deployment path.

Supporting features that would make this stronger

1. Modern UI layer for Excel-based apps

Excel-based applications would need a modern interface layer:

• forms,
• dialogs,
• navigation pages,
• buttons,
• card layouts,
• dashboards,
• responsive views,
• mobile-friendly layouts,
• role-based views,
• binding to cells, tables, named ranges, and data models.

This would create a clearer separation between data, logic, and user interface.

2. Protected workbook logic

A professional app export would require strong protection options:

• hidden formulas,
• protected named ranges,
• protected scripts or macro logic,
• defined input areas,
• digital signing,
• controlled editing,
• update mechanisms,
• possible licensing controls for commercial distribution.

3. Formula cells with controlled manual override

One frequent Excel problem is that users overwrite formulas.

A useful new cell mode could be:

default formula + optional manual override

The cell would keep the original formula internally but allow a controlled manual exception value. Excel could show whether the formula is active or manually overridden.

This would remove many helper-column and VBA workarounds in planning, pricing, grading, budgeting, and technical models.

4. Native database layer inside Excel

Excel is widely used as a database, even when that becomes fragile.

A native database layer could support:

• primary keys,
• relationships between tables,
• required fields,
• validation rules,
• change history,
• duplicate detection,
• form views,
• simple queries,
• optional cloud synchronization.

This should feel like a natural extension of Excel tables, not like a separate database product.

5. Multidimensional workbook models

Many workbooks use separate sheets for months, locations, versions, departments, or scenarios. This often creates duplication and maintenance problems.

Excel could support native dimensions for tables and models, for example:

• time period,
• location,
• scenario,
• version,
• department.

Formulas, charts, dashboards, and PivotTables could become dimension-aware.

This would be especially useful for financial planning, controlling, simulations, scientific models, and project planning.

Why now?

AI is changing how people build with Excel.

Copilot and other AI tools make it easier for non-programmers to generate formulas, scripts, models, and structured workflows. That means more users will be able to build complex Excel-based solutions.

But if AI helps users create more advanced workbooks, the next logical question is:

How can these workbooks be safely packaged, shared, protected, and used as real tools?

An Excel App Builder could be the answer.

Possible first step

This does not need to start as a massive platform.

A realistic first version could be experimental:

• selected workbook ranges,
• simple input forms,
• protected formulas,
• dashboard view,
• Windows or web runtime,
• export as an internal app,
• optional Teams or SharePoint integration.

It could even begin as an Excel Labs / Microsoft Garage style experiment to test demand and gather feedback from power users, developers, and organizations.

Core question for the community

Excel is already used as a hidden development platform.

Should Microsoft make this official?

Would an Excel App Builder / Excel Runtime be useful for your organization, clients, or internal tools?

Which feature would matter most in a first version?

• protected workbook runtime,
• modern UI layer,
• formula override cells,
• native database layer,
• multidimensional models,
• Power Platform integration,
• commercial app distribution?

I would be very interested to hear how other Excel users, developers, MVPs, and Microsoft product people see this idea.

In short:
Excel already allows millions of people to build domain-specific logic. Microsoft could turn that strength into an official, secure, and economically attractive low-code application platform.