Start it alone. Open it to a team later.
Nothing to configure on day one. On the day you hire, the team gets a shared workspace beside your own.
Build the product, not the system that tracks it.
An hour spent designing schemas, naming statuses, or tidying boards is an hour not spent shipping. Write the bug, the decision, or what is left before launch, then get back to work.
Other apps
Before you can write:
- Design the workspace first
- Decide where every kind of note belongs
- Define properties and relations
- Name statuses and workflows
- Build the views and filters
- Maintain the setup as the work changes
- Rebuild the parts that stop fitting
Then you can start the work.
Bricknote
Nothing.
Open a note. Write down what matters. Get back to building.
Let the work tell you how to organize it.
On day one, every category is a guess. Build the system too early and you spend the next month deciding where notes belong instead of using them.
Start with the Inbox. When pricing keeps coming up, create a Pricing project and file those notes as you go. Structure follows real work, so it stays useful.
Before you start a project in Bricknote.
No. Start one new project in Bricknote and leave your archive where it is. You can decide what else belongs here after you have used it for real work.
The note lands in your Inbox and stays fully searchable. File it later, or leave it there. Both workflows work.
Cmd/Ctrl+K searches note and project titles in the workspace you are using. From the same palette, you can open a result, jump to a project, or create a new note.
Yes. Account settings includes a self-service JSON export of your account data, so you can download it without contacting support.
Yes. You can capture, read, edit, search, and organize notes on mobile. The full writing experience is designed primarily for a computer.
Start with the project in front of you.
Create your free personal workspace and capture the first note. Bring over no archive. Build no system. Add only the structure you need.