AI agents, automation, and who's actually in charge

GOVERNANCE

The Digital Omnibus on AI enters into force: the “high-risk” deadline slides to 2027, but saying “you're talking to an AI” is still mandatory from 2 August 2026

Published in the EU Official Journal on 24 July and in force since the 27th, the Digital Omnibus pushes the AI Act's Annex III deadline back to December 2027. What most of the coverage of that delay leaves out: the Article 50 transparency duty — telling users they're talking to an AI — hasn't moved. It's still 2 August 2026.

The Digital Omnibus on AI, published in the EU Official Journal on 24 July 2026 and in force since 27 July, is the first formal amendment package to the AI Act since it was adopted in 2024. Its most-covered change: the application deadline for stand-alone high-risk AI systems (Annex III — employment, education, critical infrastructure, law enforcement) slides by two years and four months, from 2 August 2026 to 2 December 2027; for AI embedded in products already covered by sectoral safety legislation (Annex I), the deadline runs to 2 August 2028. But one point barely shows up in the coverage of that delay: Article 50, which requires informing users they're interacting with an AI system (unless that's obvious from context), is NOT part of it. Law firm Lewis Silkin spells it out in its 27 July analysis: “the remaining transparency obligations under Article 50 [...] continue to apply from 2 August 2026.” Six days from now.

In practice, that covers any small business that's put a chatbot or AI assistant on its site without saying so clearly from the very first exchange. This isn't a legal nicety: from 2 August, a visitor typing to an assistant that passes itself off as human — or that never mentions it's an AI — leaves the business running it exposed. We checked our own case before writing this piece, not after: Chichi, AppH's own front-desk assistant, shows “AppH virtual assistant” as a persistent subtitle the moment the chat window opens, and introduces itself as such explicitly in its very first message, across all 4 site languages — not a line buried in a terms-of-service page nobody reads.

We could have waited until 2 August to check whether Chichi meets Article 50. We did it this week instead, rereading the source code line by line, not trusting a memory of how the widget was built months ago. The gap between “we think we comply” and “we checked” is exactly the kind of gap this delay doesn't excuse. What strikes us about this delay isn't that it gives breathing room to large companies building high-risk systems — it's that it changes NOTHING for a small business that, like most of our customers, never intended to build an employee- or candidate-scoring system in the first place. The real question we ask any customer switching on an AI chatbot on their site hasn't changed, delay or no delay: does the person on the other end know they're talking to a machine, from the first line? If the answer is no, that isn't a compliance box to tick later — it's a lie of omission, and it stays one even without the AI Act.

Reviewed by a human at AppH

MARKET

A NAIC study cited by Forbes confirms it: 71% of small businesses depend on one or two people — the three questions to ask before buying an AI tool, already built into AppManager

The same Forbes article we covered yesterday (70% of AI transformations fail) carries a number closer to our own customers: according to a National Association of Insurance Commissioners study, 71% of small businesses depend on one or two people to keep running. Its advice before buying any AI tool: three questions, not a sales pitch.

The July 28 Forbes article we already covered yesterday (with the 70%-of-AI-transformations-fail number, per BCG) carries a second, less-quoted figure that's closer to our customers' reality: according to a National Association of Insurance Commissioners study, 71% of small businesses depend on one or two people to keep running. That's not a software problem — it's a human dependency no tool, AI or otherwise, fixes on its own. Which is exactly what makes the advice the article attributes to Anthony Godley (founder of Logix BPO, who grew it from one client to 1,000+ employees) useful: before buying any AI tool, ask three questions — who else has decision authority, is success actually defined, and would it work without you. Three questions that take five minutes and stop you from installing a tool nobody else knows how to run.

The article adds a concrete, almost operational recommendation: train at least one employee every month on a critical, undocumented task. That's a cadence, not a one-off project — exactly the kind of discipline most small operations have neither the time nor the instinct to impose on themselves, right when they're adding automation on top of everything else. In AppManager, a new module (Fleet, Tourism, Health) never switches on all at once across an entire operation: it starts on a narrow scope, with every agent action — a message sent, a follow-up, a stock update — requiring an explicit human approval before it executes, module by module, until the team has seen enough decisions go through to widen that scope itself. It's not a compliance checkbox bolted on afterward: it's, literally, an answer to the article's three questions, built into the product instead of left for the SMB to figure out alone.

71% doesn't surprise us: most of our customers are exactly that kind of small operation where one or two people carry everything. That's why we never built AppManager as a tool you install and then let run on its own. Every agent, in every module, waits for an explicit human confirmation before acting on anything with a real consequence — a customer contacted, an invoice sent, stock changed. That's not a technical limitation we're hoping to lift someday — it's a choice, and it stays true even when a customer asks us to move faster. "Would it work without you?" is really the right question to ask about your OWN decision process before adding an agent, not about the agent itself — software can't answer that for the owner. What we can guarantee is that once that answer is found, it keeps getting applied decision after decision, not just on launch day.

Reviewed by a human at AppH

GOVERNANCE

