You have Notion. You have Claude. You still don’t have a system.
I spend a session inside how your team actually works, put an hours number on the parts that hurt, then rebuild the fix with you in Notion and Claude — so the reasoning stays in your building after I leave.
The three questions I get asked most are the wrong three.
“What tools should we be using?” “What templates do you have?” “What agents should we build?”
I understand the instinct. You saw someone’s setup, it looked like the thing you were missing, and copying it feels like a shortcut. It is how teams end up with three task managers, a wiki nobody opens, and an AI subscription used as a search engine.
So the first rule here is a subtraction, not an addition: never automate a workflow that should not exist. Most of what a team wants to speed up should have been deleted, merged, or handed to one person a year ago.
Three better questions. Answer them honestly, in your head, right now.
-
01
What is your best person doing this week that doesn’t need to be them?
You already know the answer. That’s what makes it expensive.
-
02
How many steps does it take to do the thing your team does most often?
Not roughly. Actually. The real number is always higher than anyone guesses.
-
03
Does your team use the system because it helps them, or because you keep reminding them?
Only one of those holds up when you stop watching.
None of those were questions about software. They were questions about how your team actually works, and that’s the layer nobody described before the tools arrived.
Software can only speed up work you can already see. Everything else it just helps you do badly, faster. And it will feel like progress the entire time.
Understanding your own operation isn’t the step before the real work. It’s the thing that makes the tools worth anything.
The best systems for your team don’t exist yet.
They can’t. Yours would have to be built out of your handoffs, your bottleneck, your recurring Tuesday-afternoon slog. The person whose setup you are copying has never seen a minute of it.
That’s why the tutorial never quite transfers. A setup video, a template, the workflow another team swears by: each one is a finished answer to a question somebody else asked. You can copy the answer, but you can’t copy the work that generated it, and the work is where the fit lives. So it feels right for two weeks and then quietly stops getting opened.
The workflows and automations worth having aren’t found. They get built out of your own work, examined in a specific order.
The Operating Stack
Five layers, in the order that works. Most teams move in reverse.
Friction
Start with the thing that eats your Tuesday. The step everyone has quietly built a workaround for. The task that leaves the whole team flat. Not what is trending, not what you watched someone automate online. What is costly, in your business, this week.
Anatomy
Break the costly work apart until every step is visible, before any tool enters the conversation. What sets it off, what happens in what order, what it leaves behind. The steps that matter most are the ones nobody thinks to mention: the quick check someone always runs, the message that has to go out first, the file that gets renamed before it’s sent. Build an automation on a version of the work that’s missing those and it’ll look great in a demo and be abandoned by week three.
Connections
One step’s output is the next step’s input. A person’s habit is part of the machine as surely as any software is. Until you can see the whole circuit, including where things hand off and who is quietly waiting on whom, you are tuning parts of something you have never actually looked at.
People The key step
Every team has a few things only it can do. The judgment. The relationships. The way your best person reads a room. Name them precisely, and know where they sit in the workflow. Then everything around them is safe to hand off, because you know what you’re protecting. It’s never about needing fewer people; it’s about freeing the ones you have to do what only they can. Skip this and you automate over the part that was working.
Tools
Notion, Claude, the automations between them. This is the last decision, not the first. By the time you get here the choice is usually obvious, and usually smaller than what you would have bought on day one.
Where’s your weakest layer?
About eight minutes, and you get a real report at the end: an estimate of the hours you could reclaim, your weakest layer named, and the first thing to fix. Free, and it’s yours to keep.
Three ways in
Build With Me
Weekly coaching for you and your team. We take a workflow that actually matters this week and rebuild it together in Notion and Claude, so you learn the tools on your own operation rather than on someone’s demo. Most teams use a fraction of what these tools can do, and the gap is rarely features. It’s knowing which of your problems they can solve. One 60 to 90 minute session a week, async support in between, and anyone on your team can sit in.
The Operating Stack Audit
A full diagnosis of your operation. We start with an intake, then a working session where we go through how your team actually runs, workflow by workflow, while I surface the steps nobody has written down. You get back a written report: every recurring workflow mapped, its real cost in hours, proposed solutions built from what we found, and a sequenced roadmap ranked on time versus effort. Then a review call, and ten days to ask anything. If you never work with me again, you keep a map of your own business that you didn’t have before.
Learn Notion Accelerator
The community for professionals learning Notion. You get my Learn Notion in a Weekend course, a library of over 100 structures I’ve built from the plumbing I have had to rebuild a hundred times, yours to copy and adapt, plain-English updates whenever Notion ships something new, and questions answered by me every weekday when you’re stuck on your own build.
This is for you if
This isn’t for you if
Gabe Fernandez
I’m Gabe Fernandez. In ten years I’ve built over a hundred Notion workspaces and dozens of Claude implementations for venture capital and private equity firms, marketing and talent agencies, consulting practices, and early-stage startups. Then I stopped taking this kind of done-for-you work.
Here’s why: whether a workspace lasted had almost nothing to do with how well it was built.
The teams who wanted a template, or a finished build handed over at the end, drifted off it within a couple of quarters. The other teams stayed in the room. We pulled the work apart together, named what it was actually costing them, mapped the steps, and decided what deserved a tool. Those teams are still running what we built, and still changing it to fit their evolving needs. The difference was never the software. It was whether the thinking happened with them or to them.
So that’s the work now. I come in as a catalyst for that thinking, not as something you have to keep paying for. I study how your team actually works, show you where the hours are going, and build it alongside you in Notion and Claude so the skill stays after I leave. A teacher’s job is to make themselves unnecessary, and I mean that literally: in a perfect world, this ends with your team not needing me.
In case you were wondering
What does this cost?
The Operating Stack Audit is $2,500, fixed scope and fixed price, and you can stop after the working session and pay nothing if you do not think the report will be worth it. Build With Me is $1,500 a month in the group room, or $5,000 for one of the two private seats. The community is $47 a month. The Self‑Audit is free and always will be.
Do you build the system for me?
Mostly not. The work I do is diagnosis and teaching, so you or your team build it with me on the call. If you would rather hand it off entirely, we can talk about what that costs, or I can hand you to implementation partners I trust, who get the full audit so you never repeat discovery.
Why pay for an audit when other consultants do it free?
A free audit is a sales call with a slide at the end. This is a deliverable. You get four things:
- A 60 to 90 minute deep dive into how your team actually works, with real questions in both directions about your workflows and your tools
- A written report that shows you exactly where the gaps are and where the opportunities are, in your own language
- A list of proposed solutions, built from what we actually found rather than from a standard menu
- A sequenced roadmap of the few things to start with, in the order that gets you a felt win fastest
It’s a report, not a pitch, and it’s yours to keep either way.
Do I need to already know Notion or Claude?
No. Most clients are somewhere between "we opened an account" and "we use maybe 20% of it."
Can I bring my team?
Yes, and you should. The point is that the knowledge stays in your building.
What if I just want the community?
Then join the community. Cancel whenever. It’s a real product, not a funnel step.
Find your current
gaps and opportunities.
About eight minutes. Score your five layers. Find out which one is actually costing you.
Or just email me: gabe@learnchangedo.org