Notes on SaaS , and .
What we learn building SaaS products, written down. Pick a topic to filter.

Show the product before the feature list
OptroGrowth3 min read
Buyers decide on proof, not promises. Why the first screen of a SaaS site should show the product doing its job, and how we build heroes that do.
AureloGrowth2 min read
One line of metadata hid 15 of our pages
A canonical tag in our root layout told Google that 15 pages were copies of the homepage. What happened, how we fixed it, and how to check your own Next.js site.

DirectHomesDevelopment2 min read
Rebuild or patch? Four questions we ask first
When a SaaS product outgrows its first version, patching feels cheaper. Four questions that tell you when it isn't, from our DirectHomes rebuild.

DriiveDesign2 min read
Start with the screen where the day lives
Where you start designing a product decides what it becomes. Why we begin with the one screen people live in, from Driive, Dars and MindProbe.

CurvanceDesign2 min read
Put the risk next to the button
In products that move money, trust is won in the second before someone presses confirm. How we designed Curvance so nothing about risk is hidden.

QuackrGrowth2 min read
Answer the three questions people arrive with
Visitors arrive with a few questions and leave if the first screen ignores them. How we built Quackr's homepage around which country, which app and how much.

PortsmouthDevelopment2 min read
Build the admin, so you're not the admin
If a client has to email you to change a number on their site, the site isn't finished. How we design admin pages for the people who'll actually use them.

FoldDesign2 min read
Calm sells, even in crypto
Most crypto sites look the same: dark gradients, glowing coins and jargon. Why we designed Fold and Mozaic to feel calm instead, and what that took.

DarsDevelopment2 min read
Right to left, done properly
Arabic interfaces need more than a mirrored layout. What we learned building Dars, a revision app with Arabic set right to left and its harakat intact.