Time8: Od wewnętrznego narzędzia do skalowalnego produktu cyfrowego
Budowa i walidacja produktu SaaS od zera do pierwszych klientów
Time8
Time8 is a SaaS product created by the BB8 team that emerged from a practical need: as the company grew, managing team availability information across multiple tools like Google Forms and Google Calendar became inefficient. Rather than adopting an existing solution, the team decided to build their own product. The entire process—from initial mockups to a functioning SaaS application—took approximately three months with a team of five people.
Co stanęło na drodze
The core question driving the project was simple yet recurring: "Who is working today?" Team availability information existed but was scattered across multiple platforms—Google Forms, messaging apps, and calendars. Consolidating this information required checking multiple locations. As the team grew, this inefficiency began affecting work organization, particularly when scheduling meetings or coordinating between teams. While data was being collected, there was no centralized place to view it clearly and quickly. Existing solutions on the market offered excessive features at high per-user costs and required organizational restructuring to implement.
Jak podeszliśmy do zadania
Discovery - pierwszy krok: BB8 Intranet
The team started not with a SaaS product but with an internal intranet to test the concept. Built with Webflow, Wized, and Xano, this tool centralized team availability information and enabled leave requests. Early mockups and use-case scenarios were created in parallel with development. The no-code approach proved limited, requiring additional technical components for user authentication, team data handling, and application logic. After several weeks, the intranet was operational and used daily by BB8, validating which elements provided genuine value.
Strategia - od narzędzia wewnętrznego do produktu
With the intranet working internally, the team explored whether similar problems existed beyond BB8. Client conversations revealed that team availability and work organization challenges were widespread—information scattered across calendars, spreadsheets, messaging apps, and shift schedules. This validated the opportunity to build a product for external companies. The perspective expanded beyond project-based teams to include the HoReCa industry, where shift work and staff availability management are fundamental to daily operations.
Wyjście poza naszą projektową bańkę
Initial focus was on project-based teams similar to BB8, but research revealed this was too narrow. Conversations with restaurants, cafes, and hotels in the HoReCa sector showed that managing availability and shift scheduling had greater operational significance. These teams face continuous schedule updates, inter-shift communication, and daily availability checks. This market research shaped Time8's concept: enabling teams to check availability, create shift schedules, and manage team presence efficiently in a single platform.
Architektura produktu
Moving from internal tool to multi-tenant SaaS required fundamental architectural changes. Each organization needed isolated workspaces, users, and data while ensuring security and scalability. The tech stack was built around Next.js and React for the frontend, TypeScript for code consistency and safety, and Supabase for database, authentication, and backend logic. This architecture reflected BB8's project experience, technical experiments from the intranet phase, and a new approach incorporating AI in development.
UX i UI dopasowane do pracy zmianowej
User experience design prioritized shift workers' needs: information accessibility without navigating complex menus, immediate visibility of team status, and quick schedule updates. Design work in Figma covered key workflows including workspace creation, team member invitations, availability management, and shift planning. Particular attention went to displaying team availability clearly and enabling rapid changes. The UI design was created with implementation in mind, allowing components to map directly to frontend libraries.
Development
Development followed an integrated model where design and coding remained closely connected rather than following traditional handoff processes. The team employed an "AI-assisted product development" approach using Claude Code, treating the process as continuous conversation requiring architecture planning, decision documentation, and iterative testing. This method enabled a single product-experienced developer to lead development without traditional designer-programmer separation. The work addressed typical SaaS challenges: user authentication configuration, external service integrations, database management, and security policies.
Co się zmieniło
Time8.io launched as a functional SaaS application enabling: workspace creation for organizations, team member invitations, employee availability management, work schedule planning, and unified team status visibility. The three-month development cycle from concept to operational SaaS product demonstrated the viability of the process BB8 developed. Initial market validation occurred through direct engagement at trade shows and live demonstrations with daily team managers. The product attracted first customers using it operationally. Development continues based on customer feedback and implementation insights, with new features added directly from user needs and conversations.
Zobacz powiązane projekty
Pozwól nam poznać Twój biznes
Szukasz wsparcia dla swojego produktu?
Kilka minut rozmowy, żeby sprawdzić, czy i jak możemy pomóc.
