Streamline UI/UX Prototyping Projects

I am building a premium one-page website for a country music artist brand. This needs to feel like a real, signed artist presence, not a template or basic build.

Scope:

One-page website
Built on Squarespace
Mobile-first, fast, clean
Easy for me to update after handoff

Sections:

Hero (strong visual, artist identity)
Music (Spotify / Apple / YouTube embeds)
About (short, powerful story)
Email capture (fan list)
Social links
Contact / booking

Style direction:

Clean, modern, cinematic
Minimal but bold
Strong typography and spacing
Not overly “rustic” or cliché country
Should feel like a real brand, not DIY

What I will provide:

Brand direction
Copy
Photos / visuals
Music links (when ready)

What I need from you:

Design and build
Layout and flow (important)
Mobile optimization
Clean, professional final product

Timeline:
Looking to complete within 7–10 days.

Important:
Please send 2–3 websites you’ve designed that feel like a real artist or premium brand. Not templates.

experienced programmer to assist on company project. would involve front and back end improvement, and ui design.
this will be a pay per month project

Scout Centre – Phase 3 Project Brief
Frontend Website Build, UX/UI, Calendar Planning, Coverage Analytics & Data Contribution Layer
1. Objective
Build a polished, professional frontend web application for Scout Centre that allows football scouts, academy recruitment teams and academy operations staff to:

Search and filter grassroots fixtures and tournaments
Plan weekend scouting coverage
Save fixtures and tournaments to a personal or shared calendar plan
View detailed fixture, tournament, team, venue and source information
Track scouting coverage across teams, leagues, age groups and geographic catchments
Identify coverage gaps across a club’s recruitment area
Submit new data sources, tournaments, fixture corrections and venue/default rule changes
The frontend must be simple, fast and highly usable. The core product value is helping scouts and academy staff quickly answer:

“Which fixtures should we attend, who have we already covered, and where are the gaps in our recruitment area?”

This phase should create a customer-ready prototype suitable for pilots with academy users.

2. Phase 3 Scope
Included in Phase 3
Responsive web frontend
Dashboard page
Fixture and tournament filtering page
Calendar planning page
Fixture details page
Tournament details page
Coverage analytics page
Catchment configuration feature
Saved fixtures / planned visits
Coverage status tracking
User submission mechanism for:
New data sources
Missing tournaments
Fixture corrections
Team corrections
Venue corrections
League default changes
Age-group-specific venue/default rules
Integration with Phase 2 API
Clean loading, error and empty states
Basic authentication-ready structure
Professional UI suitable for academy users
Not Included in Phase 3 Unless Agreed Separately
Native mobile app
Advanced AI assistant
Full CRM functionality
Payment/subscription system
Advanced admin portal
Full scout report writing system
Complex role-based permissions beyond basic user/admin separation
Automated approval of user-submitted corrections
Live route optimisation
Full Google Maps integration, unless agreed separately
3. Product Principles
1. Speed to Decision
Scouts should be able to find relevant fixtures in seconds, not minutes.

2. Minimal Clutter
Only show data that helps users decide whether to attend a fixture or understand coverage.

3. Mobile-Friendly First
Many users will check fixtures while travelling, pitch-side or between games.

4. Trust and Transparency
Users need to know where the data came from, when it was last updated, and whether information has been manually corrected.

5. Easy Contribution
The product improves as users submit corrections, venues, tournament details and new sources. Contributing data must be frictionless.

6. Coverage-Led Planning
The product should not just list fixtures. It should help clubs understand where they are and are not scouting.

7. Professional Academy Feel
The platform should look credible enough for academy staff, recruitment departments and clubs to use in a professional environment.

4. Target Users
Primary Users
Academy scouts
Pre-academy scouts
Emerging talent scouts
Academy recruitment coordinators
Academy operations staff
Heads of academy recruitment
Secondary Users
Grassroots club contacts
Tournament organisers
Recruitment analysts
Academy managers
5. Core User Journeys
Journey 1: Scout Planning a Weekend
User opens dashboard
Sees upcoming fixtures and tournaments
Filters by date, age group, region, travel time and competition
Opens fixture details
Checks venue, kick-off time and source confidence
Adds fixture to calendar plan
Builds a day/weekend itinerary
Journey 2: Recruitment Lead Checking Coverage
User opens Coverage page
Sets or selects club catchment, e.g. 60 minutes from training ground
Selects age groups, e.g. U7, U8, U9
Reviews number and percentage of teams covered
Identifies teams/leagues/areas not viewed recently
Uses this to direct scouts towards priority fixtures
Journey 3: User Correcting Bad Data
User opens fixture details page
Spots incorrect venue or kick-off time
Clicks “Suggest correction” beside the relevant field
Enters corrected value and optional note/source
Submission is saved as pending review
Admin can approve and apply correction through Phase 2 override logic
Journey 4: User Submitting a New Source
User opens “Submit source” from dashboard, fixture page or footer
Adds league/tournament/source name
Adds URL and region/age groups covered
Adds optional notes
Submission is saved for admin review
Journey 5: User Finding Gaps in a Catchment Area
User opens Coverage page
Sets base location, e.g. Arsenal Training Centre
Sets catchment limit, e.g. 60 minutes by car
Selects age groups and time window
Reviews coverage percentage by age group
Opens list of uncovered or under-covered teams
Clicks through to upcoming fixtures involving those teams
Adds priority fixtures to calendar plan
6. Required Pages
Page 1: Dashboard
Purpose
Give users a clear overview of upcoming scouting opportunities, their planned coverage and key coverage gaps.

Required Sections
1. Header Summary Cards
Suggested cards:

Fixtures this week
Tournaments this month
Planned visits
Teams covered in catchment
Uncovered priority teams
Recently updated sources
2. Upcoming Fixtures
A concise list of fixtures relevant to the user.

Each row/card should show:

