Blog
Practical notes on design, product, and shipping for startups.
Practical notes on design, product, and shipping for startups.
Practical notes on design, product, and shipping for startups.
Stripe vs Paddle vs Lemon Squeezy for a SaaS selling worldwide in 2026: merchant of record vs processor, list-price fee tables, a worked $20 subscription example, when each one fits, how hard switching is, and provider-agnostic Next.js webhook code.
Read postSet a performance budget for a Next.js app used worldwide: Core Web Vitals targets, JavaScript and image size caps, testing on throttled mobile, Lighthouse CI on every pull request, and the App Router changes that save the most on slow connections. Includes config and code.
Read postKeep LLM costs predictable in a Next.js app: log tokens per user in Postgres, enforce a server-side daily token budget, route simple tasks to a smaller model after evals, use response and prompt caching, and track cost per active user weekly. Includes TypeScript and SQL.
Read postBuild a Telegram ops bot for your startup with BotFather, a secured Next.js webhook, idempotent update_id storage, a schema-checked LLM step, and approval buttons for risky actions. Includes TypeScript code, a risk table, and common failure fixes.
Read postAdd evals to an LLM feature before launch with 30 to 100 real test cases, code checks first, an LLM judge only where code cannot decide, and a CI gate on prompt, model, and retrieval changes. Includes a TypeScript runner, judge rubric, and thresholds.
Read postShip RAG on Supabase pgvector and Next.js by locking chunking, embeddings, RLS, and retrieval before you polish the chat UI. This checklist covers schema, ingest, query, evals, and cost controls so the first release answers real questions without leaking tenant data.
Read postAn MCP server exposes your SaaS tools to AI clients like Claude, Cursor, and ChatGPT in a standard way. Ship one when agents need safe access to real actions in your product; skip it if an in-app chatbot is enough. Start small with auth, scopes, and a few clear tools.
Read postMost startups should launch a responsive web app first: one codebase, instant updates, and wider reach for less money. Build mobile first only when the core value depends on the phone, like camera, location, offline use, or daily push-driven habits.
Read postHire a freelancer for small, well-defined builds you can manage yourself. Choose a studio when you need design and engineering shipped together on a timeline. Hire in-house once users pay or return and the roadmap changes weekly.
Read postUse no-code when the workflow is simple and you need a demand signal fast. Choose custom code when the product is the differentiation, data model is nonstandard, or you expect weekly product changes after launch.
Read post