Invitation only · first cohort

Keep the reason with the work.

ClippyNote is one workspace for your team's pages, databases and decisions. Every row opens into a page.

Your project lives in four places.

A chat for the decision. A doc for the plan. A sheet for the dates. A tracker for the status.

Three of them are already wrong.

The launch moved in chat. The doc, the sheet and the tracker never heard about it.

ClippyNote clips it together.

The decision, the reason, the tasks and the history. One page that stays current.

Docs can't count. Sheets can't explain. Chat can't remember.

So the reason behind a decision ends up three tools away from the work it changed.

A row is a page.
A page can hold a database.

Write the reasoning and track the work in one place. Open any row and the whole story is there.

Atlas relaunch/Decisions
DORKAL

Decisions

4 rows · Table

Table Board Calendar
  • Open any row without losing your place.
  • Properties on top. Status, owner, dates, linked tasks.
  • The story below. Reasoning, comments and history.

One database. Every way to look at it.

Switch views without copying anything. The rows, filters and permissions stay the same.

Also calendar, chart, form and feed

  • Homepage copyDoneDO22 Oct
  • Checkout QA retestIn progressRK9 Nov
  • Arabic pages reviewIn progressAL10 Nov
  • Analytics eventsDoneRK28 Oct
  • Launch emailNot startedDO12 Nov
  • Go liveNot startedRK12 Nov

Fields that do the work.

Relations, rollups, formulas, sub-items, reminders and automations, on rows that still have room for the story.

ProjectAtlas relaunchA row, and a full page
Relation6 tasks4 decisionsLinks rows across databases
Rollup2 of 6 doneCounts what's linked
Formula41days to launchCalculates from other fields
Sub-items2 openNests work inside work
Reminder12 Nov, 09:00Nudges you on the date
AutomationWhen Done, notify ownerRuns on row changes

Trust you can check.

ClippyNote shows you what a change will do before it happens, and what it did afterwards.

Move in with a receipt.

Bring a Notion export (Markdown & CSV) or your own files. Pages, databases and files come in, with a list of everything that changed on the way.

Settings/ImportExample archive
northwind-notion-export.zip48.2 MB · Markdown & CSV
Completed with warnings
Uploading and importing your archive…
  • Atlas relaunch
  • Decisions4 rows
  • Tasks38 rows
  • Client brief
  • Meeting notes12 pages
  • Team handbook

214 pages 9 databases 386 files

4 changes on import

  • 6 columns were given a type from their values (date, number, select…)
  • 2 images weren't in the archive, so they stayed links
  • A sub-page of a database row was placed beside its database
  • 1 file was skipped: password-protected

Leaving is just as clear. Export every page as Markdown and every database as CSV, with your files and a manifest.

See what a change will do before it does it.

Changing a property's type can empty values. ClippyNote checks a sample first, shows what would be lost, and keeps a version you can restore.

Projects/Change property typeExample data

Change Budget from

Text

to

Number
ProjectBudget nowAfter
Atlas relaunch12,00012000
Harbor appabout 15kEmptied
Lumen brand8,5008500
Q4 researchTBDEmptied

2 of 40 sampled cells can't be represented as numbers and will be emptied.

Converted. A version was saved first.

Before the type changeToday, 11:20 · Dana

“Saved” means the server has it.

If the connection drops, your writing stays on this device and syncs when you're back. Database edits and uploads wait for a connection, and the page tells you so.

Atlas relaunch/Meeting notes, 2 Oct Saved
You're offline. Page edits are saved on this device and sync when you reconnect. Other changes need a connection.

Client call

Agreed to move launch to 12 Nov.

Rami runs the checkout retest on 9 Nov. Amal sends the Arabic copy for review by Friday.

Arabic and English, in the same page.

Switch the interface to Arabic and the whole workspace mirrors. Each block picks its own direction, so mixed notes read correctly. Search works in Arabic too.

Interface language

Launch plan

StatusIn progress OwnerALAmal Latif Launch12 Nov 2026

We're moving launch to 12 November so QA gets one more week.

ملاحظة العميل: الصفحات العربية جاهزة للمراجعة.

Review the Checkout page with Rami on Thursday.

Interface, layout, dates and search work in both languages. Emails are in English for now.

One set of permissions, everywhere.

Search, databases, exports, the API and public pages all check the same access rules. If you can't open a page, it never shows up.

Viewing as
launch⌘K

6 results

  • Atlas relaunch: client briefShared with Client
  • Launch timelinePublished
  • Launch planProduct
  • Launch moves to 12 NovDecisions
  • Launch budgetPrivate
  • Launch emailTasks

Webhooks carry IDs, never page content. Every delivery is signed.

POST /your-endpoint
ClippyNote-Event-Type: record.updated
ClippyNote-Signature: t=1790752761,v1=5257a869…

{
  "id": "01a0f12d-2027-7215-863f-465b41fa8d14",
  "type": "record.updated",
  "created_at": "2026-10-02T08:44:17.544Z",
  "workspace_id": "…",
  "data": { "page_id": "…", "database_id": "…" }
}

Nobody has to ask why twice.

Every decision links to its reason, its tasks, its files and its history. Anyone on the team can follow the thread.

  1. DecisionLaunch moves to 12 Nov
  2. ReasonQA found the checkout bug again
  3. Tasks3 tasks moved to the new date
  4. Fileqa-regression.pdf
  5. History5 Nov → 12 Nov, by Dana

Who ClippyNote is for

Made for agencies consultancies research groups training teams and content teams of 3 to 20 people who already write things down.

Especially if your team works in العربية and English, or is ready to leave another workspace tool.

Straight answers.

What ClippyNote does today, and what it doesn't do yet.

Yes, from Notion's Markdown & CSV export. Pages, databases, row pages and files come in, and you get a list of what changed. Relations, rollups and formulas may need setting up again.

Any time. Export the whole workspace as a ZIP: every page as Markdown, every database as CSV, your files and a manifest. No support ticket.

Partly. Text you're editing on a page or row stays on your device and syncs when you reconnect. Navigation, database edits and uploads need a connection.

Not today. We would rather ship it when it's ready than put it on this page early.

Not yet. ClippyNote runs in your browser and works best on a laptop or desktop.

Not yet. There's no SSO, SCIM or SOC 2 report today. ClippyNote is built for small teams first.

Pricing isn't published yet. Ask us when you request access.

The first cohort is small, and invited.

We're starting with a handful of teams, so the people using ClippyNote can reach the people building it. Ask for a place.