Proposal for Likel
Athlete CRM, calendar, and operations
in one internal platform.
A secure internal system bringing athlete CRM, scheduling, and team coordination into one place — where each manager owns their athletes and decides when to share access with colleagues. Delivered fully working at handover, ready for Likel to operate independently.
Proposed scope for discussion. Features and priorities can be adjusted in your next briefing before build begins.
Two roles.
Clearly separated access.
Managers own the operational side — sharing, coverage, and agency records. Athletes get their own dashboard to view their schedule and update their own profile, within permissions set by their manager. See Manager workspace below for full operations.
Manager
Primary owner of athletes; controls sharing, coverage, and messaging
Primary manager · controls who sees each athlete
Athlete
Own dashboard — view schedule and update their own profile and contact details
Own dashboard · view & update their profile and events
What a manager
can do each day.
Proposed manager operations for this scope — daily actions, sharing, calendar visibility, announcements, and onboarding. Each step is manual and manager-initiated. Automation can be added in a future phase if Likel wants it.
Daily operations
Add a match, meeting, travel, or media event linked to an athlete.
Share athlete access
Pick exactly who receives access — events, profile, or custom fields.
Calendar visibility
Show on the linked athlete's personal schedule — the athlete attached to this event.
Thu 10:00 · Media day · E. Korhonen
Manager chooses who sees this event
Team announcement
Post news to all managers — agency updates, policy changes, or general coordination replacing informal WhatsApp threads.
Proposed · to be confirmed in briefing
New people joining Likel
How managers and athletes register
Proposed onboarding for new team members — domain-restricted sign-up so only verified Likel staff can join the platform.
Likel email issued
New manager or athlete receives a @likel.com address.
Sign up on platform
Register with email and password. Domain validated automatically.
Role assigned
Administrator assigns Manager or Athlete role on first login.
Workspace ready
Manager sees their dashboard. Athlete sees their own profile and schedule.
From sign-in
to scoped data.
Four sequential controls govern every session. Hover each step to see how access is narrowed before any athlete data is shown.
Domain login
Role assigned
Dashboard loads
Access scoped
Domain login
Authentication is limited to verified @likel email addresses. External accounts cannot authenticate.
Role assigned
Each session is bound to a manager or athlete role immediately after sign-in.
Dashboard loads
The interface renders only the modules permitted for that role — no excess data is sent to the client.
Access scoped
Managers see only athletes assigned to them. Every data request is filtered at the application layer.
Their athletes.
Their decision to share.
Based on our discovery conversation, manager-controlled sharing is central to how Likel works. Every athlete has one primary manager who decides if and when to invite a colleague. In this scope, sharing is manual — automation can be explored in a later phase.
Our understanding · discovery call
- Each manager works in isolation — athlete data on personal devices and apps
- Coordination happens over WhatsApp and email with no access control
- No way to formally invite a colleague when coverage is needed
- Sharing is informal; there is no record of who saw what
This reflects our current understanding from the discovery call. We welcome your input to confirm, correct, or expand on any of these points.
Proposed scope
- One primary manager assigned per athlete at creation
- Primary manager manually invites another manager when they choose
- Scoped access: events only, full profile, or custom field-level permissions
- Optional expiry date; revoke access at any time
- In-app notification to the invited manager
- Coverage tab on the athlete record: who has access, scope, and expiry
Proposed flow · E. Korhonen
S. Lindgren
Primary manager
M. Järvinen
Invited for coverage
Share with
Permission level · manager chooses
Enough for temporary coverage — schedule and event briefs, nothing else.
M. Järvinen can see
Scheduling belongs
inside the platform.
From our discovery call, we understood scheduling is an area Likel wants to address. A follow-up briefing would help us go deeper — below is our proposed approach.
Our understanding · discovery call
- Schedules spread across email, spreadsheets, and personal calendars
- Coverage managers miss events they are responsible for
- Athlete commitments disconnected from the rest of the record
- No single view filtered by athlete, event type, or date range
This reflects our current understanding from the discovery call. A follow-up briefing with your team would help us validate and go into more depth.
Proposed scope
- Day, week, month, and agenda views
- Events linked to athlete records — match, meeting, travel, media, and more
- Each manager sees events only for athletes they have access to
- Share events with selected managers, all managers, or chosen athletes
- Show to the linked athlete, selected athletes, or all athletes — manager decides
- Filter by athlete, event type, and date range
Proposed interface · Week view
June 2026
Who sees this event · Media day
Managers
Athletes
Media day shown on E. Korhonen's personal schedule only.
Manual · manager chooses each time
Eight platform features.
For discussion and refinement.
The following outlines our proposed scope for the platform. This document is for explanation only — items can be added, adjusted, or removed based on your feedback in upcoming briefings.
Deployment and handover are covered in the Delivery section. Final scope will be confirmed together before build begins.
Visual direction.
For discussion — not decided.
Interface design is not defined in this document. The sketches below are optional conversation starters — two or three broad directions Likel might want to explore once scope is confirmed. Typography, colours, logo placement, and final styling are all still to be decided together.
Note on previews
Colours and layout below are rough placeholders — not Likel branding and not final design choices.
Each sketch suggests a different mood only. What we actually build visually — fonts, density, light/dark balance, components — will be agreed in a separate design step after scope and brand assets are confirmed.
My athletes
Example colours · direction only
My athletes
Example colours · direction only
Example colours · direction only
Direction A · discussion starting point
One broad direction we could explore — a lighter screen with more open spacing. Exact fonts, components, and styling are not decided yet and would be agreed in briefing.
These sketches are conversation starters only — not design commitments. Typography, components, colours, and final styling will be defined together after scope is confirmed. Likel feedback in briefing can replace, narrow, or combine these starting points.
Five layers of protection,
applied in sequence.
Data passes through each security layer before reaching athlete records. Select a ring to review what it enforces.
Layer 05 / 05
EU data residency
All data is stored on servers within the European Union. Data does not leave EU jurisdiction at rest or in transit.
Data subject rights,
supported by design.
Six rights under EU data protection law, each addressed in the platform architecture. Select a card to see how.
Build. Confirm.
Hand over.
Delivered once fully working at handover — ready for Likel to operate independently from day one. Open each phase for proposed deliverables.