Most tool recommendations are written by people who tried something for 20 minutes and called it a revelation. These aren't. The three below each have a specific place in a builder's workflow, and a specific kind of person who should probably skip them. That distinction matters more than any feature list.
Arc
A browser that finally has opinions about how you work, for better and occasionally worse.
What: A Chromium-based browser that replaces tabs with a sidebar, Spaces, and built-in split view.
Best for: Founders or solo builders who live across 6+ contexts daily and hate tab chaos.
Skip if: You share a machine, rely on specific Chrome extensions that break in Arc, or just want a browser that gets out of your way without relearning muscle memory.
You're mid-sprint, jumping between your analytics dashboard, a Figma file, a GitHub PR, and three customer Slack threads. In Chrome that's 22 tabs and a headache. In Arc, each context lives in its own Space, and switching takes one keystroke instead of a squinting scan across a tab bar.
Start by creating two Spaces: one for work, one for everything else. The honest caveat is that the sidebar takes about a week to stop feeling backwards, and if you give up before then you'll miss the point entirely.
Try Arc →Notion
The most over-used and under-structured tool in most startups, but still the right call in specific situations.
What: A flexible workspace that combines docs, databases, and wikis into one place.
Best for: Early-stage teams that need a shared knowledge base before they're ready to justify dedicated tools for every function.
Skip if: Your team already has strong opinions about Confluence or Linear docs, or you need something that works reliably offline.
You just brought on your third hire and realized your onboarding process is three scattered Google Docs, a Loom link in someone's Slack DMs, and institutional knowledge in one person's head. Notion gives you a single place to put the company wiki, meeting notes, and product specs without buying five different tools at a stage where that's premature.
The first thing worth building is a simple company handbook with three pages: how decisions get made, how work gets shipped, and where everything lives. The caveat is that Notion rewards people who like organizing things, and penalizes teams who don't maintain it, so assign one owner or it turns into a graveyard inside a month.
Try Notion →Supabase
Postgres with auth, storage, and realtime baked in, which is more useful than it sounds if you've ever set those things up from scratch.
What: An open-source Firebase alternative built on top of Postgres, with auth, edge functions, and file storage included.
Best for: Developers who want a real relational database without spending a sprint on infrastructure before shipping anything.
Skip if: You need a highly customized backend architecture, or you're already deep into AWS with RDS and Aurora and don't want another vendor in the chain.
You're building an MVP and you want user auth, a database, and the ability to store a profile photo without gluing together four separate services and writing the integration layer yourself. Supabase handles all of it, and because it's Postgres underneath, you're not locked into proprietary query patterns you'll regret at scale.
Spin up a free project, create one table, and connect it to your frontend using the JavaScript client in under an hour. The honest caveat is that the free tier has a database pause after a week of inactivity, which is fine for a side project and annoying for anything a real user depends on.
Try Supabase →Pick the one that solves a problem you actually have right now, not the one that sounds most interesting. Installing tools you're not ready to use is just a different form of procrastination.