Concept, self-initiated. Backfill is not a real product and this was not client work.
The brief I set myself
Backfill checks database migrations before they reach production. Its buyers are backend leads who've been burned by a migration once, so every Postgres claim on the page had to be correct: an engineer who spots one wrong lock name closes the tab.
What I did
Positioning and copy around one promise: know what your migration locks before you merge it.
A visual identity taken from engineering drawings: graphite film, chalk linework, and one amber reserved for anything that blocks.
A live demo in the hero: a React code component that types a migration, measures the lock and draws the safe rewrite.
The rest of the page: the story, pricing, FAQ and a working waitlist form.
Responsive from desktop down to 390px.
Why it's built this way
Developer tools sell on proof, not adjectives. The hero shows the product doing its one job before the visitor reads a word, and the copy stays in the vocabulary engineers use themselves.