Why we built Cantuva

The problem we kept hitting

Most knowledge work still lives in a pile of tabs. A brief sits in a doc, a diagram lives in another tool, a sticky note hides in a chat thread, and a Loom waits in an inbox that nobody opens twice. Each app is fine on its own. Together they fracture attention. You spend more time reconstructing context than making decisions.

We felt this while shipping product. Design reviews jumped between Figma, Notion, and Slack. Engineering plans lived in tickets that drifted from the whiteboard photo someone took last Tuesday. The “source of truth” was whichever window was open last. When a teammate joined mid-project, onboarding meant a guided tour of five products and a shrug.

That fracture has a cost. Meetings expand to rebuild shared understanding. Decisions get re-litigated because the rationale lived in a voice note someone forgot to link. Async culture sounds good until the artifacts cannot stand alone.

What a visual workspace should feel like

Cantuva started from a simple bet: teams think spatially. They cluster ideas, draw arrows, leave notes beside a sketch, and rearrange when the story changes. An infinite canvas is not a gimmick when it matches how people already work on paper and whiteboards.

We wanted one surface where documents, notes, diagrams, and lightweight boards could coexist without forcing a single rigid format. Zoom out for the whole initiative. Zoom in for a paragraph. Keep the same URL when a teammate joins later. The canvas should feel calm under pressure, not like a novelty that collapses when a real project arrives.

That meant investing in foundations people rarely celebrate: stable selection, reliable pan and zoom, history that does not surprise you, and cloud workspaces that feel like home instead of a sync experiment. Flashy launch features are easy. Trust is harder.

Building in public from day one

We chose to build in public because early users catch assumptions faster than we do. Shipping on a visible cadence meant saying no to feature theater. If something did not help a team leave a session with clearer next steps, it waited.

Building in public also forced honest language. We write about what shipped, what slipped, and what we are still unsure about. That transparency is not a growth hack. It is a forcing function for product quality. When you explain a trade-off in public, you are less likely to ship a compromise you cannot defend.

Community feedback shaped TalkTrack, team invites, and how we think about presence on a shared board. The best comments were rarely “add more buttons.” They were stories about where context still leaked out of the workspace.

Where we are headed

Cantuva is still evolving. TalkTrack helps walkthroughs stay attached to the work. Team workspaces make ownership and membership explicit. Realtime collaboration continues to deepen so co-editing feels natural without turning the canvas into chaos.

The north star has not changed: reduce the cost of shared understanding. Tools should shrink the distance between “I think I get it” and “we can act.” Everything else is secondary.

If your work still lives across too many tabs, try Cantuva and tell us what still feels heavy. We are building this with you — and we would rather hear the sharp critique early than polish the wrong surface.