WorkpaperOS Audit: Governed Evidence Sync

What the company appears to be: WorkpaperOS Audit is a self-reported tool for audit teams that synchronizes evidence from OneDrive and Google Drive into a governed "Engagement Files" boundary. It uses Codex MCP tools and GPT-5.6 to manage file synchronization, conflict resolution, and evidence organization within an audit context.

What changed: The project evolved from an early cloud-sync foundation into a production-ready evidence workflow during OpenAI Build Week, with a focus on controlled synchronization that preserves working files while enabling governed evidence management.

Single most important open question: Is there any evidence of actual audit team adoption or usage beyond the developer's own account?

The description states that WorkpaperOS Audit is "a governed OneDrive/Google Drive evidence sync for audit teams". It provides a controlled synchronization boundary for engagement files, with:

• Recursive folder and file synchronization
• Stable-identity rename and move reconciliation
• Trash, restore, and permanent-delete workflows
• Exact-content checkpoints
• Conflict protection that avoids silently overwriting either side
• Preserved PBC request folders and evidence relationships
• Codex MCP tools for finding, organizing, mapping, and linking synchronized audit evidence

The system is described as being built with GPT-5.6 in Codex during a hackathon period, using technologies including Next.js, PostgreSQL, Supabase, TypeScript, and Microsoft Graph/OneDrive API.

Evidence: The author's own write-up.

Inference: This appears to be a file synchronization tool designed specifically for audit workflows, with built-in governance features to prevent accidental inclusion of private working files in audit records.

The description states that WorkpaperOS Audit was originally an "early cloud-sync foundation" and evolved into a "governed, production-ready evidence workflow" during OpenAI Build Week.

It positions itself as not just generic file synchronization but as a tool specifically designed around:

• Audit evidence boundaries
• PBC requests
• Folder provenance
• Conflict safety
• MCP actions constrained to the same governed subtree as human workflow

Evidence: The author's own write-up.

Inference: The positioning has evolved from a basic sync tool to a specialized audit evidence management system with governance and AI-assisted tools.

The description states that WorkpaperOS Audit is for "audit teams" who work across WorkpaperOS, OneDrive, Google Drive, email, and local working folders.

It specifically mentions that the challenge is to synchronize the right evidence without accidentally sweeping private working files into the audit record.

Evidence: The author's own write-up.

Inference: The target customer is audit teams using cloud storage platforms, with a focus on those needing controlled evidence management within engagement folders.

Not evidenced. The description does not contain any information about pricing, monetization strategy, or business model.

Evidence: None provided.

The system is built using:

• Codex (with GPT-5.6)
• Next.js
• PostgreSQL
• Supabase
• TypeScript
• Microsoft Graph/OneDrive API
• Google Drive API
• Model Context Protocol (MCP)

It was implemented during OpenAI Build Week, with the primary implementation done in Codex using GPT-5.6 for architecture, implementation, debugging, and verification decisions.

The final implementation passed focused cloud-sync and MCP tests, type checking, linting, and a production build.

Evidence: The author's own write-up.

Inference: This is a technical solution built with modern web stack and AI tools, deployed to a production URL (https://audit.workpaperos.com).

Not evidenced. There is no mention of customers, revenue, usage metrics, or any traction indicators beyond the author's own account.

Evidence: None provided.

Not evidenced. The description does not mention competitors or market positioning relative to existing solutions.

Evidence: None provided.

• Single-person team: Only one member listed (Benedict Mbecha), which may limit execution capacity.
• No traction evidence: No customers, revenue, or usage data provided.
• Unverified claims: All statements are self-reported and unverified.
• Limited scope: The tool appears to be a hackathon project with no indication of broader market adoption.
• Unclear business model: No information on how the product will generate revenue.

Evidence: Self-reported description only.

1. What is the actual use case that drove this development? Is it solving a real problem for audit teams?
2. Have you conducted any user testing or feedback sessions with actual audit professionals?
3. How do you plan to monetize this tool, and what pricing model are you considering?
4. What is your roadmap beyond the current MVP?
5. Are there any existing partnerships or pilot programs with audit firms or professional services organizations?