Cases.

A course blueprint existed only as pasted chat text — six modules, ten tools, ten expert perspectives, nine patterns, three capstones. Two hours later: a live course platform with hosted sign-in, three checkout paths and its own domain. Built the way its subject teaches: draw the graph, wire the edges, ship the smallest system that works.

1. +0 min · Blueprint locked

   Three pasted drafts reconciled into one canonical spec: six modules, ten tools, ten experts, nine patterns, three capstones, $6.93.

2. +25 min · Homepage built and verified

   Single-file dark-theme page carrying the full curriculum, checked in a headless browser before anyone else saw it.

3. +45 min · Auth provisioned

   A Single Page App created in the Logto tenant, redirect URIs set for the apex domain, sign-in and sign-up wired on every page.

4. +60 min · Payments created

   The $6.93 course link, then a $19.63/mo membership with a 30-day trial that asks for no card. Three checkout paths, all Stripe-hosted.

5. +80 min · Learn and pricing pages authored

   An interactive architecture diagnostic, a gated module map, and a membership comparison modeled on the platforms it competes with.

6. +100 min · Served from the edge

   Page HTML stored in a D1 database behind a 600-byte Worker. Content updates are one SQL statement — no build, no deploy.

7. +110 min · Live on the domain

   graphengineerings.com and www attached to the Worker; sign-in tested end to end on production.

8. Later · Streamlined

   Dark theme set as default, a project folder written to local disk, a private GitHub repo populated, and this case filed.

The two hours buy you a platform real enough to sell from. They do not write the course for you.

The case log is itself a case. Four projects existed with nothing tying them together — no record of what went in, what came out, or how long any of it took. Twenty minutes later there was a public log.

1. +0 min · Read the existing site

   Design tokens pulled from the live stylesheet so the new page would inherit the look rather than approximate it.

2. +7 min · Case format decided

   Inputs, outputs, a timestamped sequence, and a required section for what is not finished. The last one is what makes the rest believable.

3. +14 min · Written and checked

   Rendered headless at desktop and phone widths. No dead links, no console errors, timeline collapses cleanly.

4. +20 min · Live

   The deployment bundle was assembled inside the browser — existing files fetched from the live site, new ones patched in, zipped in-page and handed to the host. Nothing was uploaded from a disk.

If you cannot say what went in and how long it took, you did not run a sprint — you just did some work.

A rough prototype of a robotics marketplace, and a domain that returned 404. One hour later: a working catalogue, a compatibility configurator, role-based sign-in, and a checkout path — live on the domain.

1. 14:20
   One link in

   A prototype URL. No brief, no spec, no design file. The prototype was JavaScript-rendered, so it was read in a live browser rather than fetched.

2. 14:22
   Design system extracted

   Palette, type scale, spacing and full copy pulled from the running prototype and rebuilt as tokens — not screenshotted, reconstructed.

3. 14:27
   Original artwork authored

   The prototype used watermarked stock photography. Flagged as unusable and replaced with a hand-written SVG hero and generated per-category graphics. No licensing exposure.

4. 14:40
   Sixteen pages generated

   Home, marketplace, solutions, resources, register, account, cart, about, contact, legal, transactional. Catalogue search, category filters and sorting wired client-side.

5. 14:45
   Configurator built

   Modelled on the two reference sites: choose the application, see only components that are actually compatible, price the whole build, add it to the cart as one order.

6. 14:52
   Verified before shipping

   Headless browser run: 18 internal links resolved, zero JavaScript errors, filters and cart maths checked, mobile viewport confirmed with no horizontal overflow.

7. 15:05
   Authentication provisioned

   A Single Page App created in the Logto tenant, redirect and post-sign-out URIs set for apex, www and localhost, and vendor / customer / manager roles created.

8. 15:28
   Live on the domain

   The domain's DNS already pointed at a host with nothing deployed behind it — the cause of the 404. The site was deployed to where the records already pointed, so not one DNS record had to change.

9. 15:35
   Sign-up tested end to end

   "Register as a vendor" clicked on the live domain, landing on the identity provider's account screen with the correct application ID.

10. 15:49
    Contact details rolled out

    Phone number added to nav, footer, contact, about, legal pages, both forms and schema.org markup, then redeployed.

11. 15:50
    Source handed back

    Full project committed and streamed to the local projects folder — build script, assets, API routes, and a Cloudflare Worker variant if hosting ever moves.

The hour buys you a real system to react to. It does not buy you a finished business.

The paper that started the current era is a PDF. PDFs do not reflow, do not link, and do not read well on a phone. This is the same paper as a web page.

1. +0 min · Source in

   The paper text, and a decision: republish as a document, not as an image of a document.

2. +6 min · Structure

   Sections, equations, footnotes and the author contribution note mapped to semantic HTML.

3. +14 min · Figures redrawn

   The architecture diagram and the attention diagrams rebuilt as vector graphics so they stay sharp and readable at any size.

4. +22 min · Tables and references

   Four results tables and forty references marked up properly rather than pasted as text.

5. +30 min · Live

   Published to attentionisallyouneed.uk.

A format change is a real contribution. The paper was always good; it just wasn't readable on a phone.

The question that started Justdoit.work: can a concept graph, 14,419 bookmarks, ChatGPT memory and Codex cowork history become a published ebook fast enough to matter?

Start with what you have. Build. Publish. Improve.

The largest of these builds, and the only one with paying customers on the other side. A virtual mailbox service across three California addresses, where the mail handling itself is run by agents.

1. It set the pattern

   Own the asset, automate the operation, publish the front door. Everything after this reused that shape.

2. The agent is the product

   Not a chatbot bolted onto a website — the agents do the actual work of logging and matching mail. The site is where customers see the result.

3. Newark is the anchor

   8407 Central Ave is the Bay Area location, and the registered address behind the later projects.

Sprints are how you get to a first edition. Businesses are what you do afterwards.