Date
Kick-off time
Age group
Home team
Away team
League/competition
Venue or postcode
Travel time if available
Coverage status
“Add to plan” action
3. Upcoming Tournaments
Each row/card should show:

Tournament name
Date
Venue
Age groups
Format if available
Organiser/source
“View details” action
4. My Plan
Shows fixtures the user has already saved.

Should include:

Today / this weekend / next 7 days toggle
Fixture count
Chronological order
Remove from plan button
5. Coverage Gaps
Dashboard should preview key coverage gaps:

Teams in catchment not viewed in selected period
Age groups with low coverage
Leagues with no planned visits this week
High-priority teams with upcoming fixtures
6. Data Contribution Prompt
A simple callout:

“Seen a missing fixture, wrong venue or new league source? Help improve Scout Centre.”

Buttons:

Submit new source
Suggest correction
Page 2: Fixture & Tournament Filtering / Search
Purpose
Allow users to quickly find relevant fixtures and tournaments using powerful but simple filters.

Required Features
1. Search Bar
Search across:

Club name
Team name
League
Competition
Venue
Postcode
Tournament name
2. Filters
Required filters:

Fixture / tournament toggle
Date range
Day of week
Kick-off time range
Age group
Team
Club
League
Competition
Region
Postcode radius if available
Travel time from base location if available
Venue
Source
Coverage status
Viewed / not viewed
Planned / not planned
Data confidence / verified status if available
3. Results Table / Cards
The page should support both desktop table and mobile card layouts.

Each result should show:

Date
Kick-off time
Age group
Fixture/tournament name
Teams involved
League/competition
Venue
Postcode
Source
Last updated
Coverage status
Quick actions
Quick actions:

View details
Add to plan
Mark priority
Suggest correction
4. Sorting
Users should be able to sort by:

Date/time
Distance/location if available
Travel time if available
Age group
League
Recently updated
Coverage status
Priority/uncovered status
5. Saved Views
If feasible within budget, allow users to save common filters, for example:

U8 London fixtures this weekend
North East Sunday U9 fixtures
Tournaments within 90 minutes
Uncovered U8 teams within 60 minutes
6. Empty States
If no fixtures are found, show helpful options:

Clear filters
Widen date range
Increase catchment radius
Submit a missing source
Submit missing fixture/tournament
Page 3: Calendar Planning
Purpose
Help scouts convert fixture search into an actual plan for the day, week or weekend.

Required Views
1. List View
Chronological list of saved fixtures.

Each item should show:

Time
Fixture/tournament
Age group
Venue
Postcode
Travel time if available
Notes
Coverage status
Remove/edit action
2. Calendar View
A simple weekly or monthly calendar view.

Minimum requirement:

Fixtures appear on the correct day
Clicking an item opens fixture details
Users can remove fixtures from plan
3. Day Plan View
A focused view for a single scouting day.

Should show:

Fixtures in time order
Venue/postcode
Basic travel gap if available
Notes field
Coverage status
4. Export / Add to Calendar
Preferred functionality:

Export selected fixtures as .ics file
Add to Google Calendar / Outlook if feasible
If direct calendar sync is too complex, .ics export is acceptable for Phase 3.

5. Notes
Users should be able to add simple private notes to planned fixtures, such as:

“Watch U8 player from home team”
“Check pitch location before travelling”
“Possible double-up with 10:30 fixture nearby”
Page 4: Fixture Details Page
Purpose
Provide a clear, trustworthy single view of a specific fixture.

Required Fixture Fields
Fixture ID
Date
Kick-off time
Age group
Home club
Home team
Away club
Away team
League
Competition
Venue
Postcode
Travel time from selected base location if available
Source
Source URL if available
Scrape time / last updated time
Override status if manually corrected
Coverage status
Planned status
Required Actions
Add to plan
Remove from plan
Mark as viewed / covered
Mark as priority
Suggest correction
Submit missing information
Open source URL
Copy fixture details
Field-Level Correction Buttons
Each important field should have a small correction action next to it.

Examples:

Venue: “Suggest correction”
Kick-off time: “Suggest correction”
Team name: “Suggest correction”
Age group: “Suggest correction”
League default venue: “Suggest new default”
This is important because users should not have to fill out a long generic form when only one value is wrong.

Page 5: Tournament Details Page
Purpose
Provide a clear single view of a tournament, particularly where multiple age groups and start times are involved.

Required Tournament Fields
Tournament ID
Tournament name
Date
Time
Venue
Postcode
Age group(s)
Age-group-specific start times if available
Format
Organiser name
Organiser URL
Source
Source URL
Scrape time / last updated time
Override status if manually corrected
Coverage status
Planned status
Required Actions
Add tournament to plan
Add specific age group/session to plan
Mark as viewed / covered
Mark as priority
Suggest correction
Submit missing information
Open organiser/source URL
Copy tournament details
Page 6: Coverage Page
Purpose
Allow recruitment leads and scouts to understand how well they are covering teams, age groups, leagues and locations inside their recruitment catchment.

This is a key value-driving page and should be treated as a core Phase 3 feature.

Main Questions the Page Should Answer
What percentage of teams in our catchment have we viewed?
Which age groups are under-covered?
Which teams have not been seen recently?
Which leagues or areas are generating lots of fixtures but little coverage?
What upcoming fixtures can help us close coverage gaps?
Required Controls
1. Base Location / Training Ground
User should be able to set or select a base location, such as:

Training ground name
Address
Postcode
Example:

Arsenal Training Centre, London Colney
Sunderland Academy of Light
2. Catchment Setting
User should be able to define catchment by:

Travel time, e.g. 30, 45, 60, 90 minutes
Distance radius if travel time is not available
Preferred default examples:

60 minutes for younger age groups
90 minutes for older age groups if user chooses
3. Age Group Selector
User should be able to select one or multiple age groups:

