Six days.

02The constraint

• ×No backend access. Not a customer, not a partner — everything I had came from outside the product.
• ×Four hours of the founder explaining the product on camera, and almost none of it written down anywhere a reader could find.
• ×Four other project streams were running the whole time.

03What I built

1. 01The client's own six-portal positioning, taken as the strategy and built out as the site: supplier, contractor, employee, dealer and partner, customer, QR asset.
2. 0228 fixed routes plus a 14-lesson academy collection — 42 pages against the old site's six-URL sitemap.
3. 0338 channel videos transcribed and rewritten as lessons that stand on their own, with the film beside them.
4. 0453 answered questions, written out rather than linked to.
5. 05A three-way comparison table that leaves cells blank where the product loses, and cites its competitors' public pricing pages in the footnotes.
6. 06Ten verify scripts in the build chain — content, images, sections, videos, FAQ, motion, type scale, design law, tenure, launch routes — each one failing the build rather than warning.
7. 07No border radius anywhere on the site. A script fails the build if one appears, and fails again if the token is redeclared.
8. 08Tenure computed from the 2002 partnership date, never typed, so the site cannot go stale on its own age.
9. 09The two videos that lived on the old host re-hosted locally; they die with the subscription otherwise.
10. 10128 source images built into 558 committed derivatives, with no image CDN.

04Elapsed

Directory created

6 August 2026, 03:22

First commit

6 August 2026, 04:27

Site live, link sent

10 August 2026

Elapsed

4 days to live · 6 to full scope

05What it produced

Four days from an empty directory to a live product. Nobody had asked for it.

In the same six days: a reconnaissance corpus on a company I did not work for. A rebuilt marketing site with its own CMS. Thirty-eight of their videos transcribed and rewritten into a fourteen-lesson written academy. A reverse-engineered replacement front end running live against a production API I could only observe from outside. A patent analysis. Pricing. Three agreements.