I'm excited to finally share what we've been working on! For the last 8 months, we've been building Biscuit: an all-in-one platform for building a business. Product, payments, emails, hosting and operations built in. Today we're opening the waitlist 🎉

One of our Biscuit users found out that workflows can run on a schedule. So they built a lead finder that researches new organizations every night: who to contact and when to call. Every morning their team gets a fresh list of leads. They went from 15 to 165 signed contracts!

Working on the small details, like animating all the components when you drag one. Using FLIP (funny name, given that my nickname is flip!) to do the animations. @JoshWComeau wrote a super helpful post on this: joshwcomeau.com/react/animat…

Mutation testing is really effective with AI. Let agents inject subtle bugs in your codebase and run the test suite, if tests do not fail we do not have the required coverage.

Every app you build on Biscuit comes with its data out of the box. 🎉 No database setup. No empty placeholder screens. Your screens fill with realistic content the moment you build. Here's how 🧵

It took blood sweat and tears to build this, but every time I see the screens streaming in, I realize it was worth building it 🥹

Making good progress on tasks! You have a central "cofounder" chat that creates tasks for you, then every task a ticket (plan comments) that gets implemented & tested by sub-agents. Next up: night shift!

Opus 4.7 vs Opus 4.8 (internal @Biscuit_so benchmarks) Spoiler: Clear gains on editor & exploration tasks, but mixed elsewhere. Same prompts → here's how they differ visually 👇

Building an app backend gets tedious. Especially when it lives in code you can't see. What if instead you could see it? Modify it without touching code? In Biscuit, we visualise every step as a diagram, called Workflows. Let's walk through an example: how your app's payment checkout workflow is visualised and how you can modify it easily 🧵

Building a monetised app shouldn't mean weeks of Stripe setup, KYC forms, and API integration. With Biscuit, you enable payments in minutes. 🧵 Here's how → 1/ Enable payments Once your app is built, click "Enable payments" in the side nav (or just type it in chat). No Stripe account creation. No KYC upfront. No API keys to manage. Biscuit handles the setup and the integration. You handle the product.

This is very similar to how we’ve designed the task system in biscuit. You have a single long running chat for the project. That chat spawns tasks that contain goal/review/testing description. Then the tasks get implemented by specialized sub agents

Gemini 3 Flash vs Gemini 3.5 Flash (internal @Biscuit_so benchmarks) Spoiler: 3.5 Flash is noticeably faster... ...but 230% more expensive on our view creation benchmark Same prompt, same design system and tools as input for the models:

This is probably the only AI-driven automated test system in the world that can work on a forked database with realtime multiplayer, simulated payments, file uploads etc and produce integration tests for rapid reruns, all with very low infra costs 🔥

Sneak peek of automated tests in Biscuit 👀 Best thing is that you can pause the test at any point and take over!

I'm playing with a new UX for working with agents in Biscuit, inspired by Claude Code, OpenClaw and Linear. You have one central chat, which doesn't do work. It can only delegate work by creating tasks. Tasks are plans, but with status, comments & activity. It has an orchestrator that does discovery on the task, and spawns a team of agents to build it. Once its built, we automatically run QA on the result, and finally mark the task as "review" and hand it back to the user. I think this makes multitasking, async and proactive tasks much easier for us. E.g. we spawn a task when certain threshold of bug reports come in to fix it.

Library is here! One place for all your assets, files, images, project plans, notes - everything. Stop losing things in the chaos. Keep your project organized from day one. Build smarter with Biscuit. 🚀

Been trying a consistent style for automated initial favicons for Biscuit apps using the apps' brand colors.

People of Amsterdam, come build your app with us this Friday, 15th May at our Bakin' Biscuit event. You can spend the day in our office. This is perfect for solo builders and founders working from home - you can enjoy the canal view and delicious coffee. At 5:00PM we have demos where people show off their apps. And this time, the demos will be lit 🔥. It does not matter, if they are fully baked or half-baked. Pizza and drinks on us. 🍕 🍺 Event link is here -> luma.com/zjg0igim

Just vibe coding with @Biscuit_so Make your dream app happen biscuit.so/?invite=CARRXJ

Creating a multiplayer list is trickier than it looks. When two users make simultaneous edits, state drifts out of sync—you can't just use a regular array. Real-time tools like Figma and Liveblocks use a specific technique to solve this. It's called fractional indexing ↓

Bringing "Reels" mode into Space. Just in a couple of minutes with @Biscuit_so