The no-middleware angle
Business process automation consulting ships you middleware. Clone's Computer Agent has none.
A BPA consulting engagement ends with an artifact you now own: a UiPath .xaml workflow, a Power Automate flow, a dozen Zaps, or a small Node service gluing APIs together. Clone's architecture.tsx declares a layer literally named “Clone Computer Agent” whose sublabel is “Reads the screen, clicks, types, scrolls.” The app's own UI is the runtime surface. There is no middleware to host, maintain, renew, or repair.
What every BPA consulting engagement ships that Clone does not
Ten flavors of middleware. None in Clone's architecture.
Every artifact in the marquee is something a consultant hands you at engagement close. You now host, license, and repair it. Clone produces none of them.
The anchor fact of this page
One layer.
Reads the screen, clicks, types, scrolls.
Open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx and scroll to the layers const at line 5. There are six objects. The third (lines 17 to 23) has label “Clone Computer Agent” and, on line 20, the sublabel “Reads the screen, clicks, types, scrolls.” It is the only layer in the list whose sublabel is a list of physical UI actions.
A BPA consulting engagement produces a middleware artifact that sits between your plain-English intent and your apps. Clone replaces that middleware with the Computer Agent layer above. Every middleware-specific cost line item becomes a no-op: no Orchestrator tenant, no premium connector license, no task-quota plan, no annual maintenance retainer, no vendor lock-in. The integration surface is the app's own UI.
Four numbers, each grep-able in the source
Zero middleware. One pixel-level layer. Six total. $49 flat.
0 is the count of middleware artifacts. 1 is the Computer Agent layer in architecture.tsx. 6 is the total layer count. 49 is in pricing.tsx line 9.
middleware artifacts produced. No .xaml, no Zap, no flow definition lives in your tenant
layer of architecture.tsx (line 20) whose sublabel is 'Reads the screen, clicks, types, scrolls'
total layers in architecture.tsx. Two are yours, three are Clone, one is the apps you already run
flat dollars per month. Replaces task-quota plans, per-seat connector fees, annual maintenance contracts
Two Phase-3 deliverables, side by side
A middleware artifact you now own, or the Computer Agent. Pick one.
Toggle to see the two shapes. Both deliver the same business outcome. Only one of them requires a hosted runtime, a license stack, and a maintenance retainer.
BPA CONSULTING — PHASE 3 IMPLEMENTATION Deliverable: automation middleware, you own it. Vendor tooling varies by engagement. Scenario A UiPath • One or more .xaml workflow files • Orchestrator tenant configuration • Robot license(s) for runtime • Annual maintenance ≈ 20% of build Scenario B Microsoft Power Automate • Flow definitions in your tenant • Premium connector licenses per user • Per-seat cost from $15/user/mo and up • Flow breaks when a connector updates Scenario C Zapier + Make.com • A dozen Zaps per business process • Task-quota plan scaled to monthly volume • Multi-step Zaps at $49-$599/mo • Zaps re-author when the source app's API schema changes (quarterly, on average) Scenario D Custom API glue • A small Node service in your AWS • CI/CD pipeline and alerting to own • The consultant's Phase 5 is the handoff • Every tool without a public API is excluded from scope at this gate. Every scenario produces a wiring layer that lives between your intent and your apps. The consultant configured it; you pay to host and maintain it from this month forward.
- Vendor tool: UiPath, Power Automate, Zapier, or custom
- You host and license the middleware from here on
- Maintenance retainer ≈ 15-20% of build, annual
- Scope excludes any tool with no public API
From plain English to the app's own UI
Three Clone layers. Five apps. Zero middleware in between.
Left: your intent and the two Clone layers that plan against it. Center: the Computer Agent. Right: the apps, touched through their own windows. There is no other layer in this picture. A BPA consulting runtime would have inserted a workflow engine, a connector library, and a scheduler between center and right.
Clone runtime: intent to app, no middleware in the path
What the Computer Agent prints when it runs
Sixteen log lines. Ten invoices. One Gmail queue. Zero API calls.
This is the shape of a Monday invoicing ritual as the Clone daemon writes it to the action log. Every line is a screen read, a click, a typed string, or a verify step. No line says “invoked QuickBooks API”. No line says “authenticated via OAuth connector”. The app saw a user.
The Computer Agent loop, stage by stage
Read. Plan. Click. Verify. Write to memory. Repeat.
A BPA consultant's implementation document describes a workflow by listing tool-specific nodes (UiPath activities, Power Automate connectors, Zapier steps). The Clone runtime describes every task as the same six-stage loop, independent of which app is being driven. The loop is the runtime; the apps are the surface.
Read the screen
Clone's Computer Agent runs a vision model against your monitor. It sees a QuickBooks window the way a junior employee does: a toolbar, a dashboard grid, a 'Create Invoice' button with specific screen coordinates at the current resolution. The read is local and runs on your Mac.
Plan against what is on screen
The Planner (architecture.tsx line 13) maps your plain English request onto the on-screen affordances. It does not consult a workflow YAML or an RPA recording. It picks the 'New Invoice' button because that button is the on-screen affordance that matches the request 'invoice the Acme retainer'.
Click, type, scroll at the OS level
architecture.tsx line 20 spells out the exact verbs the Computer Agent uses. No fake keyboard synthesis, no JavaScript injected into a browser, no driver required beyond the operating system's accessibility APIs. The click lands at (412, 188). The keystrokes land in the 'Customer' field. The app sees a user.
Read the result, verify, move on
After each action the Agent re-reads the screen to confirm the modal opened, the field was accepted, the save button flashed. If the UI changed, the Planner re-plans; the Agent narrates the recovery in the chat and asks for your judgment call on any ambiguity. A RPA bot would have thrown a 'selector not found'.
Write the result to Memory
architecture.tsx line 26 declares the Memory layer with the sublabel 'Your clients, voice, templates, history'. After the invoice save, Memory records the invoice number, client, date, and amount. The next run reuses 'Memory: acme.retainer_rate = $5,000' without asking. No database to provision.
Never touched a middleware artifact
Compare the trail a BPA consulting implementation leaves in your tenant: a .xaml file in a UiPath workspace, a flow definition in a Power Automate environment, a Zap in a Zapier org. Clone's trail is a ritual markdown file at ~/.clone/memory/rituals/ and an action log in ~/.clone/logs/. Nothing in your SaaS tenants.
Six things that break middleware. None break Clone.
The tail cost of a Phase 3 deliverable is a year of maintenance.
Middleware vendors sell implementation and maintenance as separate line items because the two costs are real and distinct. The maintenance line exists precisely because APIs drift, connectors deprecate, and tenants rotate credentials. Each of the six cards below is a common trigger for middleware repair. The Computer Agent sidesteps each.
The app's API changed overnight
Zapier and Power Automate Zaps that depend on the old schema begin failing at 02:00 in their timezone. An ops engineer spends a morning mapping the new fields. A RPA bot on selectors may still work if the DOM has not changed. Clone reads the screen; the button is still where it was; no intervention.
A connector license was not renewed
Power Automate premium connectors are per-user. A billing hiccup takes the flow offline. Clone does not use connectors; it does not have a license surface to let lapse.
The workflow designer retired the old node
UiPath 2024.10 deprecated the legacy Excel activity. Consulting firms rewrote bots for clients. Clone never imported the activity in the first place.
The app has no public API
comparison.tsx row 'Works with custom or legacy apps': Clone has the check, Zapier and HoneyBook both have x. Clone works by clicking; the app does not need to publish an integration surface.
The tenant admin revoked the bot account
RPA bots and Zaps often run as a service account. When the CISO rotates service credentials, the integration breaks. Clone runs as you, from your Mac. There is no service account to rotate.
The consultant finished Phase 5 and moved on
At engagement end, the runbook and the middleware are handed to an internal operator to maintain. Clone has no middleware to hand off, so there is no Phase 5. The consultant is just a coach now.
“The Power Automate flow broke three times last quarter when the CRM upgraded. Clone just clicked the new button.”
Boutique consulting ops lead, 2026, one month after replacing a Power Automate stack with Clone
Eight rows where middleware exists and Clone does not need it
Consulting Phase 3 versus Clone runtime.
Each row is a real line item on a typical BPA consulting SOW. Clone either removes the line outright or collapses it into a runtime behavior you do not pay for separately.
| Feature | BPA consulting Phase 3 | Clone Computer Agent |
|---|---|---|
| Primary deliverable | A middleware artifact (UiPath .xaml, Power Automate flow, Zapier Zap, custom API layer) that sits between your intent and your apps. You now own, host, and maintain it. | A ritual markdown file at ~/.clone/memory/rituals/ and the Computer Agent that reads it. Zero middleware in any of your SaaS tenants. |
| How it reaches the tool | Via the tool's public API or a pre-built connector. Requires the tool to publish an integration surface and requires the consultant to configure auth, rate limits, and field mappings. | Via the tool's own GUI, driven at the pixel level by the Computer Agent (architecture.tsx line 20: 'Reads the screen, clicks, types, scrolls'). The app cannot tell Clone apart from a human user. |
| What happens when the tool's API changes | Connector breaks. Flow throws a schema validation error. Engagement requires a change order. Zaps need re-authoring. Implementation firms offer 'managed services' retainers for exactly this problem, typically priced as 20% of the original build. | Nothing changes. The button is still in the same place; Clone still clicks it. The API surface is not part of the runtime path, so it cannot break the runtime path. |
| Works with tools that have no API | Excluded from scope at Phase 1 gate. If the target is a legacy desktop ERP or a bespoke in-house tool with no integration layer, the consultant proposes a custom API wrapper or excludes the tool. | In scope by default. comparison.tsx lists 'Works with custom or legacy apps' as a check for Clone; both Zapier and HoneyBook have an x. The legacy ERP and the bespoke tool get driven the same way QuickBooks does. |
| Change order cost for a new step | A change request. Scoped, quoted, approved, built, regression-tested, deployed. Billable days range from half a day for a small Zap edit to weeks for a UiPath workflow. Consultant or internal engineer time applies either way. | Edit the ritual markdown, or just tell Clone what you want in the chat. There is no middleware deployment step because there is no middleware. |
| Hosting and infrastructure | UiPath Orchestrator tenants. Power Automate per-user licenses. Zapier task-quota plans. A Node service in AWS if the consultant chose the custom-glue scenario. Each one is a bill and an oncall responsibility. | Runs on your Mac. No hosted runtime to provision. The Memory layer is a folder on your disk; the action log is a file in your home directory. There is no SaaS bill or VPC to maintain. |
| Credential and access posture | Service accounts or API tokens configured per integration. Rotating credentials breaks the bot; CISO review is required for every new connector. | Clone uses your own logged-in sessions. If you can reach the app in your browser, so can Clone. Rotating your password rotates the bot's access too; no service account sprawl. |
| Price posture over 12 months | Implementation $16K to $250K (industry median cited in the DNAGrowth and First Page Sage surveys), then 15% to 20% annual maintenance, plus per-bot or per-seat runtime licenses (UiPath, Power Automate, Zapier). | $49 a month flat, $588 a year, no additional runtime license. Replaces the maintenance retainer outright because there is no middleware artifact to maintain. |
Who this changes the math for
Six reader profiles. Six specific BPA middleware bills.
The economics of middleware vary by platform, firm size, and regulatory regime. Below are the six buckets where removing the middleware layer changes the budget math most.
The firm that got quoted UiPath at $180K for year one
The SOW breaks out Orchestrator licenses, robot licenses, implementation days, and Year 1 managed services. Before signing, audit what the bots would actually do: open an app, click a button, type a string. Clone's Computer Agent does those three verbs as a product feature at $49/mo. If the bots are just driving existing apps, UiPath's licensing stack is paid middleware you do not need.
The ops lead whose Zaps break every quarter
You own 42 Zaps. Each Zap has a task-quota cost, and each quarter at least three break when an upstream tool bumps its API. The tail cost of maintaining this wiring layer exceeds the initial build cost within a year. Clone executes the same work with no API in the loop.
The CFO paying an annual maintenance retainer
Your RPA vendor charges ~20% of the original implementation as an annual maintenance retainer. That line item is there precisely because middleware breaks. Remove the middleware and the retainer becomes optional.
The solo consultant evaluating a Phase 3 proposal
Phase 3 in most BPA engagements is implementation: the consultant configures the middleware in your tenant. Clone's position is that Phase 3 does not need to exist as a deliverable category. The same business outcome ships with no middleware handoff.
The compliance officer auditing who has access to what
Every configured integration creates a new identity surface: a service account, a connector token, a webhook secret. Clone runs as you and leaves no new identity artifacts behind. The action log (~/.clone/logs/) records who did what and when without creating a new principal.
The CTO who still wants a BPMN map
A process map is a human-readable description of a process, and it is still useful for onboarding staff. Clone renders one from any ritual file on demand. The difference is that the map is a view; in BPA consulting, the map is often the deliverable.
Stop buying middleware. Start running apps.
Bring your BPA consulting proposal. We run the same work with zero middleware.
Send the scope your consultant quoted for. On a 30-minute call we point Clone at the same set of tools, watch the Computer Agent drive them end to end, and hand you the ritual file. If the output matches what Phase 3 implementation would have delivered, the middleware line item is a bill the product category has removed.
Book a 30-minute no-middleware auditZero middleware between your apps. See the Computer Agent read a screen.
Twenty minutes together. We drive one of your own tools, no API, no connector, no integration layer, just the pixels the Computer Agent already reads.
BPA consulting, middleware, and the Computer Agent
What is business process automation consulting, specifically?
It is a category of IT consulting where an external firm diagnoses a manual business process, maps it (typically as a BPMN 2.0 swimlane), picks a runtime platform (UiPath, Microsoft Power Automate, Blue Prism, Zapier, Make.com, or a custom API layer), configures the automation in the chosen platform, hands it to an internal operator, and maintains it under a managed-services retainer. Engagements are multi-phase (discovery, design, implementation, test, go-live, hypercare) and priced in the $16K to $250K range for a single workflow per the DNAGrowth and First Page Sage 2026 surveys. The artifact the client ends up owning is a configured middleware object: a robot workspace, a flow definition, a set of Zaps, or a bespoke integration service.
What is the single biggest gap between that deliverable and Clone?
Clone's architecture has no middleware layer. Open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx and read lines 5-42. There are six declared layers: You, Clone Planner, Clone Computer Agent, Clone Memory, Your Apps, Your Business. The Clone Computer Agent (line 19, sublabel on line 20) is the only layer whose sublabel is a list of physical UI actions: 'Reads the screen, clicks, types, scrolls'. It is the layer that makes middleware unnecessary because it uses the app's own GUI as the integration surface.
Does 'no middleware' really hold when the work is non-trivial?
Yes, for the overwhelming majority of small-firm consulting back-office processes. The work Clone routinely does on solo and boutique engagements is: pull last week's billable hours from Timely, draft invoices in QuickBooks, email them from Gmail, log outreach in HubSpot, draft a Friday retro in Notion. Five apps. Every one of them has a GUI that a human operates every day. Clone operates the same GUIs. For edge cases that truly require a middleware object (a long-running scheduled data pipeline, for example, or a multi-million-row ETL), you still reach for a data platform. BPA consulting scope has been overloaded into territory that is really just 'operate these five apps on a schedule', and that territory is exactly where Clone's Computer Agent removes the middleware need.
What is the anchor fact I can verify in the repo?
Open /Users/matthewdi/ai-for-consultants/website/src/components/architecture.tsx. Find the layers const at line 5. The third object (line 17) has label 'Clone Computer Agent' and the sublabel 'Reads the screen, clicks, types, scrolls' on line 20. Then open /Users/matthewdi/ai-for-consultants/website/src/components/comparison.tsx and find the row 'Works with custom or legacy apps' near line 29. Clone has a check; Zapier has an x; HoneyBook has an x; Virtual VA has a check. Those two files are the anchor: one declares the Computer Agent layer; the other shows it is the only automation vendor in the lineup that works with apps that have no integration surface.
How does Clone handle apps whose API does not exist or changed?
The API is not on the runtime path at all. When you say 'log the call into HubSpot', the Planner (architecture.tsx line 13) picks HubSpot as the target, the Computer Agent opens your HubSpot tab, locates the 'Log activity' button on screen, clicks it, and fills in the fields. If HubSpot released a new UI the next morning, the button is still a button with a visible label; the Agent locates it again. If an integration vendor had wired a REST call, the REST schema change would break the integration until a human re-authored it. This is why the 'Works with custom or legacy apps' row on comparison.tsx only checks for Clone.
What does a BPA consulting engagement typically quote for the work Clone does?
The SERP surveys for April 2026 put a single-workflow engagement at $16K to $250K, weighted heavily by the implementation phase. Maintenance retainers run 15 to 20 percent of implementation per year. A typical consulting workflow around invoicing, follow-ups, and reporting maps to a Power Automate flow or a small UiPath unattended bot; the hosted runtime adds a separate per-user or per-bot fee. Clone replaces the entire stack at $49 a month flat on the Solo tier.
If Clone has no middleware, what does Clone actually write to disk?
Two things. A ritual markdown file at ~/.clone/memory/rituals/NAME.md, which is a plain-English record of an intent Clone has seen you save. And an action log at ~/.clone/logs/YYYY-MM-DD.jsonl, one line per click, type, or scroll the Computer Agent performed. Neither of those lives inside a SaaS tenant. There is no UiPath Orchestrator counterpart and no Power Automate environment counterpart; the runtime is a daemon on your Mac.
Is the Computer Agent the same thing as an RPA recorder?
No. An RPA recorder captures fixed selectors (element IDs, XPath expressions, OCR template matches) that the bot replays at runtime. When the selector changes, the recording breaks. The Computer Agent runs a vision and reasoning model against the live screen at every step, so the 'Create Invoice' button is re-located at runtime, not captured at record time. Architecturally this means a UI update does not need a bot re-recording. That is the same reason comparison.tsx shows 'Works with custom or legacy apps' as a check for Clone and an x for Zapier: the Agent does not bind to a stable integration shape.
Does this replace the consultant entirely or only the implementation?
It replaces the implementation deliverable (the middleware) and the maintenance retainer (which exists because middleware breaks). A consultant is still valuable for the parts of a BPA engagement that are strategy work: picking which processes deserve automation in the first place, negotiating stakeholder buy-in, writing the compliance documentation for a regulated industry, designing the exception-handling logic. What the consultant does not need to do is author and maintain the middleware object, because there is no middleware object to author.
How is this different from Zapier, Make, and UiPath specifically?
Zapier and Make are trigger-action platforms that consume tool APIs. UiPath is an RPA platform that uses recorded selectors at runtime. All three require a middleware artifact that you now own. Clone is a computer-use system: a vision model reads the screen, a reasoning model plans the next action, an OS-level driver executes the click or keystroke. The architectural consequence is that the app sees Clone as a user, not as an integration. The comparison.tsx file in the repo has the full table; the pricing row at the bottom shows Clone at $49/mo, Zapier at $49-$599/mo, Virtual VA at $3K-$6K/mo.
What is the minimal proof I can run in an hour?
Install Clone, type into the chat: 'draft an invoice for Acme for $5,000 in QuickBooks, then email it from Gmail'. Watch the Computer Agent open QuickBooks, click Create Invoice, type the client, select the retainer template, save the draft, switch to Gmail, compose the email, attach the invoice, and queue it for your review. No API key was ever configured. No Zapier task was consumed. No UiPath bot was triggered. That is the no-middleware deliverable. If it works, the UiPath or Power Automate proposal in your inbox is a middleware bill that the product category has now priced out.
Where does a BPA consulting firm still earn its fee?
In three places. First, on process selection: deciding which of your twenty back-office rituals is worth turning into a ritual file at all. Second, on regulated-industry compliance: authoring the audit trail documentation, the legal sign-off, the HIPAA or SOC 2 context that goes alongside. Third, on change management: getting partners and operators to trust an automation enough to let it run unattended. None of those three line items require the consultant to produce middleware. The engagement shape stays; the implementation line goes away.
Keep reading
Adjacent angles on the BPA consulting category
Business Process Automation Consultant: Discovery Runs Over Your Last 12 Emails
The Phase 1 discovery angle: how Clone's step-03 pattern mining collapses a two-to-four week discovery phase into a four-second local read.
Business Process Automation Consultants Hand You a Runbook. Clone Ships a Cron Entry.
The Phase 4 runbook angle: why a PDF a human follows becomes a ritual markdown file a Planner executes on Monday at 08:00.
AI Automation Consulting Bills for Discovery. Clone Reads the Sent Folder.
The observation-over-elicitation angle: what happens when the behavior log becomes the discovery sample.
Zero middleware. One Computer Agent. $49/mo flat.
Book a call