Help new users get one real win fast.

Cadenva works best when the first run is narrow: open one workspace, connect Google Calendar, process one meeting, approve one action, and confirm the event exists. This page is the short path back to that flow.

Quick start

1. Open one workspace Use the sample workspace if you want a safe first look, or unlock your team workspace on the device you are using.

2. Connect Google Calendar Do this once for the selected workspace so approved actions can become real calendar events.

3. Add context Upload a recording, or use imported notes if you want a faster demo path before handling real audio.

4. Approve one action The product proves itself when one commitment survives the meeting and turns into scheduled follow-through.

Common issues

Workspace access expired Reopen the sample workspace or unlock the team workspace again on the current device. The app no longer assumes anonymous shared access.

Google Calendar connection failed Retry the connect flow. If a popup feels blocked or cramped, open the workflow in a full browser window and complete Google auth there.

The extraction feels too thin Use clearer audio, then review the richer action, risk, decision, and open-question sections. For a fast demo, import written notes instead of audio.

No event was scheduled Check that Google Calendar is connected, load the approval queue, and approve at least one action that is ready to schedule.

Best App Review demo path

Stay narrow Open the sample workspace first. That path avoids unnecessary setup and shows the product shape quickly.

Use notes if audio slows you down The memory import path is a valid way to show workspace context and workflow usefulness without relying on a fresh recording.

Prove one outcome The best demo is still one approved action becoming one real calendar event, not a long tour of every screen.

Support philosophy

Cadenva is still in a focused pilot stage, so support is intentionally practical: make the first run obvious, make failures visible, and remove developer-looking setup wherever possible. If the product starts feeling like tooling instead of a workflow, the right move is simplification, not another settings panel.