Give one AI support action a clear authorization boundary and a result your team can check. Start in a safe test environment with founder-guided integration; decide whether to pay after the agreed acceptance checks pass.
Who this fits
Our first partners are AI customer-support and ecommerce automation companies whose Agents already request refunds or order cancellations. Bring one action path, an engineering contact who can change its integration, and access to a test target with a separate read path. We support up to 3 design partners concurrently; this is our delivery capacity, not a claim about remaining places.
This is a collaborative integration pilot. We agree engineering time before starting; an account signup alone does not start the pilot.
Scope and price
| Stage | Agreement |
|---|---|
| Free trial | 30 active days, $0, no credit card. One project, up to two Agents, one refund or order-cancellation action in an agreed safe test environment. |
| Optional continuation | After acceptance and mutual written agreement: USD 500 per month, billed monthly for the agreed scope and operation allowance. No automatic charge or conversion. |
| Price lock | Six months from the first paid month for that same scope. This is a price lock, not a requirement to purchase six months. Expansion and renewal are quoted separately and require agreement. |
Agree an operation allowance before paid use and review usage together. Exceeding it does not automatically add fees. This pilot does not introduce automated usage billing or promise a published standard price. Separately scoped assurance reviews are not included.
For pilot usage review, count one distinct in-scope business-action request that reaches a policy decision, whether allowed, held for approval, or denied. Approval steps, result checks, and retries of that same request are not extra operations; Witnora-caused failures are excluded. Agree the deduplication window and reconciliation method before paid use. An execution receipt can support this review, but is not a complete billing ledger.
What we verify together
- Authorization: bind the intended Agent, version, environment, object, and action parameters. Required approval is explicit; rejected or changed requests cannot reuse that authority.
- Controlled execution: the agreed action goes through the registered customer-owned Gateway. Agree and test the retry/duplicate boundary; do not infer that unconnected paths are controlled.
- Observed result: compare the expected result with a separate read of the target system. A mismatch or missing observation must remain visible, not appear as verified success.
- Portable evidence: download the receipt, verify it offline against a separately trusted key, then alter a signed field and confirm verification fails. Signature integrity and business-result verification are separate checks.
- Honest interruption and recovery: interrupt the test connection, confirm the affected status does not imply current protection, and retain historical evidence. Restore the connection; require fresh observation before renewing an affected outcome claim.
Agree exact fixtures and expected results before starting. The sandbox quickstart is a reference path. The refund demo replays recorded test-mode evidence; it creates no new refund and does not prove a deployment into your business system. Production access and target-specific acceptance are a later, separate decision.
Responsibilities and blockers
The customer supplies a named engineer, scoped test access, success criteria, and a weekly review. Customer-owned components retain provider write credentials and a separate read credential locally. Witnora guides integration, fixes in-scope product defects, and reviews the evidence with the customer. Share no credentials or raw customer records in the application email.
Before starting, both sides fill in and approve:
| Item | To agree in writing |
|---|---|
| Scope and owners | Company, action, target, environment, Agent binding, customer engineer, Witnora owner, and commercial decision-maker. |
| Schedule and effort | Start date, each side's planned engineering hours, weekly review, and acceptance date. |
| Blocking defect | A reproducible in-scope Witnora defect preventing an agreed acceptance check. Witnora owns its fix. Record when blocking begins and ends; pause the trial for that period. |
| Response and handling | Acknowledgement deadline and deadline for a fix or acceptable workaround; define escalation if either is missed. |
| Pause cap and exit | Maximum cumulative paused days. At that limit either side may end the free pilot without a continuation obligation or pilot fee; agree evidence export and access revocation. |
| Paid continuation | Monthly operation allowance, included environment/support, invoice arrangements, cancellation terms, and the six-month price-lock dates. |
These fields must be agreed before the clock starts. This is not unlimited custom development or an automatic five-day fix guarantee. Scope new requirements separately. Record customer-side access delays separately and agree their effect on timing together.
What this pilot establishes
Evidence covers one named action path. It does not establish control over unregistered paths, prevent every Agent error, prove future outcomes, or provide an enterprise SLA, independent organizational audit, or compliance certification. Missing evidence stays explicitly incomplete.
Record customer engineering hours, Witnora support hours, protected-action volume, and who can approve continued spend. Evaluate technical acceptance and willingness to pay separately; a free integration commitment is not a paid-customer result.
Apply
Apply by email with your company, one action, target system, approximate monthly volume, and engineering contact. We agree scope before any integration or commercial commitment. See current plans.