Blueprints

How I build.

Not just what I use. How it all fits together, and the exact stack behind each kind of thing I build.

Marketing Website

A site whose whole job is to tell people what you do.

Web App

When people log in and the data belongs to them.

E-commerce Store

Selling physical products, and the question worth asking before you do.

Internal Workflow

Systems that do the work without anyone opening a page.

Another way to look at it

The same four side by side, at a glance. Each blueprint above has the detail and the reasoning; this is just the shape of the differences, and most of the rows are the thing that actually decides which one you are building.

	Marketing Website	Web App	E-commerce	Internal Workflow
Accounts and logins	No	Yes	Yes	Rarely
Data that differs per visitor	No	Yes	Yes	No
Takes payments	Digital only	Sometimes	Yes	No
Physical stock and shipping	No	No	Yes	No
Usually a platform, not a build	No	No	Shopify	No
Pages assembled	At build	Per request	Per request	No pages
Needs to rank on Google	Yes	Rarely	Yes	No
Has a UI	Yes	Yes	Yes	Often none
Who edits it after launch	Me, or a CMS	Its users	Platform admin	Nobody
Roughly what it costs to run	Near zero	Low but real	Monthly + per sale	Near zero

The jump that costs the most is the second row. Data that differs per visitor is what forces a database, a login and a server, and everything else on that side of the line follows from it.

Every piece is pulled from my full tools list Browse all tools