How I used ImageGen and CAD to make my first hardware prototype
I started with a Blender golf cart and a generic screen, used ImageGen to find the form, and kept pushing the CAD until one enclosure became two print architectures.
Read postJustin Hendrickson / Blog
Blog posts from inside the work.
Every post begins with something that actually happened: a product that existed first as a render, a page cycle cut to 48 hours, a reported ROAS increase that complicated the next budget decision, or a homepage that compiled before its story was true.
Published posts 04
All posts.
context_release
concept / 03source→rules→draft→public
- 01Claim tracedsource + limit
- 02Scope heldowned verb
- 03Boundary checkedpublic only
build status donetrue?
AI made the website fast. It did not make the story true.
The first homepage compiled but described almost nobody. The system improved when prompts gave way to sources, constraints, decision rights, and release gates.
Read postallocation_review
concept / 01reported return+40%
acquisition cost−35%
lifetime valueheld
Decision questionWhere does the next dollar go?
ROAS rose 40%. The next dollar was the harder question.
In a consumer growth role, reported ROAS rose 40% in nine months while CAC fell 35% and LTV held. The useful lesson was how pacing, lift validation, and channel allocation kept one dashboard metric from making the whole decision.
Read postlanding_page_loop
concept / 02Gorgias→Meta→NPS→page
- 08:14Signal connectedsupport + acquisition
- 11:32Page decisionpromise rewritten
- 47:51Release checkedcustomer response
previous loop 14 days48 hrs
Two weeks to 48 hours: rebuilding the landing-page loop
Gorgias, Meta, and NPS held different pieces of the customer problem. Connecting those signals to a page release cut the landing-page cycle from two weeks to 48 hours.
Read post