The augmented expert: agentic platforms must be built around people

At Junyr, we support SMEs and a few large companies in their AI transformation, and the value we see comes from an expert who delegates the preparation to agents, then corrects, completes and signs. The platforms on the market were mostly designed for something else: replacing a process, or staffing an organisation chart with virtual employees.

• AI still falls short of a professional on most expert work, which leaves the human at the centre of the deliverable.
• The human’s contribution is judgement on the agents’ reports, and a review only holds if the interface is designed for it.
• A benchmark of eleven platforms from nine vendors, as documented on 29 October 2026, shows the same blind spot.
• Junyr’s approach starts from the opposite end: a shared space where agents take the repetitive work and people keep the decisions.

AI still falls short of the professional

The most direct measure of AI against human experts in 2026 compares complete deliverables, and on that measure the best model matches or beats a professional on about one project in five.

• The Remote Labor Index, run by Scale AI and the Center for AI Safety, draws 240 projects “sourced directly from experienced freelance professionals” [1]. Its automation rate is “the percentage of projects where an AI’s deliverable is judged at least as good as the human standard”.
• On the leaderboard read on 29 October 2026, Claude Opus 5.5 leads with 21.25%, ahead of GPT-6 Astra at 20.83% and Claude Fable 5.1 at 17.92% (see Figure 1).
• Progress is real. In July, the Center for AI Safety wrote that the frontier had “more than quadrupled in under eight months”, while adding: “Today’s AIs still fall short of professional quality on most projects” [2].
• Automated scoring flatters the models. The same post reports that GPT-5.5 scored 6.25% when rated by humans and 17.9% when rated by an automated judge calibrated on earlier models [2].

The rate has quadrupled, and four projects in five still need the professional. We drew the same conclusion from Andon Labs’ AI-run shop in our article on agentic ROI: a good operations manager, not yet a CEO.

Fast progress, same verdict.

The report is a draft; the signature is the expert’s

An agent can produce a report in minutes, but the expert’s contribution begins where the report ends: knowing what matters to this client, what the sources do not say and what the firm is prepared to stand behind.

• Context: the agent knows what it was given. The expert knows the client’s history, the unwritten constraint and the question behind the question.
• Judgement: choosing what to keep, what to cut and what to recommend is the work the client pays for.
• Accountability: a deliverable engages whoever signs it, and a model signs nothing.

That contribution does not happen on its own. Three studies published this year show how quickly a review turns into a rubber stamp when nothing in the work is designed for it.

• In a preregistered experiment with 1,339 teachers in Greece, all grading the same exercise, a harsh grade labelled as AI-generated left an unfairness gap “22% larger” than the same grade labelled as human. “Deference was strongest among younger, highly educated, and tech-confident teachers” [3].
• A review of AI in clinical reasoning, published on 21 October 2026, warns that a “human in the loop” requirement “can be satisfied by countersigning a recommendation without examining it” [4].
• Researchers at the BCG Henderson Institute, writing in the Harvard Business Review, found that when AI was framed as an employee, “managers identified 18% fewer errors” and individual accountability for errors dropped by 9 percentage points. Their recommendation: “redesign workflows to pair AI-generated output with human judgment” [5].

At Junyr, we apply a simple rule to every document that leaves for a client. It opens with the expert’s view: one or two sentences written by a person on the team and signed with their first name. The AI never drafts it, and a document without it is not sent.

The signature is the method.

Eleven platforms, one blind spot

We read the documentation and announcements of eleven agentic platforms from nine vendors, as published on 29 October 2026, with three questions: who the platform is built for, what its unit of design is, and where the human comes in.

Platform	Built for	Unit of design	Where the human comes in
Claude (desktop, with Cowork merged in)	One person	The user’s task or conversation	”By default, Claude asks before taking an action”; documents co-written with Claude and shared by link [6]
ChatGPT Work	One person	The user’s multi-step task	The user can “approve important actions” and “change direction” during a task [7]
Microsoft Foundry	Developers [8]	The agent and its code, workflows included [9]	Approval returned by code; “implement your own approval UX and policy” [10]
Microsoft Agent 365 (Foundry autopilots)	IT, with an administrator’s approval	An agent “under its own identity”, in the organisation chart	The person who hires the instance “becomes its manager” [11]
Microsoft Copilot Studio	Makers	The agent and its tools	Approve, approve for the session or deny a tool call, inline in Teams; in development in September 2026 [12]
Salesforce Agentforce	Business users and IT	Agents with first names and jobs	Shared Slack threads on live data; no approval step described in the Dreamforce 2026 coverage [13]
ServiceNow	Process owners	”Role-scoped AI specialists”, end-to-end processes	A named supervisor answers, approves next steps or cancels [14] [15]
Google Gemini Enterprise	Knowledge workers and builders	The workflow	”Request info” and “Approval” steps; the run shows “Needs Review” [16]
Amazon Quick	Business users	A personal assistant and its agents	Autonomy from “step-by-step approval to broad goal-based execution”, approvals in a personal feed [17]
UiPath	Process owners	The orchestrated process	Human-in-the-loop tasks handled in Action Center [18]
Workday	Employees and managers	Agents by function	”If approval is needed, Sana gathers the context first and gives the manager a clear recommendation” [19]

