B&J case study — suggested narrative angles, ranked, with a recommended hybrid lead
For a portfolio entry on candidcreative.ca, here are the strongest angles in order:
"How we modeled tanks as first-class objects to build a fuel CRM from scratch." Strongest because it is specific, defensible, and tells the architecture story that competitors cannot copy. The case study lead is the data model. See B&J data model — first-class entities, including TANKS (the most quotable architecture decision).
"Walk with quiet confidence — the editorial discipline that shaped a 50-page Petro-Canada distributor site." Strongest because it is the positioning story, which is harder to fake than the technical story. The case study lead is the voice. See B&J positioning — "walk with quiet confidence" (editorial discipline, NOT a public tagline).
"From WordPress to a Next.js platform with embedded data widgets, a 350-product lubricants catalog, and AI-citation-readiness baked in." Strongest as the headline because it is the most concrete "before and after." See B&J live site inventory — page count, IA, what is planned (headline KPI: ~50 pages live vs ~6 before).
"Building the platform behind a regional fuel distributor — research first, code second." Strongest because it foregrounds Candid Creative's research depth, which is the under-told differentiator. See B&J — source documents in the project knowledge base (so the KB knows what is and is not ingested here).
Recommended hybrid
Lead with #3 in the H1 + headline KPI ("~50 live pages, 350+ products catalogued, 0 subscription costs"), then anchor the narrative on #1 (the data model) with #2 (the positioning) and #4 (research depth) as sub-themes.
Related
- decision-record B&J data model — first-class entities, including TANKS (the most quotable architecture decision)
- reference B&J positioning — "walk with quiet confidence" (editorial discipline, NOT a public tagline)
- reference B&J live site inventory — page count, IA, what is planned (headline KPI: ~50 pages live vs ~6 before)
- reference B&J — source documents in the project knowledge base (so the KB knows what is and is not ingested here)