Loading_
Loading_
Notes on building SaaS and internal systems: how we scope, design and ship them.
Most SaaS products don't fall apart at launch. They fall apart six months later, when the first unplanned feature needs a place to live. Here is what a design system has to do before you write code, and how to tell if yours works.
01
An honest opinion.
If a flow is weak or a requirement does not add up, we say so. If you still choose the first option, it stays your call.
02
Finished, not abandoned.
Every problem reaches a conclusion: a solution, a revision, or a decision not to build it. Nothing is left hanging.
03
Fixed scope, fixed price.
You see the full price before you pay anything. Projects start with a 50% deposit.
We reply with the right scope and a price, by email or on Dribbble. No discovery calls.
You think of a name, check the .com, and it's taken. Add a word, still taken. Here is how to name a software product when the obvious domains are gone, and what to check before you commit.