The table separates three families, and none of them was designed around the expert who works alongside the agents (see Figure 2).

• Personal assistants, Claude, ChatGPT Work and Amazon Quick, are built for one person and their assistant. They ask before acting, which is good practice, but the space belongs to one user: we found no documentation of several people and several agents working on the same deliverable.
• Agent factories, led by Microsoft, are built for developers and IT. The human layer is either code that a developer must write, or an agent that copies the organisation chart.
• Process platforms, ServiceNow, Agentforce, UiPath, Workday and the workflows of Gemini Enterprise, start from the process and staff it with agents. The human becomes a step that approves, answers or cancels.

The transposition of the human organisation is written into the products themselves.

• Microsoft’s quickstart creates each autopilot from a template whose identifier is digitalWorkerTemplate. Once hired, the agent “appears in your organization chart” and its creator “becomes its manager” [11].
• ServiceNow’s announcement of its “Autonomous Workforce” describes AI specialists that “deliver outcomes from start to finish, without human intervention”. In HR, “each acts as a digital employee” [14].
• Salesforce introduced at Dreamforce 2026 agents named after jobs: Casey for customer service, Paige for IT and HR, Piper for lead qualification, Hunter for outbound sales [13].
• This is precisely the framing that the BCG Henderson Institute study associates with fewer errors caught [5].

Credit where it is due: most of these platforms now give business users an approval surface. ServiceNow names the supervisor of each agentic workflow and labels the fields modified by AI [15], Google pauses a workflow for review [16], and UiPath made human-in-the-loop tasks generally available in September [18].

What remains rare is everything that happens after the approval button.

• Revising the deliverable itself, rather than approving or rejecting it.
• A shared space where several people and agents work on the same objects: the file, the quote, the email thread.
• Corrections that feed the agent’s next round of work.
• The expert’s signature on what leaves the company.

In the documentation we read, none of the eleven platforms describes the last two. The absence is documentary: a feature may exist without being documented, and we will correct this benchmark if a vendor shows otherwise.

Microsoft Foundry: a factory without a window

Microsoft Foundry deserves a closer look, because its own documentation shows plainly that a business user has no place in it.

• Microsoft presents it as “a trusted platform that empowers developers to build AI agents, models, and apps”. Its promised oversight is aimed at the same audience: “Trace and evaluate agents and models, and monitor them with built-in dashboards (preview)” [8].
• Its human-in-the-loop pattern lived in a visual workflow builder reserved for users with the Contributor role or higher on the project. That builder is going away: “Microsoft Foundry is retiring workflows on December 1, 2026”, and “Foundry is moving workflow authoring to a code-first model” [9].
• When an agent must ask before calling a tool, Foundry returns an approval request to the calling program. The sample code says it in a comment: “In production, implement your own approval UX and policy” [10].
• Creating an autopilot requires Azure CLI, the Azure Developer CLI and Docker, then a Global Administrator or AI Administrator to approve the blueprint [11].

Foundry is a good factory for those who build agents. An accountant, a salesperson or a consultant who must supervise an agent, correct its draft and decide what goes out finds no screen designed for that work. Microsoft sends them to Teams and Microsoft 365 Copilot, where approving an agent’s tool call was still listed as “In development” on 1 September 2026 [12].

What a human-centred platform must offer

A platform built around people starts from the work that people do together and gives agents a place in it, which changes the interface more than the models.

• Shared work objects. People and agents act on the same file, quote or thread, so that nobody has to copy a chat answer into the real tool. We developed this point in our article on the AI work interface.
• A review surface. The expert sees what the agent did, from which sources, and what it changed, the way ServiceNow labels AI-modified fields [15].
• Correction as a gesture. Editing, annotating and sending the work back with an instruction count as much as approving it.
• Autonomy set action by action. A draft tolerates more freedom than a payment, as detailed in our article on human-in-the-loop systems.
• A team space. Several people see the same agents and the same work, with roles that everyone understands.

The case for the team space comes from Microsoft’s own research. In its Work Trend Index of May 2026, based on 20,000 AI users in ten countries, organisational factors “account for more than 2x” the perceived impact of AI compared with individual ones: 67% against 32% [20].

• The “Frontier Professionals”, 16% of AI users surveyed, work in teams that “discuss quality standards for AI-assisted work (54% vs. 29%)” [20].
• In their teams, agent workflows, “human handoffs, and quality standards are documented and repeatable” more often: 26% against 19% [20].
• The practices that make AI pay are collective. A tool built for one user, or for one developer, cannot carry them.

Junyr’s approach: agents for the repetitive, people for judgement

Junyr is building the opposite of a virtual organisation chart: agents take on the repetitive preparation that fills a working day, and people keep judgement, decisions and signatures, in one workspace where both meet (see Figure 3).

