Build a Football Tech Portfolio from Scratch
How coaches, analysts, and career changers can show sports tech companies what they can actually do.
A football tech portfolio should prove that you understand football problems and can turn them into useful technology workflows. Sports tech companies do not only hire people who can talk about football. They hire people who can help clubs adopt products, support users, explain value, analyse needs, and build trust.
Pick a career lane first
Football technology is not one job. It includes customer success, implementation, product specialist roles, sales, partnerships, analysis, data, support, content, education, and operations. Your portfolio should point toward the lane you want.
If you want customer success, show that you can onboard a coach, solve problems, and explain value. If you want implementation, show that you can plan a rollout and manage details. If you want product, show that you understand user pain and can describe improvements. If you want analysis, show that you can turn information into decisions.
Build three strong projects
You do not need ten projects. You need three good ones that show different strengths.
Project one: a product explainer. Choose a football technology category such as GPS, video analysis, AI camera systems, recruitment data, or wearables. Explain the user, the problem, the workflow, the value, and the limits. Write it for a coach, not a software investor.
Project two: an onboarding guide. Imagine a coach is using the tool for the first time. Create a simple first-week plan: setup, training use, matchday use, review meeting, and success measure. This shows you understand adoption, not just features.
Project three: a case study. Create a realistic scenario for a team. For example, a semi-professional club wants to improve training review using video. Explain the current problem, proposed workflow, staff responsibilities, player communication, and how success would be measured after four weeks.
Use public and anonymised material
You do not need private club data. Use public information, your own session plans, anonymised observations, and mock examples. Be clear about what is fictional. A portfolio can still be useful if it shows your thinking.
Never upload private player information, club documents, internal data, or anything you do not have permission to use. Trust matters in football technology. A portfolio that leaks information sends the wrong signal.
Show football understanding
Sports tech companies value people who can speak to coaches naturally. That means understanding the rhythm of a club week, the pressure on staff, the difference between academy and first team environments, and why a tool can fail even if the product is technically good.
A good portfolio explains barriers. Coaches may lack time. Analysts may be overloaded. Players may resist tracking. Wi-Fi may fail. Staff may disagree about who owns the process. Showing that you understand these realities makes you more credible.
Show technology understanding
You do not need to be an engineer for many roles, but you should understand the product category. For GPS, learn basic load concepts. For video, learn clipping, coding, playlists, telestration, and sharing. For AI cameras, understand capture quality, camera placement, upload workflows, and review habits. For data products, understand dashboards, definitions, and the danger of messy inputs.
Technology understanding means you can explain how the tool fits into daily work. It does not mean repeating feature lists from a website.
Show communication
Communication is evidence. A clean one-page guide can show more ability than a long CV paragraph. Write like someone who can help a busy coach. Use plain language, clear steps, and honest limitations.
Include examples of emails, onboarding notes, training guides, support responses, or presentation slides. These are the artefacts many sports tech roles actually rely on.
Suggested portfolio structure
- Short profile: who you are, what lane you are targeting, and what football context you understand.
- Project one: product explainer.
- Project two: onboarding guide.
- Project three: implementation or analysis case study.
- Tool familiarity: platforms, workflows, and methods you have used.
- Evidence: coaching, analysis, playing, volunteering, sales, customer, product, or operations experience.
- Contact and CV link.
How to make it feel real
Use specific scenarios. Instead of saying I can help clubs use video better, write a scenario: an academy U16 coach has one analyst, limited meeting time, and wants to improve wide defending. Then show the workflow you would build. That feels real because it starts with a human problem.
Avoid buzzwords. Sports tech companies see enough language about innovation, transformation, and elite performance. Better to show practical thinking: what happens on Monday, who does the upload, what the coach sees, how players receive feedback, and how you know it worked.
How to use the portfolio in applications
When applying, do not send the whole portfolio with no explanation. Pick the two projects that match the role. In your cover note, say why they are relevant. For a customer success role, point to the onboarding guide. For a product specialist role, point to the user problem and workflow. For an analyst role, point to the case study and decision-making process.
The portfolio should make it easy for someone to imagine you in the job.
A 30-day build plan
Week one: choose your lane and research five companies. Write down what roles they hire for and what problems their products solve.
Week two: create the product explainer and ask someone in football to read it. If they do not understand it, simplify it.
Week three: create the onboarding guide and case study. Keep them practical and visual where possible.
Week four: build a simple portfolio page or PDF, update your CV headline, and apply to roles with a tailored note.
Final TCC advice
Your background is not too small if you can explain what you have learned from it. Coaching, playing, scouting, volunteering, analysis, sales, support, and operations can all become relevant evidence. The job is to translate that experience into the language of the company and the role.
A strong football tech portfolio says: I understand the game, I understand the user, and I can help technology become useful in the real world.