U6
U7
U8
U9
U10
U11
U12+
4. Time Window
User should be able to select coverage time window:

Last 30 days
Last 60 days
Last 90 days
Current season
Custom date range
5. Coverage Definition
User should be able to define what counts as “covered”, for example:

Fixture added to plan
Fixture marked as viewed
Team seen at least once
Team seen at least twice
Team seen in last 90 days
For Phase 3, the default should be:

A team is covered if at least one fixture involving that team has been marked as viewed within the selected time window.

Required Stats
Summary Cards
Teams in catchment
Teams covered
Teams uncovered
Coverage percentage
Planned upcoming coverage
Priority uncovered teams
Age Group Coverage Table
Columns:

Age group
Teams in catchment
Teams covered
Teams uncovered
Coverage percentage
Upcoming fixtures involving uncovered teams
Example:

Age Group

Teams in Catchment

Covered

Uncovered

Coverage %

Upcoming Gap Fixtures

U7

42

18

24

43%

9

U8

55

31

24

56%

14

U9

48

27

21

56%

11

Team Coverage Table
Columns:

Team
Club
Age group
League
Location/postcode
Last viewed date
Coverage status
Upcoming fixtures
Add next fixture to plan
League Coverage Table
Columns:

League
Age groups
Teams in catchment
Teams covered
Coverage percentage
Upcoming fixtures
Coverage Statuses
Suggested statuses:

Covered
Not covered
Planned
Needs follow-up
Priority gap
Out of catchment
Coverage Visuals
Minimum acceptable visuals:

Summary cards
Progress bars by age group
Tables with coverage status badges
Desirable visuals:

Simple map/list view of covered and uncovered teams
Coverage heatmap
Catchment boundary visual
Map visuals can be deferred if cost is too high, but the frontend should not block future Google Maps integration.

7. User Data Contribution System
This is a core Phase 3 requirement, not an optional add-on.

Contribution Types
Users should be able to submit:

1. Fixture Correction
Examples:

Kick-off time is wrong
Venue is wrong
Postcode is missing
Age group is wrong
Team name is incorrect
Fixture has been postponed
Fixture has moved to a different pitch
2. Team Correction
Examples:

Team name should be standardised
Team is linked to wrong club
Age group is wrong
Duplicate team exists
3. Club Correction
Examples:

Club name is wrong
Club has merged/rebranded
Club location is incorrect
Club default venue is wrong
4. Venue Correction
Examples:

Venue name is wrong
Postcode is wrong
Address is incomplete
League has a recurring default venue
Team usually plays at a different venue
5. League Default Correction
Important example:

“This league normally lists fixtures without a venue, but U8 games are usually played at X venue.”

Users should be able to suggest a new default venue or rule for a league, competition or age group.

6. Tournament Submission
Users should be able to submit:

Tournament name
Date
Time
Venue
Postcode
Age groups
Age-group-specific start times if available
Format
Organiser
URL
Notes
7. New Data Source Submission
Users should be able to submit:

Source name
Source type: league, tournament, club website, county FA, other
URL
Region
Age groups covered
Notes
Contribution UX
Required User Flow
User clicks “Suggest correction” next to a specific field
Small modal opens
Modal is pre-filled with:
Existing value
Fixture/team/league context
Field being corrected
User enters proposed new value
User adds optional explanation or source
User submits
User sees confirmation
Required Fields in Correction Modal
Entity type: fixture, team, club, venue, league, tournament
Entity ID
Field being corrected
Current value
Proposed value
User note
Supporting URL if available
Submitted by user ID/email if authentication exists
Submission timestamp
Status: pending, approved, rejected, applied
Important UX Requirement
Users should not need to understand the database structure. The interface should translate their correction into a structured submission behind the scenes.

8. Coverage Tracking Data Model Requirements
The frontend should expect the API/database to support the following concepts.

Team Coverage
team_id
club_id
age_group
league_id
primary_venue_id
postcode
latitude/longitude if available
in_catchment flag
last_viewed_date
view_count
coverage_status
Fixture Coverage
fixture_id
user_id or club_workspace_id
status: planned, viewed, not_attended, cancelled, priority, needs_follow_up
viewed_date
notes
created_at
updated_at
Catchment Settings
catchment_id
workspace_id or user_id
base_location_name
base_address
base_postcode
travel_time_limit_minutes
distance_radius_miles/km if travel time unavailable
age_groups
created_at
updated_at
Coverage Calculation
Default calculation:

Coverage % = teams in catchment viewed at least once within selected time window / total teams in catchment

The frontend should display the calculation clearly so users understand what the percentage means.

9. Admin / Review Requirement
Phase 3 does not need a sophisticated admin portal, but it must support a review workflow.

Minimum acceptable approach:

Submissions are saved to a database table
Admin can view them in Supabase or a simple internal page
Admin can approve/reject manually
Approved changes can then be applied through the Phase 2 override system
Preferred approach:

Simple admin review page
Filter by submission type/status
View current vs proposed value
Approve/reject button
Approved correction creates or updates relevant override
10. Design Requirements
The design quality is critical. The site must feel professional, calm and easy to use.

Desired Style
Clean SaaS-style dashboard
Modern academy/recruitment feel
Minimalist layout
Strong whitespace
Clear hierarchy
Professional typography
Simple iconography
No clutter
No gimmicky football graphics
Suggested Visual Direction
Neutral base colours
Strong accent colour linked to Scout Centre brand
Clear status badges
Rounded cards/tables
Simple navigation sidebar or top nav
Mobile-friendly cards
Key Design Priorities
Results should be scannable
Filters should be easy to adjust
Important actions should be obvious
Users should never feel lost
The product should look credible enough to show to clubs
Coverage stats should be understandable at a glance
11. Navigation Structure
Suggested primary navigation:

Dashboard
Fixtures
Tournaments
Calendar
Coverage
Submit Data
Settings
For the first release, Tournaments can either be a separate tab or included within Fixtures via a fixture/tournament toggle.

