I’ve spent a fair amount of time looking at iPacket both as a buyer and from the dealer side. I think it’s a solid solution. The UI is clean, it’s easy to share, and it does a good job packaging baseline vehicle information in one place.
From a buyer’s perspective though, what I usually see in an iPacket is essentially a digital sales brochure: OEM video, window sticker, and the same core specs that already exist on the VDP. That’s useful, but it’s still mostly static information.
Where I think there’s a missing, complementary layer is around the questions buyers are
actively asking elsewhere once they see a car.
The core question is simple: “Should I buy this car?”
But that breaks down into a lot of sub-questions buyers leave the VDP to answer:
- What should I ask the seller about this specific car?
- What’s a good answer vs. a bad answer?
- What needs to be inspected, and what should increase confidence when it shows up on an inspection?
- Does this car actually have the packages I care about, and what do those packages really mean in practice?
- Is it priced well relative to similar cars?
- What’s ownership likely to cost, and how does that compare to others in its class?
Traditionally, we give buyers raw data and expect them to interpret it on their own. Now we have the ability to take that same data and directly answer those questions for them, on the page, in context.
That’s the gap we're working on. Our thesis is that answering the inevitable questions upfront, and having buyers and sales teams looking at the same answers, keeps shoppers on the page longer and results in more confident, higher-quality leads.
We integrate directly inside iPacket as well as on the VDP:
Move the Cars Carfax Can't | Carvia Dealer Widgets | Carvia
Happy to share more or hear how others are thinking about this layer.