Superhero Design Hub Questions · Victory Truck Body · / 9

Victory Truck Body

The questions
I would be asking

Rustin asked two of these last week. The rest are the ones I would want answered if I were sitting on your side of it.

01

Why do most
projects like
this fail

32%
of configure and quote projects are counted as successful

That is the published industry figure, not my estimate. I would rather you heard it from me than found it on your own later.

What is interesting is that the software is almost never the reason. The same seven causes come up again and again, and every one of them is a project decision rather than a technical one.

01Product data was never properly structuredOptions live in someone's head, or in a spreadsheet nobody trusts.
02Integrations breakManufacturers hit integration failures more than twice as often as software companies.
03Pricing rules were never written downSo they get discovered halfway through, and the build changes shape.
04Change management is underfundedThe tool works. Nobody uses it.
05Workflows built from theoryBuilt from how a process is described, not how it actually runs on the floor.
06Scope creeps past what was agreedEverything is in scope because nothing was ever ruled out.
07No clear ownership afterwardsThe people who understood it leave, and it quietly rots.

02

And why this
one would not

Same seven, in the same order, with where each one sits in what I have proposed.

01Already structuredAll twenty six of your option groups are encoded, with the dependency rules live. You can click them today.
02No integrations in Phase OneNothing touches Salesforce or Rootstock. Prove the front end first, connect deliberately later, once it is earning.
03Rules are written downWriting them down is most of what I have already done. Where I have inferred something, I have said so out loud.
04One range, then widenPhase One is one body range out of several. Go live with two or three salespeople first if you want.
05Built, not describedYou cannot argue with a specification. You can argue with a page you have clicked.
06Scope fixed in writingOne body range, defined by the option list Tarik sent. Anything else is quoted, not absorbed.
07Repository from day oneEvery version, in your hands, from the first build onwards.

I am not claiming this cannot go wrong. I am saying I know the seven ways it usually does, and the plan is shaped around each of them.

03

What access
do you need

None.
no logins, no systems, no customer data

This is the question I would want answered before signing anything, so here is the whole of it.

×No Salesforce login
×No Rootstock or ERP access
×No copy of your customer list or contacts
×No employee records, no accounts, no payment data
×No access to your network or internal systems

What I do need is this, and the list does not grow after you sign.

✓STEP files for the option parts, the same way you sent the example body
✓Your vector logo and brand RAL references
✓Confirmation of a handful of rules I have had to infer
✓Which options count as standard on a base body

On pricing, I would rather not have it.

I will build the structure and your team enters the numbers into it. Your margins stay yours and I never need to see them.

The quote pages hold a company name, a reference, a specification and a price. No individual contact details, no payment information, nothing that would matter if it were read by the wrong person.

Where I do hold anything on your behalf it is covered by a data processing schedule in my terms, which sets out that I only process it on your instruction, and hand it back or delete it whenever you ask.

04

What we would
ask you at
scoping

Scoping happens in the first two weeks, before any modelling starts. It is a handful of questions rather than a workshop, and most of them can be answered on a message.

Here they are now, so nothing about it is a surprise.

How many body ranges do you build?Body types rather than body sizes, and not how many variations of this one. Phase One covers the dry freight van body. This tells us what a Phase Two or a second range would actually involve.
Which options count as standard on a base body?The ledger flags anything non standard. That flag is only useful if the baseline is yours rather than mine.
The walkramp matrix. Answered.Confirmed by Victory on 20 August 2026. The body runs 2 feet longer than the ramp, so a 14 foot ramp needs a 16 foot body, and 14 feet is the longest ramp built. Body sizes run 12 to 28 feet on 2 foot increments. The configurator follows the real rule now rather than my guess at it.
Does the visual appear live in front of the customer, or arrive attached to the quote?Both work. They shape different things, so it is worth deciding early.
How do your dealers configure and order today?This does not affect Phase One. It affects whether a dealer version is worth doing later.
What is your current quote turnaround?So there is a real number to measure against rather than a claim.
Who signs off a specification before it goes to the shop?The system should reinforce that step, not work around it.
Which parts can you supply as STEP files, and when?The honest answer to this is the only thing that can move the timeline.

05

Can we change
it once it
is built

Yes, and I would expect to change a fair bit of it.

What you have seen was built from an option list and a week of research. It was not built from watching how Victory actually works, because I have not seen that. So some of it will be wrong, and the review rounds inside Phase One exist for exactly that reason.

Design, layout, wording, the order things happen in, how the workflow runs. All of that is yours to shape. It is expected, not extra.

Where it becomes a quote rather than a change is genuinely new capability. A whole new option group, or another body range. That is new parts and new rules rather than adjusting what is already there.

Once it is live, most day to day changes are data rather than code. Option names, values, wording, colours. Either I do those on a message, or your own team edits them directly. I would recommend the second.

06

Why not just
extend
Salesforce

Because it is a different job, and this does not replace it.

CPQ configures and prices. It is good at that. What it does not do is produce the thing your customer actually looks at. They still receive text.

This sits in front of your quoting, not instead of it.

It takes a specification and turns it into something a fleet buyer can see, and a dimensioned drawing a leasing company can fund against.

Worth knowing for the comparison: a Salesforce CPQ project on its own runs to a median of around eighty eight thousand dollars over fourteen weeks. That is before anything visual exists.

07

What does it
cost us in
our own time

Less than most projects of this size, and I would rather set the expectation properly than undersell it.

The real ask is the option part files, and somebody senior enough to answer questions about how you actually build. Realistically an hour or two a week during scoping, a review round when the renders land, and a look at the finished pages before go live.

The honest risk to the timeline is the part files. If those arrive late, the dates move by the same number of days. Everything else is on me.

08

What if you
get hit by
a lorry

Rustin's words, and a fair question for a business betting on one person in another country.

✓A private repository Victory has access to from day one. Every version, from the first build onwards.
✓Deliberately not exotic. Static pages and plain JavaScript. No unusual framework, no platform I have locked you into. It runs on any host, and moving it would take a competent developer an afternoon.
✓A handover document alongside it. How it is built, where everything sits, how to change the option map, how to deploy it. Written for somebody who has never spoken to me.
✓A continuity clause in the terms so you are never left stranded.

The formal version of this in our industry is source code escrow, where a third party holds the code and releases it if something happens to the supplier. It costs a couple of thousand a year, and it only ever grants access, never ownership.

You are getting the better half of that arrangement for nothing.

And the quote pages themselves are static files. Every quote ever generated keeps working, even if every system of mine goes dark.

09

What if it
does not work

You have already clicked the part most projects are still arguing about at week ten.

Beyond that, the payment structure is half at the start and half at go live. If we never reach go live, the second half is never invoiced. The monthly does not begin until it is running either, and there is no minimum term on it.

Phase One is one body range out of several, deliberately. It proves the approach on your highest volume product before anything else is committed to. If you want to go further still, we can go live with two or three salespeople first and widen it once they are happy. That is a rollout decision rather than a commercial one, and it changes nothing about the price.

If there is a question in the room that is not on this page, send it over and I will answer that one straight too.