Design notesWork loopProduct notes
The loop we are designing Clarni around
Why Clarni is organised around one meeting loop, Prepare, Stay Present, Review, and Follow Through, and what each stage is designed to do and never do. Every capability described here is planned.
Clarni is for independent consultants, agency and studio leads, and founder-operators who run many client and project conversations. For them, much of the real work happens in calls and meetings. What was decided, who promised what, and which risk just changed all start life in a conversation, and then scatter across notes, threads, and documents.
The meeting itself is rarely the hard part. The hard part is walking in without knowing what moved since last time, and walking out with a list nobody looks at again. That is the gap we are designing Clarni to close, and it is why the product is organised around one loop rather than a set of separate tools.
Prepare
Before a meeting you select, a Meeting Brief is designed to bring back the decisions and open commitments that matter for it, what changed since you last met, and questions you can edit. Each point is meant to carry its source.
We want the brief to stay short. It is not a recap of everything that ever happened, and it is not written for you as a story: what changed is designed to be a comparison of the current record with the record you last saw. When there is little or no record for a meeting, the brief is designed to say so and leave room for you to add context by hand, rather than fill the gap with something plausible.
The brief is designed never to write to your calendar, send an agenda, or build a profile of the people in the meeting.
Stay Present
During the meeting, your own notes come first. The notes canvas is designed to work with manual notes alone, and typing is designed never to wait on AI. Context you ask for, or pin, is meant to sit beside your notes with its source, so you can check a point without leaving the conversation.
Anything you insert is designed to become part of your notes, still showing where it came from and still yours to change. There is no meeting bot and no passive recording in this picture.
Review
When the meeting ends, what came out of it is designed to wait for you as proposals. You are meant to decide what becomes a decision, a commitment, or a task. Until you approve it, nothing is designed to become a record, and no record or other system is meant to change.
We hold this line on purpose. Suggestions about who owes what are designed to be proposals you review first; the product is designed not to assign obligations to anyone without that review.
Follow Through
Work you approve is meant to move forward with its proof attached: each item pointing back to where it was said or written. Drafts of follow-ups are meant to stay yours to edit, and nothing is designed to go to an email, chat, or document system without your explicit confirmation immediately before it happens.
Why a loop
The four stages are meant to hand over to each other. The brief compares the current record with the one you last saw; review is the one place that record is designed to change, and only with your approval. Each turn of the loop is meant to leave the next meeting better prepared than the last.
That is also why we describe Clarni by outcome rather than by feature: work moves forward when nothing important gets lost.
Where this stands
Clarni is in development, and every stage described here is planned. This is design intent, not something you can use today, and no date is promised. The labels beside this article show the status of each capability it describes.