In the final term of a master's in marketing, a team of five students is assigned a "live client": a regional furniture retailer with forty staff, a tired website and a vague sense that it should be doing something about social media. Over twelve weeks the team audits the company's digital presence, runs a customer survey, benchmarks six competitors, builds a segmented content calendar, drafts paid-search campaigns and presents a fully costed twelve-month digital strategy to the managing director, who is delighted. He implements most of it. Two of the students put the project on their CVs; one gets a job partly on the strength of it. Everyone is happy.
Now ask a question nobody in the room asked: what would that strategy have cost if the retailer had commissioned it from an agency? A conservative answer is several thousand pounds; a realistic one, with the research included, is well into five figures. The students were paid nothing. The university was paid nothing. The retailer received professional-grade work for the price of a few meetings and a plate of biscuits at the final presentation.
Was that exploitation, or education? The honest answer is that it can be either - and often both at once. Universities across the world now run capstone projects, live briefs, student consultancies, hackathons and design-build studios in which students produce strategies, prototypes, campaigns, software, research and advice for external organisations. The pedagogical case for them is strong and well evidenced. So is the discomfort. This article takes both seriously: what students actually gain, what organisations actually receive, where the ethical lines around payment, ownership and confidentiality sit, why client expectations so often go wrong, and the question underneath all of it - whether a student on a live project is a learner, a junior consultant, or somehow expected to be both.
How big this has become
Working for real clients while studying is not a new idea, but it has moved from the margins of higher education to its centre. In the United States, the National Survey of Student Engagement - which has surveyed millions of undergraduates since 2000 - reports that around 45% of seniors have completed a "culminating experience" such as a capstone project, and around 60% an internship or field placement; at some institutions the capstone figure exceeds 80%. George Kuh's influential 2008 framework designated capstones, internships and community-based projects as high-impact practices on the strength of their associations with engagement, retention and learning gains, and recommended that every student complete at least two.
The student-consultancy model specifically has a fifty-year track record. The Small Business Institute programme, launched in 1972 as a pilot between the US Small Business Administration and Texas Tech University, placed faculty-supervised student teams with small firms as unpaid consultants; by 1995 it had involved more than 407,000 students and assisted over 163,000 businesses, with the SBA paying participating universities a few hundred dollars per completed case and the businesses paying nothing. In the UK, the Sheffield School of Architecture has run its Live Projects programme since 1999: roughly 2,150 master's students have delivered 265 real projects - feasibility studies, master plans, built structures - for community clients across sixteen countries. Business schools run "consultancy modules"; computing departments build software for local charities; design schools have long taught through live briefs from companies; engineering degrees, as we've discussed in our article on engineering group projects, are accredited partly on the basis of team design work that increasingly involves industrial partners.
Whatever one concludes about the ethics, the practice is not going away. That makes it worth getting right.
The case for: what students actually gain
The educational argument rests on more than the intuition that "real-world experience is good." Several strands of learning theory converge on live client work as an unusually powerful form of teaching.
Authenticity changes how students learn
Grant Wiggins introduced the idea of authentic assessment in 1990 - tasks that replicate the challenges and standards of performance in the real world rather than proxy exercises designed for marking convenience. The empirical literature since has been consistent: when Verónica Villarroel and colleagues reviewed the field in 2018 they found that authentic tasks - realistic context, cognitive challenge, and evaluative judgement about quality - were associated with deeper approaches to learning, higher motivation and better transfer of skills. A marketing plan for a real retailer whose managing director will actually read it is authentic in a way no case study can be, and students behave differently when it is: they check their numbers, they anticipate objections, they care.
Learning by legitimate participation
Jean Lave and Etienne Wenger's 1991 theory of situated learning argued that expertise is acquired not primarily through instruction but through legitimate peripheral participation in a community of practice - doing real, if minor, parts of real work alongside people who do it fully, and gradually moving from the edge to the centre. The apprentice tailor sews real seams on real garments. A live project is the closest a degree gets to this: students perform a genuine piece of professional practice, with a genuine client, under supervision, at the edge of the community they hope to join. The learning includes things no lecture can convey - how a client actually talks about their problem, how a brief changes under you, what it feels like to present a recommendation someone will pay real money to act on.
The experiential cycle needs a real experience
David Kolb's model of experiential learning - concrete experience, reflective observation, abstract conceptualisation, active experimentation - is the standard justification for placement and project-based education. Its first stage requires an experience worth reflecting on. A simulated client produces a simulated experience; the reflection that follows is correspondingly thin. Live projects supply the concrete experience that makes the rest of the cycle work - which is why, as we'll see, the reflective components of a capstone matter far more than students usually assume.
The employability arithmetic
Then there is the blunt labour-market reality. The Sutton Trust's 2018 research found that 39% of UK graduates in their twenties had done an internship - 46% of those under 24 - and that in competitive sectors experience had become an effective precondition of entry. Graduate recruiters consistently rank work experience among their top selection criteria. A student who can say "I delivered a digital strategy to a real client, here is the deck, here is what happened when they implemented it" has something concrete that most applicants do not. For students who cannot afford an unpaid internship in London - which the Sutton Trust costed at a minimum of £1,100 a month - a live project embedded in their degree may be the only realistic route to that kind of experience. This is a point in favour of live projects that is easy to miss: done inside a curriculum, they democratise access to experience that the internship market rations by parental wealth.
What the client gets that money couldn't buy
Finally, it would be dishonest to pretend clients gain nothing beyond free labour, because the best programmes deliver something the market genuinely doesn't. The SBI's own evaluations noted that student teams tackled "issues which are of concern to the business, but which ordinarily would not get addressed" because owners are consumed by daily firefighting. Sheffield's architecture programme works almost exclusively with community clients "who could otherwise not afford architectural services," and reports that a student feasibility study is frequently the document that unlocks grant funding for a project that would otherwise never have started. A charity that could never commission a £15,000 options appraisal is not being exploited when students produce one; it is receiving a public good.
The case against: where it becomes something else
All of which is true, and none of it disposes of the discomfort. Because the value flowing to the organisation is real, and the question of who should be paid for it does not disappear because the producer is enrolled on a course.
Price what's being transferred
Start with a comparison that makes the issue vivid. The UK's Knowledge Transfer Partnership scheme places a recent graduate - the "associate" - inside a business for one to three years to deliver an innovation project with academic supervision. It is widely regarded as one of the most successful university–industry programmes in the country. A small or medium-sized business typically contributes around £35,000 a year towards a total project cost of £80,000–£125,000, most of it the graduate's salary and the academics' time. Now consider the master's student on a twelve-week live project who produces a strategy the KTP associate might have spent a quarter of a year on. The two people may be identical: the associate is often last year's live-project student. The only difference is which side of graduation they stand on. On one side, the business pays £35,000 a year for their work. On the other, nothing.
The design professions have thought about this harder than most, because unpaid creative work has a name there. The AIGA - the largest professional body for communication designers - distinguishes five kinds of unpaid design: pro bono work for the public good; internships with educational gain; volunteer work; competitions for a prize; and speculative or "spec" work, done free in the hope of payment. Its long-standing position is that spec work harms designers (whose value is denied), clients (who get less thoughtful work) and the profession (whose economics are undermined). When the Tokyo 2020 Olympic organisers crowdsourced their emblem from nearly 15,000 unpaid entries, the AIGA wrote publicly to object that "thousands of hours of creative talent" were being taken "without compensation." Student live briefs sit awkwardly across these categories. They are meant to be the second kind - internships with educational gain. But when a profitable company briefs a design cohort, receives forty concepts, uses the best one and pays nobody, it looks a great deal like the fifth.
Who can afford to work for free?
The Sutton Trust's internship research carries a lesson that transfers directly. Unpaid work is not equally available to everyone: the students who can spend a summer working for exposure are the ones with family money and a spare bedroom in London. Live projects inside a degree avoid the worst of this, because they replace assessed work rather than adding to it. But the moment a project spills beyond its timetabled hours - the client wants "just one more iteration," the prototype has to be production-ready, the presentation is moved to a day when the student has a paid shift - the same inequality reappears. The student who can absorb unpaid overrun is not the student working twenty hours a week to eat. Programme designers who don't police scope are quietly taxing their poorest students.
The substitution problem
The hardest version of the exploitation charge is not that the student wasn't paid; it's that someone else wasn't hired. A company that runs a rolling programme of student teams to deliver its market research has, in effect, replaced a research function with unpaid labour. A council that uses architecture students for every feasibility study it commissions is not supporting education; it is avoiding a procurement. The Sutton Trust's finding that most unpaid interns did "real work… which would otherwise be done by other members of staff" is the internship version of the same problem, and it is the point at which a learning opportunity becomes a labour-market distortion - bad for graduates in that profession, and bad for the profession's willingness to train them.
The test that resolves most cases
Notice that the two lists don't actually contradict each other. They describe different projects. The charity that receives a feasibility study it could never have bought, and the plc that receives a marketing strategy it would otherwise have paid for, are not the same case, and pretending the ethics are identical helps nobody. Two questions separate them:
- Could the organisation otherwise have paid for this? If not - a small charity, a community group, a start-up with no revenue, a public service under austerity - the work is closer to pro bono, and the exchange is a legitimate one: professional-standard help the market would never have delivered, in return for a real learning context. If yes - a profitable company with a marketing budget - the university is subsidising a commercial entity with its students' unpaid labour, and needs a much better justification.
- Is the project designed around the student's learning or the client's deliverable? A project in which the brief is shaped by the module's learning outcomes, the scope is fixed by the university, the client is told in advance that the output is student work, and assessment weights process and reflection alongside the product is an educational activity that happens to produce something useful. A project in which the client sets the scope, changes it at will, expects production quality and judges the students on whether they got it is unpaid consultancy with a university's badge on it.
Sheffield's programme is instructive precisely because it applies the first test explicitly: it "works only with clients from the public and voluntary sectors," the "vast majority… could otherwise not afford architectural services," and its staff report that demand from such clients now "vastly exceeds capacity." That is a programme that has decided who deserves the gift. Many business-school consultancy modules have never asked the question, and it shows.
Where a profitable client is involved, there are ways to restore balance that fall short of paying students a consultancy rate: a fee to the university that funds bursaries or the programme itself; a commitment to interview or hire from the cohort; a defined, paid follow-on for implementation; a senior manager's genuine time as a mentor, which is worth more to students than a modest payment would be. What is not acceptable is the pretence that "exposure" is compensation. The AIGA's list of prizes offered in design competitions - "a color TV and stipends of $15" - should be read as satire, and treated as a warning.
Ownership: whose work is it?
Here is a question most students never think to ask until it matters: who owns the strategy, the code, the designs or the data when the project ends?
The default position surprises people. Students are not employees of their university, so - unlike staff, whose work generally belongs to their employer - they usually own the intellectual property in what they create, unless they have signed something that says otherwise. Which is exactly what many live-project agreements ask them to do, often in a clause nobody reads at the kick-off meeting. A blanket assignment of all IP to the client means the student cannot reuse their own code, cannot show their own designs in a portfolio without permission, and - in the rare but real case where a student idea becomes commercially significant - has given it away for nothing.
The AIGA's position on competitions is the right template: the creator retains ownership and the client receives a licence to use. For a live project that translates into a few reasonable terms every student should look for and every university should insist on:
- The student retains copyright or IP in their contribution, with the client granted a licence - non-exclusive if possible, exclusive if the client insists - to use the deliverable for its intended purpose.
- The student retains an explicit right to show the work in a portfolio and describe it in applications, subject to any genuine confidentiality redactions.
- Any commercially significant invention or product is dealt with under the university's own IP policy, not by default assignment to the client.
- Where the client requires full assignment, that is a signal the project has crossed from education into commissioned work - and the question of payment reopens.
Every UK university has an IP policy and most have a standard student–client agreement; read both before the first meeting, not after the last one.
Confidentiality: the clause that can collide with your degree
Clients reasonably want confidentiality: they are showing students their sales figures, their customer lists, their product roadmap. Non-disclosure agreements are routine. The complication - again, rarely explained to students - is that a live project is also a piece of assessed academic work, and assessment has its own requirements that a badly drafted NDA can breach.
Marked work must be seen by markers, moderators and often external examiners; it may be retained for quality-assurance audits and accreditation visits; the university may want to use it as an exemplar; the student may want to present it at a conference or turn it into a publication. A clause that says "no disclosure to any third party" makes all of this technically impossible and puts the student in the position of choosing between breaking their agreement and failing their module. The solution is a tripartite agreement - student, client and university - that explicitly carves out academic uses: assessment, moderation, external examination, archiving, and portfolio use with sensitive data redacted. Most universities have one. If yours doesn't, or the client presents its own commercial NDA instead, escalate to the module leader before signing. It is not your job to negotiate confidentiality law with a company; it is the university's.
Two further practical points. First, confidentiality cuts both ways: students working with a client's data are bound by data-protection obligations they may never have encountered, and a spreadsheet of real customers copied to a personal laptop is a breach whether or not anyone notices. Second, students should keep an anonymised version of their work as they go - client renamed, numbers rescaled - because the portfolio piece that gets you hired is the one you're allowed to show.
Unrealistic expectations, in both directions
Ask staff who run live-project modules what goes wrong and the answer is almost never the quality of the students' work. It is the mismatch between what the client imagined and what a group of learners on a twelve-week module can deliver - and, just as often, the reverse.
Research on Sheffield's programme, drawing on interviews with students, tutors and clients, identifies the core tension as the "transient nature of student involvement within an external framework": students arrive, engage intensely for six weeks, and leave, while the client's problem continues. Clients who have not been prepared for this experience it as abandonment. Clients who have been told "you will receive a consultancy report" hear the word consultancy and expect what they would get from a firm: fixed scope, professional indemnity, someone accountable for outcomes, revisions until satisfied. None of this exists. The students are assessed and then gone; the university offers no warranty; the recommendation to relocate the warehouse comes with no one to sue if it's wrong.
The commonest failure modes, from the client side:
- Scope creep. The brief was a digital-marketing audit; by week six the client wants a rebrand, a CRM selection and a pricing review. Students, eager to please and unpracticed at saying no, absorb it into unpaid evenings.
- Production-quality expectations. Computing students build a working prototype; the client puts it live, discovers it has no security hardening or documentation, and blames the students for what was always going to be a proof of concept.
- The disappearing client. The mirror image: the sponsor who was enthusiastic at the pitch does not answer emails for a month, cancels the mid-point review and leaves the team guessing about basic facts. Students are then assessed on work that depended on access they never got.
- Ideas harvesting. A company briefs three teams, attends three presentations, takes the best elements of each and thanks everyone warmly. This is the spec-work problem in academic dress.
And from the student side: treating the client as a lecturer who will tell them what to do; producing a report in academic register that no manager will read; over-promising in the pitch to win the "good" client; and - the most consequential - mistaking the client's satisfaction for the assessment criteria, of which more below.
Almost all of this is preventable by a written brief agreed before the project starts that states scope, deliverables, the level of finish ("prototype, not production"), meeting commitments on both sides, what happens if the client disengages, and - in a sentence - that the output is student work produced for learning purposes, with no warranty. Good programmes have this document. Students on programmes that don't should ask for one, because its absence is the single best predictor of a project that ends in recrimination.
Learners or junior consultants?
Underneath every issue above sits one question: what is a student on a live project? The uncomfortable answer is that they are asked to be two things at once, and the two have different rules.
As a learner, the student is entitled to make mistakes, to be assessed on process as well as outcome, to receive feedback rather than consequences, and to have the scope of their task bounded by what they can be taught. As a junior consultant, they owe the client competence, reliability and a deliverable that works. Lave and Wenger's phrase is the way to hold both: the student is a legitimate peripheral participant - genuinely doing the work, genuinely at the edge of it, and genuinely protected by their position there. The client gets real engagement and a real product; the student gets real practice; the university guarantees the frame within which failure is educational rather than costly.
The frame is the point. When a project goes wrong under a learner-first design, the module leader absorbs the client relationship, the students are assessed on how they responded, and everybody learns. When it goes wrong under a consultant-first design, the students carry the blame for a commercial failure they were never equipped to prevent, and often the unpaid hours of trying to fix it. Universities that market their students to businesses as "free consultancy" have chosen the second frame, usually without meaning to. The test of a well-designed programme is a single question: if the client is unhappy but the students did everything the module asked, who has the problem? If the answer is the students, the design is wrong.
What the marker sees that the client doesn't: the academic anatomy of a capstone
This brings us to the mistake that costs live-project students the most marks, and it follows directly from the two-hat problem. Students naturally pour their effort into the thing the client will see - the strategy deck, the app, the campaign. But the client's deliverable is usually only one component of what is assessed, and often not the largest. A capstone is an academic exercise wrapped around a practical one, and the wrapper has its own demanding requirements that the client never sees and the student frequently under-invests in:
- Research. A situation analysis or literature review that locates the client's problem in what is actually known - the theory of digital consumer behaviour, the evidence on what makes small-business websites convert, the frameworks the discipline uses to diagnose problems like this one. A recommendation without this foundation is an opinion; with it, it is an argument.
- Planning. A proposal, scope and project plan - objectives, methods, timeline, risks, division of labour - produced before the work and often assessed separately. Our earlier articles on research plans that collapse apply with full force: a live project is a research project with a client attached, and it fails for the same reasons.
- Method. A defensible account of how the evidence was gathered - how the survey was designed and sampled, how the interviews were analysed, how the benchmarking was conducted - held to academic standards, not consultancy ones. "We asked some customers" is not a method.
- Deliverables. The client-facing product, yes - but assessed against criteria the client doesn't apply: quality of analysis, use of evidence, coherence of recommendations, professional standard of communication.
- Evaluation. An honest appraisal of the outcome against the original objectives, including what didn't work, what the limitations of the evidence were, and what the client would need to do to implement. Client satisfaction is one input to this; it is not the measure.
- Reflection. A structured account - often using a model such as Gibbs's reflective cycle or Donald Schön's distinction between reflecting in and on action - of what the student learned about the discipline, about working with a client, about themselves. Sheffield assesses its Live Projects partly through "a reflective discussion between the student group and tutor and a management report submitted individually," and this is typical. Students routinely dismiss the reflective component as padding. It is frequently the component that separates a pass from a distinction, because it is where the learning - the thing the whole exercise exists to produce - is actually demonstrated.
The result is a genre that most students have never seen assembled: part research report, part project-management document, part professional deliverable, part reflective essay, each with different conventions, all required to cohere. It is a structurally strange document, and students who have written excellent essays and excellent client decks frequently produce a poor capstone because they have never seen how the parts fit together. As we've argued throughout this series, the fastest route into an unfamiliar genre is to study a well-constructed example before attempting your own - and a capstone is several unfamiliar genres at once. UKEssays' capstone project support provides model capstones written by academics in the relevant discipline, showing how the research grounding connects to the recommendations, how a methodology is defended at academic standard while remaining usable for a client, how an evaluation chapter handles a project that only partly succeeded, and what a genuinely analytical reflection looks like as opposed to a diary - alongside feedback on your own draft while there is still time to restructure it. Used as intended - to see the architecture of the whole before building your own around your own client, evidence and experience - it addresses precisely the component most students neglect. The rule that runs through this series applies here with an extra edge: the model is a scaffold to learn from, and the capstone you submit must be your own - not least because the reflection at its heart can only be written by the person who lived the project, and any marker will know within a paragraph if it wasn't.
Before you say yes: a student's checklist
- Who is the client, and could they otherwise afford this? A charity or start-up is a different proposition from a profitable company. If the latter, what is the company giving back - a fee to the programme, mentoring time, interviews, paid follow-on?
- Is there a written brief with fixed scope and stated level of finish? If not, ask for one. "Prototype, not production" and "student work, no warranty" should appear in it.
- What does the agreement say about IP? Aim to retain ownership with a licence to the client, and an explicit right to portfolio use.
- Is confidentiality handled by a university tripartite agreement that protects assessment, moderation and external examination? Never sign a client's commercial NDA without the module leader seeing it.
- How are you being assessed? Find the criteria. Note how much weight sits on research, method, evaluation and reflection versus the client deliverable, and allocate your hours accordingly.
- What happens if the client disengages or moves the goalposts? There should be a named academic who owns the client relationship. If the answer is "you sort it out," that's the consultant frame - push back.
- What is your hour cap? Decide the maximum you will give the project beyond its timetabled allocation, and hold to it. Your degree is the expensive thing.
The bottom line
Should students solve real business problems for free? The evidence says the learning is real: authentic tasks, legitimate participation in a profession, a concrete experience to reflect on and a line on the CV that opens doors the internship market keeps shut for students without money. It also says the value flowing to organisations is real - real enough that the same graduate, six months later, commands £35,000 a year for it under a KTP - and that the difference between a public good and a quiet subsidy to commerce lies in two questions: whether the client could have paid, and whether the project is built around the student's learning or the client's deliverable. Get ownership and confidentiality onto paper before the first meeting, insist on a brief that fixes scope, treat the client's satisfaction as one input to your assessment rather than its measure, and give the academic wrapper - the research, the planning, the evaluation and above all the reflection - the effort it actually earns. Done that way, a live project is one of the most valuable things a degree can offer, to students and to the organisations that genuinely need them. Done carelessly, it is unpaid consultancy with a certificate attached, and the people who pay for it are the students who could least afford to.
