A business process automation solution, scored on one question: Day 1.

A single question you ask every vendor you evaluate. On the first business day after purchase, can your team produce one real client-facing artifact using the solution against the exact stack you already have (including apps without a public API, and custom or legacy software)? If the honest answer is no, the solution is not a Day 1 solution. Most enterprise BPA platforms, including Appian, Pega, Nintex, Kissflow, IBM BPM, and UiPath, fail this test by design because their first step is connector or modeling work, not work.

Because the integration layer is a computer agent instead of a connector catalog. src/components/architecture.tsx names this layer: 'Clone Computer Agent, reads the screen, clicks, types, scrolls'. The agent operates the same apps you already use on screen, which means there is no integration gap for apps without an API (QuickBooks Desktop, Filemaker, most law-practice billing tabs) and no separate connector step to complete before the first run. The solution can start producing drafts in the first working hour.

Correct, in the traditional sense. There is no integrations marketplace, no OAuth flow per vendor, no tier that unlocks more connectors. The integration surface is whatever is visible on your screen. When a client switches from QuickBooks to FreshBooks, the change for Clone is a one-line edit in a markdown ritual file. The change for a traditional BPA solution is a new connector request, a re-auth, a remap of fields, and a regression test.

None of them produce a client-facing artifact on Day 1. Appian Day 1 is a scoping session plus a BPMN workshop. Pega Day 1 is a case-type design workshop. Kissflow Day 1 is workspace provisioning and process-by-process form design. Nintex Day 1 is connector configuration. UiPath Day 1 is recorder sessions to capture selectors against every app. Zapier Day 1 is OAuth to every source and destination app and mapping every branch. None of these are productive work for a small consulting firm, they are preconditions for productive work.

It is not unfair, it is a sorting question. The Day 1 test separates solutions that can produce value in a day from solutions that require a multi-week rollout. Enterprise BPA is the right answer for some large-company processes: multi-department approvals, regulated workflows with compliance audits, systems that serve hundreds of users. The Day 1 test catches the many small-firm buyers who are about to spend six figures and six months on a solution whose shape assumes a 500-person operating model they do not have.

Install takes under a minute. On first launch there is no account wall, no OAuth, no workspace setup. You type a sentence. Clone's Planner scans the apps you have open, picks the ones it needs, and the Computer Agent starts driving those apps. Within minutes you have a chat timeline with staged outputs: draft invoices, draft emails, CRM note updates, spreadsheet edits. You review, edit, and ship the batch. That batch is the Day 1 deliverable.

Good, that is Clone's strength. The Planner reads meeting transcripts from tl;dv, Fireflies, or Otter and carries client-specific context (the exact phrasing from your last call, the escalation rule you use when the deal is above $10K, the cc convention you always apply on kickoff emails) into the draft. Zapier and enterprise BPA cannot do this because they are state machines, not agents. UiPath cannot do this because it replays recorded clicks.

Clone Solo is $588 per year, one plan, no add-ons required to hit the Day 1 test. Clone Boutique for small teams is $129 per seat per month. A typical Appian or Pega rollout for a small firm runs $50k to $250k in year one when you count license, implementation partner, and ongoing ops. A UiPath seat plus Orchestrator plus an RPA developer to maintain selectors runs $40k to $100k per year. A Zapier Team plan plus the hours spent building and maintaining Zaps runs $5k to $20k per year depending on task volume. The Day 1 test is also a cost test, because most of the cost in enterprise BPA is the weeks of non-productive time before Day 1 of real output.

Type: save that as a ritual called weekly-invoicing, schedule monday 08:00. Clone writes a markdown file at ~/.clone/memory/rituals/weekly-invoicing.md with a schedule line at the top and the body describing the steps. The next Monday at 08:00, Clone runs it and posts the staged drafts to chat for review. No cron, no scheduler service, no vendor infrastructure, just a file on your Mac that Clone reads.

Clone's Computer Agent reads the screen semantically rather than by brittle selectors. If QuickBooks moves the 'Save and send' button or renames it, the agent still finds it. This is a hard problem for RPA tools, which record element selectors and break when those selectors change. Clone was designed to survive UI drift because UI drift is the common case in small consulting firms, not the exception.

Yes. That is what the Book a Call button on this page is for. Bring one process you want to automate. On a 30 minute call we install Clone on your Mac, you type the instruction, we watch the Computer Agent drive your actual apps, and by the end of the call you have one real artifact shipped. That is the entire Day 1 test in 30 minutes.