Procurement's job is to make the vendor prove it. Good — this page is built for that: the standard artifacts on request, published pricing with a hard ceiling, a 30-day pilot with metrics and exit criteria defined up front, and an exit story that doesn't require a lawyer. Start with hello@turtleaicoworker.com.
Answered the way you'd want them in the vendor file: what's available, what it costs, how the evaluation runs, and how you leave.
Yes. A security packet — architecture overview, data-flow diagrams, current compliance status — is available on request, and we complete security questionnaires as part of the job, not a favor. The DPA is available on request with SCCs where applicable, and the whole security posture is published for inspection on the Trust Center.
The Trust CenterPer-plan pricing, published in full — you can read the number before you talk to anyone. And there are no surprise usage cliffs, structurally: budget caps are hard stops enforced at runtime, with breach-date forecasting before you hit them. The invoice can't exceed a ceiling you didn't set.
See the plansWith the 30-day pilot framework below: install a solution pack in about 15 minutes, define success metrics before the first run, keep approvals on everything for the first two weeks, then loosen gates only on workflows that earned it — and decide against numbers, not impressions. Exit criteria are agreed in week one, so nobody has to negotiate their way out later.
Pick a pilot packDelete means delete: remove your workspace and its data is deleted — tables, knowledge, run history and stored credentials with it. Before that, your data is exportable: audit trails, table data, the evidence you accumulated during the pilot. Leaving is a supported operation, not a negotiation.
Data handling commitmentsWe won't hand you a logo wall or an arranged reference call, and we'd be suspicious of a vendor who did. What we offer instead is an evaluation that stands on inspectable evidence: a published security posture, a runtime you can gate with your own policies, an audit trail of everything the pilot did, and metrics you defined. Verify, don't take references.
The readiness guideThe structure that keeps a pilot from becoming a permanent maybe: success metrics and exit criteria are written down in week one, and week four is a decision — either way.
Time the pilot team got back, measured against the pre-pilot baseline for the same workflows.
Tasks completed autonomously versus completed under approval — the trust curve, in numbers.
How often output needed correction or a human had to step in, from the audit trail — not from memory.
Per-message token and USD tracking, summed per workflow. Compare it to what the task costs today.
Exit criteria, agreed in week 1: the metric thresholds that mean "proceed", and the ones that mean "export, delete, done." If the pilot misses them, the exit is week 4 — not a renewal conversation. Governance mechanics for the approval gates: Governance · Approvals · Analytics.
Stakeholder one-pagers for your colleagues: IT & Security · Finance · Legal.
Architecture, data flows, compliance status and completed questionnaire answers — the standard diligence bundle, on request.
Request by emailPublished per-plan pricing, including where enterprise controls (SSO, audit exports, data residency, self-hosting) live.
See pricingThe internal case for your stakeholders — finance, security, legal — pre-assembled so you're not writing it from scratch.
Get the kitTell us the workflow you want to evaluate and we'll propose the pack, the metrics, and the exit criteria — in writing, before anything is installed.
