Skip to content
BOS
{{ navCtaLabel }}
Resources Perspective 3 min read

Does the work continue when the person closes their laptop?

The most important question around agentic AI is not whether the technology works. It is whether the work itself is expected to continue beyond one person.

Martin Gents
Martin Gents
Founder of UseKase and creator of BOS

Built for one, and very good at it

A lot of organizations are still approaching agentic AI from the perspective of individual productivity. That is understandable. The current generation of AI environments is already exceptionally capable for solo operators, builders, researchers and professionals managing their own workflows.

They support research, writing, coding, planning, automation and scheduling at a very high level. They connect to tools and run tasks while you sleep. For one person, that is genuinely transformative.

What changes when the work is shared

The real consideration begins once the work extends beyond one person and starts becoming part of an operational system used by a team, or embedded into an ongoing business process.

That is where persistent, stateful systems become relevant. What changes is that agents are no longer attached to a single user session or a single device. They operate with continuity across workflows, users and time:

  • research continues overnight while teams are offline
  • proposals are prepared as pipeline stages change
  • operational workflows progress across departments
  • agents maintain memory and context across ongoing activity
  • several people collaborate through the same AI operating environment

Most businesses need both

The important distinction is not that one kind of tool is better than the other. In practice, many organizations will need both.

Some workflows are best handled by an individual working with a capable personal tool. Others require systems that remain operational beyond a single user, support shared processes, continue functioning independently of one person's availability, and build organizational intelligence that stays with the business over time.

Some work belongs to a person. The rest has to survive them being offline.

And it has to be governable

This also requires responsible implementation. Operational AI systems need governance, oversight, security and clear human accountability from the beginning, particularly anywhere they touch sensitive systems.

That is not a constraint bolted on at the end. It is a design requirement, and it is why approval, visibility and audit belong in the product rather than in a policy document beside it.

If you are working out where the line sits between a personal tool and an operational system, these are the pages that go further.

Martin Gents
Written by
Martin Gents
Founder of UseKase and creator of BOS. Writes here about running a company as one system, from doing it at UseKase first.