12. Technical Requirements
Frontend
Preferred stack:

React / Next.js
TypeScript
Tailwind CSS
Component library if useful, e.g. shadcn/ui
Alternative stacks can be proposed, but the developer should explain the trade-offs.

Backend Integration
The frontend must integrate with the Phase 2 API.

Expected API interactions:

Fetch fixtures
Fetch tournaments
Fetch fixture details
Fetch tournament details
Fetch clubs
Fetch teams
Fetch leagues
Fetch coverage summary
Fetch coverage by age group
Fetch uncovered teams
Fetch catchment settings
Save/update catchment settings
Save planned fixture
Remove planned fixture
Update coverage status
Submit correction
Submit new source
Submit tournament/source data
Performance
The site should:

Load quickly
Handle large fixture lists with pagination or lazy loading
Avoid freezing when filters are applied
Use sensible caching where appropriate
Display loading states clearly
Responsiveness
Must work well on:

Desktop
Tablet
Mobile
Mobile is especially important for scouts using the product on weekends.

13. Data Fields Required from API
Fixtures
fixture_id
date
kickoff_time
age_group
home_club_id
home_club_name
home_team_id
home_team_name
away_club_id
away_club_name
away_team_id
away_team_name
venue
postcode
league
competition
source
source_url
scrape_time
last_updated
override_status
coverage_status
planned_status
priority_status
Tournaments
tournament_id
name
date
time
venue
postcode
age_group
age_group_start_times
format
organiser_name
organiser_url
source
source_url
scrape_time
last_updated
override_status
coverage_status
planned_status
User Plans
plan_id
user_id
fixture_id or tournament_id
planned_date
notes
status
created_at
updated_at
User Corrections
correction_id
user_id
entity_type
entity_id
field_name
current_value
proposed_value
user_note
supporting_url
status
created_at
reviewed_at
reviewed_by
Source Submissions
submission_id
user_id
source_name
source_type
source_url
region
age_groups
notes
status
created_at
reviewed_at
Coverage Summary
catchment_id
base_location
travel_time_limit_minutes
time_window
age_group
teams_in_catchment
teams_covered
teams_uncovered
coverage_percentage
upcoming_gap_fixtures
14. Key Components to Build
Core UI Components
Navigation shell
Dashboard cards
Fixture result row
Fixture result card
Tournament result card
Filter sidebar/drawer
Date picker
Age group selector
Catchment selector
Coverage summary card
Coverage progress bar
Coverage table
Coverage status badge
Data confidence badge
Add to plan button
Correction modal
Submit source modal/page
Calendar/list view
Empty state component
Loading skeletons
Error messages
15. Authentication Assumption
If full authentication is not included in Phase 3, the frontend should still be built in a way that can support it later.

Minimum options:

Temporary demo login
Single-user prototype mode
Supabase Auth integration if feasible
User-specific features affected by authentication:

Saved fixtures
Calendar plans
Notes
Coverage status
Catchment settings
Submitted corrections
For a pilot product, Supabase Auth is preferred if affordable.

16. Deliverables
The freelancer/developer should deliver:

Fully working frontend application
Responsive dashboard
Fixture/tournament filtering page
Calendar planning page
Fixture details page
Tournament details page
Coverage analytics page
Catchment settings flow
User correction submission flow
New source submission flow
API integration with Phase 2 backend
Clean, reusable components
Deployment-ready codebase
Basic documentation
Handover video or walkthrough
List of assumptions and known limitations
17. Suggested Milestones
Milestone 1: UX/UI Design
Deliverables:

Wireframes for all core pages
Visual design direction
Component style guide
Mobile and desktop layouts
Pages:

Dashboard
Fixture search
Calendar plan
Fixture details
Tournament details
Coverage
Correction modal
Submit source form
Milestone 2: Frontend Scaffold
Deliverables:

Project setup
Routing
Navigation shell
Design system/components
Dummy data connected to all pages
Milestone 3: Dashboard + Fixture Search
Deliverables:

Dashboard page
Fixture/tournament search page
Filters
Results table/cards
Sorting
Empty/loading states
Milestone 4: Details Pages + Calendar Planning
Deliverables:

Fixture details page
Tournament details page
Add/remove from plan
Calendar/list planning view
Notes
Coverage status updates
Milestone 5: Coverage Page + Catchment Settings
Deliverables:

Coverage dashboard
Catchment setting control
Age group coverage table
Team coverage table
League coverage table
Uncovered teams list
Upcoming gap fixtures
Milestone 6: User Contributions
Deliverables:

Field-level correction modal
Submit source page/modal
Submit tournament/source information
Store submissions through API
Confirmation states
Milestone 7: API Integration, QA and Deployment
Deliverables:

Full API integration
Bug fixes
Responsive testing
Performance checks
Deployment
Documentation
18. Acceptance Criteria
Phase 3 is complete when:

A user can search fixtures and tournaments using filters
A user can open a fixture/tournament details page
A user can add fixtures/tournaments to a plan
A user can view their plan in list/calendar form
A user can mark fixture coverage status
A user can set a catchment area from a base location
A user can view coverage percentages by age group
A user can see covered and uncovered teams within catchment
A user can identify upcoming fixtures involving uncovered teams
A user can suggest corrections at field level
A user can submit new sources
Submitted corrections/sources are stored in a structured format
The frontend integrates with Phase 2 API
The site works on mobile and desktop
The design looks polished and professional
The product is suitable to show to pilot users
19. Questions for Developer/Freelancer
Please respond with:

