Project Submission

Project Submission

🖼 Project Gallery


🎉 Congratulations on your effort through the week! We have a total of 33 projects competing for the coveted Winners of FanHack 2024!

[MUST READ] General Guidelines


1️⃣ Users can choose their desired AI tech stack from providers Amazon or Google. Amazon is our preferred partner and will be providing deep dives into their AI tooling options such as Bedrock. Google will also be providing similar training sessions into their AI options such as Vertex. Both Amazon and Google will provide mentorship throughout the hackathon if you choose to work with their tools.
2️⃣ If the chosen tech stack is AWS, the Fanhack solution should be developed within the AWS Lab environment, unless there is a strong requirement to hook into existing AWS DEV APIs. If a team's solution needs to be developed in AWS DEV because of an integration need, that team needs to guarantee proper tear-down and cleanup of all FanHack assets, including all associated data assets (e.g. S3). Also, perfect tagging of assets is required. Please refer to all the points under this section carefully. Also, please notify Kshitiz Garg and Thanigai Vellore about AWS DEV usage upfront. AWS QC/Prod is not allowed to be used
3️⃣ Use of regulated data as per Fanatics Data Classification (such as PII data) for training models is not permitted. Please go through the Generative AI policy document carefully.
4️⃣ If Data is to be transferred from AWS to GCP (or in the reverse direction), then it should be done in the secured way by strictly following the linked guidelines.
5️⃣ Applying team name labels to AWS/GCP services is mandatory (e.g. fanhack-2024-<team name>) so that the total project cost can be metered.
6️⃣ Each team is subject to a $100 cap in AWS/GCP cloud services or resources usage. If your team requires more than this you will need to submit reasoning via slack DM to either Kshitiz or Mackenzi and get authorisation in advance. Otherwise, exceeding this limit could impact your overall project score.
7️⃣  If the chosen tech stack is AWS, please exercise caution when invoking higher cost models many times, since each model in Amazon Bedrock has a different cost model. If your solution requires an external Vector Database (RAG) please be frugal with cluster sizing.
8️⃣ We might have to terminate the AWS/GCP services/resources just after the hackathon to keep the costs in control.
9️⃣ Self hosted model is allowed, but we should prioritise models available via AWS/GCP. As a general rule - whatever the open source model is, it must be self contained with no calls to external services outside of our network (otherwise we would be dealing with situations similar or worse than data breaches)
 
Please note the following:
The use of AI tools are approved for the Hackathon as long as no personal, confidential, or restricted information is used with the AI tool. Participants and/or their Hackathon Team who use AI technologies do so at their own risk. In the event where the Participants and/or their Hackathon Team exposes proprietary, sensitive, confidential, or personally identifiable data to an AI tool, AngelHack reserves the right to disqualify such Participant and/or their Hackathon Team from the Hackathon and any consequences arising thereof shall be solely borne by the Participant and/or their Hackathon Team.

Themes & Challenge Statements


FanHack 2024 has 3 themes, each with their own set of challenge statements.

Teams can only submit their project for 1 of the 3 hackathon themes, even if their project is applicable across multiple themes.
Our advice is to frame your project clearly for 1 theme, as the narrative of your pitch is also a key judging component!
There are 3 overall themes which you can choose to build your project on in this AI based hackathon. Under each theme, we have listed some potential challenge statements to help guide your team in coming up with an implementable idea for your project.
However, if you have an idea that does not fall into any of the challenge statements stated below, do not fret! We are also accepting ideas outside of the challenge statements stated below, as long as they fall within any of the 3 themes, and still follow the AI theme (considering GenAI as a subset).

The 3 Themes


