Build a Student Portfolio That Shows How You Solve Business Problems
Tom
Digital Business & Systems Consultant · Singapore

The business projects in a student portfolio persuade people when they show the evidence behind your recommendation, not when they show impressive-looking results. Put each project on one page: the problem, your role, the work, what was tested and what you learned, with an honest label on every result. A labelled demo or fictional project is fine; a big number you cannot support is not. Below: a seven-part structure, four evidence labels and a filled-in example.
Key takeaways
- Lead with the problem and your role, not the tools.
- Give every result one label: Demo, Tested with N people, Used by a real business with permission, or Not measured.
- Fictional and class projects belong in a portfolio when labelled.
- Show real work only with permission, and strip out private details.
- End with what you learned, including what contradicted your idea.
What a business-problem portfolio piece needs to show
A lecturer, employer or business owner reading your portfolio asks three things. Did you understand the problem? Did you do something sensible about it? Are you honest about how well it worked? Polished screenshots answer only the middle question, and "increased bookings by 40%" with no explanation raises doubt, especially for a short class project.
| Looks impressive | Shows how you think |
|---|---|
| Built a booking app | Mapped where bookings were lost, then built a demo to test one fix |
| Increased sales by 30% | Not measured yet; the owner agreed to count enquiries for a month |
Explain the problem and your role
Describe the problem in the business's terms, not the technology's: "customers messaged three times to confirm one appointment" rather than "needed a booking system". Then say whose problem it was: a real business (named only with permission), an unnamed one, a class brief or a fictional business.
Say exactly what you did
In group work, separate "I" from "we". "I ran three of the five interviews; a teammate built the form" is more credible than claiming the whole project. If a lecturer or supervisor set the brief, say so.
Show the work with permission
Work from a job, internship, attachment or a business owner's request is not automatically yours to show. Ask first, remove names, contact details and screenshots of private chats, and check your institution's rules and any agreement you signed. My guide to turning student work into a case study without exposing private information covers the permission request and what to remove. Without permission, describe the problem in general terms or rebuild the example with made-up data.
Then choose one or two pieces that prove your main point: a before-and-after, a flow diagram, an interview summary or a demo screenshot with made-up data. If you used the matrix in side hustles for university and degree students, its "evidence you keep" column is your raw material; this page decides which piece goes where.
State what was tested and what remains a demo
Put one of these four labels next to every result, number or claim:
| Label | What it means | Example wording |
|---|---|---|
| Demo | Built to show an idea; no real users or customers | Demo with made-up data; not used by the business |
| Tested with N people | Specific people tried it; say who and how many | Tested with six classmates acting as customers; five finished a booking |
| Used by a real business, with permission | Used in real work, and the owner agreed to it being shown | Used by the owner for two weeks; shown with her permission |
| Not measured | You do not know the effect yet | Not measured: the owner had never counted enquiries |
"Not measured" is not a weakness. It shows you know the difference between a change and a result. A small test is not a business outcome either: six classmates finishing a booking shows the steps are clear, not that real customers will book more.
Fictional work is fine. An invented business, labelled as fictional from the title down, shows the same thinking without anyone's private data. My guide to exploring business before eighteen suggests demonstration projects that need no real customer or payment.
The one-page portfolio case-study structure
Copy these seven headings onto one page, or one screen of your portfolio. Keep each part to a few lines.
| Section | What to write | Watch out for |
|---|---|---|
| 1. Title | The problem, plus Demo or Fictional if it applies | A title that names only the tool |
| 2. The problem | Who has it, what happens now, what it costs in time or mistakes | Guesses written as facts |
| 3. My role | What you did, what others did, who set the brief | Claiming the whole team's work |
| 4. What I did | The steps: interviews, mapping, drafts, a demo | A list of software instead of steps |
| 5. The work | One or two pieces, shown with permission or rebuilt | Real names, chats or customer details |
| 6. Evidence | Each result with its label | Numbers with no source |
| 7. What I learned | What worked, what contradicted your idea, what you would test next | Leaving out the surprises |
A filled-in example
(fictional example) Shu Hui is a full-time university student. For a service-design module, her group of three looked at a two-person pet grooming salon. The owner agreed to it being described but not named. Her page reads:
- Title: Fewer late-night booking messages for a small grooming salon (class project, demo).
- The problem: The owner confirms appointments by WhatsApp after closing; most messages ask which slots are free.
- My role: I interviewed the owner and wrote this page; teammates built the demo form and slides. Our lecturer set the brief.
- What I did: Mapped each step from first message to appointment, then helped design a demo form listing open slots.
- The work: A before-and-after flow diagram and two demo screenshots with made-up slots.
- Evidence: "Most evenings are spent replying": Not measured, the owner's estimate. "Customers can book without help": Tested with six classmates acting as customers; five finished, one got stuck choosing a time. The form itself: Demo, never used with real customers.
- What I learned: The owner liked the slot list more than the form, so a weekly message listing open slots might be enough for now. Next test: post it for a month and count the questions.
The upside: every claim has a label, and her recommendation is narrower than the demo, which is what a careful reader wants to see. The effort and uncertainty: it took much of a semester's module time, the owner has decided nothing, and no business result exists yet. The page says so.
Where a website or web app fits
You do not need a paid website to build a portfolio; a shared document is enough. Sometimes, though, a case study shows that a business owner needs a clearer website that explains the service and makes enquiring easy. Through website development I build custom-coded, mobile-first business websites with contact forms and handover documentation, for a separately agreed scope.
Something people log in to, such as a booking tool or client portal, is web app development, which I scope and quote individually. Either way, the owner decides; your part is honest evidence.
Your next step
Pick one project, whether class work, a part-time job (with permission) or a fictional business, and fill in the seven headings. Label every result. Evidence thin? My guide to turning a course project into a customer problem interview shows how to gather more.
Sources (checked 31 October 2026)
Frequently Asked Questions
Can a fictional example belong in a portfolio?
Yes, if it is labelled as fictional or a demo from the title down. It shows how you think without exposing anyone's data; just never present invented results as real ones.
What if I cannot disclose the client or workplace?
Describe the type of business and the problem in general terms, leave out names and private details, and rebuild any example with made-up data. Check your institution's rules and any agreement you signed before showing anything from real work.
What if my project had no measurable result?
Label it Not measured and say what you would measure next. A reader trusts an honest gap more than a number with no source.
Can I include group projects?
Yes. Separate what you did from what the team did, and describe your own part specifically.
How long should a portfolio case study be?
One page or one screen: seven short sections and one or two pieces of work.
Has a portfolio project shown that a business owner, or your own tested service, needs a website that explains the offer clearly? Message me for a no-commitment chat about what it would need to show. You do not need a paid website to build a strong portfolio.
No obligation. No sales pitch. Just an honest conversation.