Tellbyte

A relationship is more than a row in a roster.

An athlete-management prototype bringing recruiting, conversations, service work and approvals into a shared relationship record.

Selected work by Omar Samad. This project documents a product prototype and its design decisions. It is not presented as a Tellbyte client contract or a released athlete-management service.

Omar’s role
Product designer & design engineer
Project status
Product prototype

Relationships lose context when the work moves between teams.

Athlete business management connects recruiting, representation, documents, conversations and follow-up. A roster alone cannot explain what happened, who is responsible now or which commitment still needs attention.

The prototype needed to help a colleague resume that work without rebuilding the relationship from scattered messages. It also needed to keep a prepared draft distinct from an approved action.

Use the athlete record as the shared point of return.

The product framing centers on a persistent relationship history. Today, Athletes, Recruiting, Operations and Approvals offer different views of the work while retaining the same athlete and source context.

Task ownership, missing information and review states are designed as part of the main experience. A next step includes the person responsible and the information required to move it forward.

  • Prioritize with a reason: The Today view connects an item needing attention to its owner, current state and next decision.
  • Keep the relationship intact: Recruiting and service work lead back to the athlete’s conversations, documents and prior activity.
  • Review before an action leaves: Approval views distinguish a prepared draft, unresolved details and a reviewed action.

A coherent product ready to be challenged.

The documented result is a connected prototype spanning desktop and mobile. It makes the core product decisions available for review before claiming operational impact.

The public portfolio identifies task-based testing with relationship and operations teams as the next research step. No adoption, revenue or completed usability-study result is claimed for this prototype.

  • Shared context: Relationship continuity. Conversations and previous work remain available when the team returns to an athlete.
  • Visible ownership: Accountable handoffs. Work names the responsible person and explains the next step.
  • Reviewable actions: Prepared is not approved. A draft and a consequential action retain distinct states.
View Omar’s original case study

Discuss the project scope, delivery requirements and the next useful step with Tellbyte.

Discuss your project