The Two-Tab Stack

Dictate into Slack, email, LinkedIn, or any app and get polished, send-ready text. Wispr Flow strips filler and formats everything. 89% of messages sent with zero edits. Works on Mac, Windows, and iPhone.

Start flowing free

I was sitting at a dinner in Austin last month when a founder across the table started listing the software her company used to run operations.

She got to seventeen before I stopped her. Slack, Notion, Airtable, Asana, Monday, Jira, Linear, ClickUp, Zoom, Loom, Calendly, Zapier, HubSpot, Salesforce, Stripe, QuickBooks, and something called Motion. Her team was twelve people. The monthly software bill was over nine thousand dollars. And she was asking me what tool she should add next because her team felt “disorganized.”

I nearly swallowed my fork.

Listen. I run a fully automated wealth business with a network of contractors, a growing portfolio, a content operation that ships four pieces of long-form writing a week, and a family I actually see. My entire business operates out of two browser tabs. Two. I know it sounds like a flex, and sure, it sort of is, but the real point is this: your tool stack is either compounding your leverage or quietly strangling it. There is no middle ground.

Today I’m going to pull back the curtain on how I structure the whole thing. You don’t need to copy it exactly. You probably shouldn’t. But you do need to understand the architecture, because the principle is the same whether you’re running a solo operation or a thirty-person team: fewer tools, deeper integration, single source of truth. That’s the game.

Let’s get into it.

Why Most Stacks Are a Disaster

Before I describe the two tabs, I want you to understand what goes wrong when people build stacks the normal way.

The typical founder or investor adds tools the way a squirrel adds acorns. Something new comes out, it solves a narrow problem, they sign up, they integrate it halfway, and six months later they have a graveyard of half-configured SaaS accounts that all kind of do the same thing. Nobody on the team knows which tool is the canonical one. Data lives in seven places. Automations break because the plumbing is spaghetti. Every new hire needs a week of training just to figure out where things are.

Here’s the cost. Not the sticker price on the invoices, though that’s ugly too. The real cost is cognitive. Every tool you add is another interface your brain has to map, another password, another notification stream, another place where a decision could get lost, another vector for things to fall between cracks. Studies I’ve seen put the average knowledge worker at around forty interruptions a day from tool-switching alone. If you think that’s compatible with deep strategic thinking, I have a bridge to sell you.

The wealthy operators I know almost universally have small stacks. Not because they’re cheap. Because they understand that every integration point is a liability, and every single-source-of-truth failure is an operational tax they pay forever.

The Architecture: Source of Truth Plus Execution Layer

Here’s the frame. Every business, every portfolio, every life system really, has two functions. It needs to store information and it needs to act on information. That’s it. Everything else is fluff.

The first tab is your source of truth. This is where every piece of information your business depends on actually lives. Customer data, project status, financial records, investment positions, decisions, standard operating procedures, contracts, everything. If it matters, it lives here. Not in email. Not in Slack. Not in someone’s head. Here.

The second tab is your execution layer. This is where things actually happen. Automations fire, documents get created, messages get sent, calendars get updated, deals get moved, money gets moved. The execution layer reads from and writes to the source of truth. It doesn’t have its own memory. It’s glue, not storage.

Get this architecture right and you can run almost any operation with stunning efficiency. Get it wrong and no amount of new software will save you.

For me, the source of truth is Notion, and the execution layer is Make.com. Those are my two tabs. Everything else plugs into one or the other or both. Slack, email, Calendly, Stripe, my brokerage feeds, my affiliate dashboards, my calendar, my banking pulls, the whole orchestra, none of it is primary. They all feed information into one of the two tabs.

Let me walk you through how this actually works day to day.

Tab One: The Source of Truth

My Notion workspace has, for illustration, about a dozen top-level databases. Opportunities, Investments, Projects, Content, Contacts, Contracts, Financials, SOPs, Weekly Review, Meeting Notes, Ideas, and Decisions.

Each one has strict schema. I don’t mean “I tried to keep it tidy.” I mean locked-down properties, required fields, templated new-entry forms, and relational links between databases. When a new deal enters the Opportunities database, it’s linked to the Contacts database so I know who referred it, and it’s linked to the Projects database if I end up pursuing it. When I close an investment, it migrates from Opportunities to Investments with the relationship preserved. Nothing lives as a loose note.

The Decisions database is maybe my favorite. Every non-trivial decision I’ve made in the last three years is in there with the date, the context, the options I considered, the reasoning, and the outcome. It’s the closest thing I have to a compounding brain. When a new situation comes up, I search for analogous decisions, and eighty percent of the time I find something useful. Future you is going to thank past you for keeping this log.

Here’s the critical piece: nothing gets created outside Notion and then copied in. If information is generated elsewhere, I use automation to pipe it in. Which brings us to the second tab.

