Help

How Arc works

Arc turns project conversations into a record of decisions that both you and your client have agreed to. Here is the whole thing, in order.

The loop, end to end

  1. Capture — a conversation happens. Record it on site, or bring a transcript you already have.
  2. Import — paste or upload it into a project. Arc reads it and proposes the decisions it can evidence.
  3. Review — you accept, reword or discard each one. Nothing reaches your client unreviewed.
  4. Send — your client opens a private link and agrees, or amends in their own words.
  5. Keep — everything agreed lands in the ledger, exportable and printable.

The point of the order is that nothing is recorded as agreed until both sides have said so. Arc proposes; you curate; your client confirms.

Importing a conversation

Open a project and use Import. Two ways in:

  • Paste the text of a transcript or notes.
  • Upload a .txt, .md or .vtt file — the formats meeting tools export.

If you connect a meeting source, recordings arrive in your Inbox instead, where Arc suggests which project each belongs to. You confirm, re-pair or discard — nothing is filed into a project without you saying so.

Arc is deliberately conservative. It will not turn a musing, a floated number or a parked item into a decision, and it records nothing it cannot quote. If a firm decision has a detail still pending, that lands as an open question attached to the decision rather than as a fact.

Reviewing what Arc found

Proposed decisions appear in the project with the exact passage they came from, so you can check the claim against the words. You can reword one before it goes out — your wording, not the model's, is what your client sees.

Missed something? Open the transcript and pin the line yourself. It becomes a decision like any other.

Send a batch and your client gets an email with a private link. No account, no password, no app. They see each decision in plain language and either agreeor amend — and an amendment can carry their own suggested wording, which you can accept in one click.

Links are private and per-recipient: treat one like a key. If a client has more than one contact, the person you nominate as primary is the one whose agreement moves the record; others can read and comment.

The agreed ledger

Every agreed decision, grouped by category, each with its evidence and who agreed it when. It prints cleanly to PDF from your browser, which is what most people send on or file.

The record is append-only. When a decision changes, the new one supersedes the old and both stay visible with their dates — so "when did this change?" always has an answer.

Recording on site

The iOS app records on your phone, which is where site conversations actually happen, and the transcript flows into Arc for import. Useful when the decision is made standing in the room rather than on a call.

Plans and limits

Free covers one project end to end. Paid plans raise how many projects, people and monthly imports you get. Reviewing, sending, exporting and your clients' use are never metered — only the AI reading new material is.

When you reach a limit Arc says which one and how much you had used. Nothing already in the record is affected, and monthly allowances reset at the start of the next month.

When something looks wrong

  • A decision looks wrong or invented. Check the quoted passage first — if the quote doesn't support it, discard it and tell us; that's a bug worth knowing about.
  • Arc found nothing. A conversation where nothing was decided genuinely yields nothing. Under-claiming is deliberate.
  • Your client can't open a link. Links expire. Re-send from the project.
  • You can't get in. Use the sign-in link by email, or reset your password from the sign-in screen.

Still stuck? Contact us — a person reads every message, and telling us what you expected to happen is the most useful thing you can include.