Executive summary
This framework turns the graduation project into the first year of a business. Students graduate with a validated product, a business model, a launch plan and a direct path to funding, so self-employment becomes a real option on graduation day.
It runs inside the existing capstone timeline and does not replace academic standards. Each project is assessed twice: on academic rigour and on commercial evidence.
The framework has six stages, each closed by a gate review:
- Idea selection
- Validation
- Build and test
- Business model
- Launch readiness
- Funding and support handover
The first two stages carry the most weight, because that is where most students get stuck: choosing a problem or challenge worth solving and proving that customers actually want it solved.
Who it serves: final-year students, their academic supervisors, universities seeking stronger graduate outcomes, and SME support and financing entities looking for a pipeline of ready ventures.
The problem
Most graduation projects end as a report on a shelf. The work is often good, but it was never designed to meet a real customer, so it stops the day the grade is given.
Students get stuck at predictable points:
| Where | What happens | Root cause |
|---|---|---|
| Choosing the idea | Topics are too broad, too academic, or picked from a list of past projects | No source of real problems or challenges; starting from a technology instead of a need |
| Choosing the idea | Weeks lost switching between ideas | No clear criteria to compare options |
| Validating | Feedback comes only from friends, family and classmates | No access to real customers; no interview method |
| Validating | "People liked it" is treated as proof | No standard for what counts as evidence |
| Validating | Students hold on to a weak idea | Changing direction feels like failing the course |
| After graduation | A working prototype with no licence, team agreement or funding path | Commercial steps sit outside the academic process |
The framework fixes these by giving each stage clear tools, a defined output and a gate decision, and by linking the final stage to the entities that license, mentor and finance new businesses.
Guiding principles
- Problem or challenge before solution. No student proposes a product until they can state a real customer's problem or challenge in one sentence.
- Evidence over opinion. Decisions at each gate rest on what customers did, not what they said.
- Pivoting is progress. Changing or dropping an idea based on evidence is rewarded, never penalised.
- Academic and commercial together. The research method, literature review and technical quality remain; the commercial work runs alongside them, not after.
- Real customers from week one. Every student talks to people outside the university early and often.
- Ownership is clear. IP, team roles and equity are agreed in writing before the product has value.
- A handover, not an ending. The final gate connects graduates to licensing, mentoring and financing so the project continues after graduation.
Framework overview
Six stages run across the final academic year, starting one semester before the capstone and continuing 12 months after graduation. Each stage ends with a gate where the supervisor, a mentor and an external member decide whether the team moves on.
Stages 1 and 2 start early on purpose: a team that enters the capstone with a validated problem or challenge spends its build time on the right product. Stages 3 and 4 overlap so the business model uses real pilot data.
Stage 1 · ends at Gate 1
Stage 1: Idea selection
The goal of Stage 1 is one approved problem or challenge worth solving, chosen with evidence and clear criteria, before any product is designed. It starts in the semester before the capstone and ends at Gate 1.
Problem or challenge? A problem is something that already goes wrong or costs the customer today, such as wasted stock or slow approvals. A challenge is a goal the customer wants to reach but cannot yet, such as entering a new market, meeting a new standard or serving more people with the same staff. Both qualify, and every tool in this framework works with either.
Why students get stuck here
- They start from a technology ("an app using AI") or a topic ("renewable energy") rather than a specific customer's problem or challenge.
- They have no source of real problems or challenges, so they recycle past project titles.
- They have no criteria to compare ideas, so they switch repeatedly or pick the first one.
- They fear choosing "wrong" and losing the semester.
Tool 1.1: The problem and challenge bank
The university maintains a live bank of real problems and challenges submitted by partners. Students may still bring their own idea, but must run it through the same screen.
| Source | What they submit | How to collect |
|---|---|---|
| SMEs and entrepreneurs | Operational pain points, growth challenges, tasks they pay for or do manually | Short submission form via SME support entities and chambers |
| Corporates and industry partners | Process gaps, unmet supplier needs | Annual call for problems and challenges; partner workshops |
| Government entities | Service and efficiency challenges | Innovation challenge briefs |
| Faculty research | Findings with a possible market use | Research office listing |
| Students' own lives | Problems and challenges in their family business, community or part-time job | Personal problem log during the pre-capstone semester |
Each entry records the problem or challenge owner, a contact person willing to be interviewed, and the sector. An entry with a named contact is worth more than one without.
Tool 1.2: The problem-first statement
Every idea enters as a problem or challenge statement, never as a product. Use the form that fits:
Problem form
[Customer] struggles with [problem] when [situation], which costs them [time, money or risk].
Example: Small restaurant owners struggle to track ingredient waste when placing weekly orders, which costs them money on spoiled stock.
Challenge form
[Customer] wants to [goal] but cannot because [obstacle], which costs them [time, money or opportunity].
Example: Family farms want to sell directly to city supermarkets but cannot meet their packaging and traceability standards, which costs them the higher margin.
A statement is rejected if the customer is "everyone", the problem or challenge is a solution in disguise ("they need an app"), or the cost cannot be named.
Tool 1.3: Divergence funnel
- Generate: each student or team lists at least 10 problem or challenge statements from the bank and their own log.
- Shortlist: cut to 3–5 using a quick gut check on interest and access to customers.
- Screen: score the shortlist with the viability scorecard (Tool 1.4).
- Test lightly: 3–5 quick conversations per top idea to confirm the problem or challenge is real.
- Select: one chosen problem or challenge plus two backups.
Tool 1.4: Viability scorecard
Score each shortlisted problem or challenge from 1 (weak) to 5 (strong). Weights favour what most often kills student ventures: weak pain and no access to customers.
| Criterion | Weight | Score 1 | Score 5 |
|---|---|---|---|
| Pain severity | 25% | Nice to fix, no one complains | Urgent, costly, customers already try to solve it |
| Customer access | 20% | Student knows no one in the segment | Student can reach 20+ potential customers within two weeks |
| Willingness to pay | 20% | Customers expect it free | Customers already spend money on a workaround |
| Feasibility in timeline | 15% | Needs skills, licences or capital the team lacks | MVP buildable by the team within the capstone |
| Market size and growth | 10% | A handful of customers | A clear, reachable segment that is growing |
| Founder fit | 10% | No interest or background | Strong personal link, relevant skills or network |
Weighted score = sum of (score × weight). Recommended threshold: 3.5 out of 5 to proceed, with no single criterion below 2. Weights and threshold can be tuned by each university.
Outputs of Stage 1
- One selected problem or challenge statement plus two ranked backups
- Completed scorecards for the shortlist
- Notes from the light-test conversations
- Named customer segment and at least 20 identified people to interview in Stage 2
Gate 1: Problem or challenge approval
Reviewed by the academic supervisor and an assigned mentor. Decision: approve, approve with conditions, or return (choose a backup or repeat the screen). Academic fit is checked here too: the problem or challenge must support a research question worthy of a capstone.
Stage 2 · ends at Gate 2
Stage 2: Validation
The goal of Stage 2 is proof, from real customer behaviour, that the problem or challenge matters and that a specific solution is wanted. It runs alongside the literature review and research design, and ends at Gate 2 with a go, pivot or drop decision.
Why students get stuck here
- They don't know who to interview or how to reach them.
- They pitch their idea and ask "would you use this?", which produces polite yeses.
- They treat compliments as evidence.
- They see competitors as a reason to quit, or claim they have none.
- They avoid pivoting because it feels like failing the course.
Tool 2.1: Customer discovery interviews
Target: 15–20 interviews with people in the chosen segment, none of them friends, family or classmates. At least half should be people who currently face the problem or challenge in their work or daily life.
How to reach them: contacts from the problem and challenge bank, SME support entities and chambers, LinkedIn, industry events, sector WhatsApp groups, walk-ins to relevant businesses, and faculty and alumni networks.
The rules:
- Ask about the past, not the future. "Tell me about the last time this happened" beats "Would you use…?"
- Don't pitch. The idea is not mentioned until the final minutes, if at all.
- Dig into cost. What did it cost them in time, money or stress? What have they tried?
- Listen for workarounds. A spreadsheet, a hired person or a manual process is strong evidence of real pain.
- Ask for the next step. An introduction, a follow-up, or a trial sign-up.
Two students attend each interview where possible: one asks, one takes notes. Notes are logged in the evidence tracker within 24 hours.
Tool 2.2: The evidence ladder
Not all signals are equal. Every finding is graded on this ladder, and Gate 2 requires evidence from the upper levels.
- L5Gave commitment: signed a letter of intent, pre-ordered or paid a depositStrongest
- L4Gave time: joined a waitlist, booked a demo, agreed to a pilotStrong
- L3Showed a current workaround or money already spent on itStrong
- L2Described the problem or challenge in detail from their own experienceModerate
- L1Said the idea is nice or interestingWeak — ignore
Minimum for Gate 2 (recommended): at least 10 interviews at Level 2 or above, at least 5 at Level 3 or above, and at least 3 at Level 4 or above. Universities can raise the bar for teams aiming to launch at graduation.
Tool 2.3: Competitor and alternatives scan
Students map every way customers handle the problem or challenge today, including non-obvious alternatives.
| Alternative type | Examples to look for |
|---|---|
| Direct competitors | Products solving the same problem or challenge for the same customer |
| Indirect competitors | Products solving it for a different segment or in a different way |
| Manual workarounds | Spreadsheets, paper, WhatsApp, hiring someone |
| Doing nothing | Customers who accept the cost |
For each, record price, strengths, weaknesses and why a customer would switch. The output is a clear answer to: why would a customer choose us over what they do today?
Tool 2.4: Value proposition
The team writes one sentence, tested in later interviews and refined until customers recognise themselves in it:
We help [customer] achieve [outcome] by [solution], unlike [current alternative].
It is supported by a one-page value proposition canvas: customer jobs, pains and gains, matched to the product's features, pain relievers and gain creators.
Tool 2.5: Solution test
Before any build, the team tests the solution concept cheaply: a landing page with a sign-up, a clickable mock-up, a paper prototype or a manually delivered service. Results are logged on the evidence ladder.
Outputs of Stage 2
- Interview log and synthesis of findings
- Completed evidence tracker meeting the Gate 2 minimum
- Competitor and alternatives map
- Tested value proposition and canvas
- Solution test results
Gate 2: Go, pivot or drop
| Decision | When | What follows |
|---|---|---|
| Go | Evidence meets the minimum and points to one clear solution | Proceed to Stage 3 |
| Pivot | The problem or challenge is real but the customer, focus or solution needs to change | Repeat targeted interviews (usually 2–3 weeks), then return to Gate 2 |
| Drop | The problem or challenge is not pressing enough, or customers cannot be reached | Move to a backup idea from Stage 1; the work so far still counts for assessment |
The gate panel grades the quality of the process and the evidence, not whether the original idea survived. A well-evidenced pivot can score higher than an unproven go.
Stage 3 · ends at Gate 3
Stage 3: Build and test
The goal of Stage 3 is a minimum viable product (MVP) used by real customers, with measured results. This is where the technical and academic core of the capstone sits.
Key activities
- Define the MVP: the smallest product that solves the core problem or meets the core challenge for the first customer segment. Features not linked to Stage 2 evidence are cut.
- Build in short cycles (two to three weeks), with a customer test at the end of each cycle.
- Run a pilot with 3–10 early users or one pilot client, ideally from the Stage 2 interviewees who reached Level 4 or 5.
- Set 2–3 success measures before the pilot (for example: weekly usage, time saved, task completion, repeat use) and track them.
- Collect feedback in a structured log and decide what to keep, change or remove.
Outputs
- Working MVP or prototype
- Pilot report with measured results against the success measures
- Feedback log and change history
- At least one testimonial or written pilot confirmation
Gate 3: Product readiness. The panel checks that the MVP works, that real users used it, and that the results support moving forward. Academic assessment of technical quality happens here.
Stage 4 · ends at Gate 4
Stage 4: Business model
The goal of Stage 4 is a business model that shows how the venture earns money and what it needs to reach break-even. It runs in parallel with the second half of Stage 3, using real pilot data.
Key activities
- Complete a Business Model Canvas, with every block linked to evidence from Stages 2 and 3.
- Choose the revenue model (subscription, per-transaction, licence, service fee, commission) and test pricing with pilot users.
- Estimate unit economics: cost to acquire a customer, revenue per customer, and gross margin.
- Build a simple 3-year financial plan: start-up costs, monthly operating costs, revenue forecast, cash flow and break-even point.
- Define the go-to-market plan for the first 12 months: first segment, channels, first 10 paying customers.
Outputs
- Business Model Canvas
- Pricing test results
- 3-year financial plan with stated assumptions
- 12-month go-to-market plan
Gate 4: Viability. The panel checks that the numbers are realistic, the assumptions are traceable to evidence, and the funding need is clear.
Stage 5 · ends at Gate 5
Stage 5: Launch readiness
The goal of Stage 5 is that the venture can legally operate on graduation day. These steps are often skipped, and they are the ones that stop graduates from trading.
Key activities
- Legal form and licence: choose the right legal form under local rules (for example sole proprietor, freelance or self-employed registration, home-based business or limited company) and prepare the application with the relevant registration authority.
- IP ownership: agree in writing who owns the product: the student, the team, the university or a split. The institution's IP policy applies; where it leaves room, the framework recommends terms that let student founders commercialise their own work.
- Founders' agreement: roles, decision-making, time commitment, equity split and what happens if a founder leaves.
- Brand and presence: name check, domain, basic website and social profiles.
- Operations basics: bank account requirements, invoicing, data protection and any sector-specific approvals.
Outputs
- Licensing route and prepared application
- Signed IP agreement
- Signed founders' agreement
- Launch checklist completed
Gate 5: Launch readiness. Confirms the team can begin trading once licensed, with no open ownership disputes.
Stage 6 · handover
Stage 6: Funding and support handover
The goal of Stage 6 is that no ready venture is left alone at graduation. Each one is handed to the right support path, matched to its stage and needs.
Demo day. Teams pitch to a panel of SME support entities, financing programmes, investors, incubators and potential first customers. The panel scores investment readiness, not presentation style alone.
Support pathways
| Venture readiness | Pathway |
|---|---|
| Paying customers and clear model | SME membership, financing programmes, banks and investor introductions |
| Strong pilot, no revenue yet | Incubator or accelerator place, grants, mentoring |
| Validated idea, product still early | Pre-incubation, continued mentoring, part-time founder track |
| Not continuing | Project archived to the problem and challenge bank for future students; IP terms respected |
Post-graduation follow-up
- Mentor check-ins at 3, 6 and 12 months after graduation
- Simple tracking of licence status, revenue, jobs created and funding raised
- Alumni founders invited back as mentors and bank contributors
Outputs
- Investor-ready pitch deck and one-page summary
- Assigned support pathway and named contact
- 12-month follow-up plan
Roles and governance
Each team has two guides: an academic supervisor for rigour and a mentor for commercial judgement. Neither replaces the other.
| Role | Responsibilities | Involved in stages |
|---|---|---|
| Student team (1–4) | Owns the venture, does the discovery, builds, decides at each gate | All |
| Academic supervisor | Research quality, methodology, technical standard, academic grade | All gates |
| Commercial mentor | Customer access, market judgement, business model review | 1–6 |
| Programme coordinator | Runs the problem and challenge bank, schedules gates, tracks progress and KPIs | All |
| Industry partners | Submit problems and challenges, host interviews and pilots, act as first customers | 1–3 |
| SME support and financing entities | Licensing guidance, demo day panel, financing and membership pathways | 5–6 |
| Gate panel | Supervisor, mentor and one external member; decides at each gate | Gates 1–5 |
Governance: a small steering committee (university, one industry representative, one SME support entity) meets each semester to review results, update the problem and challenge bank and adjust scorecard weights or gate minimums.
Expert and community engagement
Industry experts and community experts are built into every stage, and the programme coordinator assigns them to teams. Students are still learning what kind of help they need, so the coordinator matches them rather than leaving the choice to them.
Two kinds of expert
| Group | Who they are | What they bring |
|---|---|---|
| Industry experts | Sector specialists, corporate professionals, technical leads, bankers, investors, lawyers | Sector depth, technical review, market access, pilots, funding links |
| Community experts | Business owners, SME members, retired professionals, alumni founders, community leaders | Practical experience, honest feedback, local networks, long-term mentoring |
Where they plug in
| Stage | Industry experts | Community experts |
|---|---|---|
| 1. Idea selection | Submit real problems and challenges to the bank; flag crowded or closed markets | Share everyday pain points; give a reality check on ideas |
| 2. Validation | Open doors to interviewees in their sector | Act as interviewees; coach students on approaching business owners |
| 3. Build and test | Technical review; host pilots in their organisations | Act as early test users; give usability feedback |
| 4. Business model | Check pricing, margins and sector costs | Sanity-check numbers from experience |
| 5. Launch readiness | Legal, licensing and IP advice | Share lessons from starting their own business |
| 6. Funding handover | Sit on the demo day panel; make investor introductions | Mentor the venture for 12 months after graduation |
Across all stages, the external member of each gate panel alternates between an industry and a community expert, so every team hears both views.
Levels of commitment
| Level | Commitment | Typical activities |
|---|---|---|
| Contributor | One-off | Problem submission, a talk or clinic, a demo day panel seat, one interview |
| Stage expert | One stage, 3–4 sessions | Office hours, technical or financial review, gate panel member |
| Team mentor | One team, the full journey | Regular check-ins, gate attendance, post-graduation follow-up |
Coordinator-led assignment
- Build the pool. Experts register once and are tagged by sector, skill (finance, technology, legal, marketing, operations), preferred stage, commitment level and available hours.
- Assign a team mentor at Gate 1. Once the problem or challenge is approved, the coordinator matches each team with one mentor based on sector, the team's skill gaps and mentor capacity.
- Add stage experts as needed. At each gate, the panel notes what the team lacks next, and the coordinator assigns a stage expert to cover it.
- Check the fit. A short review after the first month; if the match isn't working, the coordinator reassigns without penalty to either side.
- Balance the load. No mentor takes more teams than their stated capacity, and no team goes without a mentor.
As students mature, they can request a specific stage expert from the pool for later stages. The coordinator approves the request.
Recurring formats
- Monthly office hours: teams book 20-minute slots with available experts.
- Stage clinics: one short practical session per stage, led by an expert (for example, how to run a customer interview, how to price a product).
- Demo day: experts score ventures and make introductions.
Sources of experts
- SME support entities and their member networks, including community mentoring programmes
- Chambers of commerce and industry associations
- Industry partners already contributing to the problem and challenge bank
- University alumni, especially graduates who launched ventures through this framework
- Investors, banks and financing programmes
Recognition
- Certificate and annual recognition at demo day
- Public acknowledgement on university and partner channels
- Early visibility of promising ventures for experts interested in investing or partnering
Expert code
Every expert signs a one-page code before working with students:
- Guide the team; never take over the project or its decisions
- Keep student work and data confidential
- Declare any conflict of interest, including interest in investing
- Make no claim to IP or equity in student ventures, unless agreed separately in writing after graduation
Assessment model
The capstone grade combines academic and commercial assessment. The recommended split is 60% academic and 40% commercial, adjustable by each university and programme.
| Component | Weight | What is assessed |
|---|---|---|
| Research and methodology | 20% | Research question, literature review, method, analysis |
| Technical quality of the product | 25% | Design, build quality, testing, documentation |
| Final report and defence | 15% | Clarity, rigour, reflection |
| Problem selection and validation | 15% | Quality of Stage 1 and 2 process and evidence, including pivots |
| Pilot results and business model | 15% | Stage 3 and 4 evidence and realism |
| Launch readiness and pitch | 10% | Stage 5 and 6 outputs |
Rule: commercial marks reward the quality of evidence and decisions, not commercial success. A team that drops an idea for good reasons can earn full marks for validation.
Success KPIs
Targets are set by each university after its first cohort establishes a baseline.
| KPI | Measured when |
|---|---|
| Share of teams passing Gate 1 on first review | Each semester |
| Average interviews per team; share meeting Gate 2 minimum | Each semester |
| Share of teams with a pilot user or client | End of Stage 3 |
| Share of teams with signed letters of intent or first revenue | Graduation |
| Ventures licensed within 6 months of graduation | 6 months after |
| Ventures still operating at 12 months | 12 months after |
| Funding raised and jobs created by graduate ventures | 12 and 24 months after |
| Problems and challenges submitted to the bank by partners | Each year |
| Student and partner satisfaction | Each cohort |
Implementation roadmap
A university can adopt the framework in four steps over roughly one academic year before full rollout.
- Prepare (2–3 months): secure leadership approval, appoint a programme coordinator, align the IP policy, recruit the first mentors and sign up SME support and industry partners.
- Build the problem and challenge bank (1–2 months): run the first call for problems and challenges with partners; target at least three entries per student team.
- Pilot (one cohort): run the framework with one department or a volunteer group of teams; train supervisors on the gate process and assessment model.
- Review and scale: use pilot KPIs and feedback to adjust weights, minimums and templates, then extend to more departments.
Open questions to settle with each university
- Does the capstone span one or two semesters, and when does the pre-capstone stage start?
- What is the current IP policy for student work?
- Which departments pilot first?
- Which SME support and financing partners join the demo day and handover?
Local adaptation
This is a global framework. Each adopting institution applies its own local rules, without changing the stages, gates or tools:
- Business registration and licensing routes
- Residency or visa conditions that limit self-employment for international students
- Eligibility rules of local support, incubation and financing programmes
- The institution's intellectual property policy and disclosure duties
- Research ethics approval for interviews and surveys with people
- Data protection rules for storing interviewee details
Fillable templates
Appendix: Templates
Fill in each template directly on this page. Your entries are kept in this browser only, so nobody else sees them. To share a template with your team, supervisor or mentor, save it as a Word file and send that.