Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
131 changes: 0 additions & 131 deletions docs/commercial/battlecards.md

This file was deleted.

17 changes: 6 additions & 11 deletions docs/commercial/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -3,8 +3,7 @@
This section is the buyer-facing collateral for OpenAdapt's commercial
offers. Every price and claim here matches the public
[pricing page](https://openadapt.ai/pricing) and the
[qualification evidence appendix](../get-started/what-works-today.md). Where a
term is not yet finalized it is marked explicitly rather than implied.
[qualification evidence appendix](../get-started/what-works-today.md).

## The offer ladder

Expand All @@ -21,12 +20,11 @@ The ladder is sequential by design: qualification before pilot, pilot before
production. The sprint is paid even when the correct outcome is not to
automate; a well-evidenced "do not automate" is a full-value deliverable.

## Sales and evaluation collateral
## Buyer and evaluation resources

| Document | Use it when |
|---|---|
| [Qualification Sprint one-pager](qualification-sprint.md) | Introducing the entry offer to a buyer. |
| [Statement of Work template](sow-template.md) | Drafting the sprint contract. |
| [Scope and prerequisite checklist](scope-checklist.md) | Confirming the customer can actually start. |
| [Qualification report outline](qualification-report-outline.md) | Showing a buyer what they will receive. |
| [Acceptance matrix template](acceptance-matrix.md) | Agreeing pass/fail criteria up front. |
Expand All @@ -35,19 +33,16 @@ automate; a well-evidenced "do not automate" is a full-value deliverable.
| [External Citrix zero-install brief](citrix-external-brief.md) | A buyer whose workflow lives behind Citrix or VDI. |
| [OEM architecture and commercial brief](oem-brief.md) | A vendor that wants to embed verified execution. |
| [Procurement FAQ](procurement-faq.md) | Procurement, legal, and vendor-risk questions. |
| [Competitive battlecards](battlecards.md) | Positioning against RPA, agents, and scripts. |
| [ROI worksheet](roi-calculator.md) | Building the economic case with the buyer's own numbers. |
| [Legal document outlines](legal-outlines.md) | Structuring design-partner and publication agreements. |

## Honesty rules for this section

These documents follow the same rules as the public site:

- No invented customers, quotes, or case data. The one referenced case study is
[published with preliminary figures and a pending-confirmation caveat](https://openadapt.ai/customers/rvu-audit-heart-care).
- Customer results name the workflow and the result actually reported. See the
[RVU audit customer case](https://openadapt.ai/customers/rvu-audit-heart-care).
- No claimed certifications. SOC 2 status is stated plainly in the
[security packet](security-packet.md).
- Bounded evidence stays bounded. Qualification evidence for one workflow,
application, and environment is never presented as a general support claim.
- Competitors are credited for what they are genuinely good at. See the
[battlecards](battlecards.md).
- Commercial terms are established in a customer-specific written proposal and
agreement, not in public templates.
77 changes: 0 additions & 77 deletions docs/commercial/legal-outlines.md

This file was deleted.

2 changes: 1 addition & 1 deletion docs/commercial/oem-brief.md
Original file line number Diff line number Diff line change
Expand Up @@ -80,7 +80,7 @@ your marketing as in ours.
environments, and support; per-end-customer workflow qualification is scoped
separately or delivered by the partner using the qualification tooling.
- Early OEM partners operate under a
[design-partner structure](legal-outlines.md): defined feedback obligations,
customer-specific design-partner agreement: defined feedback obligations,
early access to the reference API, and input into its shape.
- The engine is MIT-licensed and auditable; embedding does not depend on a
proprietary black box for its safety story.
Expand Down
14 changes: 6 additions & 8 deletions docs/commercial/procurement-faq.md
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@ A fixed-scope engineering assessment of one workflow, from $15,000 (native,
RDP, and Citrix scopes typically $25,000 to $40,000), delivering a signed
go/no-go report, coverage matrix, and evidence pack. It is paid regardless of
outcome; "do not automate" is a full-value deliverable. See the
[one-pager](qualification-sprint.md) and [SOW template](sow-template.md).
[Qualification Sprint one-pager](qualification-sprint.md).

**Is there a subscription?**
OpenAdapt Cloud is $500.00/month for managed browser execution of approved
Expand All @@ -27,11 +27,11 @@ environment, runners, evidence, support, and requalification scope. OEM
embedding is typically $75,000 to $150,000 per year plus integration.

**Does the sprint fee credit toward production?**
A portion of the sprint fee credits toward the first production year; the
exact percentage is being finalized: **[FOUNDER TO CONFIRM]**.
Any production credit is stated in the customer-specific written proposal. No
credit is implied by this public documentation.

**What are the payment terms?**
Per SOW; the template proposes 50% at signature, 50% at delivery for sprints.
The customer-specific written proposal and agreement state the payment terms.

## Licensing and lock-in

Expand All @@ -53,10 +53,8 @@ operator-verifiable no-egress posture. See
## Security and compliance

**Are you SOC 2 certified?**
No. OpenAdapt does not hold a SOC 2 report and does not claim certification;
an internal controls matrix and evidence plan are maintained, and the target
date for an observation period is **[FOUNDER TO CONFIRM DATE]**. See the
[security packet](security-packet.md).
No. OpenAdapt does not hold a SOC 2 report and does not claim certification.
See the [security packet](security-packet.md).

**Will you sign a BAA / process PHI in your cloud?**
The managed cloud lane is for non-regulated data. PHI-bearing workflows run in
Expand Down
2 changes: 1 addition & 1 deletion docs/commercial/qualification-report-outline.md
Original file line number Diff line number Diff line change
Expand Up @@ -92,7 +92,7 @@ The seeded-fault results, summarized in the
| Field | Definition |
|---|---|
| Volume and time baseline | Customer-provided run volume and manual minutes. |
| Modeled savings | Per the [ROI worksheet](roi-calculator.md), under conservative assumptions, with every input attributed. |
| Modeled savings | Customer-specific economic model using conservative, attributed inputs. |
| Costs | Sprint, pilot, production, and operational intervention costs. |

## 9. Evidence pack manifest
Expand Down
10 changes: 4 additions & 6 deletions docs/commercial/qualification-sprint.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,8 +23,6 @@ sprints or scoped extensions.
- The sprint fee is due regardless of outcome. **"Do not automate" is a valid,
full-value result**: you paid for a defensible decision, and a well-evidenced
no saves you the far larger cost of a bad production deployment.
- Conversion credit: a portion of the sprint fee credits toward the first
production year. Exact percentage: **[FOUNDER TO CONFIRM]**.

## When the clock starts

Expand Down Expand Up @@ -74,8 +72,8 @@ We recommend against automation, and say so in the report, when for example:
example uncontrolled application releases with no test tenant).
- A direct API or batch interface already exists that makes GUI automation the
wrong tool. We will tell you to use it.
- The volume and value do not clear the [ROI worksheet](roi-calculator.md)
under conservative assumptions.
- The volume and value do not clear an agreed economic threshold under
conservative assumptions.

## Acceptance criteria

Expand Down Expand Up @@ -114,5 +112,5 @@ qualified fixture set:
pursuing.

Start by describing the workflow at
[openadapt.ai/qualify](https://openadapt.ai/qualify), or use the
[Statement of Work template](sow-template.md) to contract directly.
[openadapt.ai/qualify](https://openadapt.ai/qualify). The written proposal and
agreement define the exact scope, payment schedule, and production options.
Loading