Papyrus by Beag Labs

Backofficesuperintelligenceharness.

A deployable AI execution platform that enables organizations to automate complex back-office operations across existing systems of record using configurable data models, durable agents, human approvals, and governed workflows.

Papyrus solution brief · 4-page PDF

Marketing emails

One email with the PDF · No spam

Get started with commercial →

Model the business. Orchestrate the process.

Enterprise Classes

Define entities and source identities spanning subsidiaries, finance systems, documents and legacy records.

Existing systems of record

Preserve Dynamics 365, Odoo, NetSuite, mainframes and other authoritative applications; connect only the permitted operations.

Durable agents and workflows

Run multi-stage operations with checkpoints, error handling, human approval and governed writes.

Forms and integration tools

Build purpose-fit interfaces with model-aware workflows, MCP tools and scoped system connections.

Inside Papyrus / Guided interface preview

Define your Classes. Design your workflows.

A product-derived walkthrough using Papyrus’s actual Class editor field types, drawer terminology, and Workflow Designer inspection semantics. Example data is illustrative; no live environment is connected.

PPapyrus
Demonstration data

Classes / Define

Vendor Invoice

Model an invoice linked to a vendor and legal entity.

DRAFT

New class

Set the class name, field types, and record statuses.

Name

Vendor Invoice

Title field

vendor_name
Fields
Add field
Vendor name
vendor_name
Short textRequired
Legal entity
legal_entity
Link to recordRequired
Invoice total
invoice_total
NumberRequired
Source system
source_system
Short textOptional
Approval status
approval_status
Short textOptional
DraftReviewPosted
Schema migrations require governance
Create class

Illustrative sample records · Interface reconstruction from Papyrus source · Animation respects reduced-motion preferences

See it work

Every part of the harness, live.

These are working demos on sample data. Click through them: edit a policy in plain English, approve an agent's write, inspect a Class, and watch a deployment come up.

01 / Workflows

Policies you can read, edited in plain English.

Approval rules become a canvas of steps with quorums, amount conditions and SLAs. Ask for a change and Papyrus proposes it as a diff; a lint catches unassigned seats and missing controls before anything goes live.

Workflow · Procurement approvals
Trigger · purchase request submitted
Budget owner review1 of 1
ARAlex Rivera
SLA 1 day
Finance review1 of 3
PPPriya Patel
SOSam Okafor
MCMaria Chen
SLA 2 days
Director sign-off1 of 1
if amount > $25,000
Unassigned seat
SLA 3 days
Post to ERP

Green: added · orange: changed · dashed red: removed

Ask for a change

02 / Action ledger

Agents propose. People approve.

Every write to a system of record arrives as a field-level diff with the agent's reasoning. Approval releases it to an executor and adds it to a hash-chained record.

Action ledger · proposed write

Proposed by the AP agent · awaiting Papyrus.Action.Approve

Create vendor bill VB-20931 in NetSuite

FieldBeforeAfter
VendorAcme Supply Co.Acme Supply Co.
Legal entity∅Beag Holdings East
Amount∅$18,240.17
Matched PO∅PO-7741
GL account6100 · Supplies6120 · Facilities supplies
Due date∅Nov 20, 2026
AI

Three-way match passed. PO-7741, receipt GR-1180 and the invoice agree within $0.42. GL moved to 6120 because the PO line is facilities supplies.

Approver: Maria Chen
  1. A-2203 Update vendor terms · NetSuite · Priya Patel prev 00000000 → 4d22dd9e
  2. A-2204 Create receipt · Dynamics 365 · Sam Okafor prev 4d22dd9e → 71f57482

03 / Classes

One record, every system.

Classes are your own record types. Each one maps to the source records that hold it, so agents and people work with one Vendor instead of four.

Class · Vendor
1,284 records · synced 2 min ago

Acme Supply Co. is one Vendor in Papyrus and four records in the systems that hold it.

  • Dynamics 365Vendor account · read + writeV-00118
  • Oracle NetSuiteVendor internalId · read + write4518
  • Mainframe APVENDOR NO · read · writes via approval004518
  • SharePointVendor folder · read/Vendors/Acme

04 / Deployment

One codebase. Three ways to run it.

Commercial teams run the hardened image in their own AWS or Azure account. Government cloud and DoD installs run the same build inside your boundary, with offline licensing and no callback to us.

Deploy · papyrus
▌

Evaluate the real workflow

Bring the real systems, entity model, source permissions and exception cases. Validate a Class definition, inbound record sync, a scoped action, human approval, replay and a successful authorized system-of-record update. Integration availability and implementation effort depend on the customer's environment.

Request a technical walkthrough →