48 Hours, One Team, One Prototype

Last weekend, I did something completely new for me: I joined a hackathon and spent 48 hours in a hub building a product from scratch with people I had only just met.

I didn’t go in with my own idea, even though I’m the kind of person who always has a dozen concepts floating around. I went with an open heart and a simple goal: to get the experience. I wanted to listen, feel the energy, and see if any pitch genuinely resonated.

And it did — just one.

When the pitching started, most ideas were interesting, but only one clicked. I walked up to Ira, who pitched the initial idea, and we started talking. We aligned on how we both saw the problem and what kind of solution would make sense.

From there, the team formed naturally. A couple of project managers joined. Developers joined. In the end, we were seven people, and it felt surprisingly balanced — the kind of mix you’d intentionally recruit for a real “day one” startup team.

A hackathon forces pace and clarity

There’s no room for vague roles, endless debating, or waiting until the “next meeting.” Within hours, we had a clear problem statement, a direction, and responsibilities. Everyone leaned into what they were best at — product thinking, UX, logic, pitch structure, prototyping, validation, and technical build.

I also found myself organically stepping into the team lead role — something that comes naturally to me. I ended up:

• organizing standups

• managing time blocks and priorities

• keeping the pace up

• making sure responsibilities were clear

• shaping the storyline and refining the pitch.

  
  

In short: the problem and the prototype

Here’s the core issue we tackled:

SMBs don’t have continuous visibility into short-term cash risk.

Forecasting and “what-if” testing are still mostly spreadsheet-driven — manual, fragmented, and slow. The forecast is almost always behind reality: payments come in late, costs change, tax weeks hit, and payroll lands.

In other words, many businesses don’t fail because they’re unprofitable on paper — they fail because cash timing becomes a silent killer.

Our solution: WhatIF — a “cash assistant” for stress-testing

We built WhatIF Sandbox: a 13-week cashflow stress-testing tool that turns spreadsheet forecasting into something more immediate, visual, and decision-oriented.

The goal wasn’t “another forecast.” The goal was simple: help leadership see runway risk early and test scenarios in minutes — not days.

I walked away with a few things I’ll carry forward:

1) A reminder of how powerful fast collaboration can be

Seven people who didn’t know each other… working like a real team within a few hours. Honestly, I want to bring more of this rhythm and clarity into my own teams.

2) Confidence through vagueness

Not “I have all the answers,” but: "I can enter uncertainty, find the right people, and build something real — fast".

3) Pressure doesn’t break good teams — it reveals them

In 48 hours, you see who communicates, who takes responsibility, who stays calm, who pushes forward, who supports others, and who keeps quality high.

4) AI doesn’t replace product thinking — it accelerates it

We used Lovable to help us move faster. It didn’t give us the business model or the narrative — it enabled us ship quickly, so our thinking became tangible.

5) We need more of this

Hackathons make building accessible. They turn “someday” into “done by Sunday.”

I came for the experience

— and I got exactly that, and more.

I met brilliant people.

I watched a real team form in real time.

I found my place in it.

And I learned (again) that with the right setup, focus, and AI tools, you can go from idea to a working prototype in a very short time.

Here is a snapshot of the working prototype we built: