Varun OS
Case study
Appearance
ResumeContact
InventFundsProduct case study

Connecting people who build ideas, fund them and help deliver the work.

InventFunds brings Founder, Funder and Fixer workflows into one product. The design had to support project creation, discovery, evaluation, collaboration and NDA management across web and mobile.

Role
UI/UX Designer
Contribution
Product UI, states and implementation review
Platforms
Responsive web + mobile
Implementation
Angular + Ionic collaboration
BuildFounder

Create projects, define phases and bring collaborators into the work

EvaluateFunder

Discover projects, review details and structure investment decisions

ContributeFixer

Build a specialist profile, find opportunities and collaborate securely

Product evidenceFunder dashboard
Real interface from the project. Financial values and user details shown in the screen are representative.
01

Product model

Three roles enter the product with different goals.

Founders need to turn an idea into a structured project. Funders need enough information to compare opportunities and make a decision. Fixers need to show their expertise and find work where they can contribute.

The product could not use one generic dashboard for every user. Navigation, information priority and actions had to change with the selected role while shared project records remained connected.

Shared layerProjects, people and files

Common records connect work across roles.

Role layerDifferent decisions

Each dashboard prioritises the next action for that role.

Trust layerNDA and permissions

Access changes as collaboration becomes formal.

Product evidenceRole selection and Fixer profile
Real mobile screens showing how the product establishes a role before collecting role-specific information.
02

Founder workflow

Turn an early idea into work that other people can understand.

The Founder flow progressively structures a project through details, phases, team access and collaboration terms. This keeps the initial setup manageable while creating enough context for Funders and Fixers later.

01Define

Project basics and purpose

02Plan

Phases, files and requirements

03Invite

Team members and access

04Agree

Terms before collaboration

Product evidenceFounder collaboration setup
Real web screens showing permission assignment and collaboration terms.
03

Funder workflow

Move from discovery to evaluation without losing project context.

Funders browse projects, open detailed records and move through a guided evaluation process. The interface keeps project information, people and financial decisions connected instead of spreading them across unrelated screens.

The investment flow divides a complex decision into clear steps. Funders can review participants, define contribution details and confirm the structure before moving forward.

Product evidenceDiscovery and project evaluation
Real web screens showing project discovery, detail review and the structured investment process.
04

Fixer workflow

Make specialist expertise useful for project matching.

Fixers create profiles around expertise, industries and experience. The mobile experience then uses that context to support discovery, saved opportunities, collaboration and communication.

Decision

Collect expertise as structured profile information rather than relying only on a free-text bio.

Reason

Structured skills support clearer project discovery and help Founders understand why a Fixer may be relevant.

Trade-off

Detailed onboarding improves matching context, but it increases the effort required before the profile feels complete.

Product evidenceFixer dashboard and discovery
Real mobile screens showing the Fixer workspace and opportunity discovery.
05

Trust and NDA

Make document status visible before people share sensitive work.

NDA information originally needed clearer separation by role and status. I worked on role-specific cards, current and past NDA sections, global templates and the empty, loading and error states around them.

The design treated NDA status as part of the collaboration workflow. Users needed to understand what was active, what required action and which document governed the project before accessing sensitive information.

CurrentActive project NDAs
ActionReview or sign
ReferenceGlobal NDA template
RecoveryEmpty, loading and error states
Trust-state architecture
The NDA component is a workflow, not a document cardReview the state model that controls access, action and recovery.

Portfolio reconstruction based on delivered design.

Component variantsState coverageVisible cueUser purpose
EmptyNo NDA exists

Explains who can create the agreement and what happens next.

DraftNot shared

Keeps incomplete legal context out of the collaboration flow.

ReviewAction required

Shows who must read or sign before access changes.

ActiveAccess governed

Identifies the agreement currently protecting the project.

ExpiredPast agreement

Keeps historical context without implying current access.

ErrorDocument unavailable

Protects sensitive access and provides a recovery action.

Product evidenceNDA and collaboration communication
Real web and mobile screens. The case study focuses on visibility and state design rather than legal document content.
06

Handoff and reflection

Design decisions continued into implementation review.

01

Design

Created role-specific dashboards, workflows, states and responsive interfaces.

02

Implementation support

Worked with the Angular and Ionic structure, reviewed component behaviour and checked UI styling.

03

Design QA

Compared implemented screens with the intended hierarchy, states and responsive behaviour.

What the work established

A connected product model across web and mobile

The design covered role-based dashboards, project discovery, investment decisions, collaboration and document access.

What I would improve next

Validate the longest decisions with real users

I would test Founder setup, Funder evaluation and Fixer onboarding separately, then measure where users pause, leave or need support.

Outcome boundary

Formal usability results, adoption metrics and investment outcomes were not available. This case study documents the delivered design work and the next validation steps without inventing business impact.