Invite-only beta · System of record for agent workflows

Approved workflows
for AI agents
that cannot guess.

Workflow Record turns messy policies, playbooks, and runbooks into reviewed agent workflows with source boundaries, missing evidence, approval state, and refusal rules.

New teams should join the beta first. Sign in is for approved users and invited teammates.

Pricing Exceptionspricing_exceptions.workflow.json
Approved
Approved source

Pricing Exception Guidelines

sha256 verified at approval
Agent can answer
  • 0-10%: AE discretion
  • 10-20%: Sales Manager
  • 20-30%: Director of Sales
  • 40%+: CEO approval
Agent must refuse

Bypass requests, unsupported exceptions, or questions outside this approved source boundary.

Exports
OpenAI toolClaude toolYAML

The problem

Agents do not need more search.
They need approved operating rules.

The refund rule is in one doc. The escalation path is in a playbook. The pricing exception note lives in a sales folder. Search can find all of it, but an agent still needs to know what is approved, current, and safe to use.

Workflow Record becomes the record of approved agent workflows: source boundary, detected rules, missing evidence, reviewer, export, and refusal behavior.

From docs to agent license

One approved workflow file becomes the boundary agents reuse.

01

Compile

Upload a narrow operational doc. Workflow Record extracts rules, source boundaries, and missing evidence.

02

Review

Owners see what is ready, what is blocked, and which questions the workflow can safely answer.

03

Approve

Approved workflows lock the reviewer, source boundary, refusal cases, and output format into the file.

04

Export

Download .workflow.json or copy OpenAI, Claude, snippet, instructions, or YAML artifacts derived from it.

Pricing Exceptions

Sample approved workflow state

Status
ApprovedOwner reviewed
Source boundary
1 policyPricing Exception Guidelines
Blocking gaps
0Discount bands and approvers present
Exports
3.workflow.json, OpenAI, Claude

Supported agent workflows

The painful workflows ops teams ask about every week.

The beta starts with narrow agent workflows where the output must be a rule, approver, threshold, exception, or approved phrase: pricing exceptions, discount approvals, refunds, escalations, and rollback rules.

Support

  • Refund policywindows, approval thresholds, chargeback handling
  • VIP escalationsresponse times, escalation paths, churn risk

Sales

  • Discount approvalsroles, caps, and approval chains
  • Pricing exceptionswhen and how to deviate from standard pricing

Engineering

  • Rollback policyauto-rollback triggers, approval rules, tier thresholds
  • Incident analysisroot cause, missed safeguards, recovery issues

Marketing

  • Messaging guidancewhat to say and what to avoid by audience

Not enterprise search

Search finds knowledge. Workflow Record records what agents are allowed to use.

Keep using Glean, OpenAI, Slack, or your docs as discovery tools. Workflow Record is the agent workflow system of record for teams that need to know which workflow is approved, which evidence supports it, who reviewed it, and what an agent must refuse.

  • Enterprise search across every document
  • Generic chat over company knowledge
  • Anything the team has not reviewed
  • Strategy or brainstorming questions
  • Live integrations or autonomous actions

Who buys this

Ops teams approving agent behavior

Govern refunds, escalations, pricing exceptions, and rollout rules before assistants answer or route work.

Agencies and consultants packaging client knowledge

Turn repeat procedures, intake steps, and exception rules into portable workflow files clients can review.

Builders shipping agents over private workflows

Export source-bounded instructions, tool specs, snippets, and refusal cases without inventing a governance layer.

Early access pricing

Start with one approved workflow.

Private beta plans are manually activated while we onboard the first teams. Start free, prove the workflow file, then upgrade when you need more sources, teammates, or exports.

Free workflow trial

$0

Create one approved .workflow.json file from your own docs. Good for proving the loop before paying.

Builder

$49/mo

For solo devs, consultants, and small teams creating agent skills from operational docs.

Team pilot

$499/mo

For ops teams that need multiple approved workflow files, team review, and higher visual extraction limits.

Workflow setup sprint

For teams that want help fast: we turn messy docs into 3 approved workflow files, exports, and a handoff call. Includes 30 days of access.

From $3k

Common questions

What the beta is good for.

The product is intentionally narrow. These are the boundaries to understand before you upload company knowledge.

What kinds of documents should I upload during beta?

Upload the docs people already ask about: refund rules, escalation playbooks, pricing exception notes, rollout runbooks, approved messaging guidance, PDFs, and screenshots of operational procedures.

What should I avoid uploading during beta?

Please avoid regulated data, personal information, customer data, and anything you would not want in an early beta workspace. See our privacy and data handling page for the current beta scope.

Who can access my workspace data?

Only authenticated members of your workspace can access that workspace in the product today. Because this is still a private beta, we recommend sharing only materials you are comfortable using in an early product.

Is this a general document search tool?

No. Search finds relevant knowledge. Workflow Record is the system of record for approved agent workflows: what evidence supports the workflow, what is missing, and what the agent must refuse.

Does this replace OpenAI Agent Builder?

No. Workflow Record gives you a reviewed .workflow.json file plus OpenAI tool specs, Claude tool specs, copy-paste integration snippets, and instructions generated from it. The source docs and approvals stay in your workspace.

How does beta access work?

Join the waitlist and we review early teams manually. Approved users receive an email when access is ready, and invited teammates can join an existing workspace by signing in with the exact email that was invited.

Join the beta

Bring one painful workflow. We will help you turn it into an approved agent contract.

Private beta data guidance

Upload only operational materials you are comfortable sharing in an early product. Please avoid regulated data, personally identifiable information, customer data, and highly confidential materials during beta. We can manually delete workspace data on request. See our privacy and data handling page for the current beta scope.