Theme 1: Brilliant at the basics


  • How can we create content at scale using GenAI?
    • Generate unique, engaging, experimental, SEO friendly content for Fanatics websites, social media, blogs and marketing campaigns, tailored to different segments of the Fanatics community, by analysing fan data.
  • How can we use GenAI to enhance our efficiency and productivity
    • Create on-demand graphic+logo designs, considering logo usage guidelines for each League (consider some dummy rules to begin with - e.g., logos cannot be “altered/distorted/cut”, logos cannot appear in certain colours, pantone colours must be used, etc.). Example:
      • Create a T-shirt design including the New Orleans Saints logo beneath a halo
    • Team out designs - Recreate the same logo placement for all other teams given one team’s graphic with a logo on the centre front of a T-shirt. Example:
      • Create a T-shirt design in the style of graffiti artists (say, Andy Warhol) using the logo of X NFL team (and team it out)
    • Create a tool to generate multiple creative versions of store visuals to showcase our creative range of potential store options to business owners
    • Automate the analysis for security issues, incidents, unfinished RCAs etc.
    • Provide summarised knowledge around meetings, wiki, slack conversations etc.
  • How can AI help us to improve our product offerings?
    • Detect mismatches with image/logo, colours, sizes, descriptions around merchandise, considering the league's rulebook (consider some dummy rules to begin with - e.g., logos cannot be “altered/distorted/cut”, logos cannot appear in certain colours, pantone colours must be used, etc.).
    • Develop a computer vision system for the MTO process that automates the quality checking process in apparel manufacturing and embellishment production, reducing human error, increasing efficiency, and ensuring product consistency
    • Offer dynamic product pricing based on factors such as demand, competitor pricing, and customer segmentation, maximising revenue and profitability
  • How can we integrate AI based solutions with social media platforms to acquire/retain fans/B2B customers?
    • Capture and act on micro-moments/anomalies-based demand signals.
    • Participate in social media/discussion boards and product discussions etc. Perhaps a potential tool could be created to scrape all the conversations happening on thousands of fan sites, blogs, reddit's around the world, and extrapolate useful themes which Fanatics can then use to improve our products/services.
    • Optimise influencer selection by evaluating their audience reach and engagement metrics to maximise impact and ROI.

Theme 2: Elevating Fan Experience


  • How can we provide personalised shopping assistants using AI/GenAI?
    • Invent virtual shopping assistants that provide personalised recommendations, styling advice etc.
    • Enhance accessibility for fans, such as real-time sign language interpretation, audio descriptions for visual content etc.
  • How can we create AI based immersive experiences for our fans?
    • Create immersive and interactive experiences for fans, such as virtual try-ons, personalised product previews (for e.g. allow a fan to upload a picture or use a camera to see what a product looks like before they buy) etc.
    • Offer visual search engine to find products online by uploading/capturing images
  • How can we revolutionise Fan services using GenAI?
    • Transform Fan/B2B services, by providing instant, 24/7 support through intelligent chatbots to tackle various queries in real-time
  • How AI/GenAI can help us further enhance fan engagement?
    • Create experiences that increase fan engagement during live events, including personalised highlights, predictive analytics for games, and interactive second-screen experiences.
    •  

Theme 3: Profitability and Free Cash Flow


  • How do we manage product inventory in a better fashion using AI?
    • Analyse sales data and fan data (or B2B customer data), and predict demand for specific products to allow businesses to optimise inventory levels
  • How could we improve cash flow forecasting with AI?
    • Analyse historical data, market trends, and external factors to generate highly accurate cash flow forecasts, to allow us to plan for upcoming expenses, optimise working capital, and make better financial decisions
  • How could AI help us to automate account receivables?
    • Automate tasks like sending invoices, chasing overdue payments, offering discounts for early payments etc.
  • How do we better monetize targeted marketing and promotions using AI?
    • Analyse fan data to identify the most profitable segments and personalise marketing campaigns accordingly

🏆 Prizes


👑 FanHack 2024 Overall Winner: $3000 USD for the entire team

✨ FanHack 2024 Best in Theme A: $2000 USD for the entire team

✨ FanHack 2024 Best in Theme B: $2000 USD for the entire team

✨ FanHack 2024 Best in Theme C: $2000 USD for the entire team

 
  • All prize money listed above will be paid in USD
  • Prize money listed above will be divided and paid equally to each member of the winning team. If you are participating as a solo hacker, you will be entitled to the full prize money stated above
  • Prize money will be "grossed up" (amount after tax and withholdings)
  • Prizes will not overlap, i.e. the “Overall Winner” cannot also be the winner for “Best in Theme A”
 

Judging Criteria


Creativity & Innovation (25%)
Creativity & Innovation (25%)
How creative was the team in developing an innovative solution for the challenge?
Is the solution novel in its approach to the problem?
Does the solution change the way we work?
Presentation & Execution (25%)
Presentation & Execution (25%)
How well was the project executed and explained?
How would you rate the level of effort put in by the team to create high-quality pitches and project prototypes?
Did the team meet the expectations of the submission criteria and take pride in packaging the delivery of their submissions?
Business & Tech Impact (25%)
Business & Tech Impact (25%)
Did the team create an application that can have a real and valuable business and tech impact?
What is the level of effort put in by the team for the execution of their code & prototype?
Feasibility & Deployment Readiness (25%)
Feasibility & Deployment Readiness (25%)
How feasible is this idea for Fanatics if it was to be operationalized?
How adaptable is it across the organization?
Is this project created with the intention to be deployed immediately/with minimal adjustments?
Each criteria has equal weightage.

