Launch strategy for Penske Digital Fleet, a first SaaS platform entering a category with a credibility problem, and a launch experience designed to turn that distrust into the differentiation.
Huge Inc. · 2026Penske Transportation Solutions, launching Digital Fleet, its first SaaS fleet-intelligence platform.
GTM strategy through design and build of the launch experience. Huge Inc., invite-only partner.
Product Strategy lead: research synthesis, user strategy, personalization, conversion architecture, launch options, delivery definition.
~15 across strategy, design, content, and technology.
A genuinely differentiated product, decades of operational credibility and an AI engine trained on real fleet outcomes, aimed at buyers the category has trained not to believe anyone.
The target buyer runs a fleet of 50 to 2,000 vehicles and should have been receptive. They weren't, and the research explained why. Fleet software vendors systematically over-promise and under-deliver, and the buyers know it. These are operators who discover products through peer networks, evaluate over months with a full committee at the table, and treat every "AI-powered" claim as a red flag rather than a reason to buy.
The product also had to launch without brand equity in the category, without public customer proof, and with naming still unresolved. Into that skepticism, the standard SaaS playbook, a feature grid behind a Request a Demo wall, would have been invisible: every competitor already runs it.
For this buyer, the website isn't a support tool for the sales process. It is the sales process.
How do you launch a first SaaS product into a market whose defining characteristic is earned distrust, and turn the category's credibility crisis into the product's differentiation?
I co-led the stakeholder interview program with our business strategy lead and synthesized it with two further streams: the client's own multi-year customer research, several hundred interviews deep before we arrived, and independent industry evidence. Their program had been built to answer what product to build; it was never designed to answer how this buyer buys. I extended it into that go-to-market territory, and the extension surfaced what the launch would hinge on: the near-total absence of the category from the review sites buyers trust, and the loss-aversion reality of the purchase. These operators buy to avoid pain, downtime, compliance exposure, being burned by another vendor, not to chase upside, which the category's gain-framed messaging entirely ignores.
The differentiation strategy came from a benchmark I built comparing what category leaders like Samsara, Uptake, and Fleetio claim in their marketing against what their customers report in reviews. The pattern was systemic, in a market projected to reach $122.3B by 2035. The strategic implication wrote itself: Penske should not out-promise the category; it should out-prove it, risk removed, not gains promised.
I defined the ideal customer profile, the DIY-owner fleet operator, and the sub-segments inside it, each with its own journey map and its own threshold for believing a software claim. The structural consequence was the Buying Committee Layering model, built on one insight: the site's primary audience is not the buyer. It is the internal champion who has to sell the product to a CFO, an IT lead, and an operations owner without a vendor in the room.
The research verdict was blunt: a single Request a Demo form won't work for a skeptical, multi-month buyer. I designed conversion as graduated commitment across three tiers, so the majority of visitors who will never book a demo on a first visit still convert in a way that moves the journey forward.
Within a vision co-created with our design and technology craft leads, I owned the personalization strategy: an experience that observes behavior and surfaces the most relevant next asset for each visitor, without requiring them to configure anything or identify themselves. I structured it as five intelligent moments across the journey, each designed around the fleet operator's actual decision logic and progressively personalized by the client's intelligence engine. For an audience that distrusts AI claims, the strategy made the site the proof: the product's intelligence demonstrated rather than asserted.
I led the kickoff workshop that assigned clear ownership across the third-party ecosystem the site had to live in, helped produce the full IA sitemap and blueprint with the content strategy team, and built the roadmap with user value, business value, and effort scoring. Delivery ran on weekly sprint briefs I wrote for the next set of pages, each illustrated with sketches of the content blocks the page needed to carry its narrative. The sketches gave the UX and design teams direction a prose brief can't, and because the client found it hard to hand us requirements, the briefs made recommendations they could react to instead, keeping them in the loop and the crafts aligned sprint after sprint.
Two decisions defined the engagement more than any deliverable.
From kickoff I framed the launch as three paths of increasing intelligence, a craft-led experience, a rules-driven companion, and a fully agentic experience, each with its capabilities, content requirements, technical dependencies, team implications, and timeline. That framing is why AI personalization was on the table from day one rather than a late addition, and it did its hardest work after the vision landed: when leadership wanted the most advanced experience at launch, they could choose with the trade-offs in view, and the ambition got a structure that could survive delivery.
Every competitor leads with AI claims, and the research said the buyer discounts exactly that language. The resolution was to stop claiming and start demonstrating: intelligence the visitor experiences on the site itself, with specificity and proof carrying the words.
The vision landed strongly enough to create its own problem: leadership didn't want the agentic experience as a future state. They wanted it at launch.
That response converted a standard-scope website engagement into a materially larger program conversation. The expanded ambition wasn't rejected or rubber-stamped; it was sequenced, through the options framework built for exactly that decision.
Most go-to-market work optimizes the message. This engagement changed the unit of strategy: when the buyer's defining trait is earned distrust, the product's first job is to be believed, and the website carries that burden alone, long before a salesperson enters. Research extended from what to build into how the buyer buys, differentiation built on proof instead of promises, and a launch designed as graduated trust: go-to-market treated as a product in its own right, engineered to earn the next step in a category that has stopped believing its vendors.