What I learned after noticing empty offices and building a flexible workspace platform

kranthi kiran — Wed, 21 Jan 2026 11:54:36 +0000

A few months ago, I kept noticing something odd around me.

Freelancers, remote workers, and small teams were struggling to find decent workspaces without locking themselves into expensive monthly coworking plans. At the same time, offices and coworking spaces had empty desks and unused meeting rooms sitting idle most days.

That disconnect stuck with me.

Instead of jumping straight into building a “startup,” I decided to slow down and treat this as a learning experiment. I wanted to understand whether this was a real problem or just something I personally observed.

Start with the problem, not the product

Before writing serious code, I spoke to freelancers, remote workers, and a few office managers. The feedback was consistent:

People want flexibility, not long-term commitments

Office owners hate seeing unused space but worry about misuse and trust

Simplicity matters more than feature depth early on

This helped me avoid over-engineering and focus only on what actually mattered.

Building small and listening early

I’m currently building a simple platform that allows people to book desks, private offices, or meeting rooms by the hour or day, while letting office owners list unused spaces. But more importantly, I’m keeping the product intentionally small.

Every conversation teaches me something new. Often, what users struggle with isn’t what I originally assumed.

What I’m learning so far

Marketplaces are harder than they look

Feedback is more valuable than assumptions

Shipping something small beats waiting for perfect

I’m sharing this here to learn from others building in public. If you’ve worked on marketplaces, PropTech, or products for remote teams, I’d love to hear what surprised you most.

DEV Community: kranthi kiran

What I learned after noticing empty offices and building a flexible workspace platform