VZU Sheets .
Spreadsheet-as-API. Build, validate, query.
Capability
VZU Sheets
12
Engineers
VZU Sheets is the data capability in the VZU family — spreadsheet-as-api. build, validate, query. Operated by Virtual Zero Unbound Inc. (Vancouver), Plex Dubai (MENA), and Wahix (India). Ships on the NetWit Agentic OS runtime. SOC 2, HIPAA, ISO 27001 posture. Audit trail by default. RBAC at the agent level.
The position
Spreadsheets, engineered.
VZU Sheets is the spreadsheet-as-API practice. The spreadsheet is the most-used data tool in the world. The spreadsheet is also the most-misused data tool in the world. VZU Sheets treats the spreadsheet like a database: type-checked, validated, queryable, auditable.
We do spreadsheet engineering. We do spreadsheet validation. We do spreadsheet-as-API. We do spreadsheet-to-database migrations. The output is a spreadsheet that doesn't break, a validation report, a queryable API, or a migration path. The work is the spreadsheet. The work is the data. The work is auditable.
VZU Sheets engineers are senior. They have shipped spreadsheets at scale. They know the formula patterns. They know the data patterns. They know when the spreadsheet is the right tool and when it's the wrong tool. They know that the right answer to "should we use a spreadsheet?" is sometimes "yes" and sometimes "no." The data is the work. The data is auditable.
The practice, in pictures
Three things we get right, every time.
Production The proof
BookFlow financial reconciliation. XLSX-based reconciliation.
XLSX-based financial reconciliation for the BookFlow platform, including the booking ledger, the Stripe payouts, the refund queue, and the tax export. Built by VZU Sheets in 3 weeks.
- → Type-checked headers with validation rules
- → Reconciliation against the booking ledger + Stripe payouts
- → Refund queue with status tracking
- → Tax export with jurisdiction-aware rules
-
3
Weeks to ship
-
100%
Reconciled
-
0
Spreadsheet errors
-
Daily
Auto-refresh
The engagement
How we work, end to end.
- Format
-
XLSX + CSV
XLSX for the engineer. CSV for the operator. Both. The format is the contract.
- Validation
-
Type-checked headers
Every column has a type. Every type has a validator. The validator runs on save.
- API
-
Queryable
The spreadsheet is a database. You can query it. The query returns JSON. The query is auditable.
- Versioning
-
Git-tracked
Every change is a commit. Every commit has a diff. Every diff has a review.
- Migration
-
To Postgres when ready
When the data outgrows the spreadsheet, we migrate it. The migration is auditable.
Long-form essay
VZU Sheets.
A working essay.
Why the spreadsheet is the operator's daily reality. Why the sheets API is the work. Why the senior engineer with the audit trail is what ships the sheets that ship the report.
Chapter 01 · The brief
A sheets API, not a macro.
VZU Sheets started with a brief from a financial services operator in Vancouver. 200 staff. 4,000 spreadsheets. A macro that had been built in 2014, never refactored, and was now running the operator's daily close. The operator's close took 4 hours. The operator's close was 12% error-prone. The operator's CFO spent 30% of their time on the close.
The brief from the operator was specific: ship a sheets API. A versioned schema. A test harness. An audit trail. A sheets API that the operator's finance team could rely on. A 6-week ship. A 12-month payback on the close cost reduction.
The hardest part wasn't the spreadsheets. The hardest part was that the API had to be the operator's API — not VZU's API. The schema, the tests, the audit. The operator owns the goal. VZU ships the work. The API is the operator's posture: unbound.
Chapter 02 · The work
Versioned schema. Type-checked. Queryable.
The work is the senior engineer who has shipped 50+ production sheets APIs. The work is the engineer who knows the difference between a macro and an API. The work is the engineer who writes the versioned schema, the type check, the query interface, the audit trail.
We build the API on the operator's spreadsheets. The API is auditable. The API is the record. The API is the work.
We ship in three passes. The first pass is the foundation — the schema, the type check, the query interface. The second pass is the migration — the 4,000 existing spreadsheets are versioned, typed, and audited. The third pass is the polish — the dashboard, the alert system, the documentation. The output is a working API. The API is auditable. The API is the work.
“The spreadsheet is the operator's daily reality. The sheets API is the work. The senior engineer with the audit trail is what ships the sheets that ship the report.”
— VZU Sheets, run #1
Chapter 03 · The result
6-week ship. 4k sheets. 4hr → 18min close.
The API shipped in 6 weeks. 4,000 spreadsheets versioned. Schema check on. The close went from 4 hours to 18 minutes. The error rate went from 12% to 0.3%. The CFO's close time went from 30% to 5%. The payback was 8 months.
The API is now the operator's primary financial surface. The API is the operator's first impression. The API is the operator's first sale. The API is the operator's posture.
The brief expanded. VZU Sheets now runs as a weekly iteration for the operator. Every week, new sheets are versioned. Every week, the type check runs. Every week, the operator's API is the operator's API. The sheets are the work. The runtime is the engine. The work is the work.
18min
close · 4k sheets · 0.3% error rate
Chapter 04 · The why
Why the spreadsheet is the operator's daily reality, not the engineer's.
VZU exists because the seam is the work. VZU Sheets exists because the spreadsheet is the work. The spreadsheet is what turns a brief into a posture. The spreadsheet is what turns a posture into a destination. The spreadsheet is what turns a destination into a legacy.
VZU Sheets is a senior practice. The engineers who do the work have shipped 50+ production sheets APIs. They have reduced close time from 4 hours to 18 minutes. They have reduced error rate from 12% to 0.3%. They write the code so the operator's API is the operator's API.
VZU Sheets is fixed-fee, fixed-scope, audit-first. The brief is the contract. The work is the work. The runtime is the engine. The audit trail is on from the first character. The seam is the work. VZU ends the seam.
The VZU Sheets practice
The work, in motion.
Every brief becomes a working product in days. Every product is engineered for the long term — clean architecture, real audit trails, real operators in the loop. The VZU Sheets practice at VZU is built on senior engineering, the NetWit runtime, and a refusal to ship anything we wouldn't put on a public domain.
The VZU family