The issue is rarely the cap table. It is the path around it.
The VSOP sheet says who should receive how many virtual units. The signed letter lives in Drive. People knows the leaver, finance knows the pool, founders remember the promise.
At the next financing round, the current total is not enough. The useful answer is the history: which allocation, which document, which return, which source.
The sheet says yes. The document is missing.
Allocations are promised faster than they are documented. Flowers keeps the transaction and document together.
A leaver triggers another manual calculation.
Unvested units belong in the history as a return, not as a cell comment.
Investors ask for history.
A current total is weak when the source of each movement is unclear.
From allocation letter to ledger
- Select template: allocation letter or framework agreement
- Collect grant data: beneficiary, amount, vesting, strike price
- Generate document: approved variables are filled from structured data
- Signature and archive: the result stays attached to the transaction
- Write ledger entry: allocation, pool event or return with source and status
What the VSOP ledger captures
Flowers does not only store a number. Each movement gets context, status and source.
- Transaction type and status
- Effective date and source
- Employee context and role
- VSOP delta and pool delta
- Vesting, cliff and rhythm
- Leaver type and return
- Document source and signature status
- Workflow link and comment
Cap table tools and Flowers do different jobs.
Cap table tools
Strong for ownership structure, stakeholder portals, financing rounds, reporting and equity-specific administration.
Flowers
Strong in the operating process: template, allocation, signature, people context, leaver return and auditable transaction history.
If you use Ledgy, Carta or Pulley, Flowers does not have to replace them. Flowers closes the operational gap before and around that system.
Already proven as an internal Flowers process
- Internal ledger for pool events, allocations and returns implemented.
- Allocation letter prepared with 16 verified template variables.
- HR document process extended with a VSOP path.
- Historical source rows backfilled with provenance markers.
Your advisors define the framework. Flowers executes it.
VSOP work is legally and tax sensitive. Flowers is not legal or tax advice. Framework agreements, leaver clauses and tax treatment remain with your advisors.
Flowers makes sure the agreed process runs the same way each time: correct template, correct data, correct archive, correct transaction history.
Frequently asked questions
What is VSOP management?
VSOP management keeps virtual participation operationally clean: allocations, vesting, returns, documents, status and sources are captured in a traceable process. Flowers gives this work a workflow and an auditable transaction history.
Does Flowers replace a cap table tool?
Not as a blanket claim. Cap table tools are strong for ownership structure, stakeholder portals and equity reporting. Flowers closes the operational gap around allocation workflows, document templates, signatures, people/leaver context and ledger evidence.
How does Flowers create allocation letters?
The approved template lives in the document template list. The workflow collects the required data and fills the approved variables. The signed result stays attached to the transaction.
What happens with leavers and unvested shares?
Returns are not just notes in a spreadsheet. Flowers can capture them as their own ledger transaction with exit date, leaver type, unvested amount, return and source.
Can existing Google Sheets be imported?
Yes, existing sheets can be the starting point. The important step is a clean backfill: every row needs a source, a status and a clear meaning so the ledger does not become another unclear spreadsheet.
Is Flowers legal or tax advice?
No. Your lawyers and tax advisors define the framework. Flowers helps your team execute and document the agreed process consistently.
Who is the process built for?
Founders, CFOs, finance, people and operations teams in startups and scaleups that no longer want to manage VSOP allocations across disconnected spreadsheets, Drive folders and Slack messages.
What does the transaction history store?
For example transaction type, status, effective date, VSOP delta, pool delta, vesting data, leaver information, document status, source and workflow reference. Sensitive fields are permissioned per company setup.
Bring your VSOP spreadsheet.
We show which allocations, returns, documents and process steps become a Flowers workflow.
Analyze your VSOP process