Company profile · 3 min read
Callback is an auditable model harness for complex business operations
Callback orchestrates long-running operational workflows across ERP, CRM, HRIS and other systems with permissions, versioning and exception review.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Callback fits an operator who needs complex workflows run across existing business systems and wants the process to be auditable, permissioned and changeable.
What it does
Callback describes a model harness for complicated operations. Its current homepage shows workflows across cloud providers, ERP, CRM, HRIS, SAP, Salesforce, Microsoft 365 and on-prem systems. Operators define processes, document tribal knowledge, review exceptions and keep versioned snapshots of how work runs. Callback homepage YC profile
The case material is concrete. Callback describes a logistics workflow that recovered 2% revenue, a regulated financial workflow that increased verification capacity by more than 30%, and an oil-and-gas land-record workflow that screened $15m in lease value. These are company-presented cases, not independent benchmarks.
Why I’d look closer
The useful distinction is process ownership. Callback is not presenting a generic chat interface. It says the workflow remains an auditable system of action, with role-based permissions, versioned process snapshots, exception routing and rollback.
That is the right shape for operations teams where the hardest part is not model output but keeping a long-running process accountable.
The founders’ backgrounds also fit the operating wedge. The YC profile describes Alan Xie’s product work at Microsoft and AWS and Paulo Bautista’s experience managing large delivery and call-center operations.
What could make it the wrong choice
Callback is likely a forward-deployed product. The operator has to define the process, connect systems, document tribal knowledge and decide who can approve exceptions. A company looking for a plug-and-play chatbot may not have the ownership required.
Pricing is not published in the checked sources. The homepage says SOC 2 controls and permissioned execution; procurement should request the scope, audit materials, data boundary and recovery process rather than infer them from the marketing page.
My editorial take
I would shortlist Callback for a company with a costly, cross-system workflow and an operations leader willing to own the process definition. I would not start with every back-office process. Start with one workflow where inputs, exceptions and success are visible, then expand only when the audit trail is better than the old spreadsheet-and-inbox process.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | Auditable AI workflow orchestration for business operations |
| Buyers | Enterprise operations teams across logistics, finance, manufacturing and other sectors |
| Workflow strengths | Integrations, versioned processes, permissions, audit logs and exception routing |
| Pricing | Not published in the checked sources |
| Main fit question | Is there a complex process worth formalizing and continuously improving? |
Sources checked
Callback homepage, YC profile and public case-study material were checked on 2026-09-19.
Cohort context
Callback is listed in Summer 2024. In our 2026-09-18 directory snapshot, 161 of 248 listed companies in that cohort have YC’s primary industry label B2B (64.9%). This is a current-directory comparison, not an original intake count or a performance ranking. Nine-cohort dataset.
Public website snapshot
Observed 2026-09-19T16:16:52.501Z in raw homepage HTML. This records visible metadata and advertised links, not agent execution or product quality.
| Signal | Homepage observation |
|---|---|
| Product description metadata | Observed |
| Canonical link | Observed |
| H1 or H2 heading | Observed |
| Typed structured data | Observed |
| Docs/developer link | Not observed in this response |
| Pricing link | Not observed in this response |
| llms.txt link | Not observed in this response |
| Markdown alternate | Not observed in this response |
Public observations · Collection method. Missing links here do not establish that a capability or file is absent elsewhere.
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