Project Overview

Backoffice is the product small operators use to run the working day. Inquiries, contacts, follow-ups, bookings, availability, and the catalog of what a business sells all live in one workspace, so nobody has to reconstruct a customer's history out of a spreadsheet, an inbox, and a chat thread.

Challenges

Small teams outgrow their tools long before they can afford a suite. The product had to:

• Replace scattered spreadsheets and chat threads without demanding a migration project first.
• Keep every workspace's data strictly isolated, with owner and manager roles that mean something.
• Make the work that is actually overdue visible, rather than presenting another empty dashboard.
• Stay one product as CRM, bookings, catalog, and messaging were added over time.

Our Solution

We built Backoffice on a shared platform backend, so each capability stays owned by its own domain while the operator sees one application:

• CRM: Inquiries, contacts, notes, and reply deadlines that make responsiveness measurable.
• Bookings: Availability, holds, and the booking lifecycle kept distinct from calendar blocks.
• Catalog: One record for every offering a workspace sells, reused by every other capability.
• Platform Foundations: Shared identity, per-workspace authorization, and subscription-ready entitlements.
• AI Assistance: Optional reply drafting through Kakapo, always reviewable and never automatic.

Results

• One Place to Work: Customer context, commitments, and bookings stop living in separate tools.
• Faster Replies: Overdue inquiries surface where members start their day instead of going unnoticed.
• Room to Grow: New capabilities arrive as sections of the same product, not as another subscription.