Submission Artefacts


Each team should appoint 1 person to submit your project onto the submission portal before 11:00am PDT on 26 April 2024, Friday.

‼️
Only AI-based solutions will be accepted in this hackathon.
Mandatory Artefacts
Mandatory Artefacts
1️⃣
Project Details
  • Intended business impact (max 30 words)
    • Measurable effects/outcomes of the project in Fanatics ecosystem
  • Project Description (max 100 words)
    • This is a detailed description of your team's project containing an overview of what problem is being addressed, why this solution is important and how it benefits Fanatics and/or our customers
  • Selected hackathon theme
  • A list of tech stack (solutions, technology infrastructure, technology services, etc.) used by the team to build your project
    • Users can choose their desired AI tech stack from providers such as Amazon and Google. Amazon is our preferred partner and will be providing deep dives into their AI tooling options such as Bedrock. Google will also be providing similar training sessions into their AI options such as Vertex. Both Amazon and Google will provide mentorship throughout the hackathon if you choose to work with their tools.
If the team is building a part of a bigger project that already existed, the Project Description must also:
  • State that the submission is part of a bigger project that already existed
  • Include a list detailing the improvements and progress made to the project during the course of the hackathon.
2️⃣
Project’s GitHub/GitLab Repo Link
One member of the team is to create the project's GitHub/GitLab Repo and share the access with the rest of the team to collaborate on.
  • The team will save all submission items onto this GitHub/GitLab Repo where the judges may access the items during the judging period.
  • GitHub/GitLab repo should host the application’s code, a README file, any other deployment files and testing instructions.
 
If the team is building a part of a bigger project that already existed, follow the steps below:
  1. Create a new GitHub/GitLab Repo for the project
  1. Upload / Import whatever has already been done to the new repo as the initial commit BEFORE the start of the official hacking period.
  1. Push the new commits, deployment files and testing instructions made during this hackathon to this repo
Judges will only identify and assess the codes and improvements made during the official hack period.
3️⃣
Pitch Video (3 min) A video demo showcasing the project in action.
  • In a pitch video, the team speaks directly to their audience and explains the benefits of their idea or solution. Since this deliverable is a recording of you talking on camera, it is advised that you assume there is a live audience as you speak/record.
  • This is a video recording of your team introducing your project and solution (as though you are in front of a live audience pitching in a physical hackathon!)
  • The idea is for you to emphasise on the What/Why/Wow elements of your project.
  • The video recording may be done over any video recording software you wish, however, your entire team should be present in the recording.
  • It is highly recommended for all the teams to check the pitch video to ensure it is working properly, with no background noise, under 3 minutes (and not intentionally sped up to fit the 3 minutes timeframe), with clear pitch and the recording is not muffled, etc.
    • Please note that if the pitch video/voice recording is not clear or above 3 minutes, it can lead to disqualification of the project.
 
Optional but Good To Have Artefact
Optional but Good To Have Artefact
4️⃣
Project Demo Link
This is the URL to the live working environment of the solution the team has developed.
If the team is building a part of a bigger project that existed before the start of the Hackathon, the Project Demo must:
  • Showcase the improvements and progress made to the project during the course of the hackathon

Submission Portal


REMINDER: All teams are to submit before 11:00am PDT on 26 April 2024, Friday to qualify for the hackathon prizes.
REMINDER: All teams are to submit before 11:00am PDT on 26 April 2024, Friday to qualify for the hackathon prizes.
Make sure ALL members of your team have registered for the hackathon.
Make sure ALL members of your team have registered for the hackathon.
Only 1 participant from each team will need to submit the project on behalf of the team. All teams are encouraged to submit as soon as possible before 26 April 2024 to avoid last-minute submissions and missing the deadline.
Only 1 participant from each team will need to submit the project on behalf of the team. All teams are encouraged to submit as soon as possible before 26 April 2024 to avoid last-minute submissions and missing the deadline.
Begin your submission via this portal. If all the submission items are not yet completed, you may put placeholders.
Begin your submission via this portal. If all the submission items are not yet completed, you may put placeholders.
FanHack 2024 Project Submissions Portal
If you need to make edits or updates to your submission, you may do so before the submission deadline via the unique login link sent to your registered email.
If you need to make edits or updates to your submission, you may do so before the submission deadline via the unique login link sent to your registered email.
If you face any issues or require help during submission watch our Project Submissions Video Walkthrough below, contact us on the FanHack 2024 Slack Channel.
If you face any issues or require help during submission watch our Project Submissions Video Walkthrough below, contact us on the FanHack 2024 Slack Channel.
Video preview
Project Submissions Video Walkthrough