Answered plainly.

Those are chat tools: you open one, ask a question, close the tab, and nothing persists but a transcript. Every session starts by re-explaining your business, and the answer is only as good as what you happened to paste in. Arc holds the company’s context permanently — what you decided, why, what must stay true — and brings it to every question without being asked. It also carries that context into the AI tools you already use, so you stop re-explaining the business to a stranger every morning.

A CRM remembers your customers. A wiki stores documents you have to maintain by hand. Neither watches whether what you wrote down is still true. Arc keeps the reasoning behind decisions, tracks the assumptions underneath them, and tells you when new evidence starts contradicting one. The difference is not storage. It is that Arc has an opinion about whether the contents are still valid.

No. Nothing consequential leaves Arc or changes in your business without your explicit approval, and there is no autonomous mode waiting to be unlocked. Arc proposes; you decide. This is a design commitment, not a setting.

It is the objection we take most seriously, because most decision logs die exactly there. Arc starts with a guided interview that asks only the high-value questions, plus whatever you already have. After that it learns from the work you were already doing and drafts entries for you to confirm. If keeping the memory current depended on your discipline, it would not survive a hard month — so it does not depend on it.

It tells you. It will not fill the gap with a confident guess. Missing information is shown as missing, estimates are labelled as estimates, and beliefs you supplied are labelled as yours rather than laundered into facts.

Neither do we, and Arc is built as the opposite of that. Its job is to make your judgment better and more transferable, not to substitute for it. Every consequential recommendation shows its evidence, its uncertainty, and what would have to be true for the conclusion to change — so you can disagree with it on the merits.

You do, and yes — whenever you want, in a form you can actually use. The commitment matters more than usual here, because the thing being stored is your company’s reasoning. Detailed security and hosting commitments are on the trust page, including which of them are live today and which are pre-launch commitments.

No. Arc sits above them. Your CRM stays your CRM, your books stay your books. Arc is the layer that remembers what you decided and why, which is precisely the thing none of those tools holds.

You can, and some people should — there are good open-source patterns for exactly this. What you are taking on is the part that is not the prompt: keeping the capture alive, keeping evidence graded honestly, noticing contradictions you would rather not notice, and maintaining all of it through the months when you are busiest. That maintenance is the product.

Not yet. It is pre-launch, and the current step is Founding Arc — ten owner-operated companies building it with us. There is no public signup and no price yet. We will talk to more than ten, so applying puts you in the conversation rather than in a queue. If the description of the problem sounds like your week, that is the door.