Skip to main content
Operational CRMFeatured Proof

STR Command Center

Operational CRM prototype for short-term rental management — 18 routes covering reservations, briefings, pricing, market context, property ops, and communication workflows.

18 routes~19,500 linesOptional backend
STR Command Center screenshot

Problem

Model a full small-business operational surface in one dashboard.

Build

18 routes spanning inventory, bookings, customers, revenue, operations, and reporting

Outcome

Operational CRM prototype modelling a small business across 18 routes.

Sales Value

When selling CRM, PropTech, or operational SaaS to SMBs, I understand how operators think about reservation pipelines, guest communication, and daily dashboard workflows because I designed that surface as eighteen routes. The design decision I would point to is separating the daily briefing from the focus view: most dashboards show everything and help you decide nothing. It is a prototype with a paused backend, and I describe it that way.

Tech Stack

Next.js 16TypeScriptReact 19Tailwind CSSVercel

Highlights

  • 18 routes spanning inventory, bookings, customers, revenue, operations, and reporting
  • Separate briefing and focus views — orientation and prioritisation as distinct surfaces
  • Pricing built alongside market context, because pricing is an information problem first
  • Optional backend by design — the application runs and demos with no database configured
  • Fuzzy search across operational records via fuse.js
  • Consumes scss-palette-library, my own design-token package