Choices for today / Four perspectives

Different roles Different decisions to make

Read these four sets of proposals as a map of your counterparties. In-house teams decide what to own. Firms decide what to sell. Technology providers decide what access to demand. Consumers and small businesses decide when to stop trusting the process. Your strategy has to meet all four.

Each seat weighed all four futures. What follows are recorded proposals, offered here as starting points for your own discussion. They are not a shared plan, and none is a record of action taken.

The same four possible futures, seen from four seats: in-house legal, law firms, technology providers, and people seeking legal help.
How the four seats used the futures
Four seats, the same four futures.

The people who built the scenarios were not the people who responded to them, and each seat read all four worlds through its own stakes, so one future can produce opposite priorities for a company, a provider and a person seeking help. The responses sort proposals three ways: expected to hold up across futures, dependent on conditions, and aimed at keeping the ability to adapt. Those labels record judgment calls, not proven results.

Recorded proposals / In-house legal

Decide what legal should own

The sharpest move here sorts legal roles by the work involved, the judgment required and the trust placed in the person, before any outsourcing decision. A sourcing strategy that starts from cost gives judgment away by accident. One that starts from this map gives it away only on purpose. This seat has the most to gain in the first two futures, where the company keeps the power to change the system’s answer, and the most to lose in the third, where the recorded worry is data handed to others. The map is how it decides, one sourcing choice at a time, which of those futures its contracts are building.

Map roles by work, judgment and trust. Use that map to decide what to retain and what to outsource.

Build an override switch in case of failure.

Promote “minimum standards of legal engagement.” The record does not specify the standards.

See proposed actions and concerns in each future
Paraphrased from the source record. A concern records a worry, not a forecast.
Possible futureRecorded proposalConcern raised
1. The company builds the systemBuild a legal service the business can trust, with clear responsibility for its decisions.A machine cannot carry accountability.
2. Legal directs the networkKeep assembling technology that advances business outcomes with legal judgment.Continually having to justify spending.
3. Providers own the infrastructureChoose partners the company can trust and who remain aligned with the business.Losing control of data handed to others.
4. People own the final sayEncourage new licenses for different kinds of legal practitioners.The balance between embracing automation and holding human authority is left open, on purpose.
Consider for your organization · Guide interpretation

Which capabilities, knowledge and decisions must stay under your organization’s control?

Paraphrased from photographs and a transcript in the source record, dated June 24, 2026.
Recorded proposals / Law firms

Rebuild delivery around relationships and capability

The bet here combines technology with relationships, and the recorded concerns undercut it from inside: slow adoption, and the erosion of the junior work that builds senior judgment. A firm that automates its own training ground has to say where the next decade of judgment comes from. The four futures treat this seat differently. The second keeps firms close to clients on the client’s terms, and the third offers firms part ownership of the machinery if they move early. The concern recorded against the fourth future is the firm’s survival itself. In all four, the firm’s business turns on the same question: what a client still pays it to answer for once production runs on a system.

Use technology to improve and diversify service delivery.

Build the data and technology capabilities the new model depends on.

Keep investing in talent and client relationships.

See proposed actions and concerns in each future
Paraphrased from the source record. A concern records a worry, not a forecast.
Possible futureRecorded proposalConcern raised
1. The company builds the systemShift toward proactive advice and counsel.Keep investing in experienced people and professional development.
2. Legal directs the networkCombine technology and services with trust and relationships.No caution is recorded for this future in the source record.
3. Providers own the infrastructureExplore a combined service or legal services provided as shared infrastructure.Slow adoption and attachment to the status quo.
4. People own the final sayStay agile and differentiate through judgment.The firm’s survival itself.
Consider for your organization · Guide interpretation

What will clients still choose you for when more legal production is automated?

Paraphrased from photographs and a transcript in the source record, dated June 24, 2026.
Recorded proposals / Legal technology

Make the systems work in practice

Features barely appear in these proposals. They turn on access and proof: connect to the customer’s systems, show results the customer can verify, and earn the data access the service depends on. A tool the customer cannot integrate or audit loses to a worse one they can. This is the seat that builds the third future if the other seats let it: every integration deepens the customer’s reliance on systems the provider runs, and these proposals decide whether that reliance stays earned. In horizon terms this seat lives in H2, where every deployment is somebody’s experiment until the results hold up, and the tests it should expect to meet are the in-house seat’s map and the consumer seat’s route of appeal.

Make tools work with customer systems, demonstrate results and help customers introduce and use them. Build the ability to advocate for the sector.

Secure access to the customer data and systems needed to make the service work.

Stay close to how customers use the service. Invest in relationships and a reputation they can trust.

The available record preserves this seat’s overall proposals, but not a complete set of actions and concerns for each future.

Consider for your organization · Guide interpretation

Can customers integrate your tools, see their value and trust how they operate?

Paraphrased from photographs and a transcript in the source record, dated June 24, 2026.
Recorded proposals / Consumers & small businesses

Make access and trust part of the design

This perspective speaks for the people your system will process. Its asks are concrete: affordable help, fair default settings, and a real route to challenge a decision that goes wrong. Companies meet those conditions by design, or meet them later in front of a regulator. Only the fourth future is built around this seat’s central ask, a person who can stop the machine, and even there the record leaves the power contested. That is why these proposals aim at defaults: the seat with the least power inside any single agreement has the most riding on the rules that apply to all of them.

Build support across technology, law and politics for fair treatment, access to help, rights and , including a fair chance to challenge decisions.

Bring separate community and leadership groups together.

Agree on that make legal help easier, faster and cheaper to obtain.

See proposed actions and concerns in each future
Paraphrased from the source record. A concern records a worry, not a forecast.
Possible futureRecorded proposalConcern raised
1. The company builds the systemMake the case that access to legal protections supports economic success.Disruption and public revolt.
2. Legal directs the networkFund shared principles for services that take consumer needs into account.Disruption and public revolt.
3. Providers own the infrastructureBuild due process, fair treatment and transparency into the standard settings of services.Social unrest.
4. People own the final sayReconsider licensing and rules about who may provide legal help.Apathy and alienation.
Consider for your organization · Guide interpretation

Whose experience gets better, and what recourse do people have when the system fails them?

Paraphrased from photographs and a transcript in the source record, dated June 24, 2026.
One concrete proposal / From the in-house record
“Build an override switch in case of failure.”

The in-house record offers this as insurance against failure. Treat it as a test, not a standard: an override exists only if a specific person has the information to see the failure, the skill to judge it and the authority to make the stop hold. Nothing in the record says that standard was agreed, and nothing says one was built.

Source record, June 24, 2026
Decisions still open / Guide interpretation

Proposals need owners, resources and a test of success

The record ends where your work starts: with proposals and no delivery plan. Three questions carry the discussion into your organization.

Who would take responsibility?

A proposal needs someone to lead it, resources to carry it out, and a way to assess whether it helps.

Could a person intervene effectively?

A right to challenge an automated decision depends on usable information, relevant expertise and authority to act.

Whose experience needs to be tested?

No set of proposals written about consumers and small businesses can stand in for them. Their direct participation is how you test the promised benefits and find the needs the proposals missed.

PUT THE IDEAS TO WORK
Test a current decision against the four futures