Superb.One – Internal CRM from Concept to MVP
Superb.One brings recruitment, scheduling, tasks and team information into one internal platform. I designed the product structure, workflows and UI, working with the CEO, PM, CTO and developers to turn early requirements into a working MVP in approximately five months.
Role
Product type
Team
Design scope
Project Overview
Superb.One is an internal CRM and operations platform for a video production team. It brings recruitment, studio bookings, tasks, time tracking and team information into one workspace, replacing workflows previously spread across spreadsheets, shared folders and calendars.
Problem Statement
Daily operations were spread across spreadsheets, Google Drive and Google Calendar. Completing one task often meant finding information in several places.
Recruitment records and CVs were stored separately. Studio bookings required calendar checks and additional coordination. Employee and resource information was distributed across folders and tables.
The team needed a shared workspace for these workflows. The challenge was to define how that workspace should function and deliver a usable first version within a short timeline.
Discovery
I worked with the CEO, PM and CTO to translate operational needs into interface requirements. The CEO brought requirements and feedback from the client, while the PM organised them into tasks.
Some inputs described the information people needed without defining the workflow around it. I used sketches, references and wireframes to clarify what users needed to see, which actions they could take and what should happen next.
We reviewed work almost daily as sections became ready. These discussions shaped both the individual screens and the structure of the platform.
Product Structure & Priorities
As the workflows became clearer, I organised them into the product navigation and prioritised sections for implementation.
User Management was an early priority: invitations and role assignment were needed to give the first users access. The core operational workflows could then be introduced as the product developed.
Across sections, I established reusable patterns for forms, tables, statuses and actions.
This kept related interactions consistent and supported delivery within the MVP timeline. Reporting was planned for further development, with more detailed analysis and visualisations to follow.
Exploration & Design
Team Performance
Team Performance illustrates how I turned an initial list of requirements into a screen structure. The team wanted to review hours, tasks, contractors and clients, but the layout had not been defined. I collected visual references and sketched ideas by hand to discuss which information belonged together.
I proposed an overview followed by progressively more detail: yearly trends, exact monthly values and a breakdown of the selected month. The chart supported comparison over time, while the table and monthly breakdown made the underlying figures accessible. The sketch became the basis for the digital design and subsequent reporting development.
Core Workflows
The same approach guided the operational sections: organise the information around the task and keep the relevant actions within reach.
Recruitment
I brought the CV, contact details, status and comments into a single candidate profile. Recruiters could review a candidate’s information alongside their recruitment history. Filtering by position also made previous candidates easier to revisit when a relevant opening appeared.
Studio Scheduling
I organised bookings by location, with studios listed down the side and dates across the top. This allowed users to compare availability across studios within one schedule. Daily and weekly views supported different planning needs, while filters narrowed the schedule by location, client or assignee.
Development & Launch
I prepared interface states and implementation specifications, documenting how screens and interactions should behave. I reviewed designs and implementation questions with the CTO and developers, clarifying details as development progressed.
The team launched a working MVP in approximately five months, bringing recruitment, studio bookings, employee records, tasks and time tracking into one platform. Early usage then informed further improvements.
Feedback & Iteration
Company Contacts
During a demonstration of the released product, we noticed that employees were storing contact names, phone numbers and email addresses in the company description field.
The field had been intended for a short business introduction. In practice, people also needed a place for their contacts within that company. Descriptions and contact details were becoming mixed and inconsistent.
I expanded the company form to support one or more contact people. Their information appeared in a dedicated Contact Details block in the company Overview. This gave business descriptions and contact information separate, consistent places in the interface.
Outcome & Reflection
My contribution covered product structure, workflow design, UI, implementation specifications and revisions informed by early usage.
Lessons Learned
Sketches and frequent reviews turned incomplete requirements into concrete workflows the team could agree on.
Early usage revealed needs missing from the original requirements, leading to improvements such as structured company contacts.