Retool vs Building Your Own Internal Tool: a Cost-Benefit Analysis

Verdict up front: Retool wins for teams under 20 seats and tools that will exist <3 years. Custom wins for teams over 50 seats, mission-critical workflows where Retool's limits hurt, or when you need features Retool can't build (mobile, embedded, real-time collab). The crossover is around 30 users × 36 months = €10,800 in licensing, which is the cost of a small custom build.

Retool pricing in 2026

• Free: Up to 5 users, 500 workflow runs/month, basic features
• Team: €10/user/month, 5k workflow runs/month
• Business: €50/user/month, unlimited workflow runs, SAML SSO, audit logs
• Enterprise: Custom (typically €100+/user/month with self-hosted option)

The pricing trap: Team tier is positioned as €10/user but the real cost is Business at €50/user because most internal tools need SAML SSO and audit logs for compliance. At 20 users, Business costs €12,000/year. At 50 users, €30,000/year.

Custom build cost (Madrid market, 2026)

A typical internal tool — CRUD dashboard for ops team, 8-12 views, role-based auth, integration with 2-3 internal APIs:

• Design + spec: 1 week, €3,000
• Development: 4-6 weeks, €6,000-€12,000
• Deployment + auth setup: 1 week, €1,500
• Total greenfield: €10,500-€16,500
• Ongoing maintenance: €300-500/month

Stack we use for most: Next.js + Supabase + Vercel/Cloudflare Pages. Auth via Supabase + Google OAuth. Hosting under €30/month. Total monthly cost ~€330-530.

The break-even calculation

For a 20-person ops team using the tool for 3 years:

• Retool Business: €50 × 20 × 36 = €36,000
• Custom build: €12,000 + (€400 × 36) = €26,400

Custom wins by €9,600 at this scale. But this assumes:

• The tool's requirements don't change much (you don't need ongoing dev time)
• You have someone to maintain it
• You can wait 6 weeks for v1 instead of 1 week on Retool

The hidden costs of Retool

• Vendor lock-in: Retool's apps don't export cleanly. Migration off Retool is essentially a rebuild.
• Performance ceiling: Retool apps slow down past 50 components or 10k rows in a table. Re-architecting on Retool means starting from scratch within Retool.
• Mobile is weak: Retool Mobile exists but is limited. Building responsive Retool apps is a workaround, not a solution.
• External customer access: Retool Embed exists but doubles the price.

The hidden costs of custom

• Bus factor: If the developer who built it leaves, who maintains it?
• Feature requests: Each new view is real engineering work, not a drag-and-drop change.
• Security updates: npm audit alerts, OS patches, library upgrades — all on you.
• Auth complexity: Don't roll your own auth. Use Supabase, Auth0, or Clerk — but that's another monthly bill.

Side-by-side

When Retool wins

• You need a tool live in <2 weeks
• Team size will stay under 20 users
• Tool lifespan <3 years (project-based, will be replaced)
• Workflow is standard CRUD + dashboards (no real-time, no mobile, no embedded)
• You have no engineering capacity to build or maintain

When custom wins

• 50+ users (per-seat pricing dominates)
• Tool will exist 3+ years
• You need mobile, real-time, or embedded customer access
• Complex business logic Retool can't model cleanly
• You have engineering capacity (in-house or contracted) for build + maintenance

The third option: hybrid

Use Retool to validate the workflow (1-2 weeks, free or Team tier). Run it for 3-6 months. If it sticks, rebuild as custom. This avoids the "build it perfectly first" trap and the "stuck on Retool forever" trap.