1 designer + base44 + 3 days without proper sleep = Overdrive🤍 A job tracking system for a car repair shop.

✱ One board showing every car on the floor, where each one stands and what’s holding it up. Add a car, assign the work, and from there it tracks itself- what’s late, which parts have landed, who’s in today. Visit history, receipts, and a widget that tells you the next free slot you can offer someone.

Three days. Not smooth ones. But it’s live❗️

✱ Now the why, because none of those features were my idea.

My client owns the shop. Four mechanics, up to seven cars a day, no front desk. For months he’d complain about the same stuff whenever we talked: parts he ordered and forgot about, mechanics starting one car and getting pulled onto another, people asking when they can bring a car in and him not knowing what to say.

It was never a brief, of course, he was just talking. But one day I asked him properly: what do you need to see the moment you walk in?

✱ He said four things. And those four made sense as widgets, naturally.

Nothing on the job board gets typed in by a person. For example, a car shows as blocked because the mechanic who has it is off today- the board works that out and writes the reason on the card. He doesn’t walk around the shop asking anyone, he can just see it now.

✱ And the part nobody puts in these posts😅

→ It is my first time ever (!) using Base44 and I started without a paid plan, so I had a hard limit on how many prompts I got. You can’t iterate your way to something like that. Every prompt had to arrive already correct, which meant almost all of the work happened before I typed anything. I designed every screen and every state in Figma first, then worked out exactly what to ask for and in what order. I spent hours with Claude and Google figuring out how to phrase things, what would break, what to check before changing anything. I’d write a prompt and then throw it away and write a better one, because a wasted prompt cost more than the time did 🤷🏻‍♀️

Honestly, the constraint made it better. No aimless tinkering. Every change had a reason before it was made, and I still got every core feature I wanted in there.

✸Research: https://miro.com/app/board/uXjVEWOXy9k=/?share_link_id=813311021448 ✸Walkthrough: https://www.loom.com/share/69ffa2d58ca24e7bb10676be5173cdc2 ✸Overdrive live demo: https://overdrive-shop-flow.base44.app ✸X thread: https://x.com/gurvchler/status/2114517480152740121?s=20 ✸LinkedIn post: https://lnkd.in/p/dysRmrNw

Well done! And love the "no proper sleep" detail - sounds so familiar 😂

FirstReply — reply first, win the booking

Description

Event venues lose bookings because they reply a day late. By then the client has booked somewhere else. FirstReply answers every inquiry with a priced proposal and a held date in seconds.

The automation 1. An inquiry arrives from the venue page, or staff paste in an email. 2. AI extracts event type, date, guests, budget and requests, each with a confidence level and the exact words it came from. 3. Missing date or guest count? It writes a clarifying reply instead. 4. It matches the smallest free space that fits (or the two nearest free dates when it's booked), prices the right package and holds the date for 5 days. 5. The client gets their own proposal page and books with one tap. The hold becomes a confirmed booking. 6. Unsure details, over-budget totals or Review mode send it to a review queue first. Humans step in only when needed. 7. Views, acceptances and expiring holds update the pipeline and alert the team live. Every step is logged to the second.

The design A full design system first (tokens, type scale, components), built as a clickable prototype, then rebuilt in Base44 from prompts. Client pages are mobile-first; the venue side is desktop-first.

Try it Client side: firstreply.base44.app · Venue side: firstreply.base44.app/dashboard