Recommended frontend stack and why
Whether you recommend Supabase Auth in this phase
Estimated hours by milestone
Fixed-price quote by milestone
Examples of previous SaaS/dashboard design work
How you approach responsive design
How you would build the correction/submission flow
How you would build the catchment/coverage page
Whether you can support API integration with FastAPI/Supabase
What assumptions you are making about the Phase 2 API
What would be excluded from your quote
20. Non-Negotiables
Excellent design and usability
Fast fixture search and filtering
Mobile-friendly experience
Field-level correction mechanism
New source submission mechanism
Coverage page with catchment settings
Coverage percentage by age group
Covered/uncovered team lists
Clean API integration
Clear data provenance and last-updated information
Simple calendar planning flow
Professional enough for academy pilots
21. Future Phase Ideas
Not required for Phase 3, but the build should not block these later:

AI scouting assistant
Advanced coverage analytics dashboard
Google Maps integration
Route planning
Club/team priority scoring
Scout assignment workflows
Paid subscriptions
Multi-club workspaces
Role-based permissions
Player watchlists
Scout report integration
Mobile app
Appendix: Page-by-Page Mockup Guidance
These are not final designs, but they show the intended layout, hierarchy and information architecture.

Mockup 1: Dashboard
Layout:

Left sidebar navigation
Top bar with search, date range and user/workspace
Summary cards across the top
Upcoming fixtures list on left
My plan panel on right
Coverage gaps and data contribution prompt below
Key visible elements:

Fixtures this week
Planned visits
Teams covered
Uncovered priority teams
Upcoming fixture rows
Add to plan buttons
Coverage status badges
Mockup 2: Fixture Search
Layout:

Left filter sidebar
Main results table/cards
Search bar and saved view controls at the top
Quick actions on every row
Key visible elements:

Date range filter
Age group filter
League filter
Catchment/travel time filter
Fixture/tournament toggle
Results table
Add to plan
Suggest correction
Mockup 3: Calendar Planning
Layout:

Top controls for week/day/list view
Main calendar or day-plan area
Right-side selected plan summary
Key visible elements:

Chronological fixture plan
Venue/postcode
Notes
Coverage status
Export .ics button
Mockup 4: Fixture Details
Layout:

Main fixture summary card
Detail fields in two-column layout
Correction buttons beside important fields
Source/data provenance panel
Coverage/planning panel
Key visible elements:

Home vs away
Date/time
Venue
Postcode
League
Source
Last updated
Add to plan
Mark viewed
Suggest correction
Mockup 5: Coverage Page
Layout:

Catchment controls at top
Summary cards
Age group coverage progress table
Team coverage table
Upcoming gap fixtures panel
Key visible elements:

Base location
Catchment: 60 minutes
Age group selector
Time window selector
Coverage percentage
Teams covered/uncovered
U7/U8/U9 breakdown
Add next gap fixture to plan
Mockup 6: Submit Data / Corrections
Layout:

Simple form-driven page or modal
Submission type selector
Context-aware fields
Optional supporting URL/note
Clear confirmation state
Key visible elements:

Submit new source
Submit tournament
Suggest correction
Current value
Proposed value
Supporting source

Looking for a brand designer to create visual identities for two medical companies. Think logos, color palettes, typography, brand guidelines, and basic collateral.

Overview

We’re looking for an experienced UX/UI designer to help us define the concept, structure, and user experience for a new internal Marketing Hub built on SharePoint (Microsoft 365).

This is NOT a development/build project.
We are looking for UX thinking, structure, and wireframes only.

The goal is to create a modern, product-like experience that connects campaigns, content, requests, and performance—and feels nothing like a traditional SharePoint site.

Objective

Design a concept that:

* Becomes a single source of truth for marketing
* Is visually engaging and easy to use
* Encourages employees to return regularly
* Supports campaign visibility, asset reuse, and requests

Key mindset:
“If this wasn’t SharePoint, what would you design—and how would you bring that into SharePoint?”

Scope & Deliverables (Fixed)

We are working to a strict fixed budget, so the scope is intentionally focused.

1. Homepage Wireframe (High Priority)

* Layout and structure
* Key components (campaigns, requests, news, social, performance)
* Personalisation ideas (e.g. “recommended for you”)
* Clean, modern dashboard-style UX

2. Campaign Page Wireframe (Critical Page Type)

* Campaign overview structure
* Asset access (download/reuse)
* Sales enablement content (e.g. email snippets, decks)
* Performance / reporting section
* Clear user journey

3. High-Level Site Map

* Main sections (Campaigns, Assets, Brand, Requests, Insights, etc.)
* Navigation structure
* How users move through the site

4. UX / Design Direction (Light)

* Look & feel references
* Interaction principles
* Suggestions to make SharePoint feel more like a product

Context

We already use:

* Microsoft SharePoint (Microsoft 365)
* Microsoft Teams
* OneDrive
* Power Automate
* Power BI

We also have:

* Existing request workflows (Forms → Power Automate → Planner)
* Campaign performance data (via CRM/Journeys + Power BI)
* Internal content owners (“champions”) who will maintain the site

Talent We Are Looking For

* Strong UX/UI design experience (dashboard, intranet, or SaaS-style design)
* Ability to simplify complex requirements
* Clean, modern design thinking
* Experience designing internal tools, content hubs, or similar platforms

Bonus for us: Familiarity with SharePoint or Microsoft 365 environments

Clear Expectations

We are looking for:

* Practical, usable outputs (not long documents)
* Clear wireframes and structure
* Thoughtful UX decisions explained simply
* A focus on usability over decoration

How We Like to Work

* Clear, direct communication
* Quick feedback loops (we will respond promptly)
* Iterative approach (early draft → refine)
* We prefer simple tools like Figma for collaboration

What We Don’t Want

* No development work
* No generic templates
* No overly long strategy documents without visuals
* No over-engineering

Timeline & Budget

* Timeline: 2–3 weeks
* Budget: Fixed ($1,250 USD / ~£1,000)

Final Note

We’re looking for someone who can help us create something that feels like a product, not a platform.

