For Principals running portfolios Mac · 15+

Your meetings
finally have a memory.

One quiet companion that remembers what was said three weeks ago, what's still open, and who owes what.

Your meetings finally have a memory.

Seriesly listens to your recurring meetings, then briefs you before the next one — who's waiting, what changed, what's still open.

Download for Mac ↓ See it work →

Pulled from three prior 1:1s, automatically. The next move, drafted before you walk in. Linked sources stay on your machine.

Seriesly · 1:1 with Sarah Chen

Today · 13:00 · 30 min·Brief auto-prepared

Sarah is still waiting on you.

Three weeks running. Pricing call for the Q3 enterprise rollout.

Open loop She brought up the pricing call with Lina in your last 1:1 (Apr 21) and the one before. Sarah is blocked.

Last said Sarah: "Let's revisit once we have the discount band signed off — I'll wait."

Changed Q3 rollout target moved to Q4. JIRA · ENT-441, two days ago.

For you Decide on the discount band before this meeting, or set a date with Lina.

Your meetings finally have a memory.

Below is what Seriesly remembered for one director, this morning, before she opened her calendar.

Download for Mac ↓ How it works →

Open loops · this week

07 items · Tue 09:14

21d Sarah is still waiting on the pricing call with Lina. Mentioned in three 1:1s. RECUR

9d You owe Marcus the eng hiring rubric. Promised in Monday standup. OWE

4d Mobile launch slipped to June 14. You haven't told the board yet. DELTA

2d Priya floated a re-org during the all-hands debrief. Worth a follow-up. NOTE

1d Confluence page on Q3 OKRs edited by Jamie — two metrics changed. DELTA

§ The argument

002 / Home

You don't run one meeting; you run a portfolio of them. The 1:1 with Sarah is a thread across months. The pricing review is a thread across quarters. Nobody pays you to remember the threads — they pay you to decide what to do about them. Seriesly is a quiet companion that remembers the threads. It runs on your Mac, listens to your Zoom and Google Meet calls, and keeps everything in a local database on your own machine. The unit is the meeting series, not the meeting. That changes what a notetaker can be.

§ The product

003 / Home

Five surfaces. One chief of staff, distilled.

Brief me before every meeting.

Twenty minutes before your 1:1 with Sarah, Seriesly drafts a single page. What you talked about last time. What she's been chasing across the last three meetings. The JIRA ticket she filed yesterday that you haven't read. The thing you said you'd do and didn't.

It's the briefing a good chief of staff would slide across your desk — except now you have one for every recurring meeting on your calendar, not just the board meeting.

Brief · 1:1 with Sarah Chen · 12:45 today

Drafted 12 min ago·4 meetings · 1 JIRA · 1 doc

Sarah will ask about pricing again.

She has brought it up in your last three 1:1s. Each time, you said "next week."

Threads Pricing rollout (3 meetings) · Hiring her #2 (2 meetings) · Mobile cutover (1 meeting)

She last said Sarah: "I can hold the line for another week, but Q3 enterprise is starting to slip without it."

You promised A decision on the discount band by Friday. Apr 28, end of 1:1.

Net new Lina escalated the same question to you in Slack on Monday. Same thread.

What I'm forgetting, who owes me, what I owe others.

Every commitment you've made in a meeting, every commitment made to you, every question you raised and never answered — held in one ledger and aged. Seriesly is the only thing in your stack that hears the moment Marcus says "I'll have it by Thursday" and remembers on Thursday whether he did.

Open loops · all sources

21d Sarah waiting on pricing call with Lina · 3 meetings SHE OWES YOU

9d Eng hiring rubric for Marcus · promised Monday standup YOU OWE

5d Reply to Priya's re-org floating · raised in all-hands debrief UNRESOLVED

4d Board email re. mobile slip to June 14 · you said you'd send Wednesday YOU OWE

2d Discount band sign-off · escalated to you in Slack by Lina YOU OWE

What changed while I was away.

Two days at a board retreat, a week in Lisbon, a Friday spent in deep work. When you come back, the question isn't "what happened" — it's "what changed that I need to act on." Seriesly diffs your portfolio across the gap and writes the memo.

Delta · You were away May 5 → May 9

Before — last Friday

Mobile launch targeted June 7. Engineering tracking confidence at 75%.

