HPBuilt: finished builds published where customers actually look

A performance shop was finishing impressive custom builds and then not showing them to anyone, because writing it up meant reconstructing the parts list from an invoice and copying photos between two places. We built one build record that publishes to both the shop's storefront and an enthusiast publication.

The situation

The work was the marketing, and the marketing was not happening. Photos were on the phones of whoever took them. The parts list existed as an invoice. Getting one build published in both places meant assembling all of it twice, in two different formats, and it kept losing to actual work in the shop.

What we built

One record per build: the vehicle, the photos, and the parts that went into it, imported from the list the shop already produces rather than retyped. From that record the build publishes to the shop's own storefront and to an enthusiast outlet, each formatted the way that destination wants, without anyone assembling it a second time. Publishing can be queued to go out on a schedule, because the moment a build is finished is the moment nobody has time.

• One build record: vehicle, photos, and the parts that went in
• Parts imported from the list the shop already produces
• Publishes to the shop storefront and to an enthusiast outlet
• Each destination formatted its own way from the same source
• Scheduled publishing, because nobody has time on delivery day

Interface illustrations. Abstracted representations with placeholder content — never client data.

What changed

Finished builds get published, which is the whole point. The same record feeds both destinations, so the storefront and the write-up cannot drift apart.