The MVP foundations you will not throw away

Fast does not have to mean disposable. Four things worth doing properly in week one.

Sample article6 min readSquad 02
01

Auth, tenancy, migrations, deploys

Everything else in an MVP can be rough. These four cannot, because every later feature sits on top of them, and replacing them means stopping. Spend the first week here and the next twelve go faster.

02

What to skip

Design systems, microservices, a mobile app, analytics dashboards. All of it can wait until there is a user asking for it. The product that proves the idea is smaller than the product in your head.

Illustrative excerpt
create table tenants (id uuid primary key, name text not null);
alter table projects enable row level security;
-- Boring on day one. Priceless on day four hundred.
03

The rule

Build the smallest thing that can be used for real, on foundations that survive being right.

Sample article. Written to show the register, not to claim the result.

More on product.

  1. 01

    Building right-to-left interfaces from day one

    Mirroring a finished English product is the expensive way. Here is the cheap way, and the three things that never flip.

    Product5 min readSquad 03

Next article.

Payments

5 min readStore the ledger, not the balanceRead the article

Got something complicated?

Tell us what you're building. You'll hear back from an engineer, not a sales team.