Q3 pricing with Lina open since April. Sarah blocking.

Priya mentioned a possible re-org but did not press it.

After — this morning

Mobile launch slipped to June 14. Engineering confidence now 90%.

Pricing: Sarah blocking · Lina escalated direct to you.

Priya circulated a re-org draft to two VPs on Wed.

Catch me up on Sarah, or pricing, or the mobile effort.

A live page per person and per topic, assembled from every meeting they appeared in. What they care about. What they've committed to. Where you last left off. Open in the cab on the way to dinner with them, and arrive primed.

Person · Sarah Chen · Head of Enterprise

Sarah Chen

14 meetings · since Aug 2024

Sarah is currently most blocked by the open pricing question with Lina. Her team's Q3 enterprise pipeline depends on the discount-band decision; she has raised it in three consecutive 1:1s and once over Slack. She tends to surface concerns indirectly — listen for "I can hold the line." Cares about: her team's autonomy, the mobile cutover, hiring her #2.

Apr 28 Last 1:1. Pricing surfaced for the third time. You committed to a decision by Friday. Apr 21 Joint review with eng leadership. She agreed to wait on mobile cutover until June. Apr 14 1:1. Floated her interest in hiring a deputy. You said yes but didn't open the req. Apr 03 Strategy off-site. She pushed for the Q3 enterprise plan; got reluctant buy-in.

Spike a question across every source.

Calendar, JIRA, GitHub, Confluence, Google Docs, your Obsidian vault — and every meeting you've ever had. One question, every source, with quoted citations back to the moment something was said. The answer is grounded in what's on your machine, not what a model thinks the answer should be.

Research · spike

When did the team first agree the mobile launch could slip past June 1?

Searched · 41 meetings · 12 JIRA · 6 Confluence · 19 docs

MTG · Apr 02 "Honestly, June 1 was always the optimistic case. I'd plan for the 14th." — Marcus, eng leads sync, 14:32

JIRA · MOB-204 Target date silently changed from Jun 01 → Jun 14 by Jamie, two days after that meeting. — Apr 04 · no comment thread

DOC · OKR Q2 OKRs document edited: "ship mobile by Jun 01" → "ship mobile by mid-June." — Apr 11 · Sarah Chen

§ A Tuesday

004 / Home

Eight forty-three a.m. The board retreat ended Friday. You open the laptop and there is a small notification on the menu bar that says three deltas worth knowing about. You read them in ninety seconds.

Nine fifty-five. Your 1:1 with Sarah opens in five minutes. The brief is already on screen. You see the line about pricing — third time she's raised it — and you make a decision before she has to ask.

Three p.m. Mobile launch review. You open the topic brief on the way in. It tells you the launch slipped four days, and that Marcus had already said it would, twelve days ago, in a meeting you didn't attend. You stop interrogating the date and start asking better questions.

Six p.m. You close the laptop. There were thirty-one things you could have forgotten today. You forgot none of them, because you were not the one remembering.

how a director used Seriesly, last week

§ The shape

005 / Home

It lives on your machine.

Storage

Local first.

The database is a SQLite file on your disk — FileVault is the layer that encrypts it at rest. The audio is captured by the Mac you're already using; transcription runs on-device when you ask it to. Nothing about your meetings sits on someone else's hard drive by default.

You can open it.

It's a file. You can move it to another Mac, back it up, or open it with the SQLite tools you already have. Seriesly does not own your data the way a SaaS does.

Shape

Single player today.

Seriesly is for the one principal whose context this is. There is no team workspace, no shared folder, no admin console. That is intentional — the loops in your head are yours.

Sync, when it comes.

Multi-device sync is the v2 question. When it arrives, it will be end-to-end encrypted across your own devices and nowhere else. You will get a clear month's notice before anything changes.

Reach

Mac, by design.

Seriesly is built for macOS 15 and later, on Apple silicon. The audio capture, the menu-bar daemon, the on-device models — all native. The app is fifty megabytes; it boots in under a second.

The other places.

It reads from Google Calendar, JIRA, GitHub, Confluence, Google Docs, and your Obsidian vault — through APIs you connect, on credentials you own.

Set sail

The next meeting remembers itself.

Open it once. Connect the calendar. Run a 1:1. By the next one, the brief will be waiting on your desk.

Download for Mac · v0.7.2 ↓ See pricing →