Student Business Projects With Friends: Agree Roles, Ownership and Exit Plans

Tom — Singapore Digital Business & Systems Consultant

Tom

Digital Business & Systems Consultant · Singapore

7 min read Article date First published
Student Business Projects With Friends: Agree Roles, Ownership and Exit Plans

Starting a business with friends as students goes better when you agree the rules before building a website or app. Settle four things: whether you are learning or selling, and who does what; how you record decisions and contributions; who holds the domain, email, social and code accounts, with at least two people able to recover each; and how a friend can leave or the project can stop. The one-page charter below covers all four. It is a conversation tool, not a legal contract.

Key takeaways

  • Agree whether you are learning or selling; roles, money and customer promises differ.
  • Log decisions and contributions from day one, so disagreements stay factual.
  • Decide who holds each account before building, with at least two people able to recover it.
  • Write down how someone leaves and how the project stops. Leaving is normal, not a betrayal.

Separate learning roles from commercial roles

Most student teams start with an unpaid learning project: coursework, a holiday experiment or a portfolio piece. A commercial project means customer promises, money and deadlines that affect real people. Teams often drift between them unnoticed, which is when friendships get strained.

QuestionLearning projectCommercial project
What counts as success?What you learned and can showA customer served as promised
Who can promise outsiders anything?Nobody; you are asking questionsOnly the person the team names
What happens to money?No sales; agree how small costs are sharedAgreed in writing before the first payment

Give every role one owner and one backup

Name roles by responsibility: customer contact, building, design and content, and records. Each has one owner and one backup to cover exams or illness. Roles can rotate in a learning project; in a commercial one, one named person makes customer promises, so customers never get mixed answers.

Before any money changes hands

ACRA says regular for-profit activity, including home-based and online work, generally needs registration unless exempted, and that you must be at least 18 to register a business. Pass holders should check with their pass issuer first. Check your own case, and if the idea began as coursework, check your school's rules before using it outside class.

If any of you is under 18, involve a parent or guardian before taking payments. For a formal agreement about money, a name or who owns the work, get professional advice; the charter is no substitute.

Record decisions and contributions as you go

Memories differ, so keep two short logs in a shared document:

  • Decisions log. Date, decision, who agreed, why, and when to review it: "12 Jan: version one takes bookings only; payments wait. All agreed. Review after exams."
  • Contributions log. Who did what, roughly how long it took, and any money or equipment put in. Facts, not values.

The logs do not settle who owns what, but they keep disagreements factual and give each of you honest material for a portfolio that shows how you solve business problems.

Decide who holds the domain, email, social and code accounts

Settle this before building. The usual failure is quiet: the domain on one friend's personal email, the social page on another's phone number, the code in a third person's account. If one of them leaves or loses a phone, the project is locked out.

  • Each account has one agreed holder, written in the charter.
  • Logins and recovery go to a project email that at least two of us can open.
  • Where a platform allows several admins, we add a second person instead of sharing a password.
  • Backup codes are kept where at least two of us can reach them, and the list is reviewed whenever someone leaves.

It is the same check I suggest to every business owner: who really controls your domain, email and data.

Plan how to stop or hand over before you start

Agreeing an exit while everyone is friendly is far easier than inventing one mid-argument.

  • If one friend leaves: agreed notice, tasks and files handed over, access removed and recovery details changed the same day, agreed portfolio credit, and one named person telling any customer.
  • If the project stops: what triggers it (an end date, exams, no customer interest by a review date, or anyone asking), how unfinished customer work and any payments are handled, and whether each account is kept, handed over or closed.

The one-page project charter

Fill this in together in one sitting, in a shared document, then read it back aloud. It is a conversation tool, not a legal contract.

SectionQuestions to answer
ScopeWhat problem, for whom? What is in this version, and what waits?
Learning or commercialWhich is it today, and who decides if that changes?
RolesOwner and backup for customer contact, building, design and content, and records
DecisionsWhere the log lives; do we decide together or by majority?
ContributionsTime, money and equipment each person puts in, as facts
AccountsDomain, email, social pages and code: each holder, the login email and the two people with recovery access
Shared recordsWhere customer notes and money records live, and who can see them
If one friend leavesNotice, handover, access removed, portfolio credit
How we stopTriggers, telling customers, and what happens to each account and file
Review dateWhen we reread this, for example after exams

If a line sparks disagreement, you have found the talk you needed before building.

A fictional example: three friends and a coach's booking page

(fictional example) Kai Xiang, Nurul and Rohan are friends on different ITE courses. Their class project is a booking page for a badminton coach Nurul knows, who takes weekend bookings in a group chat. With their lecturer's agreement, they keep going after it is marked.

The charter takes one evening and one argument, over the domain. Nurul handles the coach, Kai Xiang builds, and Rohan does design and the social page. The domain goes in Nurul's name, with a project email all three can open. It stays a learning project until the coach asks to pay.

Six weeks in, Rohan takes more weekend shifts at his part-time retail job, a choice the others respect. The exit plan keeps it calm: two weeks' notice, design files moved to the shared folder, admin access removed and portfolio credit agreed. One gap: the social page's recovery phone was still his; they fixed it that day.

The upside: the project and the friendship both survive. The effort and uncertainty: the charter cost building time, two people now cover three roles, the coach has not decided whether to pay, and they may stop at their review date.

When the project needs a real system

Most student projects should stay manual for a while. If people keep using yours and the manual version strains, a booking tool, client portal or dashboard is web app development, which I scope and quote individually, with a breakdown by milestone. An internal WhatsApp-and-spreadsheet workflow is operations digitalisation.

Bring your charter; it answers who holds each account and who approves decisions. I am a supplier for an agreed scope, not a fourth teammate: see what you handle and what to outsource and how a scoped project runs from brief to handover.

Sources (checked 31 October 2026)

Frequently Asked Questions

Who should control the domain and accounts?

The person the team agrees will carry the project on, named in the charter. Use a project email at least two of you can open, so at least two people can recover every account.

What if one friend wants to leave?

Follow your charter's exit section: notice, a handover of tasks and files, access removed, recovery details changed and portfolio credit agreed. Leaving is normal, not a betrayal.

Is a project charter a legal contract?

No. It is a plain-language conversation tool. If money, a name or ownership of the work is at stake, get professional advice before any formal agreement.

Do we need to register a business?

Check ACRA before you charge customers. Its page says regular for-profit activity generally needs registration unless exempted, and that you must be at least 18 to register.

What should we agree before taking any money?

Who may quote prices and promise delivery, where money is kept and recorded, how costs are shared and what happens to money if the project stops. Put it in writing, and get professional advice if the amounts matter.

Has your team's manual version shown that people need a booking tool, portal or dashboard? Bring your charter and a short brief, and I'll talk you through what a first version could include and who should hold each account. It is a conversation, with no commitment, and your studies come first.

No obligation. No sales pitch. Just an honest conversation.

தொடர்பு