One balance.
Your whole team.

Yes — 14 days, no credit card. Pick the plan that looks closest to your month and start; the choice only pre-configures your billing, it doesn't limit what you can do during the trial. If you land on the wrong one, changing it later takes a click.

Volume, and the rate you pay for it. Starter, Pro, and Scale all unlock exactly the same product — the same workflows, artifacts, memory, and code coverage. Moving up buys a bigger monthly balance at a lower price per credit. Enterprise is the only tier that adds capability: custom workflows, gov-tech integrations, and account management are available on Enterprise and nowhere else.

On credits, which your whole team draws from one shared balance. Credits meter the work the platform does, not who is allowed to log in. Run out and you can top up at any point in the month, or move up a plan.

If running out is the worry, you don't have to watch it. Set an automatic top-off threshold and the balance refills before it ever reaches zero. Set a maximum alongside it and it can never run past the budget you've agreed to — so the account looks after itself in both directions.

Per team. One balance for the whole organization, shared across everyone you invite. Adding a colleague costs nothing until they actually run work, which is the entire point — seats punish exactly the behavior everyone wants, which is sharing. It's also where per-seat pricing quietly overcharges.

Most departments and firms have a few heavy users and a long tail of people who need Ichi once a month, or twice a quarter — and a seat license bills every one of them the same. You end up paying full freight for the reviewer who asks two code questions a season, or you ration the licenses and leave people out.

Credits make that fair: an occasional user costs almost nothing, so you can put the whole team on it and still only pay for work that actually runs.

It depends on the work. A quick code question is small; a workflow that runs end to end and leaves a finished document is substantially more, because substantially more work happens. Nothing is capped by category, so the mix is yours.

A team that lives in workflows spends its credits automating work it used to do by hand. A team that lives in chat spends them on Ichi as an assistant that knows the codes and the project. Most teams do some of both, and that works too — it's one balance, so you never have to predict the split in advance. Only three things draw credits: chat messages, workflow runs, and processing the files you upload. Everything else is included. The calculator above turns your real monthly volumes into a credit figure.

Almost everything. Three activities draw from your balance — sending a chat message, running a workflow, and processing a file. Nothing else does.

Storage isn't metered, so every planset, project, and memory can stay in Ichi as long as you want at no cost. Seats aren't metered, so inviting the whole department is free until those people actually run work. There are no per-project fees, no charge for the prompts, memories, or artifacts you've already created, and no platform fee on top of the Starter, Pro, and Scale plans. If it isn't chat, a workflow run, or a file being processed, it doesn't touch your balance.

No — we don't think a flat fee for each sheet makes sense. Different teams on different projects have their own needs for what checks to perform, what edits to make, and what to produce at the end, so Ichi isn't designed like that. Our customers have the flexibility to ask Ichi to do a little or a great deal of work for each code, document, or sheet analyzed, and to decide what types of artifacts are generated.

Top up mid-month in packs, or move up a plan. Nothing stops mid-work and nothing is billed by surprise — you'll see the balance drawing down as you go. Worth knowing: a top-up costs a little more per credit than committing to the plan above it, so if you're topping up most months, moving up is the cheaper answer and we'll say so.

One consequence worth naming: because we won't stop work already in flight, your balance can go slightly negative. That's deliberate. It isn't fair to start a workflow, get eighty percent through it, hit zero, and watch it stop — so the workflow finishes, the chat answers, the file completes processing. Only once you're actually out does Ichi hold new work: no new chat messages, workflow runs, or file intake until you top up or move up.

On monthly plans, yes — for one month. Anything you don't spend carries into the next billing period, so a quiet month isn't wasted, but it only rides along once: whatever is still unused at the end of that second month expires.

Annual plans work differently. The whole year's credits are issued at once, up front, and unused credits expire at the end of the year. If your volume is seasonal, or you don't see a plan that fits your needs, please reach out to us at connect@ichiplan.com to help build a custom plan in our Enterprise tier.

For Starter, Pro, and Scale, no. Month-to-month, maximum flexibility — and annual billing saves 10% because some organizations prefer it, especially in government procurement, not as a lock-in.

Enterprise is different by design. Those engagements run from annual to multi-year, shaped by the nature of the work and how the team is organized. We've been through a range of contract structures on both sides of that — government jurisdictions with their own procurement rules and approval cycles, and private enterprises with theirs — so the term is something we scope with you rather than something you pick off a page.

No, with one distinction worth being precise about. Projects, memories, and prompts are unlimited, and so are seats. Storage is free regardless of size — a 1KB memo and a 1GB drawing set both cost nothing to keep, and you can keep as many as you like. We don't meter bytes. What is metered is AI processing: having Ichi read a file draws credits, and plansets are the heaviest of those because they're read sheet by sheet. So the limit isn't on what you store, it's on how much you ask Ichi to work through in a given period — which is exactly what the plan balance is for.

We've been through it — AI policies, security review, data handling — with departments that started with no AI policy at all and finished deployed department-wide. In practice that means a few things. We can contract on our paper or on yours, whichever your process needs. We have draft AI policies we can adapt if your jurisdiction doesn't have one yet. We carry a range of insurance policies to meet administrative requirements. And we can comply with public records requests and the related obligations that come with working for a public agency.