• Agents prepare. Overnight, they summarise email threads, suggest up to three actions per thread and assemble a morning briefing of stalled projects, dormant relations and weak signals [21].
• People decide. An assistant drafts the reply and the email stays a draft: sending is a human gesture. An agent works on a plan that a person approved, and the AI can submit but never approve [21].
• The same objects for both. Each document exists in a version written for people and a structured version for agents, and agents appear in the team roster, labelled as such [21].
• A rule above the tools. Junyr’s charter states that every commitment to a client or a supplier is validated by a person [21].
• A platform the company owns, hosted on its premises with the models it chose, for the reasons set out in our article on agentic ROI.

The relief is real but should be stated carefully. The 2026 research we reviewed in our article on mental load shows a lower perceived effort more clearly than measured time savings, and we do not claim a return that our assignments have not measured.

The path does not change either. Equip people first, let them imagine the company of tomorrow, then give agents objectives on a platform the company controls, with a human checkpoint before anything binding, as in decision-gated development.

The last word belongs to whoever signs

The question to ask an agentic platform is where your best expert sits when the agents have finished, and what they can do there.

• If the answer is “in a developer’s code”, the platform was built for the factory.
• If the answer is “in front of an approve button”, it was built for the process.
• If the answer is “in a space shared with the team, where they read, correct and sign”, it was built for people.

AI will keep progressing, and the share of projects it completes alone will grow. The client will still want to know who stands behind the deliverable.

The benchmark reflects vendor documentation and announcements read on 29 October 2026; a feature may exist without being documented, and several of the features cited are in preview or in development. The Remote Labor Index measures freelance projects with no confidence interval published, and the studies on human review were conducted with teachers, clinicians and managers in specific settings. The description of Junyr’s features comes from the company’s internal specification of September 2026; the relief of repetitive work is a field observation, not a measured return.

Sources

1. Scale AI and Center for AI Safety, Remote Labor Index leaderboard, automation rate on real freelance projects, read on 29 October 2026.
2. Mantas Mazeika, A Significant Increase in Digital Labor Automation, Center for AI Safety, 1 July 2026.
3. Sofoklis Goulas, Rigissa Megalokonomou and Panagiotis Sotirakopoulos, ‘Why do experts miss AI’s errors? Evidence from a randomized labeling experiment’, PNAS Nexus, doi:10.1093/pnasnexus/pgag146, 9 June 2026.
4. José Daniel Sánchez, ‘Augmentation or erosion? Artificial intelligence and the transformation of clinical reasoning: a critical narrative review’, Frontiers in Digital Health, vol. 8, 21 October 2026.
5. Matthew Kropp, Julie Bedard, Megan Hsu and Lisa Krayer, ‘Research: Why You Shouldn’t Treat AI Agents Like Employees’, Harvard Business Review, study of more than 1,200 managers, 6 May 2026, read on BCG’s site.
6. Anthropic, Claude Cowork and chat are now one Claude, Claude blog, 16 September 2026, updated 23 October 2026.
7. OpenAI, Get started with ChatGPT Work, ChatGPT documentation, read on 29 October 2026.
8. Microsoft, What is Microsoft Foundry?, Microsoft Learn, 13 August 2026, updated 24 September 2026.
9. Microsoft, Build a workflow in Microsoft Foundry (Preview), Microsoft Learn, 31 July 2026, updated 19 October 2026.
10. Microsoft, Connect agents to MCP server endpoints, Microsoft Learn, 28 October 2026.
11. Microsoft, Quickstart: Build your first autopilot, Microsoft Learn, 26 August 2026, updated 23 September 2026.
12. Microsoft 365 Message Center, RM570434, Microsoft Copilot Studio: Enabling makers to require human approval for tool calls, status “In development”, 1 September 2026, read on the mc.merill.net archive.
13. Salesforce Ben, Biggest Dreamforce ‘26 Announcements: Everything in a Nutshell, 25 September 2026.
14. ServiceNow, ServiceNow brings Autonomous Workforce to every major business function, press release, 5 May 2026.
15. ServiceNow, In-product agentic AI, product documentation, Brazil release, updated 10 September 2026.
16. Google Cloud, Use human-in-the-loop steps, Gemini Enterprise documentation, updated 28 October 2026.
17. Amazon Web Services, Amazon Quick, What’s New, 17 June 2026.
18. UiPath, Action Center release notes, September 2026, entry of 16 September 2026.
19. Workday, Workday to Bring Sana Everywhere Employees Work, Including Claude, Gemini Enterprise, Microsoft Copilot, Microsoft Teams, and Slack, press release, 13 October 2026.
20. Microsoft and LinkedIn, Agents, human agency, and the opportunity for every organization, Work Trend Index 2026, survey of 20,000 AI users in ten countries, 5 May 2026.
21. Junyr, company charter (updated 12 September 2026) and internal specification of the Junyr Suite building blocks (11 and 12 September 2026), internal documents, not public.