A Fleet survey of 500 IT leaders confirms it: 7 in 10 are racing into AI without the infrastructure foundation that makes it governable — exactly what AppManager builds in from day one

Fleet Device Management's "Road to AI in IT" report, published July 23, puts a number on a gap we already suspected: 46.5% of IT teams rank AI-driven automation as their top priority for the next two years, but only 29.6% are prioritizing infrastructure as code — the foundation that lets you know, after the fact, what an agent did and why.

The headline number is simple and blunt: across more than 500 surveyed IT leaders, 70% are pursuing AI automation without first laying down the infrastructure-as-code that makes it governable. The report spells out what that looks like on the ground: 87% of teams still manage endpoints manually or only partially automated (just 13% call themselves "fully autonomous"), 79% take more than a day to deploy a critical security patch, and 60% don't even have full visibility into their device fleet. Meanwhile, "shadow AI" is quietly piling up: the average enterprise runs 14 AI applications, but IT has real visibility into only 4 of them — and 78% of employees already use personal AI tools at work, outside any oversight. Fleet CIO Allen Houchins puts the risk plainly: "without that foundation, orgs risk chasing AI outcomes without the governance, visibility and controls required to deploy them confidently." Co-founder and CEO Mike McNeil goes further: "infrastructure as code turns AI from a chatbot into a force multiplier for IT teams."

AppH's take: this report says, with enterprise-scale numbers, exactly what we've been telling much smaller SMBs from day one — automation was never the problem; what happens WHEN it gets something wrong is. An IT team that can only see 4 of the 14 AI apps actually running in its company can't govern them or defend them when something goes wrong; an SMB that turns on an agent with no approval log is in that exact same spot, just with even less of a safety net behind it. In AppManager, every agent action with a real consequence — a message sent, a payment collected, a stock change — waits for an explicit human confirmation before it executes, and that confirmation stays reviewable afterward, module by module. That's not a talking point we pull out once a client is already convinced: if a prospect asks us to wire up an agent that acts without leaving that trail, we say no, even when it costs us the sale — that's precisely the foundation this report says is missing for 70% of the IT teams it surveyed.

Reviewed by a human at AppH

MARKET

Forbes and BCG confirm it: 70% of AI transformations fail — almost never because of the technology, because nobody wrote the decisions down

A Forbes piece from July 28 cites the Boston Consulting Group: 70% of enterprise AI transformations fall short of expected results, and the identified cause is organizational culture, not the tool. The starker number — 95% of AI pilot projects produce no measurable return, per MIT — hides a simpler problem: most small businesses never wrote down how they actually make decisions.

According to MIT (Project NANDA), of the $30-40 billion invested in generative AI over the past two years, only 5% of pilot projects produce an identifiable return; a ManpowerGroup/Everest Group study (80 HR leaders, published July 22) found that only 3% of leaders feel genuinely ready to lead an AI-enabled team, and McKinsey reached almost the same conclusion (1% full AI maturity). BCG goes further on the cause: companies that put at least 10% of their AI budget into training and change management are 1.5x more likely to succeed than those that don't. The article finally leans on a first-hand account from Anthony Godley (founder of Logix BPO, who grew it from one client to over 1,000 employees): "the biggest barrier to AI adoption isn't technology, it's founder dependency — if every important decision still comes back to one person, AI only exposes that bottleneck faster." His advice: document every decision and approval first, before even choosing a tool — "AI amplifies operational maturity. It doesn't replace it."

This 95% failure number shouldn't convince anyone to distrust AI — it should convince them to distrust launching AI before writing down how their business actually makes decisions. Our approval panel doesn't do that homework for the owner: it can only log the decisions they already know how to make. If nobody in the business knows who's allowed to approve a refund or a stock order, no software fixes that on day one, ours included. What we can promise is that once that authority is clear, every decision leaves a searchable trail — for a small business caught in the founder dependency Forbes describes, that's already half the fix.

Reviewed by a human at AppH

GOVERNANCE

The World Economic Forum says it plainly: once an AI agent is the one paying, knowing who the customer is stops being enough

Santander and Mastercard just executed Europe's first end-to-end payment initiated by an AI agent inside a regulated banking environment. The WEF's warning: banks no longer just need to verify identity — they need to understand intent, authority and context before money moves.

The piece (Deya Innab, Eastnets) describes the same shift we're already living in business software: agentic AI moving from giving advice to taking action. When what it executes is a payment, the consequence is immediate and hard to reverse. The EU AI Act and the UK's CMA already make clear the business stays accountable for what its agent does — there's no way to hand that accountability off to the software.

AppH's take: we don't move money autonomously and have no near-term plan to — but the WEF's vocabulary ("intent, authority and context," not just identity) is exactly what we're already trying to capture in every approval logged on our panel. The day we build something like an automatic supplier payment or an automatic refund, the first non-negotiable requirement will be the same audit trail Santander and Mastercard already built — not a lighter version of it.

Reviewed by a human at AppH

MARKET

Cisco ships small models that catch 150× more bugs per dollar than GPT-5.5

