About Tabnook · Joyce Akiko

I had the same problem every day. So I built the fix myself.

Hi, I’m Joyce Akiko. My background is in operations and product. I spend my whole workday in the browser, holding context it refuses to hold for me, and Tabnook is the tool I built to fix that. It stays entirely on your machine.

Free · join the waitlist
Joyce Akiko, creator of Tabnook

The story

Every case lived across a dozen tabs. I was the only thing holding it together.

Here’s my actual day. I work in a healthcare field where the compliance load is heavy and everything happens in the browser. Every case pulls in its own cluster of tabs, so I’m never holding one thing. I’m holding 6 cases at once, and the only place that remembers which tab belongs to which case, and why, is my own head.

That’s the part that wore me down. The number of tabs was never really the issue. It was rebuilding that map every hour, all day, and then losing it completely whenever my computer restarted over the weekend. I’d open Chrome on Monday to a group called pending, 11 tabs inside it, and not one clue about which thread I’d been pulling.

The browser kept the tabs. It threw away the why.

Chrome’s own groups don’t fix that. Close a window and an unsaved group is gone, restart and it can come back in fragments, and even when one survives there’s nowhere to write down the single thing that would make it useful on Monday. It was never about having too many tabs. The context I needed every day had nowhere to live except a memory that gives out exactly when I’m juggling the most.

“I’m not holding one thing at a time. I’m holding 6 cases at once, each one a cluster of tabs, and the only place that remembered which tab went with which case was my own head. I built Tabnook so it didn’t have to be.”
Joyce Akiko
Joyce Akiko Creator of Tabnook

How this happened

It started as a problem I couldn’t stop thinking about.

Nobody assigned this. I had a problem that cost me focus every day, so on my own time I looked into whether other people had it too, sketched what a real fix would need to do, and built it. I held it to the standard I’d hold anything I owned. A backup before every change, staged rollouts, and nothing marked done until I’d verified it worked.

The part I keep coming back to is the friction itself. Most of us learn to live with the small things that quietly cost us an hour a week, until we stop noticing them. Finding one of those, working out exactly why it’s there, and building the thing that removes it is the work I care about most. Tabnook is one I got to carry the whole way, from a daily annoyance to something other people can use.

What I built

Tabnook is the tab manager I needed and didn’t have.

It keeps your tab groups from disappearing when you close them, lets you leave a note on any tab you’ll come back to, and brings a group back on schedule when you snooze it. One search runs across all of it. The features page walks through exactly how each part works.

It started out called Tabby, because I like cats and the name made me smile. Tabnook is the grown-up version of the same idea: a place for the tabs you’re not done with yet. It lives in Chrome’s side panel and stays on your machine, with no account and nothing leaving the browser.

Free · join the waitlist
0network requests made by Tabnook
0accounts required to use it
0third-party dependencies
1click to reopen any saved group

Background

The experience that taught me how to build it.

Experience
10+ years in operations and project management

Teams of 3 to 500. 98% of projects delivered on time and under budget. Project management has been the thread through every role I’ve held.

Previously
Director of Product Management, Presidio

Led end-to-end delivery for a B2B SaaS platform, aligning engineering with the C-suite, and rolled it out to 2,000+ employees with 95% adoption.

Consulting
Fractional COO and operations lead

Six years running operations for fast-growing clients across industries. CRMs, learning platforms, payment systems, and process automation, owned end to end.

Education
MS, Human Resources Development · Villanova

A science degree grounded in data analytics and evidence-based management. BA, Psychology, Ithaca College. The systems thinking came first.

How I build
Operator discipline, applied to shipping software

Backups before every change, staged rollouts, and nothing marked done until it’s verified. The same governance that keeps a project on schedule keeps a build from falling apart.

Results
98% of projects delivered on time and under budget

Across a decade of operations roles: a 34% cost reduction, 38% less manual work through automation, and the lowest team turnover in 10 years. The numbers came from fixing the systems underneath them.

That last line, nothing marked done until it’s verified, is not a slogan. Try to skip it.

How a change ships here
Backup. Stage. Verify. Then done, and not before.
1Backup
2Stage
3Verify
4Done
A change is ready. Run the backup first.
Joyce Akiko

I built this for you

I built it for myself first. Then I saw how many people were stuck in the same place.

If you spend your day moving between projects that each live across a handful of tabs. If you keep tabs open because they're the only thing remembering what you were doing.

If you've lost a group to a restart and rebuilt it from memory, again, and felt that small useless flush of dread when you couldn't quite get it back.

Tabnook is for you. I built it because it's for me too.