Gmail

This guide gets you from a default Gmail inbox to a system you actually run, instead of one that runs you. It is for founders, operators, and small B2B teams who live in email and want it to behave like infrastructure: fast to triage, easy to search, and wired into the rest of the stack. I am assuming you already know how to send a message, so I will spend the words on the decisions that compound.

Getting set up

The first real decision is the account type. If this is for a business, use Google Workspace with your own domain, not a free address. A free Gmail address signals hobby, hurts deliverability on cold and warm outreach, and locks you out of admin controls you will want later. Workspace gives you the domain, the admin console, shared drives, and the ability to add aliases and group addresses, and it is worth paying for from day one.

Once the account exists, set up authentication properly before you send anything that matters. That means publishing SPF, DKIM, and DMARC records for your sending domain. This is the single biggest lever on whether your mail lands in the inbox or the spam folder, and most people skip it. If you send any volume of outreach or newsletters, get DMARC to at least a monitoring policy and watch the reports before tightening it.

Next, decide your label and filter architecture before the inbox fills up. Gmail does not use folders, it uses labels, and a message can carry several at once. Resist the urge to build a deep tree of nested labels that mirrors a filing cabinet. Search is so strong that you rarely need to file by hand. A handful of labels that map to actions or relationships (clients, billing, recruiting, waiting-on) beats thirty topic labels you will never reopen. Turn on the features that change how the inbox behaves: keyboard shortcuts, conversation view, and a sensible inbox type. Most operators do well on the Priority Inbox or a multiple-inboxes setup rather than the default single stream.

How to actually use it

The core workflow is triage, not reading. Open the inbox to make decisions, not to consume. Go top to bottom and put every message into one of four buckets: do it now if it takes under two minutes, defer it if it needs real work, delegate it, or archive and forget it. The goal of a session is an empty or near-empty inbox, where "empty" means every message has a decision attached, not that you answered everything.

Lean on search instead of scrolling. Gmail search is the feature that makes the whole product work, and the operators get fluent in its syntax: from:, to:, subject:, has:attachment, older_than:, is:unread, and quoted phrases. Once you can find any message in three seconds, the pressure to file everything disappears, which is why the flat-label approach holds up.

Use filters to do the triage you would otherwise do by hand. Every time you find yourself archiving, labelling, or routing the same kind of message twice, build a filter for it. Receipts skip the inbox and land under billing. Notifications from a tool you tolerate but do not read get auto-archived and labelled so they are searchable but invisible. This is where Gmail goes from a passive inbox to something that pre-sorts your day before you open it.

For sending, build reusable templates for the messages you write repeatedly (intro replies, scheduling, polite declines) so you are editing instead of composing. Schedule send when you are clearing your inbox at an odd hour but do not want to land in someone's inbox at midnight, and set undo-send to its longest window so you always have a few seconds to catch the wrong attachment or the missing context.

Power moves

The plus-addressing trick is underused: anything you send to you+tag@yourdomain still reaches you, so you can sign up to tools as you+toolname@ and then filter or trace exactly who leaked your address later. Pair that with a filter and you have a clean way to segment sign-ups without extra accounts.

Send-as aliases let you run several public addresses (support@, hello@, your name) from one inbox and reply from the right face without switching accounts. For a solo operator or a tiny team this keeps everything in one place while looking like a structured company.

Learn the search operators that most people never touch: list: to find everything from a mailing list, rfc822msgid: to jump to an exact message, and combinations like from:X older_than:1y has:attachment to clean up or audit history fast. Turn on confidential mode for genuinely sensitive sends where you want an expiry. And if you process volume daily, the keyboard shortcuts (archive, label, next, reply) are the difference between a ten-minute triage and a forty-minute one, so commit them to muscle memory.

Where it fits your stack

