Celeste Motors

Days 4-7

On a fourteen-day build, what overruns is almost never the code: it is the validation round trip that drags, then the layout reopened too late, once half the development is already written.

• Three desktop and mobile mockups laid down before any development
• Sign-off taken on the mockup, not on half-written development
• Adjustments running alongside the start of development

ErgebnisThe fourteen-day schedule holds: validation no longer blocks the build, it runs alongside it.

Days 8-10

This is where it is won or lost: several bidders on the same car, a connection dropping in the final seconds. Show a stale price and the buyer bids against an amount that no longer exists.

• Bid price updated to the second, for every bidder on the lot
• Simultaneous bidders handled on the same vehicle listing
• Automatic recovery of the auction after a dropped connection

ErgebnisBuyers always bid against the real price, including in the closing seconds of a sale.

Days 11-13

A back-office is judged in daily use: if it is painful, the team stops posting arrivals and the online catalog ends up lying about what is actually for sale. The employee hired later never saw anyone use it.

• A complete back-office to post arrivals without going through a dev
• The team trained on the day of the production launch
• Onboarding videos for the staff who join the team later

ErgebnisThe online catalog keeps matching what is actually for sale, including for staff who arrived later.