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.

Workflow Record
Pricing exceptions workflow

Ready for approval. Agent may use discount bands, approval roles, valid reasons, invalid reasons, and Year 1 concession guardrails after owner review.

Ready to reuse
  • Approved by workspace owner before skill export
  • Download .workflow.json, then copy Claude, OpenAI, integration snippet, instructions, or YAML
Illustrative mock

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.

How it works

1

Compile

Workflow Record compiles repeat operating rules into bounded agent workflows, then can use AI on demand to draft richer details inside the source boundary.

2

Approve

Owners and admins approve what agents may use. If an approver, threshold, exception, or source is missing, the workflow stays blocked.

3

Export

Approved workflows download as one .workflow.json file with Claude tool specs, OpenAI tool specs, integration snippets, instructions, YAML, and refusal boundaries derived from it.

Agent workflow registry

In two minutes, see what agents can use and what still needs review.

Upload a few operational docs and get an agent-facing registry: proposed workflows, approved contracts, blocked workflows, missing evidence, and copy-ready agent artifacts.

4

Proposed agent workflows

Pricing exceptions, refund handling, escalation routing, messaging guidance

1

Approved agent contracts

A source-bounded workflow agents can reuse

3

Knowledge gaps

Missing approvers, thresholds, and source docs

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

1

solo builders and consultants

Create source-bounded workflow files for agents without building a full governance layer from scratch.

2

small agencies and SMB teams

Turn repeat procedures, client intake steps, and exception rules into reusable agent skills.

3

Support Ops

Govern refund approvals, chargeback handling, and escalation rules before an assistant answers customers.

4

Sales Ops / RevOps

Turn discount bands, pricing exceptions, and approval chains into reviewed agent instructions.

5

Customer Success Ops

Keep VIP escalation paths, account handoffs, and churn-risk playbooks inside approved boundaries.

6

teams building agents but afraid of wrong answers

Show what is approved, what is missing, and what the agent must refuse before automation runs.

Early access pricing

Start with one approved workflow.

No self-serve billing yet. Early customers start with a free workflow trial, then convert through a manual invoice or payment link while we learn which plans deserve automation.

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

From $3k

We help turn messy docs into 3 approved workflow files, exports, and a handoff call. Includes 30 days of access.

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.

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.

Can I delete uploaded files?

Yes. You can delete an uploaded file from the workspace, and the product removes both the stored file and its matching source record. See our privacy and data handling page for the current beta scope.

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.

Who should test this first?

Real estate brokerages, staffing and recruiting agencies, marketing and creative agencies, and small ops-heavy firms with one repeat workflow are the best early testers.

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

We are looking for design partners with one painful workflow to turn into an approved agent contract. Pricing exceptions, refunds, escalations, rollback rules, listing procedures, recruiting intake, and creative approvals are the best fit right now.

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.