Floor plans

HoneyBook's first native floor planning tool, built for its highest-value vertical.

Role: End-to-end product design
Timeline: Apr – Jun 2026
Team: Product, Engineering, Research
Company: HoneyBook

0–1
Product design
UX/UI

The HoneyBook Floor Plans builder with a venue floor plan laid out on the canvas.

Overview

Venues are one of HoneyBook's highest-revenue verticals. They're also the customers most likely to need a floor plan for every event.

Without a native tool, venue teams were piecing the workflow together across Canva, Prismm, and AllSeated. HoneyBook already had the booking data, client portal, and relationship. It was missing the tool.

The problem

Floor planning was a completely separate job.

Build a plan in another tool, export it, email it, get feedback, update it, and send it again. Different people ended up working from different versions. None of them were connected to the contract, guest count, or client portal.

The opportunity: bring floor planning into the project itself, creating one shared source of truth.

Research

Version control was the real problem, not drawing.

We studied 13 tools, mapped the venue workflow end-to-end, and spoke with early users.

The biggest pain wasn't creating a floor plan. It was knowing which version was current.

We also found that venues work in two modes: set up a space once, then adapt it for each booking. Most existing tools didn't account for that.

HoneyBook also had something competitors didn't. The context around the plan already lived in the product: guest counts, contracts, clients, and relationships.

Competitive analysis comparing 13 floor planning tools across the venue workflow.

I would LOVE to see a floor plan feature that could be used on the platform successfully.

— Venue member

Workspace

Before designing the builder, I designed where it would live.

Floor Plans became a dedicated tab inside every HoneyBook project.

I defined three statuses to separate preparation from sharing, distinct experiences for venues and clients, and a creation flow that surfaced templates from the start.

Floor Plans inside the project. Create, manage, and share plans without leaving HoneyBook.

We deliberately started small.

The first version wasn't meant to solve everything.

We wanted to get a working product in front of real venues, learn from how they actually used it, and use that feedback to shape what came next.

V1 launched to 30% of venue members with the core builder:

1 · Element panel
Furniture, shapes, rooms, and text. Organized by category. Drag or click to place.

2 · Status bar
The plan's name, its project, and its current publish status, at a glance.

3 · Canvas
An infinite grid with a 1×1 ft scale indicator. Build freely, set the scale once.

The V1 Floor Plans builder, annotated: (1) the categorized element panel, (2) the status bar, (3) the infinite canvas with a 1×1 ft scale indicator. — V1 builder.

Feedback

We shipped to 30%. Then we listened.

11 venue members responded. The signal was clear.

63%: Real dimensions & scale
The biggest reason members weren't switching from their current tools.
54%: Blueprint uploads
Members wanted to start from an existing venue layout instead of drawing from scratch.
45%: More object types
Dance floors, bars, podiums, screens. The library needed to support real event use.

Templates, a clearer wall tool, and the ability to lock elements rounded out the feedback.

Direction

The feedback gave us a clear path forward.

I helped align Product, Engineering, and the venue team around what to ship first and what would make the product genuinely competitive.

Align the MVP
Focus V1 on the core builder so we could launch quickly and learn.

Set the V2 priorities
Turn member feedback into a roadmap centered on scale, blueprint uploads, templates, and precision.

Protect the product vision
Partner through build and QA to keep Floor Plans native to the HoneyBook project, not a standalone tool.

V2 · Templates

Build once. Reuse everywhere.

Venues set up the same spaces again and again.

Templates let them save a room once and reuse it across bookings without starting from scratch every time.

Saving a floor plan layout as a reusable template from inside the builder. — **Save as template.** One click from inside the builder saves the layout to the account-level library.

The Floor plan templates tab, listed under My Templates. — **Floor plan templates tab.** Lives under My Templates alongside file and email templates.

Choosing an existing template as the starting point for a new floor plan. — **Create from template.** When starting a new floor plan, pick an existing template as the starting point.

V2 · Scale

Floor plans needed to work in the real world.

7 of 11 members said scale was the biggest reason they couldn't switch to HoneyBook.

Blueprint upload
Start with the venue's actual floor plan and calibrate it to real-world dimensions.

Canvas rulers
See real measurements as you build.

Live dimensions
Know the exact size of any selected element.

V2 · Precision

More control. Less guessing.

We redesigned the wall interaction and added tools for measuring and locking elements in place.

The builder could now behave more like something venues could actually use to plan a physical space, not just draw one.

Result

One place for every plan.

Floor Plans now lives inside the HoneyBook project alongside the booking, client, and event context it belongs to.

No exports. No second tool. One source of truth.

Floor Plans after V2. Templates, saved plans, and the full planning workflow, inside the project.

Impact

Members found it without being asked.

Floor Plans launched June 10 with no marketing push and opened to 100% of venue members on July 5.

By day 27:

1,019: Floor plans created
746: Unique creators
1.37: Average plans per user
41: Shares per day

These numbers came entirely from organic discovery before the first marketing push.