// notes — documents
designed — not builtNotes that belong to something.
Nothing of Notes is built yet — this is the design, published as it stands. The idea it is built around: a note is not a loose page. It hangs off the client, the deal or the proposal it is about, and from that record you see its notes.
the idea
The editor is not the point.
// Designed, not built. Every line below is a plan.
- Pages with blocks — text, headings, lists, checklists, callouts — in folders, with tags and search
- A typed link to the records that already run the business: a client, a deal, a project, a proposal
- From the record, its notes. From the note, the record. The knowledge stops living in someone’s private doc
- Author and last edit, so a shared page has a person behind it
why it is last
A backlink needs something to link to.
It depends on the others
The value is the link to clients, deals and proposals. Building it before those records exist would produce a notes app — which the world does not need another of.
The design is done
Requirements, screens, data model and decisions are written and reviewed. What is missing is the building, and saying so is cheaper than pretending otherwise.
No date, on purpose
The modules that clients are waiting on come first. A date we would move twice is worth less than an honest “not yet”.
What it does NOT do yet
Read this before anything else on this page:
- No code has been written. There is no Notes module in the product today.
- What exists is the design — requirements, screens and decisions, written and reviewed.
- There is no date. Notes is last in the build order, on purpose: it depends on records the other modules create.
- Everything below is written in the future tense because all of it is future.
// what is real today
Two modules are in production.
Miira answers WhatsApp leads and Kiipu collects. If you want to see what niiko actually does today, start there.
See Miira →