A simple notes system for founders

What a founder's notes system needs to do

A founder's week is customer calls, investor meetings, hiring conversations and a stream of decisions, most of them made in a hurry. A notes system for that life has one job: let you look up what someone told you and what you decided, months later, in under a minute.

The system in this post fits in any notes app. It has three note types (conversations, decisions and ideas), one naming pattern for every note, and a weekly review that keeps it from turning into a pile. You can set it up this afternoon.

Why memory isn't enough

You'll be sure you remember what the pilot customer asked for. You probably don't. A review of research on memory for conversation found that after a short delay, people may recall from memory fewer than 20% of the specific ideas that were originally expressed (Brown-Schmidt & Benjamin, 2018). Most of those studies looked at everyday conversations, not sales calls, but there's no reason to think a founder juggling six calls a day does better.

The cost shows up later: a feature built on a request nobody made, an investor update that contradicts what you told them last quarter, a decision reopened because no one remembers why it was made.

Note type 1: conversations

One note per conversation. Customer calls, investor meetings, advisor chats, candidate interviews. Write it during the call if you can, and finish it in the five minutes right after, while the context is fresh.

• Who, their role, and how you know them.
• What they said, with the important phrases in quotation marks. "We re-enter every order by hand" is worth more than "pain with data entry".
• What they asked for, or agreed to.
• Your interpretation, kept separate under its own line, so you can tell later what they said from what you concluded.
• Follow-ups, each with a date.

Note type 2: decisions

A short note each time you decide something you might need to explain later: pricing changes, a hire, dropping a feature, choosing a supplier. It takes two minutes and saves a long argument.

• The decision, in one sentence.
• The date and who made it.
• Why, including the conversation notes that informed it.
• Options you considered and rejected, and why.
• When to revisit it, if ever.

The rejected options are the part people skip and later wish they had. Six months on, someone will suggest the thing you already ruled out, and the note tells you whether the reason still holds.

Note type 3: ideas

Ideas arrive in the shower, on a walk, halfway through a call about something else. Give them one note, an inbox, and add a line each time: the idea, the date, and where it came from. Don't organize it. The weekly review does that.

Name every note the same way

Most of the value of a system comes from naming. A useful pattern is date, type, then who or what:

• 2026-10-22 call, Dana Ruiz, Harbor Logistics
• 2026-10-22 decision, annual plans only for pilots
• 2026-10-22 investor, Sam Lee, seed follow-up

Putting the date first in year-month-day order means notes sort in time order in any app. Research data guides recommend the same: Carnegie Mellon's library advises that dates should always be yyyy-mm-dd to organize files chronologically, and warns that a naming convention breaks down if not followed consistently (Carnegie Mellon University Libraries). Pick a pattern and keep it. A messy pattern you always use beats a clever one you use half the time.

The thirty-minute weekly review

Once a week, same time, go through the week's notes in this order:

1. 1Follow-ups: scan every conversation note from the week. Anything not yet done goes on your task list with a date.
2. 2Patterns: did two or more customers say something similar? Write one line in a running "what we're hearing" note, with links to the calls.
3. 3Decisions: did you decide anything without writing it down? Write it now.
4. 4Ideas inbox: for each line, either delete it, turn it into a task, or leave it for next week.

The review also clears your head. In a set of experiments, unfinished goals caused intrusive thoughts during unrelated tasks, and letting people make specific plans for those goals eliminated the interference (Masicampo & Baumeister, 2011). Turning a loose follow-up into a dated task is that kind of plan.

What to skip

• A tagging scheme with dozens of tags. Dates, types and names do most of the work.
• Folders inside folders. Search finds names faster than you can click through a tree.
• Templates for every meeting type. The conversation template covers almost all of them.
• Migrating everything to a new tool every few months. Consistency matters more than the app.

Making your notes searchable later

The real test of the system is a question like "what did pilot customers say about onboarding?" three months from now. Good names get you to the right notes. Reading them still takes time.

That's the problem Lumyo is built for, for founders and teams as well as students. You can dictate a conversation note right after a call, each note gets a summary and a category automatically, and you choose which notes a chat reads. Answers cite their sources, so tapping one opens the exact line a customer said. For more on finding what was said in a call, see how to find what was said in a meeting or customer call.