Antares-350M and Antares-1B, two open models from Cisco focused solely on code vulnerability detection, scanned 500 repositories in 15 minutes for under $1 — the same job took GPT-5.5 five hours and over $100.

Cisco's bet isn't "bigger," it's "more specific": a small model, running locally (sensitive code never leaves the client's server), trained for one task, wins on cost-per-result against a giant general-purpose model.

AppH's take: we're not training our own model just because Cisco did. But if a client needs high-volume recurring monitoring (like the mining fleet case), this confirms it's worth evaluating a small, purpose-built model instead of overpaying for a giant generic one.

Reviewed by a human at AppH

GOVERNANCE

EY: 75% of agentic AI's value is lost between silos — not inside them

Even though 88% of employees already use AI, only 28% of organizations turn that into real business outcomes, per EY. The cause: AI operates within each function, but the real value is in coordinating across functions.

The report is honest about a gap almost nobody solves well: "episodic, not continuous" governance, and poorly defined escalation/exception protocols — even when a company already claims to have "human in the loop."

AppH's take: this report reads almost as a direct critique of how the market uses "human in the loop" without defining real escalation. It obliges us to document, for every client, exactly at which step a human intervenes and what happens if something goes wrong — not just claim it on the website.

Reviewed by a human at AppH

CRITIQUE

"More autonomy doesn't eliminate human work — it concentrates it"

A first-hand account: an autonomous agent (nicknamed "Molty") started self-assigning tasks and even wrote its own reminder cron job. The result wasn't less human work — it was all the work funneled into one reviewer.

The author is candid: reviewing Molty felt more like censoring inappropriate content than giving real feedback. His uncomfortable conclusion — "autonomy doesn't subtract human work, it changes its shape and concentrates it into review" — is exactly the critique a studio like ours, which sells human-in-the-loop, has to be able to answer head-on.

AppH's take: this critique forces us to be honest with ourselves. If our approval panel floods the business owner with mindless clicks, we've failed the same way Molty did — just with better marketing copy. The right answer isn't removing the human, it's designing better what we show them and when.

Reviewed by a human at AppH

MARKET

Forbes tells small businesses: start your AI agents "low," scale up only once they earn your trust — the exact same principle already built into AppManager

In a March 27 piece, Forbes lays out a 5-level "autonomy spectrum" for small businesses: start your first AI agents at levels 2-3 (answering questions, screening leads), and only move to more autonomous levels (like drafting brand content) once the agent has actually proven it can be trusted.

The piece (TerDawn DeBoe, who covers small-business AI strategy and ROI) gives 3 concrete examples: an agent that answers client questions (level 2, easy-to-measure time savings), one that screens incoming leads (level 3, better prioritization), and one that drafts brand-consistent content (level 4, so a new client doesn't have to wait while you're busy with existing ones). Its core advice — don't start at high autonomy because it "sounds more advanced," earn it first — is the same standard we already apply, except in AppManager it isn't just strategic advice: it's built into the approval panel itself, where every agent action (sending a follow-up, marking a purchase order received, approving a draft) waits for a human to confirm it before it executes, no exceptions for anything with a real consequence (a send, a charge, a stock change).

AppH's take: we agree with Forbes' advice almost word for word — not because it's convenient for us to say so, but because we built it this way before reading the piece. The real difference is in the fine print: we don't leave human approval as a best practice the small-business owner has to remember to apply — we put it directly in the product's workflow, with a record of who approved what and when. If you're evaluating your first AI agents, the question we'd suggest asking isn't just "what autonomy level should I start at?" but "where does the record live that a human approved this, and can I see it later?" — that's what separates real control from good intentions.

Reviewed by a human at AppH

MARKET

Anthropic launches Claude for Small Business — and "let it run on its own" is an option, not the default

On May 13, Anthropic unveiled a bundle of connectors and 15 ready-to-run agentic workflows (QuickBooks, PayPal, HubSpot, Canva, Docusign) built for U.S. small businesses: plan payroll, close the month, chase overdue invoices, launch a campaign. Anthropic's own core promise: you approve the plan first — or, once you're ready, let it run end-to-end.

The package doesn't replace the tools a business already uses — it installs on top of them: it inherits whatever permissions each employee already had in QuickBooks or Drive, and doesn't train its models on customer data by default on Team/Enterprise plans. In Anthropic's own survey, half of small-business owners named data security as their single biggest hesitation about AI — the launch is built, item by item, to answer exactly that objection.

AppH's take: hearing Anthropic itself say "you approve the plan before anything sends, posts, or pays" is the strongest validation we could ask for of our own stance — we don't need to convince anyone a human has to stay in the middle, the company that builds the model is now saying it too. The real difference is in one detail worth looking closely at if you're evaluating tools like this: here, "run end-to-end without asking me anything" is an option the owner can switch on. In AppManager, for any action with a real consequence, that door doesn't exist, and we don't offer it as an advanced option either — not because we doubt Anthropic, but because we'd rather not hand a workshop or optical-shop owner the decision of when to let their guard down.

Reviewed by a human at AppH