01 / Web application
My Companions
Purpose-built tools for the everyday work that falls between the tabs. One platform, six focused companions.
- Focus
- Product design · Full-stack development
- Current state
- Actively building
- Built with
- Next.jsTypeScriptConvexClerkTailwind CSS
The problem
Working in hospitality made the friction obvious: useful information lives in too many places, and staff need answers while taking care of guests. Similar gaps show up in materials research, reading, and personal workflows.
What I built
- Built a shared Next.js application with six modular product areas, rather than separate apps with duplicated infrastructure.
- Used Convex for real-time data and Clerk for identity, with team and user access boundaries for different companions.
- Developed hotel knowledge and operations surfaces, a construction materials library, and chapter-aware reading references.
- Kept each companion focused on its own workflow while sharing navigation, UI components, and platform services.
The engineering behind it
The interesting challenge is the boundary: some information belongs to a team, some belongs to a person, and each companion needs its own access rules. A shared registry keeps product metadata and navigation consistent.
Meet the companions
Hotel Companion
Front-desk knowledge and daily operations.
Builder Companion
Materials, supplier information, and project workflows.
AI Companion
A workspace for agents, tasks, and shared knowledge.
Reading Companion
A chapter-aware reference that keeps spoilers out.
Budgeting Companion
Shared expense tracking for everyday life.
Author Companion
Writing and manuscript management.
Where it is today
The platform contains six companions and is under active development. Individual workflows are at different stages; the AI workspace and hospitality forms are continuing to evolve.