ABOUT HONEYCOMB

Built by operators.
Used by the team that built it.

Most building software is built by software people who've never run a building. Honeycomb is the other thing. We sell the platform our own team uses to run real real estate every day. The product gets better because we feel the bugs first.

THE FOUNDING TEAM

Two halves of the same problem.

Honeycomb's founding team has decades of experience across two disciplines that almost never end up in the same room: data infrastructure and commercial real estate. That overlap is the reason Honeycomb exists in the shape it does.

Background · Data infrastructure

Greenplum

Years inside the massively-parallel data warehouse that powered some of the largest data workloads on earth. Lesson learned: every system in a building produces data, but the data is worth nothing until you can ask one question and get one answer across all of them.

Background · Commercial real estate

Quadrant Investment Properties

Operating, acquiring, repositioning, and selling buildings as a CRE principal. Lesson learned: the operational side of a building is where the next dollar lives, and almost nobody on the software side of the industry actually understands how a building gets run on a Tuesday afternoon.

Honeycomb is built where those two worlds meet: data infrastructure that can handle every signal a building produces, and operating instincts honed inside a real CRE portfolio. Most PropTech misses one or the other. We started Honeycomb because the platform we wanted didn't exist.

THE LAB

We run a real building.
So our software has to actually work.

Cue is the coworking brand we operate: two Dallas coworking locations inside larger buildings, including 21,000 sf at St. Paul Place. Cue is a separate business; what makes it run as well as it does is the Honeycomb technology underneath.

At St. Paul Place, Honeycomb runs both the wider 273,000 sf building and Cue's space inside it. That's where we proved what happens when the silo between "coworking tenant" and "building operations" collapses: members share amenities with building tenants, ownership sees both populations on one dashboard, and Cue went from 15% to over 90% occupancy after implementing Honeycomb and rebuilding its marketing.

Cue is also our lab. New product gets shipped to Cue first. If it works against our own P&L, it goes to customers. If it doesn't, it gets fixed before anyone else has to live with it.

WHAT WE BELIEVE

Buildings shouldn't run on
ten disconnected apps.

A building is one system, not ten.

Most modern buildings are stitched together from ten independent vendor apps. Tenants juggle them. Managers stitch them. Owners can't see across them. Honeycomb is the operating system that ties them into one.

Operators should build operator software.

We've seen what happens when buildings buy software from teams that don't run buildings. We're the team that runs buildings. The product is opinionated in ways that only show up after you've actually had to use it on a Tuesday at 4pm.

Start where the dollars are. Then run the whole thing.

Parking comes first: fastest payback, lowest disruption, highest pain. Once parking runs on Honeycomb, nothing about your building is broken enough to justify staying on the rest of the stack. We grow into the whole asset because the integration is the whole point.

Show the math. Defend the claim.

We publish how we think about the numbers: $1/PSF in NOI, +35% parking oversell, live parking revenue in under 30 days. We'd rather be in a room defending a number we believe than puffing a number we don't.

Talk to a building operator.

Thirty minutes. We'll run the math on your building and tell you honestly whether Honeycomb is a fit. Not a salesperson on the call. An operator.