Case study · Automotive

Four working weeks,
from a prototype to production.

A dealership finance tool started as a vibecoded prototype: a front end that could show a deal, and nothing behind it a store could run. The budget was small, so a month of work was spread across a longer horizon. Low commitment. A collaborative workflow. Four working weeks later, it was a production product.

Industry
Automotive · dealership finance
Engagement
Prototype to production
Commitment
Low — a month of work, spread out
Working time
4 weeks
4 wk
Prototype to production
Working time, not calendar
1 month
Of effort, spread out
A longer horizon, on purpose
Low
Commitment to start
See progress, then decide
Together
Collaborative workflow
The product shaped in the open
The starting point

A prototype that looked finished

The idea was a desk for a dealership: pick a vehicle, structure the deal, see the payment, see what the store makes. Someone had already vibecoded a front end that demonstrated it. It looked like software. It was a prototype — a generated UI with the calculator on the page, and no production system underneath.

The budget to take it further was small. That ruled out the usual shape of a build:

  • A demo standing in for a product. Vehicle, payment, profit — all visible, none of it backed by a real catalog, real values, or a lender’s rates.
  • A budget that cannot buy a team and a quarter. The conventional path is a large commitment up front, before anyone knows the idea deserves it.
  • Progress you only see at the end. A lumped project hides whether the prototype is becoming something a dealership can use.
  • A workflow that keeps the client outside the work. Spec, disappear, deliver. A small budget cannot afford a miss at the end of that.
What we built

The prototype, made into the product

The front end stayed the seed. Around it we built the production application: Laravel and React, the deal desk a store actually runs. Four working weeks of effort, spread across a longer horizon so each step was visible and the commitment stayed small.

  • The deal desk, in production. Structure a deal — vehicle, payment, rate, term, aftermarket products — and see what the store makes.
  • Real vehicles, real values. A catalog, imports, and valuations that move when the mileage and the deal change. The prototype’s numbers became the system’s numbers.
  • The rest of the desk. A market scan over inventory, lender rate sheets, credit applications, and a profit scoreboard. The workflow around the calculator, not just the calculator.
  • A month of work, shown as it happened. Spread out on purpose. Low commitment at the start. Collaborative the whole way — the next slice followed what the last one proved.
Before & after
 The prototypeThe production product
What existedA vibecoded front endA dealership desk you can run
StackA generated UILaravel · React
The numbersOn the pageCatalog, values, lender rates
CommitmentA full build, or nothingA month of work, spread out
How you saw itAt the end, if at allProgress along a longer horizon
Working time—4 weeks
How a small budget did it

AI gets the idea to market faster

Four working weeks is enough when AI does the volume of the build and the people stay on the product. The small budget changed the shape of the engagement: a month of work, split across a longer horizon, so progress was visible and the commitment stayed low. The workflow was collaborative. Each slice was something to react to, and the next slice followed.

4 wk
of working time, from a vibecoded prototype to a production product. The calendar was longer on purpose. The effort was a month, spread out so a small budget could see the idea become real before committing further.

What that workflow was for:

  • Start small. A month of work is a decision you can make. A staffed quarter is a decision most prototypes never earn.
  • See it as it grows. Spreading the month out meant the prototype’s replacement showed up in pieces: the desk, then the values, then the rates, then the profit.
  • Decide together. Collaborative, because a low commitment only works if the people with the idea are in the work, not waiting on a reveal.

The same idea, pointed at a product that did not exist yet, is a longer story: a full application, API and mobile included, written by AI and shipped in about four to five months. Read that story.

The impact

A production product, on a small budget

The prototype stopped being a demo. A dealership can run the desk: vehicles, values, payments, lender rates, and what the store makes. It took four working weeks of effort, arranged so a small budget could watch it happen.

4 wk
Working time to production
A vibecoded front end became the dealership product.
Spread
A month of work, a longer horizon
Progress stayed visible. The commitment stayed low.
Faster
Idea to market, with AI
The volume of the build fit a budget that could not staff it.

Four working weeks is the effort. The calendar was longer because the budget was small: that month was spread out so progress was visible and the commitment could stay low. We are not publishing the contract value or a dealer count.

A prototype you want in market?

AI gets an idea there faster, and the way in can be a month of work, spread out, low commitment, collaborative. Fifteen minutes is enough to see if yours fits.

Book a call→All case studies