Gmail is the hub the rest of a growth and ops stack plugs into. It pairs natively with Google Calendar and Meet, so scheduling and calls never leave the surface. Your CRM almost certainly has a Gmail extension that logs threads against contacts and deals automatically, which is how you keep a record of every client conversation without copy-pasting. Outbound and sequencing tools send through or alongside your Gmail identity, which is exactly why the SPF, DKIM, and DMARC setup earlier matters so much.

Beyond that, Gmail exposes an API that lets you automate the parts that filters cannot reach: routing parsed data into a database, triggering a workflow when a specific sender writes, or feeding messages into an agent that drafts replies. If you are building an operating system around your inbox rather than just reading it, the API is where the real leverage sits.

Pitfalls to avoid

The biggest mistake is treating the inbox as a to-do list. It is a queue of other people's priorities, and if you let it set your day you will always be reactive. Move real tasks out into a task system and keep the inbox for triage. The second mistake is over-engineering labels and filters until you spend more time maintaining the system than using it; start flat, add structure only when a real pattern repeats. The third is ignoring deliverability until mail starts bouncing or landing in spam, by which point your domain reputation is already damaged. Set authentication up first. Finally, do not run a serious business off a free consumer address, and do not let undo-send and the longer confirmation windows tempt you into firing off replies you have not actually read.

INTERVIEW EWOUD: How is your own Gmail / Workspace set up, and what does your label and filter architecture actually look like in practice?

INTERVIEW EWOUD: What is the one inbox workflow you rely on daily to stay on top of email across multiple ventures, and how does it connect to the rest of your stack?

INTERVIEW EWOUD: What is your hard-won tip for Gmail that took you too long to learn, and what mistake do you wish someone had warned you about?

Gmail is Google's email service, the inbox most of the world already lives in. It handles sending, receiving, and organising email, with strong search, conversation threading, labels and filters, and spam handling that quietly does a lot of work. For businesses it shows up as the email layer inside Google Workspace, running on a custom domain alongside Calendar, Drive, Docs and Meet.

Where it fits

Gmail fits almost any team that wants email to just work and to sit next to the rest of their documents and calendar. It is the natural default for a solo founder or a small B2B team running on Google Workspace: you point your domain at it, and your whole communication and document stack lives in one account. The search is genuinely good, the spam filtering saves you hours you never notice, and because so many people already know the interface, onboarding is close to zero.

It is a weaker fit if your business runs on Microsoft 365 and Outlook, where staying inside one ecosystem matters more than Gmail's strengths. It is also not the tool for high-volume outbound sequencing or transactional sending: that is a job for a dedicated sending platform or a sales engagement tool, with Gmail as the human inbox behind it, not the engine.

The honest take

The strengths are real. Search is fast and forgiving, threading keeps long conversations readable, filters and labels let you build a quiet system that sorts mail before you see it, and the reliability is the kind you stop thinking about. Tied into Workspace, it removes the friction of bouncing between email, calendar and documents, which for a small operation is most of the value.

The trade-offs are equally real. The conversation-threading model is divisive: some people find it indispensable, others find it hides messages and groups things they would rather see separately. Labels are powerful but they are not folders, and people coming from Outlook often fight that mental model for a while. Heavy filter-and-label setups can drift into clutter that you then have to maintain. And the deeper point: living in Gmail means living in Google's ecosystem, with your business email tied to one provider's account, terms, and privacy posture, which is a strategic dependency worth being deliberate about rather than defaulting into.

INTERVIEW EWOUD: What is your personal verdict on Gmail in one or two flowing sentences?

INTERVIEW EWOUD: Your star rating out of five, and is Gmail in your own stack today and why or why not?

INTERVIEW EWOUD: The one line you would tell a peer who is deciding whether to run their business email on Gmail?

Gmail is Google's email service, available as a free personal account or as part of paid Google Workspace plans that add a custom domain, admin controls and business support. It serves individuals for personal mail and businesses for day-to-day team email rather than as a bulk marketing or transactional sending platform. It includes spam filtering, search, labels and a programmatic API for reading and sending mail.

Founders and teams who want reliable day-to-day business email on their own domain