Productivity - Setup Guide

How to set up Netlify

Otto's honest, no-fluff walkthrough. Every step here is what we'd actually do if we were sitting at your keyboard. Real gotchas first, real steps second, and a link to the personalized version at the bottom.

Read these before you start

• Bandwidth overages on Pro are $55 per 100GB, which surprises teams whose site went viral or serves large video/assets [source: netlify.com/pricing and community complaints on Hacker News about bandwidth billing].
• Serverless Functions have a 10-second execution timeout on free/Pro (26 seconds on Enterprise). Long-running work must use a background function (also limited) or move to another platform.
• Netlify's build environment is a Linux container with limited persistent state; complex builds may need custom plugins or a different build approach.
• Preview deploy links are public by default; password protection is Pro-tier.
• Redirects and headers are configured via _redirects and _headers files or netlify.toml; getting SPA routing and API proxying right requires reading the docs.

The 7-step setup

1. 1

   Create your Netlify account

   Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.

   Open Netlify signup
2. 2

   Complete the initial onboarding

   Skip the marketing questionnaires when you can. Fill only the fields that actually configure the product - name, timezone, your first workspace or project. If Netlify pushes you into a setup wizard, take it - it usually accelerates the first productive session.

3. 3

   Connect your existing tools

   Wire Netlify into the rest of your stack. The integrations that most people set up first: GitHub, GitLab, Bitbucket, Git repos generally, custom domains with automatic TLS, Sanity, Contentful, Sanity, Prismic (headless CMS integrations), Stripe, Auth0, Netlify Identity (built-in auth), Netlify Forms (built-in form handling), Slack, Zapier, Sentry, Datadog, most CI/CD tools via webhooks.. Do these before importing data - clean integration first, data second.

4. 4

   Import your existing data (only what you'll actually use)

   Do NOT bulk-import everything. Import the last 30 days of the ONE workflow you're moving over first. Prove it works. Then import more. Big-bang migrations are how Netlify deployments die in month 3.

5. 5

   Set up your first real workflow

   Pick the single most-frequent task you'll do in Netlify - the daily-driver workflow. Configure it end-to-end. Use it live for a week. Do not touch any other feature yet. Adoption failure comes from teams trying to use everything on day one instead of the one thing that actually pays.

6. 6

   Add your team (if applicable) and set access

   Once your solo workflow works, invite one teammate at a time. Watch them use it. The friction points you missed are the ones they hit. Fix those before scaling to more users. Never invite 20 people at once - you'll get 20 confused people and 0 useful feedback.

7. 7

   Compound with the right pairings

   Recommend Netlify for agencies building marketing sites, frontend developers shipping JAMstack apps, and small businesses wanting a modern, fast, deploy-on-git experience. Recommend Vercel when the client is on Next.js and wants the deepest Next.js support (Vercel makes Next.js; features land there first). Recommend Cloudflare Pages when bandwidth cost matters (Cloudflare's bandwidth is effectively free). Recommend Fly.io or Railway when the app is more than frontend.