The business could not pause for a rebuild
Vintage 72 already had customers, vendors, established routines, and legacy sales data. The challenge was not to replace everything at once. It was to improve the parts that caused friction while preserving the tools and habits the team still needed.
That made sequencing a product decision. Each new capability had to be useful on its own, fit the daily rhythm of the store, and leave room for the next part of the system.
A connected system built in practical layers
The platform now spans several related jobs:
- A public storefront and local-business presence
- Internal views that make legacy sales information easier to use
- A scheduling product that replaced a hand-drawn calendar
- Controlled vendor access to relevant reporting
- Operational reporting and analytics that support better decisions
The value is not one feature. It is the continuity between public experience, staff workflow, vendor trust, and business visibility.
Design close to the people doing the work
This is product work inside a real family business, which means feedback is immediate and constraints are concrete. A technically elegant idea still fails if it adds steps at the register, creates confusion for a vendor, or asks the team to maintain information twice.
The work combines observation, product strategy, interface design, full-stack development, data integration, and gradual rollout. Small improvements are treated as parts of a longer operating model rather than isolated fixes.
A schedule built around the store's actual rhythm
The schedule manager replaces a hand-drawn calendar with one shared monthly view. Managers can see coverage, approved time off, open shifts, staff hours, requests, and draft changes before publishing updates to the team.
The product supports the way the store already works while making coverage gaps and changes easier to understand.
The same schedule supports a faster operational view
Managers can switch from the monthly calendar to an agenda view when they need to scan assignments day by day. The same product grammar carries publishing state, requests, coverage, time off, and team hours across both views.
The portfolio capture follows the current production interface while replacing every staff name and assignment with fictional records.
Recurring work becomes a reusable system
Team access and regular-shift patterns live beside the calendar. Managers can maintain staff roles and PIN-based access, record the shifts people usually work, distinguish committed assignments from preferences, and use those patterns as the starting point for auto-fill.
The system captures recurring scheduling knowledge without hiding the manager's judgment.
These screens are synthetic-data captures aligned to the current production portal and scheduler designs. Together they show the public site, vendor reporting, shop-wide operations, schedule publishing, recurring shifts, team access, and day-to-day staffing without exposing business records.
Future passes can add approved before-and-after comparisons, a clearer rollout timeline, and verified evidence of what changed for staff and vendors.