• If this wasn’t SharePoint, what would you design for this project and how would you bring that experience into SharePoint?
• Please share 1–2 examples of dashboard, intranet, or content hub designs you’ve created. Briefly explain your thinking behind one of them.
• How would you structure a homepage so users can quickly find campaigns, assets, and request support?
• This project has a tight budget and scope. How would you ensure you deliver high-quality work without overcomplicating it?
• How do you typically work with clients on wireframes (tools, feedback process, iterations)?

Here’s a quick overview of what we need:

• Refine the UI/UX for our upcoming basketball version (flows, hierarchy, clarity, usability).
• Review our existing soccer app and suggest improvements for consistency across sports.
• Align visual language and interaction patterns to create a cohesive product experience.

We’ll share current designs and user flows to guide the discussion.

We are seeking a talented designer to breathe new life into our existing WordPress website. The goal is to enhance the user experience, improve navigation, and modernize the overall look and feel. The ideal candidate will have a strong portfolio demonstrating their ability to create visually appealing and functional WordPress sites. Familiarity with responsive design is a must, as our site needs to be mobile-friendly. If you have a keen eye for design and a knack for WordPress customization, we would love to hear from you!

We’re building an Islamic services app called Emani, focused on Umrah Badal (proxy Umrah), and we’re looking for a serious, reliable development team to take over and complete the project end-to-end.

Umrah Badal is a service where someone performs Umrah on behalf of another person — typically someone who is deceased, elderly, sick, or unable to travel. The app allows users to request this service, and verified providers carry it out while documenting each step to ensure transparency and trust.

We previously had a development team working on this, but they unexpectedly left mid-project. Because of that, we are not starting from scratch — there is already a foundation in place that you will take over and continue.

Right now, we have:
• A designed UI/UX for the mobile app
• A partially completed landing page (needs to be continued and improved)
• An existing codebase and project structure
• A defined workflow and full product documentation
• A tool stack already set up, including things like GitHub, AWS/GCP services, Sentry, Expo, Resend, and domain setup (full access will be provided)

You will be expected to review the current setup, clean up anything necessary, and move forward with building the product properly.

The app itself is a single application with multiple roles, not separate apps. A user can act as a customer or a provider within the same app. Customers can book Umrah on behalf of someone, while providers (after approval and verification) accept and complete these requests.

The full platform includes:
• Booking flow and order management
• Provider matching and execution flow
• Step-by-step service tracking with photo, video, and voice evidence
• Payment handling (held and released upon completion)
• Admin dashboard for managing providers, orders, and disputes

From a technical perspective, we are working with:
• React Native (Expo) for the mobile app
• Node.js backend
• PostgreSQL database
• A Saudi-compliant backend server (data residency is required)
• Integrations such as OTP authentication, push notifications, and payment gateways

We are looking for a team that can come in, understand the system quickly, and take full ownership of completing everything — from mobile app development to backend, integrations, admin panel, testing, and deployment.

The current setup already includes a solid tool stack that supports both development and deployment. The codebase is managed through GitHub, with error monitoring handled via Sentry. The mobile app is being built using Expo (React Native), while Framer is used for the landing page design, which is partially completed and needs to be continued. Infrastructure and cloud services have been explored using Google Cloud, though the final deployment will be on a Saudi-compliant backend server. Apple Developer (ADP) is set up for iOS deployment, and the domain has already been purchased and configured. Email and communication services are handled through Resend. Overall, the foundation is already in place — the next team will be expected to take ownership of this setup, refine it where necessary, and build on top of it to deliver a complete, production-ready platform.

This is not a simple freelance task. We want a team that thinks in terms of building a real product, with proper structure, scalability, and reliability. Communication is very important — we’ve already experienced developers leaving mid-way, so consistency and commitment matter a lot.

The project is already broken down into clear milestones (user flows, backend, provider functionality, admin dashboard, QA, and launch), and full documentation will be shared once we start.

The timeline is around 10–12 weeks, with a milestone-based budget, and there is strong potential for a long-term partnership after this phase. I want to reiterate that saudi compliance methods is needed and if this does not suit you please do not apply.

When applying, please include:
• Examples of real apps you’ve built
• How you would approach taking over an existing project
• Whether you are applying as a team or individually

NOTE: DIRECT CONTACT WITH THE CONCILIO TEAM WILL IMMEDIATELY DISQUALIFY YOU.

Concilio Labs is a rapidly expanding enterprise in the hospitality technology sector, delivering innovative solutions to hotels, aiming to boost operational efficiency and elevate the overall guest experience. We’re looking for an individual with grit, integrity, curiosity, and yearns for greatness. If you thrive working in a fast-paced company and are ready for a new adventure, Concilio Labs could be the next step in your career.

We are seeking a Senior UX/UI Designer to create modern and interactive experiences for users of our products and solutions. Our ideal candidate is a self-directed individual who possesses strong creative, technical, and problem-solving skills. Our new Senior UX/UI Designer is devoted to customer satisfaction. This drives our designer to create products that are easy to use and encourage consumer engagement. The candidate must have strong experience in creating concepts for web and mobile applications by designing graphics and user interface layout regarding images, typography, color, style, and related aesthetic concepts.

OBJECTIVES OF THIS ROLE
Create innovative product designs in collaboration with internal and external stakeholders to understand business requests, desired outcomes, and create innovative product visions
Work seamlessly with the Delivery team to develop and maintain signature aesthetics, standards and brand integrity
Collaborate with the Delivery and Development Teams to iterate on new and complex user experience interaction
Identify and evaluate potential opportunities to improve existing web, mobile, and interactive designs
Create wireframes, storyboards, and prototypes in Figma
Envision and develop intuitive, scalable, and engaging interactions and experience designs for multiple platform
Work with our in-house QA team to test features and incorporate user feedback into design iterations
Ensure the creation and implementation of customized experiences for the digital user
Provide guidance on the implementation of UX/UI research techniques and testing activities to assess user behavior
Create responsive designs for multiple contexts and devices (desktop, tablet, mobile)
Research and conduct informal testing to validate design directions and inform new thinking for key features
Establish and promote UX/UI design guidelines, best practices and standards

