How UniSphere works

Your project. Your people. Built together.

Find college students who want to build what you want to build. Post a project, join a specific role, and turn a shared idea into work you can show.

Student login See an example project

From idea to completed project

From “I have an idea” to “we built this.”

Post

Post the project. Name the roles.

Describe what you are making, what exists already, and the roles that would move it forward. A project gives people something specific to respond to.

Demo · Static preview · Project and role

Campus Reuse · Product designer

Build a clickable listing prototype and revise it after usability testing.

Team up

Choose the people to build with.

Students browse projects and request a particular role. The owner sees what they want to own and why they are a fit before deciding.

Demo · Static preview · Application status

Example request · Pending

The owner reviews the selected role and proposed contribution before accepting.

Build

Bring the team into one conversation.

An accepted request adds the teammate to the project and opens a shared conversation. The introduction immediately becomes a place to work.

Demo · Static preview · Team conversation after acceptance

Example planning message

“Let's review the listing sketches together and agree on the next prototype task.”

Finish

Keep a record of what you built.

The owner marks completion. Recorded roles and collaborators remain on member profiles. The record is owner-managed, not independently certified by UniSphere.

Demo · Static preview · Completed-project record

Listing and collection prototype

Recorded role: Product designer. Completion is marked by the project owner.

Two ways to get started

See how the flow works before creating an account.

Joining a team

Read the project, choose an available role, and send a request. Track its status; an accepted request opens the team conversation.

Explore a project and its roles

Finding teammates

Save a draft, describe the deliverable, and define roles before publishing. Review incoming requests and accept the teammates you want to build with.

Read the draft and publishing guide

The Demo shows fictional plans. Application status and team messages require an account and stay private in the student app.

Proof of work

The project ends. The record stays.

Project owners mark completion. Profiles show recorded roles and collaborators; UniSphere does not independently verify each contribution. Shared records may remain under a deleted-account label after account deletion.

Illustrative completed-project record

Listing and collection prototype

Recorded role: Product designer
Example contribution: Designed the listing screens and revised the collection flow using the team's research notes.
Collaborators and completion date: This fictional record has no real members or completion date.
Record source: In the app, the project owner marks completion and roles come from the project membership record. UniSphere does not independently certify each contribution.

View the full example and deliverables

Continue in the student app

Ready to start something at ASU?

Explore real opportunities in your verified school community, or post an idea and name the teammates you need.

Browse ASU projects Post your project