Methodology

How we measure

We distinguish project evidence from illustrative cost models and diagrams. This page says which assumptions a calculation uses, what each picture shows and what we do not measure.

What we do not measure

  • Measured money saved. We have not run a controlled comparison. Dollar figures in the repeated-work calculator are assumption-driven API-equivalent estimates.
  • Hours saved. Without a recorded baseline for the same work, there is nothing to compare elapsed time against.
  • Business impact. Nothing here connects Orchard to a shipped outcome or a revenue number.
  • Whether more agents are cheaper. Parallel work saves time only when review and coordination cost less than the rework they prevent. Any honest comparison has to count every session, retry, review and rework round.

The repeated-work cost model

The landing-page calculator is an editable worked example, not observed savings. It estimates one thing only: model spend on work the provider is asked to do more than once. Staff time, tools, infrastructure and subscription charges are outside it, and it does not price Orchard.

  • The unit of work: one task is one job handed to an agent, run as a multi-step session rather than a single question. The agent reads, runs something, reads the result and continues, and every step re-sends the context so far. The default assumes 180,000 input and 12,000 output tokens of work you actually wanted, per task.
  • Six sources of repetition: oversized context (90,000 input tokens per task), verbose output (5,000 output), re-reading to self-check (45,000 in, 3,000 out), duplicated investigation (5% of tasks at 200,000 in and 12,000 out), overwritten changes (3% at 150,000 and 14,000) and builds on an unagreed approach (7% at 260,000 and 20,000). Each is separately switchable, and every figure is editable.
  • Monthly estimate: people × tasks per person per day × working days, then each source’s share of those tasks at its repeated tokens and the selected model’s list price. The default 25 people, 15 tasks and 22 days produce 8,250 tasks and a modeled bill of $18,967 a month on Claude Opus 5, of which $9,067 — about 48% — is repetition.
  • The prevention share is yours, not ours: the 50% default is a scenario to test. It is not measured Orchard effectiveness, a customer outcome or a quote. At 50% it avoids $4,533 a month.
  • Coordination costs something: staying in step means extra calls, so the model charges an overhead as a percentage of the bill you still pay, never a flat fee — an empty workload therefore owes nothing. At the 5% default that is $722, leaving $3,812 a month, about 20% of the bill. Remove no repetition and the result is a loss of $948, not a floor at zero.

Rates checked 2026-09-17, in USD per million tokens (input / output / cache read): Claude Sonnet 5 $2 / $10 / $0.20; Claude Opus 5 $5 / $25 / $0.50; GPT-6 Astra $10 / $50 / $1.00. These are standard API rates; Astra uses its short-context tier. Tokens are priced uncached, so the estimate is conservative for teams already getting provider cache hits; caching is a separate saving and is excluded. Equal token counts compare prices, not model quality or equal work.

Useful first-time work is held constant across both bars: doing the job once costs the same either way, so only the repeated portion moves. Annualisation repeats one identical month twelve times and is not a forecast. These are API-equivalent costs; on a subscription, avoided work may preserve an allowance rather than reduce an invoice.

Before trusting the output, check the modeled monthly bill against a real invoice and adjust tasks per day until it matches. To establish actual savings, record a baseline and compare matched tasks at equivalent accepted quality, counting every provider usage category on both sides. Our workspace capture demonstrates recorded activity; it does not establish how much repetition Orchard removes. Downloading the scenario exports the selected assumptions, rates, sources, formulas and full-precision results.

Which pictures are real

The site carries an anonymised workspace graph and illustrative diagrams. Diagrams with no recorded data behind them, such as the policy walkthrough, are labelled as illustrative.

The communication network on the homepage is an anonymised workspace capture. On message routes, the number of moving dots follows the recorded message count, so a busy route shows more of them. Memory and action routes are counted in different units, so they carry one dot and claim nothing about volume, and dashed placement routes carry none. Timing is not measured latency: how fast a dot travels means nothing.

How the event explorer was built

The three paths are synthetic projected examples based on current Orchard Engine source. They explain the persistent PubSub adapter, local PTY messenger, and inbound relay event bridge. They do not replay a captured log, connect to a running engine, or measure elapsed time.

The tool example follows an instrumented hook through the raw occurrence ledger and a separate, derived coordination view. A failed ledger append blocks that agent-events broadcast. Independent hook ingestion may already be queued, and tool execution remains unknown. Stored envelopes are redacted; that does not mean every live transport carries only the redacted copy.

The message example follows the local PTY delivery lane. Native agents and remote targets use other paths. A delivered signal can include deferred input. A processed receipt comes from a target-session hook or turn boundary without matching the message ID. It is not evidence that a particular instruction was understood or completed.

The peer example uses an eligible derived coordination event. Inbound filtering, occurrence capture and local projection are separate boundaries. Raw tool hooks are not automatically forwarded through this route. Socket acceptance does not prove peer processing, and this is not a guarantee of lossless or identical history on every machine.

The JSON panels use authored identifiers and readable summaries. The occurrence ID, message ID and transport correlation ID represent different things. No private event payload, session identity or machine name is published.

Explore the event paths

Chat coordination and model choice

Chat model selections and worker runtime settings are separate. Hosted model availability depends on configuration and provider access. Local Chat requires a compatible model and ready runtime; enabling a hosted DeepSeek option does not install a local model. These choices do not imply automatic selection of the cheapest model or equal capabilities across models.

Individual usage rows describe individual calls. Comparing prices or token counts alone cannot establish equivalent task scope, output quality or total delivery cost. Include coordination, review and rework in a comparison, and include hardware and operation for local inference.

Limits worth knowing

  • Recall is best effort. Stored context can be incomplete or stale, so the underlying source stays the authority.
  • Runtimes differ. Tool access, hooks and permissions are not the same across Claude Code, Codex and OpenCode. Configuring a runtime is not the same as Orchard choosing a model for you.
  • Connecting a tool grants no universal access. Where your data goes depends on the provider, integration and runtime you configure. Orchard does not create a sandbox around them.