ABOUT YOU
Strong attention to detail and care for producing polished work
Excellent written and oral communication skills
Self starter and self motivated
Resourceful and proactive with solid problem solving skills and a talent for recommending viable solutions
Lead the design of complex interface and user interaction layouts and graphics, most of the time balancing multiple online projects efficiently
Exceptional creative, technical, and analytic skills
Exceptional relationship building skills
Demonstrates great work ethic and positive attitude
Generate and communicates ideas and designs to end users and team members
Advocates for user-centered design in all products and solutions
Ability to prioritize tasks and goals independently

SKILLS AND QUALIFICATIONS
Bachelor’s degree in in Design, Visual Design, or related field
7+ years of graphical design experience (portfolio and samples required)
Proven work experience as a Senior UX/UI Designer or similar role
Expert in design and wireframe using Figma
Prior experience in visual/interaction design, branding and identity, and typography
Experience defining design systems that work across a complex products
Experience working in collaboration with Product Owners, Project Managers, and Developers in agile environments
Strong portfolio that demonstrates creative concept development and graphic design, UX, UI Design work across multiple platforms
Experience in UX/UI research to amplify design impact
Able to work in a team and independently to develop and resolve designs, enhancements, and fixes on tight timelines
Experience in a fast pace environment is a bonus
Advanced communication skills to collaborate with various stakeholders
Excellent time-management skills
Experience in hospitality and/or luxury sector is a bonus

Hey,

I'm Owen. A multidisciplinary designer and creative director based in Bangkok.

I'm currently working with a small start-up company as we speak, but also looking for someone to convert my Figma portfolio site to Framer, purely for my side hustle profile. This will help me to move faster, and I'll be able to focus on refining the actual content I'm putting into the CMS.

The site is quite simple and very intuitive. Less is more style, industrial-minimal, interactive, playful, and letting the work do the explaining kind of approach.

