Our best SaaS tools (and how we actually use them)
The complete stack of a product studio building SaaS products: dev, design, growth and ops. Real tools, real costs, real lessons after 3 years.

Why your tech stack matters more than you think
In episode 25 of Public SaaS Builders, we decided to put everything on the table: every tool we use daily at Figue, how much it costs, and most importantly why we chose it. No sponsored placements, no generic lists copied from Twitter. Just the reality of a product studio that builds SaaS products like ReactIn and Gramlab, and helps founders bring their products to life.
Your tool choices are not trivial. Every tool adds complexity, cost, and cognitive overhead. We've made mistakes (plenty), changed our minds (often), and eventually converged on a stack that makes us fast without making us fragile. What follows is the result of 3 years of iteration.
spent on Claude AI tokens to accelerate our dev and products
Figue internal budget, 2026
The dev stack: Next.js, tRPC, Drizzle, and the monorepo that changes everything
Our technical stack is the foundation of everything we build. We've optimised it for one goal: ship fast without accumulating technical debt. After testing Rails, Remix, and even full serverless, we converged on a setup that lets us launch an MVP in 3 weeks.
Next.js 15 + React 19 + TypeScript
Next.js is our default framework. Server Components, Server Actions, the App Router: everything is there to build apps that are fast on both client and server. React 19 brings the Server Functions and preloading we were missing. TypeScript is no longer a choice, it's a prerequisite. We don't start a project without it.
tRPC + Drizzle ORM + PostgreSQL
tRPC gives us end-to-end type safety between frontend and backend. No more API contracts to maintain, no more serialisation bugs. Drizzle ORM replaces Prisma: it's faster, lighter, and its SQL-first approach fits how we think. PostgreSQL remains unbeatable for reliability and advanced features (JSONB, full-text search, row-level security).
Turborepo monorepo + Vercel
We manage everything in a Turborepo monorepo: web app, mobile app, landing page, shared packages (server, core, UI, config). Turborepo's incremental caching cuts our build times by 3x. Vercel for deployment: zero config, automatic preview branches, and native Next.js integration that saves us hours every week.
Claude AI: $5,000/month in tokens
This is our most unexpected investment. We use Claude for code review, test generation, refactoring, and even client spec analysis. That's roughly $5,000/month in tokens, and it's our best ROI. A senior dev costs $8,000 to $12,000/month. Claude doesn't replace anyone, but it amplifies every developer on the team. We also integrate it into our products via the Vercel AI SDK.
The design stack: Figma, Framer, and the component system
Design at Figue isn't a separate department. It's integrated into the dev process. We don't make mockups that rot in Figma while devs build something else. Design is iterative, collaborative, and directly tied to code.
Figma + Shadcn UI
Figma remains essential for complex flows and interaction specs. But we never start from scratch. We use Shadcn UI as our component base, which is essentially a collection of Radix UI components styled with Tailwind. The huge advantage: components live in our code, not in a node_module. We customise them at will. This avoids the never-finished design system syndrome.
Framer for landing pages
For marketing pages and product landing pages, we use Framer. It's a no-code builder that generates clean, fast code. The growth team can iterate on acquisition pages without pulling in a dev. We use it for ReactIn pages, Gramlab pages, and some client pages. The result: pages scoring 95+ on Lighthouse with no extra effort.
The goal isn't having the prettiest design system. It's having a system that lets you ship fast without sacrificing visual quality. Shadcn UI + Tailwind CSS delivers exactly that: a framework that produces professional results without spending weeks designing every button.
“The best design system is the one your team actually uses. Not the one with the most components in Figma.”
The growth stack: ReactIn, Plausible, and automations
Having a great product isn't enough. You need to get it in front of the right people. Our growth stack is built around one principle: measure everything, automate the repetitive, keep humans for strategy. And yes, we eat our own cooking: ReactIn is our primary acquisition tool.
ReactIn: our own LinkedIn prospecting tool
ReactIn is a product we built ourselves to automate LinkedIn prospecting intelligently. Multi-step campaigns, lead enrichment, automatic scoring. We use it every day for Figue and for our clients. It's our number one B2B acquisition channel, and it's also proof that a product studio building its own tools understands client challenges better. Discover our complete GTM approach at /gtm.
Plausible + DataFast for analytics
We ditched Google Analytics 2 years ago. Plausible is lightweight, privacy-respecting, and surfaces the metrics that matter without drowning in vanity metrics. DataFast (another studio product) gives us real-time business dashboards: MRR, churn, LTV, all connected directly to Stripe. No need for Mixpanel or Amplitude when you know exactly what you want to measure.
Make + Slack: the glue for automations
Make (formerly Integromat) connects everything that doesn't talk natively. New ReactIn lead? Slack notification + automatic enrichment + CRM entry. New Stripe payment? Notification in the client channel + dashboard update. We have over 40 active Make scenarios. The cost: roughly $80/month to replace what would otherwise need a full-time ops person.
The ops stack: Linear, Notion, Stripe, and the rest
Ops tools are often overlooked. Yet they're the difference between a studio that delivers in 3 weeks and one that takes 3 months. Our philosophy: one tool per need, no duplicates, and everything must communicate.
Linear for project management
We've tried Jira, Asana, ClickUp, Notion Projects. Linear is the only one that doesn't slow us down. The interface is fast (genuinely fast, not 'fast for a PM tool'), keyboard shortcuts are excellent, and cycles/sprints are well thought out. We manage all client and internal projects in Linear. The cost is negligible compared to the time saved.
Notion + Cal.com + better-auth
Notion for documentation and knowledge bases. Cal.com (open source) for booking, directly integrated on our site at /call. better-auth for authentication across all our apps: it's an open-source TypeScript library that replaces Auth.js/NextAuth with a much cleaner API. We use it in Figue Studio, ReactIn, and all our client projects.
Stripe for everything money
Stripe handles our subscriptions, client invoices, and SaaS product payments. We use Stripe Billing for subscriptions, Stripe Invoicing for project invoices, and webhooks to sync everything with our database. The Stripe + Drizzle + tRPC combo gives us an end-to-end type-safe billing system. We documented our bootstrapping vs fundraising approach at /blog/bootstrap-vs-levee-de-fonds.
for our entire ops stack (excluding salaries and AI tokens)
Figue internal budget, 2026
Conclusion: the stack doesn't make the product, but it makes the speed
At the end of the day, no tool will save a bad product. But the right tools, well assembled, make the difference between a studio that ships in 3 weeks and one that struggles for 3 months. Our stack isn't perfect. We question it regularly. But it has one merit: it's battle-tested in real conditions, on our own products and our clients'.
If you're launching a product and want to understand how a product studio can help you move faster with the right tools, we're happy to chat. That's exactly the difference between a vendor and a technical partner: a partner shares their tools, processes, and mistakes. Learn more about the difference between a product studio and a traditional agency at /blog/product-studio-vs-agence.
“The best tools are the ones you master completely, not the ones with the most GitHub stars.”
Related articles

Tech as a Service: senior engineering reinforcement to ship 3x faster
You have a technical team but a velocity bottleneck? Plug-and-play senior reinforcement lets you hit deadlines without hiring. Here is how, and when to use it.

ReactIn: from side project to full LinkedIn outreach tool
How an internal LinkedIn prospecting tool became a $6K MRR bootstrapped SaaS, with zero paid advertising or fundraising.

We tripled our prices: the real pivot behind our design offer
How we went from a $2K/month design subscription to a $6K+ premium product studio. Fewer clients, 3x revenue per client, better quality.

Bootstrap vs fundraising, freelance vs agency, solo vs co-founders: our founder choices
3 dilemmas that define your startup trajectory. A look back at our choices at Figue, with real numbers and hard-won lessons.

Product studio vs traditional agency: why it changes everything
Agencies optimise for volume. Product studios optimise for outcomes. Here's why that makes all the difference for your project.