Building a marketplace platform for on-demand storage in 12 weeks

The hospitality and retail sectors face a recurring constraint: seasonal inventory spikes create temporary storage demand, but long-term warehouse contracts are inflexible and expensive. Hotels accumulate off-season furniture and décor. Restaurants store equipment between renovations. Retailers need overflow space before holiday peaks. Each business solves this problem in isolation — renting from the same handful of generalist warehousing companies, paying premium rates, and committing to contracts they don't fully use.

Keepwhat saw this friction as an untapped marketplace opportunity. Thousands of small- and mid-sized logistics providers across Europe had spare capacity sitting idle between contracts. Connect that supply to seasonal demand, and both sides win — hosts monetise empty space, renters pay less than commercial warehouses, and utilisation improves across the logistics sector. But the marketplace didn't exist, and building one from scratch on a traditional software timeline meant months of planning, design iteration, and fundraising before a single customer could test the concept.

What we learned

Twistag compressed a typical 6-9 month marketplace build into a 12-week sprint by prioritising ruthlessly. The MVP solved two problems: matching supply to demand, and proving the unit economics worked. We built a two-sided marketplace in React and Node.js running on PostgreSQL and AWS, with user authentication, real-time availability updates, booking flows, and payment collection. The design was mobile-first — logistics providers needed to list inventory on phones, and renters needed to search and book on the go.

The architecture decision that mattered most was decoupling the booking system from the logistics backend. Rather than integrating with each partner's ERP systems in month one (which would have doubled the timeline), we built a simple API boundary and handled fulfilment coordination manually. Once the marketplace proved demand existed, integration became a backlog feature — the manual work stayed contained and scalable.

We shipped the marketplace in 12 weeks. Keepwhat onboarded the first three logistics partners as beta hosts, and within four weeks they had thirty paying customers. The supply side proved the strongest constraint — renters queued up the moment listings appeared. The mobile-first design and manual fulfilment together meant Twistag could handle real load without getting stuck on integration work that wasn't pulling its weight.

What this shaped

The marketplace generated €5K in monthly recurring revenue by month four — more than the company projected for month eight. Conversion from inquiry to booking ran at 20%, well above typical marketplace benchmarks. By month four, the platform had onboarded five major European logistics providers and 100 active customers across hospitality, retail, and short-term events.

The manual fulfilment work we'd deferred became an asset, not a bottleneck. Because Twistag handled the first hundred transactions by hand, we understood edge cases and customer friction points that a direct ERP integration would have missed. By month six, Keepwhat had shifted from proving unit economics to scaling acquisition. The 12-week MVP had compressed a two-year capital raise into a working business.

What this proved