Invoicing automation software that needs no API and no migration.

Yes. The Computer Agent layer in Clone is the one that reads the pixels and clicks the buttons. That is the architectural separation spelled out in src/components/architecture.tsx: a Planner layer interprets your instruction in plain English, and the Computer Agent layer drives whatever application is on your screen. Neither layer requests an API key. You never sign into a developer portal, you never rotate a secret, you never wait on an admin to grant OAuth scopes. The only credentials that exist are the ones you already have: your QuickBooks login, your FreshBooks login, your Google account. Clone uses them through the apps the same way you do.

Clone opens the QuickBooks Desktop window you have on your Mac and drives it through accessibility APIs. No Web Connector, no Intuit sync service, no QBWC.exe. The Monday ritual says 'open QuickBooks Desktop, click Customers > Create Invoices, enter these line items'. Clone executes that instruction at the UI level. Upgrading QuickBooks Desktop does not break Clone, because Clone is not bound to a specific API schema. If Intuit renames a menu item, you edit one line of the ritual. The architecture principle src/components/architecture.tsx lines 56 to 59 is literal here: 'Clone uses the apps you already pay for. Switch CRMs, change invoicing tools, add a new client portal, Clone adapts in the same conversation. No re-wiring required.'

Yes, and many solo consultants do. The ritual points at your invoice-template.gsheet, Clone opens it, appends a row with the client name, line items, rate, and total, and uses File > Download > PDF to export the invoice. The PDF lands in your Drive. Clone then opens Gmail, drafts the send-to-client email with the PDF attached, and either waits for your review or sends on its own if that client is in the auto_send list. This is the same path a human assistant would take. The Sheet remains yours, the template remains yours, and no third-party app sits between you and your client's paid invoice.

All supported, because they are just browser tabs. Each of those tools gates its API behind a tier most solo practices do not purchase. Clone does not care. It opens the tab, navigates to the billing screen, clicks 'New Invoice', fills the time entries and the rate, saves the draft, and captures the invoice number from the confirmation message. When Clio releases a new version of its billing UI, you update the ritual sentence that says 'click Billing > New Invoice' if a menu moved. That is a markdown edit. It is not a vendor integration request.

Under ten minutes for the first real draft. That ten minutes breaks down as: one minute to install the app, two minutes to write memory/rituals/invoicing.md (eight to twelve lines for a typical solo practice), five minutes to run the ritual once while watching and fix the one rate that was wrong, one minute to approve the drafts. Compare against the Bill.com or Stampli onboarding which assumes IT access, API credential provisioning, and a chart-of-accounts mapping phase measured in days. The speed comes from the fact that Clone has nothing to provision server-side. All the state lives in your markdown file.

Anything with a screen works. Harvest, Toggl, Clockify, Clockk, Rize, Everhour, or a manually maintained spreadsheet. The ritual sentence 'read timely entries since last monday, group by engagement' becomes 'read harvest entries since last monday, group by engagement' with a one-word edit. Clone opens the time tracker's report page, extracts the rows it sees, and uses them. The same pattern applies if you change time trackers mid-year: update one word, re-run the ritual, done. No integration to deprecate.

Client files, emails, contracts, transcripts, and the Memory layer itself never leave your computer. This is the first architectural principle, in src/components/architecture.tsx lines 46 to 50: 'Clone operates your desktop apps from your desktop. Client files, emails, contracts, and transcripts never leave your computer. Your engagements stay confidential by default.' When Clone drafts an invoice in QuickBooks Desktop, the data travels from your Timely window to your QuickBooks window without a stop in anyone else's cloud. The Planner may call a model to interpret your English instruction, but the attached client data is not sent along with it.

Edit one line of memory/rituals/invoicing.md. The apps_this_month section maps each client key to an invoicing app. Change 'acme: quickbooks_desktop' to 'acme: freshbooks' and the next Monday run uses FreshBooks for that client and QuickBooks Desktop for the others. There is no migration, no re-wiring, no vendor setup. The ritual is the source of truth, the apps are interchangeable surfaces.

Zapier needs a trigger, a filter, a branch, and an action configured for every path. That is unmanageable for a consultant whose path diverges per client. It also requires an API integration for every downstream tool, which cuts out Desktop, Clio, and custom Airtable. HoneyBook replaces your stack end-to-end: CRM, proposals, invoicing, client portal. If you are already invested in QuickBooks plus Gmail plus your CRM, HoneyBook asks you to abandon them. Clone does neither. It reads plain English, it drives the apps you already pay for, and it leaves your stack alone. The comparison table in src/components/comparison.tsx lines 6 through 77 puts the three side by side: Clone is the only row that scores a check on 'Works with custom or legacy apps', 'Set up in under 10 minutes', 'Data stays on your machine', and 'No vendor lock-in' at the same time.

The ritual produces drafts, not sent invoices, on the first run and on review_first clients. You see every draft link in the chat. If Clone typed $225 where the rate should have been $275, you fix it in the QuickBooks or FreshBooks window the same way you would fix any draft, and you update the rate in memory/rituals/invoicing.md so the next Monday does not repeat the mistake. The architecture principle 'Always reviewable' (src/components/architecture.tsx lines 61 to 63) is literal: every action is logged and reversible, and you can roll back an entire morning of work with one click.

A few seconds per line slower on the run itself, because Clone interacts through the UI rather than a batch API call. The tradeoff is measured against setup and change cost, not run cost. An API-integrated tool may be marginally faster on Monday morning, and meaningfully slower on the first day, on the day you change tools, on the day QuickBooks Online blocks a non-Advanced plan from the endpoint you need, and on the day legal asks for a new DPA. On a typical solo practice running 8 to 20 lines per week, the run-time cost is a fraction of a minute. The setup-time savings are days.

$49 per month on Solo, no per-invoice fee, no integration tier, no implementation services line. There is a 21-day free trial before the first charge. A typical SERP competitor ranges from $28 per user (Method) to $79 per user (Bill.com Team) to quoted enterprise (Stampli, Tipalti, Rillion, HighRadius). The pricing model is different because Clone has nothing to provision on the vendor side: no cloud compute, no API quota, no integration catalog to maintain. The app is a file on your disk and the ritual is a file on your disk.