Verso Day 23 — why we are designing a Universal Object Model even though the product already works
Day 23 of building Verso (projectoye.com) — a workspace OS replacing your fragmented tool stack with one AI-native environment.
Today was direction-setting. Had a conversation with a co-founder about where the product goes next — and landed on a concept we are calling the Universal Object Model.
The question that started it: Verso has Notes, Spreadsheets, Presentations, Forms, Canvas, Folio — all working, all real-time. But each one is its own island. What if they were not?
What the Universal Object Model enables:
Search across everything from one place — not just your notes, not just your spreadsheets. Everything in Verso, one search.
Cross-tool linking — link a row in a spreadsheet to a note, a form response to a canvas element, a presentation slide to a document section.
AI with full workspace context — instead of AI that only knows about the document you have open, AI that understands your entire workspace and can draw connections across tools.
The product already works. The UOM is what makes it a platform.
Curious — do you think cross-tool linking is something people would actually use day to day, or is it a power-user feature?
Replies