Productivity - Setup Guide
How to set up Retool
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.
What you're signing up for
Medium. Developers pick it up in an afternoon. Connecting a Postgres database and building a first CRUD app takes 30 minutes. Building production-grade internal tools with permissions, error handling,
Read these before you start
- Retool has been criticized for pricing changes over the years. The 2023 shift to per-user + per-editor pricing raised bills for teams with many end-users [source: retool.com/pricing and Hacker News threads on pricing changes].
- Retool apps live on Retool's cloud by default. Sensitive data leaves your infrastructure unless you self-host (Enterprise tier) or use Retool's on-prem agent.
- Custom code (JavaScript queries) runs client-side; complex logic gets slow and hard to debug.
- Version control was historically weak; the Git-sync feature added in 2023 improved this but is Team+ tier.
- Retool Mobile (mobile apps) and Retool Workflows (server-side automations) are separate products under the same umbrella; buying one does not include the others.
The 7-step setup
- 1
Create your Retool account
Sign up at the link below. Free tier available - no card required. Use your business email so you can invite teammates later.
Open Retool signup - 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 Retool pushes you into a setup wizard, take it - it usually accelerates the first productive session.
- 3
Connect your existing tools
Wire Retool into the rest of your stack. The integrations that most people set up first: Postgres, MySQL, MongoDB, DynamoDB, BigQuery, Snowflake, Redshift, Firestore, Stripe, Twilio, SendGrid, Salesforce, HubSpot, GraphQL, REST APIs, gRPC, Google Sheets, Slack, S3, GCS, Azure Blob, GitHub (for source control), OpenAI, Anthropic (via API).. Do these before importing data - clean integration first, data second.
- 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 Retool deployments die in month 3.
- 5
Set up your first real workflow
Pick the single most-frequent task you'll do in Retool - 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
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
Compound with the right pairings
Recommend Retool for engineering teams (5+ engineers) that repeatedly build internal admin/ops tools. Recommend for B2B SaaS support teams needing custom workflow tools on top of production data. Do NOT recommend for non-technical teams, customer-facing apps, or businesses without a database and API. Recommend Airtable or Bubble for lighter no-code use cases.
Pricing you'll hit
- **Free:** Up to 5 users, unlimited apps, unlimited API queries, all data connectors. Generous for small teams. - **Team:** $10/user/month + $5/user/month for each additional editor, adds custom domains and integrations with source control. - **Business:** $50/user/month + $15/user/month for editors, adds SSO, audit logs, permissions, module reuse. - **Enterprise:** custom quote, adds on-prem/sel...
Want it personalized to YOUR business?
Otto builds a custom Retool setup for your exact context.
The steps above are the universal path. Run a 30-second scan and Otto tailors them to your industry, team size, existing stack, and the specific pain points you're trying to fix.
Get my personalized setup