Orzu needed to communicate an ambitious community and opportunity platform without relying on slides alone. Partners had to understand the vision while being able to inspect how its main roles would actually work.
Case study
Orzu Platform
A public pitch and role-switching product demo that makes a student-network platform inspectable from student, employer, and administrator perspectives.
The light-mode role portal starts with an explicit role choice, making the platform's three perspectives immediately inspectable.
Built a narrative pitch site and an interactive Angular demo with distinct student, employer, and admin workspaces connected by a shared product model.
Turned a platform proposal into two evaluable artifacts: a persuasive public narrative and an interactive product demo that stakeholders can inspect role by role.
Context
Orzu began as a platform idea for connecting Uzbek students abroad with community, opportunities, employers, events, and institutional support. The communication challenge was as important as the interface challenge. A conventional presentation could explain the ambition, but it could not show how a student, employer, or administrator would experience the product.
The project included product concept development, information architecture, a public pitch, and an interactive demo under PenguinDev. The result is intentionally split into two layers: a narrative website for context and a role-based product prototype for inspection.
From Pitch to Product Surface
The pitch site introduces the problem, community context, proposed modules, roadmap, and operating model. It is designed for stakeholders who first need to understand why the platform should exist. Clear routes into the demo prevent the pitch from becoming a dead-end presentation.
The demo starts with a role portal. Visitors can enter as a student, employer, or administrator without credentials, making comparison part of the experience. Each role receives distinct navigation, dashboards, and actions while sharing the same visual and conceptual system.
Students see profile progress, career matches, community groups, events, and startup activity. Employers see opportunity publishing, talent discovery, applications, and pipeline movement. Administrators see the coordination layer: users, groups, opportunities, content, moderation, partnerships, events, and platform signals.
Decisions and Tradeoffs
The main product decision was to demonstrate breadth through connected role journeys rather than a collection of unrelated mock screens. An employer opportunity should make sense beside the student’s career pipeline and the administrator’s governance surface. The system map makes those relationships explicit.
The second decision was to keep the prototype easy to enter. Authentication buttons and role selection communicate the intended identity model, but the demo itself does not hide behind credentials. That lowers friction for a pitch audience and lets a technical reviewer inspect the product structure directly.
Because this is a concept and demo rather than a production launch, its numbers and activity states are illustrative. The portfolio labels it accordingly and does not imply live adoption.
Public Demo
Both artifacts are publicly accessible. The pitch demonstrates narrative and stakeholder communication; the Angular demo demonstrates role-aware application structure, responsive dashboards, workflow framing, and a coherent interface system across three user types.
Result
Orzu makes an ambitious platform proposal tangible enough to discuss, test, and critique. The pitch and demo remain clearly labeled as pre-production work that would still need validation before launch.
Contact
Let's talk.
For professional opportunities, collaborations, or selected freelance work.
Open to conversations Frankfurt, Germany Europe/Berlin
GitHub penguindevteam@gmail.com