Tab Two: The Execution Layer

Make.com is where my business actually runs. I currently have about seventy active scenarios. They handle everything from deal flow intake to client onboarding to content publishing to monthly financial reconciliation.

I’ll give you a concrete example. When someone books a call through Calendly, a Make scenario fires. It grabs their form responses, enriches the contact with data from Clay, creates a new entry in the Contacts database in Notion with the enrichment attached, creates a prep document linked to the contact with a pre-filled research template, and sends me a Slack message with the prep link ten minutes before the call. I walk into the meeting prepared without having lifted a finger after the calendar invite.

When I close a deal, a single button in Notion fires a scenario that updates the deal status, drafts a contract using a template, sends it out for e-signature, creates a project in the Projects database, schedules kickoff tasks, and pings the client with a welcome email sequence.

When I publish a newsletter on Beehiiv, a scenario cross-posts to Substack, pulls performance data back into Notion for my weekly review, and creates social snippets for scheduling through Buffer.

Meeting recordings from Fathom automatically generate summaries, extract action items, and pipe those action items into the appropriate project or opportunity in Notion. I haven’t taken a meeting note by hand in eighteen months.

You see the pattern. The execution layer reaches across every tool I use, pulls information into the source of truth, and pushes action back out. But from my perspective as the operator, I’m only ever looking at two tabs. Everything else is backstage.

The Rules That Make It Work

The architecture is the easy part. Keeping it clean over time is where most people blow it. Here are the non-negotiables.

Rule one: No duplicate data. If it exists in Notion, it doesn’t exist anywhere else as a primary record. The version in my bank, my brokerage, my CRM of ancient memory, none of those are sources of truth. They’re feeder systems. The source of truth is Notion. Period.

Rule two: Every automation has an owner and an expiration date. I review all Make scenarios quarterly. If a scenario hasn’t fired in ninety days, I delete it. If it’s been modified three times in ninety days, I rebuild it from scratch. Automations decay. Feeding the rot is more expensive than killing the scenario and starting fresh.

Rule three: One tool in, one tool out. When I add a new capability to my stack, something has to leave. No exceptions. This rule alone has prevented about fifty tools from accumulating.

Rule four: If I find myself manually moving data between tabs more than three times, I automate it. Three strikes and it gets wired up. This keeps the automation layer growing in proportion to actual need instead of theoretical need.

Rule five: The weekly review is sacred. Every Monday morning, for roughly forty minutes, I sit in the source of truth and review every active project, investment, and opportunity. I touch each one. I decide what moves forward, what dies, and what changes. Nothing compounds without a cadence of honest reassessment, and the two-tab architecture only works if you actually look at it.

What Gets Sacrificed

I’ll be straight. This setup is not for everyone.

If you have a team of fifty, you’re probably going to need a dedicated communications tool that isn’t Slack, and a dedicated CRM that isn’t a Notion database. The two-tab setup scales beautifully up to maybe ten people and starts to strain after that. Past twenty, you’ll want more specialized tools and you’ll need a real operations person to manage the plumbing.

But for solo operators, lean teams, investors managing portfolios, and content businesses, this architecture is almost unreasonably powerful. You will not miss the fifteen tools you removed. You will not suddenly become “disorganized.” In fact, the opposite. The clarity of a single source of truth is addictive, and the power of a real execution layer, once you feel it working, makes every other setup look like duct tape.

The other sacrifice is upfront investment. Building the schema takes a weekend. Wiring up the first twenty Make scenarios takes another. You will feel, while you’re doing it, like you’re not making money. That’s the trap. You’re building the machine that prints money while you sleep. Don’t quit on day three.

Your Move This Week

Open a doc. List every tool in your current stack, the monthly cost, and the last time you logged into it. I guarantee half are dead weight.

Then, for each remaining tool, ask one question: is this the source of truth for something, or is it an execution layer for something, or is it both? Anything that can’t answer clearly is probably going to be pruned.

Next, map your architecture. Pick your source of truth. Pick your execution layer. Decide which tools graduate to feeder status and which get cut entirely. Give yourself two weekends. Turn the lights off on at least five tools. See how it feels.

My bet: you’ll lose nothing operationally and gain back twenty hours a month and a couple thousand dollars in SaaS fees. Plus something less tangible but more valuable: the feeling of knowing where everything is.

Until Friday.

Alex Rivera

Wealth Architect at Wealth Grid

Imagine it's 2031. Markets have been chaotic for years. Your coworkers are stressed. You're not. Because five years ago, you did something boring. You opened YieldClub, turned on Autopilot, and your yield started converting into Bitcoin every day. Quietly. Automatically. YieldClub earns up to 12% APY and routes your yield into Bitcoin automatically. No lockups, no guesswork.

Start Stacking BTC