Learn the system. Enter its screens. Become proficient inside the environment someone else designed.
Bring an environment. State the outcome. Let software prepare itself around the person.
App People and Stack People
The New Divide in 2031
By 2031, assume that 300 million people have moved substantially from apps to personal stacks.
They still encounter apps. Their employers still use established systems. Governments, banks, hospitals, universities, and large companies still maintain standardized software.
But these people no longer organize their digital lives around those applications.
They have their own data environments. Their files, records, preferences, procedures, history, and AI agents are organized around them. Their AI writes software when necessary, creates temporary interfaces, and connects to outside systems through APIs, command-line interfaces, MCP servers, and other machine-readable channels.
They do not open software and ask what it allows them to do.
They tell their stack what they want accomplished.
At the same time, the app industry has not disappeared.
The major app companies have fought back aggressively. They have added AI assistants, automated workflows, natural-language features, improved interfaces, and generous bundles. Many have maintained large, stable, and profitable user bases.
Their businesses are no longer growing as rapidly as they once did, but they remain deeply embedded in companies and institutions. Millions of people still begin work each morning by opening the same collection of applications.
The world now contains two increasingly different kinds of people:
App people and stack people.
The distinction is not primarily about which software they use.
It is about how they think.
The App Person Learns the System
An app person encounters a new piece of software and asks:
“How does this work?”
They learn the menus.
They learn the fields.
They learn the workflow.
They watch the training videos.
They discover the shortcuts.
They become proficient in the system as it was designed.
This can make them an excellent employee. Large organizations depend on people who understand established procedures, follow controls, maintain consistency, and know how to operate the company’s systems correctly.
The stack person encounters the same software and asks a different question:
“What does this system need from me?”
The stack person may never become highly skilled at navigating its interface. Their AI reads the documentation, examines the available machine interfaces, maps the required data, and learns how the company expects information to be submitted.
The stack person does not necessarily resist the company’s process.
They may follow it precisely.
But they do not personally perform every step through the company’s screens.
Their stack does.
That difference becomes enormously important.
Conforming to the Form, Not the Interface
A stack person can conform to a company’s requirements without adopting the company’s interface as their working environment.
Suppose a company requires every sales opportunity to be recorded in its customer-management system.
The app employee opens the system, creates the opportunity, completes the required fields, updates the stage, adds notes, schedules the follow-up, and periodically returns to maintain the record.
The stack employee may never open the customer-management application.
After a meeting, the employee speaks to their AI:
“Update the Henderson opportunity. They are interested in the enterprise package, but security approval is the main obstacle. Schedule a follow-up for next Thursday and prepare the technical material they requested.”
The employee’s stack converts that instruction into the precise form required by the company. It creates the correct records, uses the approved categories, attaches the appropriate documents, schedules the follow-up, and preserves a copy of the relevant information in the employee’s own system.
The company receives exactly what it requires.
The employee simply does not use the company’s interface to provide it.
This is the central accommodation organizations will have to understand.
The stack person is not necessarily asking to ignore the company system.
The stack person is asking for permission to interact with it through their own Personal Operating System.
They will conform to the form.
They will not willingly surrender to the interface.
Hiring a Stack Person
Hiring a stack person is different from hiring an app person.
An app person arrives with experience.
A stack person arrives with accumulated capability.
Their stack may contain years of working methods, research patterns, templates, analytical procedures, decision rules, communication preferences, code, agents, and structured knowledge.
It knows how they prepare for meetings.
It knows how they evaluate opportunities.
It knows how they organize projects.
It knows how they write.
It knows how they check their own work.
It knows which questions they usually forget to ask.
It knows how they prefer information to be presented.
It knows what requires their attention and what can be completed without it.
The company is not merely hiring one person.
It is hiring a person whose capability has been compounding for years.
This employee may appear to have superpowers.
They prepare faster.
They remember more.
They produce more complete work.
They move easily between disciplines.
They learn unfamiliar subjects quickly.
They can create specialized software for a task in hours rather than waiting for the company’s technology department to add a feature.
They may accomplish in one afternoon what previously required several people and several meetings.
But the company cannot treat this person exactly like a conventional software user.
Telling a stack employee to abandon their own system and perform all work manually inside the company’s applications is similar to hiring a skilled craftsperson and requiring them to leave their tools at home.
They can do it.
They simply become much less capable.
The Employee Brings an Operating System
For most of the industrial era, the employee brought labor to the company.
The company supplied the machinery.
During the app era, the employee brought knowledge and experience, while the company supplied the software environment.
In the stack era, the employee increasingly brings an operating environment of their own.
This creates a new employment question:
How much of the employee’s personal stack may enter the company?
That question is not answered by a traditional bring-your-own-device policy.
A laptop is only hardware.
A personal stack includes memory, agents, data structures, workflows, models, code, preferences, and years of accumulated operational intelligence.
It may be far more valuable than the device on which it runs.
It may also create far more risk.
The employee’s stack may contain information from previous employers.
It may use external models.
It may store copies of company data.
It may create code the company does not understand.
It may take actions through company systems.
It may combine personal and corporate information.
It may preserve knowledge after the employee leaves.
The stack person can be extraordinarily productive, but only if the company develops rules that allow this capability to operate safely.
The New Employment Agreement
By 2031, sophisticated companies will address the personal stack directly in employment agreements.
The old employment agreement was written for human work performed through company-owned tools.
The new agreement must recognize that the employee may use personally controlled intelligence and software to perform that work.
The agreement will need to answer practical questions.
Which company systems may the employee’s stack access?
Which company data may enter the personal environment?
Must company information remain inside a protected portion of the stack?
Which AI models are approved?
What actions may be performed automatically?
Which actions require human approval?
What records must be preserved for audit?
Who owns code generated while doing company work?
Who owns improvements made to the employee’s preexisting stack?
What happens to company knowledge when employment ends?
Can the employee take their general methods and agents with them?
Can the company retain procedures created by the employee’s stack?
These questions cannot be handled by simply banning personal AI.
Companies that ban personal stacks entirely will protect themselves from some risks.
They will also make themselves unattractive to many of the most capable workers.
The better approach will be governed participation.
The company defines the boundaries.
The employee’s stack works within them.
The Corporate Interface Changes
Today, companies design interfaces primarily for human employees.
By 2031, leading companies will design two interfaces for every important system.
One will be for people.
The other will be for personal stacks.
The human interface will include screens, menus, forms, dashboards, and reports.
The stack interface will include APIs, command-line tools, structured permissions, event streams, machine-readable documentation, and secure agent protocols.
For app employees, the company interface remains the workplace.
For stack employees, it becomes an emergency entrance.
Their normal work occurs through the machine interface.
This changes the meaning of good enterprise software.
The best system will no longer be the one with the most attractive dashboard.
It will be the one that allows authorized personal stacks to understand it, use it, and comply with it reliably.
A company may still require a particular accounting structure, sales process, approval chain, or regulatory record.
But it will become less concerned with whether the employee personally clicked the correct sequence of buttons.
The company cares about the accuracy, security, authorization, and auditability of the result.
Onboarding Changes
Traditional onboarding teaches the employee how to use company applications.
Here is the customer system.
Here is the project-management system.
Here is the expense application.
Here is the document repository.
Here is the learning portal.
Here is the communication platform.
The employee spends days or weeks learning where everything is located and how each system works.
Stack onboarding is different.
The employee grants a protected portion of their Personal Operating System access to the company environment.
The company publishes its systems, policies, definitions, permissions, and procedures in machine-readable form.
The employee’s stack studies them.
It learns what the company calls a customer, project, expense, confidential document, approved supplier, completed task, and reportable incident.
It maps the employee’s personal vocabulary to the company’s vocabulary.
It tests the available connections.
It identifies conflicts.
It asks the employee and company administrator to resolve the few ambiguities that matter.
The app employee is trained to use the company.
The stack employee’s system is trained to work with the company.
Stack People Compound Faster
The most important difference between app people and stack people may be compounding.
An app person can become extremely skilled, but much of that skill remains tied to particular software.
They know how to perform an advanced report in one system.
They know how to configure a campaign in another.
They know how to navigate a certain enterprise platform.
When the application changes, some of that knowledge loses value.
The stack person accumulates capability at a different level.
Their system learns the underlying task.
It learns how they evaluate evidence, prepare decisions, communicate uncertainty, structure a project, and detect errors.
When one application disappears, the stack adapts to another.
When a new tool becomes available, the stack learns it.
When the employee changes industries, many of the working methods remain useful.
The stack person becomes less dependent on the continued existence of any particular app.
Their capability travels with them.
This creates a widening gap.
An app person may have ten years of experience using software.
A stack person may have ten years of experience embedded in software that continues working for them.
Management Changes
Managing stack people is also different.
The app-era manager often supervises process.
Did the employee update the system?
Did they complete the required fields?
Did they follow the approved steps?
Did they attend the training?
Did they use the correct template?
A manager of stack people must focus more heavily on outcomes and boundaries.
Was the result correct?
Was the action authorized?
Was the evidence preserved?
Were company policies followed?
Were uncertainties escalated appropriately?
Did the employee’s stack expose the reasoning and records necessary for review?
The stack employee may use a process the manager never sees.
That can be unsettling.
Managers are accustomed to equating visible activity with work. They understand familiar interfaces and established workflows. When an employee produces excellent work without visibly performing the usual steps, the manager may suspect that corners were cut.
Sometimes they will be right.
A stack can make mistakes at speed.
But forcing stack employees to reproduce traditional manual behavior merely so management can observe it wastes the advantage.
The solution is not to require visible labor.
It is to require visible accountability.
App People Wait for Features
The difference becomes especially visible when an organization encounters a new problem.
The app person searches the existing system.
Is there a feature for this?
Is there a template?
Can the software be configured?
Should we purchase an additional module?
Can the technology department build an integration?
Is there another app we could add?
The stack person begins somewhere else.
What information is required?
What result do we need?
What rules must be followed?
What capability is missing?
Can my stack create it?
This does not mean the stack person always builds custom software. Often, using an existing service remains faster and safer.
The difference is that the app is no longer the boundary of possibility.
For the app person, the available features define the available actions.
For the stack person, the desired outcome defines the required software.
Open field test Give both worlds the same new problem
Possibility begins with what the installed system already exposes.
Possibility begins with the outcome, the rules, and the capability that must exist.
The Stack Person Expects Change
App people and stack people develop different expectations about change.
The app person expects software to change periodically.
A new version is released.
A feature is added.
An interface is redesigned.
A vendor announces an improvement.
The user adapts.
The stack person expects software to change continuously.
“This report is no longer useful. Replace it.”
“This approval process is too slow. Simplify it.”
“These records should be related differently.”
“Create a temporary system for this project.”
“Remove it now that the project is complete.”
The app person sees software as a product.
The stack person sees software as a material.
It can be shaped, combined, discarded, and recreated.
That expectation extends beyond software.
Stack people become less tolerant of procedures that exist merely because changing them was once expensive.
They ask why the form has twelve fields.
They ask why the approval requires three departments.
They ask why the report is produced every Friday.
They ask why the organization stores the same information in four places.
They are not necessarily rebellious.
They simply come from an environment where unnecessary structure can be removed by speaking.
Education Divides Too
By 2031, schools and universities will face the same divide.
The app student is taught to use approved software.
The stack student arrives with a Personal Operating System that already knows how they study, research, write, calculate, organize sources, and test understanding.
The app student completes the assignment inside the required platform.
The stack student’s AI interprets the assignment, gathers the relevant material, creates temporary tools, and helps manage the entire learning process.
The question will no longer be whether students use AI.
The question will be whether the institution can distinguish between delegated production and genuine understanding.
Schools that simply ban personal stacks will increasingly resemble schools that once banned calculators or computers.
Schools that accept all stack-produced work without changing assessment will fail for the opposite reason.
Education will have to measure the student rather than the interface.
Can the student explain the conclusion?
Can the student defend the reasoning?
Can the student respond to an unfamiliar challenge?
Can the student recognize when the stack is wrong?
The stack student may have extraordinary reach.
Education must ensure that the person remains present inside that reach.
Entrepreneurship Changes
A stack person can start a business differently.
The app entrepreneur begins by assembling software.
They choose accounting, customer management, email marketing, design, e-commerce, scheduling, analytics, payroll, project management, and dozens of other services.
Before serving the first customer, the business may already have a substantial monthly software bill and a fragmented collection of databases.
The stack entrepreneur begins with a private environment.
The database is organized around the business and its owner.
The AI creates the workflows and temporary interfaces required for the first customers.
Specialized outside services are added only when necessary for banking, payments, compliance, communication, or other regulated functions.
The business does not begin with a software stack assembled from apps.
It grows from the founder’s personal stack.
This allows a very small company to operate with capabilities once available only to a much larger organization.
The stack entrepreneur can appear to have a finance department, marketing team, research group, software staff, and operations function.
In reality, there may be one person and a highly developed Personal Operating System.
App Companies Remain Profitable
None of this requires the immediate collapse of the app industry.
Many app companies remain profitable in 2031.
They have strong brands, trusted records, mature security, regulatory approvals, established customer relationships, and enormous installed bases.
They add AI features aggressively.
They allow users to speak instead of click.
They automate repetitive tasks.
They offer their own agents.
They make their interfaces easier to use.
For app people, these improvements are valuable.
The software becomes more capable without requiring a fundamental change in how the person works.
But the app companies face a deeper problem.
They are improving the app at the same time stack people are leaving the app as a category.
A faster horse does not answer the person who no longer wants to ride.
The app vendor believes the competition is another app with better features.
The stack person believes the app itself is the unnecessary feature.
The Stable Install Base
This produces an unusual market.
App companies retain millions of loyal users.
Their revenue is stable.
Their products are deeply embedded in institutions.
They raise prices, bundle services, and generate healthy profits.
But their user populations age.
New users increasingly begin with stacks.
Young workers do not necessarily reject apps. They simply do not build their working identities around them.
An app may be required by an employer, bank, school, or government agency. The stack person treats it as an external system to be satisfied.
The app person lives inside the application.
The stack person passes through it.
This distinction is difficult to see in installation statistics.
Both people may technically have the app.
Only one of them is truly its user.
Two Different Kinds of Independence
App people and stack people possess different forms of independence.
The skilled app person can work independently inside a known system.
Give them access, and they know what to do.
The stack person can construct a working system around an unfamiliar problem.
Give them the outcome, constraints, and available information, and they can often create the necessary capability.
The app person is operationally independent.
The stack person is architecturally independent.
Both remain valuable.
But in a world of rapid change, architectural independence becomes increasingly powerful.
The stack person does not need the environment to be prepared in advance.
They bring an environment capable of preparing itself.
The New Digital Class Divide
The difference between app people and stack people eventually becomes economic.
A strong personal stack requires time, knowledge, confidence, and access to capable AI.
It improves through use.
Every correction can become a standing instruction.
Every completed project can become a reusable procedure.
Every new domain can become structured knowledge.
Every useful tool can be absorbed into the system.
The person who starts earlier accumulates an advantage.
By 2031, a mature stack may represent years of compounding capability.
Two equally intelligent people can receive the same assignment.
One begins from a blank screen and a collection of apps.
The other begins with a system that already understands how they work.
The difference in output may be dramatic.
This creates a new form of inequality.
Not merely access to AI.
Not merely the ability to write prompts.
The deeper divide is between people whose digital capability compounds and people whose digital work repeatedly begins again inside someone else’s application.
The Company Must Choose
By 2031, every serious organization will have to decide what kind of worker it is designed to employ.
An app company requires employees to enter its systems, learn its interfaces, and perform work according to standardized procedures.
A stack-compatible company publishes secure machine interfaces, clear data rules, explicit permissions, and auditable requirements. It allows an employee’s Personal Operating System to participate without surrendering corporate control.
The first company may feel safer.
The second company will often move faster.
The winning model will not eliminate standards.
It will separate standards from interfaces.
The company still determines what must be true.
The employee gains greater freedom in how the work is accomplished.
That is the bargain stack people will expect.
The Person Becomes the Platform
The app era organized people around software.
The stack era organizes software around people.
That change produces different workers, different students, different entrepreneurs, different companies, and eventually different institutions.
App people become highly capable within systems designed by others.
Stack people continually design systems around themselves.
App people accumulate software skills.
Stack people accumulate software capability.
App people wait for features.
Stack people describe changes.
App people adopt the company interface.
Stack people connect their operating system to the company’s required form.
Neither group disappears in 2031.
But they no longer inhabit the same digital world.
One lives inside applications.
The other carries a platform of their own.
3 thoughts on “App People and Stack People”