I'll attach the reference in .png for you. But basically, I needed help making them all responsive. I wanted to:
- (1) Create a 3-column CMS grid style with ratio-preserving image cards that do an image swap while hovering. Also, the ability to get on Framer and continuously add more content in the future.
- (2) At the same time, these reusable components would come in a chamfered corner (this might be when I needed help with clip-path polygon, single CSS variable controls all corners or some other ways. Because it's not just a simple corner radius).
- (3) A light/dark toggle that switches between two layout modes. First Ref - Light mode: grid view ↔ Second Ref - Dark mode : full-scroll view based on the project. Chamfered nav tabs with categories filter that floats and could be hidden.
- (4) If this project works out, I'll continue to commission you for other interactive components on the landing page. The fun turntable thing.

Cut to the chase, I got all design work laid out and would be happy to walk you through what I need. Wonder if you'd be interested to take this further? If yes, what's your availability?

Appreciate it big time. 🙏

K.I.T. Group is seeking proposals from experienced web designers and/or web design agencies to create a modern, user-centered visual design for its corporate website. This RFP focuses exclusively on web design (UI/UX), not development. The selected partner will be responsible for delivering high-quality design concepts and assets that can later be implemented within a WordPress (preferably Elementor-based) environment.

1. Objectives
• Develop a contemporary, visually compelling design that reflects K.I.T. Group’s international and professional positioning.
• Enhance overall user experience through clear structure, intuitive navigation, and engaging layouts.
• Integrate accessibility principles into the design from the outset.
• Support multilingual content presentation (initially English and German).
• Retain the current website structure to preserve SEO performance while improving usability within that framework.

2. Scope of Work
The selected agency will be responsible for:
• Conducting a design audit of the current website.
• Developing a refreshed visual identity for digital use (aligned with existing brand guidelines, if applicable).
• Creating wireframes and user flows based on the existing site structure.
• Designing high-fidelity mockups for key page templates (e.g., homepage, content pages, landing pages).
• Proposing design solutions to highlight K.I.T. Group global offices on the homepage (e.g., map, visual modules, or other interactive concepts).
• Ensuring designs are adaptable to WordPress/Elementor implementation.

3. Design Requirements
• Clean, modern, and professional aesthetic.
• Strong visual hierarchy and readability.
• Fully responsive design concepts (desktop, tablet, mobile).
• Consistent use of typography, color, and imagery.
• Scalable design system (components, style guide).

4. Accessibility
• Designs must follow accessibility best practices (e.g., WCAG 2.1 or later).
• Considerations include:
o Color contrast compliance.
o Readable typography and sizing.
o Clear navigation and interaction patterns.
o Design support for screen readers and keyboard navigation.

5. Multilingual Design
• Design must accommodate English and German content at launch.
• Layouts should be flexible for text expansion and contraction across languages.
• Consideration of future additional languages is required.

8. SEO Considerations (Design Perspective)
• Maintain the existing site structure and hierarchy.
• Ensure designs support SEO best practices (clear heading structures, content prioritization, etc.).
• Avoid disruptive structural changes that could impact search rankings.

9. Deliverables
• Wireframes for key templates.
• High-fidelity UI designs for all major page types.
• Responsive design versions (desktop, tablet, mobile).
• Design system / style guide (colors, typography, components).
• Design assets ready for handoff (e.g., Figma, Adobe XD, or similar).
• Design specifications for developers.

8. Collaboration & Handoff
• Close collaboration with K.I.T. Group stakeholders.
• Iterative design process with feedback cycles.
• Clear documentation to support seamless development implementation (WordPress/Elementor).

9. Proposal Requirements
Web designers / Agencies should include:
• Profile and relevant design experience.
• Portfolio of comparable web design projects.
• Approach to UX/UI design and accessibility.
• Proposed timeline and milestones.
• Tools used (e.g., Figma).
• Cost estimate.

10. Evaluation Criteria
• Quality and relevance of design portfolio.
• Understanding of UX, accessibility, and multilingual design.
• Ability to balance modern design with existing structural constraints.
• Clarity of process and collaboration approach.
• Cost and timeline.

• Describe your recent experience with similar projects
• Include a link to your GitHub profile and/or website

UX/UI Designer Needed for AI Assistant Mobile App (Modern, Minimalist Design).
We’re looking for a detail-oriented UX/UI designer to design a clean, intuitive prototype for a brand-new AI assistant mobile app.
The scope includes 6–8 core screens, such as:
- Login / Onboarding
- Landing / Home
- Practice Mode
- “Learn About Me” Mode
- Standard Chat Mode
- Settings
We want someone who can craft a modern, minimalistic experience with a strong focus on usability, clarity, and visual hierarchy. The design should feel polished and thoughtful—not just visually appealing, but also highly functional.
Requirements:
- Strong experience in mobile UX/UI (iOS/Android)
- Ability to design in both light and dark modes
- Attention to micro-interactions, spacing, and typography
- Experience designing AI/chat-based interfaces is a plus
- Ability to deliver high-fidelity prototypes (Figma preferred)
- You’ll collaborate closely with us to refine ideas and translate product concepts into a seamless user experience.

If you have a strong portfolio showcasing clean, modern designs, we’d love to see your work.
More details will be shared with the selected candidate.

• Describe your recent experience with similar projects
• Include a link to your GitHub profile and/or website

Designer-Developer to Reimagine the Presentation of a Working SaaS Product — 2 Week Sprint
The situation
Our code works. The product is live, functional, and serves real users. The data engine is solid.
What needs to change is the presentation. The interface is dated. It does not match the sophistication of what the product actually does underneath.
What we're hiring you for
To make the presentation exceptional.
We will sit down with you and explain the theory of what we have built — the intellectual foundation, the mechanic that makes the product work, the philosophy behind it. Then we will walk you through the existing product so you understand what it does today.
You will design from that understanding. We are not handing you a spec to execute. We want you to absorb the theory, then come back to us with creative presentations of how the product could look and feel. More than one direction. Real ideas.
Scope

Design only. No integration with our codebase. No access to our repo.
Landing Page
Roughly 8 core screens, plus the components inside them.
Deliverable: a complete Figma file (every screen, every state) and a working static HTML/CSS/JS prototype you can walk us through.
Our existing development team handles integration after handoff.

Timeline
Two weeks from kickoff. The product works. We are reimagining the presentation, not rebuilding the product.
Who we're looking for
Someone exceptional at this craft.

Sharp. You read a brief and see what it is actually asking for.
Bright. You absorb complex material quickly and translate it into design decisions.
Highly skilled. You have shipped real product UI for real users at a high standard.

You design in Figma and you write your own HTML/CSS/JS prototype. We are hiring one person who does both well, not a handoff between two.
Reference points for the visual register: Linear, Posthog, Notion, Stripe, Vercel, Arc. Modern data-product. Confident, clean, treats the user like an intelligent adult.
If you are early-career or this would be your largest project to date, this is not the right fit. We are hiring at the top of the pool and the rate quote should reflect that.
How to apply
Send us:

Two or three real work samples — direct links or screenshots of data-rich product interfaces you personally designed and built.
A short paragraph on how you would approach the first 48 hours of a project where you have to absorb a complex theoretical foundation before designing anything.
A flat rate for two weeks of full-time focused work. One number, not a range.

Templated proposals will not be read. The 48-hour paragraph is the most important part of your application — it is how we know you read this post.
Anti-circumvention
This job is exclusive to Upwork. Any attempt to contact our company directly outside the platform — through our website, email, LinkedIn, or any other channel — will result in permanent disqualification from this project and any future work with us. We hire on Upwork because the structure protects both sides.
Final note
The product works. The theory is rich. The presentation needs to be exceptional, and the person we hire needs to be exceptional too.
If that excites you, we want to hear from you

Hello!

I Need help with landing page the buyer once click meta advertisement and lands on product page. My website is nestessentialplus.com. Its a dropshipping platform. I have use wordprees and flatsome theme for website. Please let me know we need to fix or we can have a call and discuss.

Thanks
Amit

I need an experienced designer specialized in taking complex, dense data (like PV generation, battery discharge, and utility rates) and making it intuitive through dashboards. Expert at creating interactive charts (graphs, flow diagrams) that allow users to toggle between different time periods (daily, weekly, monthly, yearly).

• Describe your recent experience with similar projects
• What frameworks have you worked with?

See above. I need you to develop book cover for me based on photos I am going to send you and I need photos for the interior of the book (56) converted for E-book (low resolution) and paperback and hardcopy (high resolution). The low resolution for the E-book should be compatible for a download E-book.

You should have the files I sent you. I will be sending you some additional pictures for consideration for the cover via Email.

I expect the price of this effort should be $550 and expect the work done in about one week.

I am building a prototype device that mixes and dispenses liquids. I need some one to build it for me .
I need help with:

• Creating a simple wiring plan (12V system)
• Ensuring pumps run correctly and safely
• Designing a basic mixing setup (avoid contamination)
• Recommending any small missing components
• Optionally helping with simple relay or ESP32 control

IMPORTANT:
I am NOT looking for:
- custom PCB design
- full engineering development
- manufacturing-ready CAD

This is an early-stage prototype. I just need a working system I can demonstrate.

Deliverables:
- simple wiring diagram
- parts confirmation
- step-by-step build instructions

Budget: Open (looking for efficient, practical help)

Timeline: ASAP

I need someone to quickly fix a few issues in an existing Figma website design.

This is a small and simple task mainly adjusting spacing, alignment, and cleaning up the layout.