B&J architectural decision: custom platform vs Manage Petro / PDI / Cargas — why custom won
Created 2026-05-24
This is the most interesting story angle outside the tanks-as-objects decision. The KB has flagged it as worth interrogating, and it is.
Industry-standard options that B&J could have bought
- Manage Petro — cloud, marketed at exactly this segment
- PDI Enterprise — legacy big-iron ERP
- Cargas Energy — Microsoft-stack ERP
- RR Fuel / Adam Software / Boltrics — regional ERPs
Why custom won — six reasons
- Pricing model. Industry ERPs charge per-seat or per-tank; for an operation of B&J's size this is consistently more expensive over a 3–5 year horizon than building it.
- AI integration. B&J's roadmap explicitly includes AI-assisted lubricant search and AI-assisted consumption modeling — neither is available in the industry ERPs, and the integration cost on top of those platforms approaches the cost of building from scratch.
- Custom marketing-site integration. The marketing site, the customer portal, the CRM, the lubricants catalog, and the embedded data widgets all share a design system, component library, and API layer. No industry ERP integrates with a marketing site in this way; they integrate by exporting a CSV.
- Domain modeling fidelity. Generic CRMs (HubSpot, Salesforce) do not model tanks, contracts, degree-day zones, or multi-site accounts. Industry ERPs do, but they impose their own data model — which does not always match how B&J actually operates.
- Self-hosting. No subscription costs, full data sovereignty, no platform lock-in. B&J's data lives on a self-hosted VPS at ~$10–20 CAD/month all-in.
- The Petro-Canada relationship. B&J is a Petro-Canada authorized wholesale marketer. The lubricants catalog (350+ products), the cardlock network (SuperPass/Petro-Pass), the brand surfacing — all need to be modeled in a way that an off-the-shelf ERP does not support natively.
[Verified — synthesized from crm_project_plan.docx, BoucherJones_MarketingSite_TechStack.docx, Kevin's memory]
Honest counter-argument (for balance in any writing)
Building custom takes longer than buying. The trade-off is short-term speed vs. long-term fit + cost + AI capability. B&J chose long-term fit.
[Our observation] — this is the line to include if the case study reader is comparing approaches.