PITCH CONNECT / INVESTOR, COMPANY & ADMIN EXPERIENCES
Trust, built into the flow.
One platform. Three very different needs. I rebuilt the UX for a curated investment product so investors could discover companies, founders could see progress, and admins could protect quality.
ROLE
Product & UX Designer
TEAM
School of Coding & AI
CLIENT
Confidential
STATUS
Live · Client confidential
01 / CONTEXT & OWNERSHIP
The problem behind the product.
The existing product had inconsistent journeys and developers ready to begin. Its central tension was trust: companies needed enough feedback to stay engaged, investors needed their identities protected, and the admin needed control over the quality of every pitch.
What I owned
I owned UX and UI across investor, company, and admin journeys: auditing existing flows, defining the information architecture, exploring wireframes, creating high-fidelity designs, and handing off directly to development. The design work ran from January to February over six weeks.
02 / THE DECISIONS THAT SHAPED IT
The thinking behind the screens.
01
Make phase one a complete experience.
Messaging, offer tracking, connections, and meetups were deferred. The initial release focused on pitch submission and capturing investor interest. I designed each surface around that scope without displaying gaps for future features.
Reducing scope gave the first release a clear purpose.
02
Share signals, protect identities.
Companies need to know whether a pitch is generating interest. They do not need to see who is watching. I separated aggregate views and interest counts from identifying investor information, which remained visible only to the admin.
The permission boundary became part of the information architecture.
03
Choose one pitch structure.
Rather than offering multiple templates, I designed a standardized pitch structure. A consistent format gives investors a repeatable way to assess companies and gives founders a clear submission path.
The tradeoff was less presentation freedom in exchange for a more comparable review experience.
04
Put review where it adds value.
Admin approval was removed from initial company setup and retained before a pitch becomes visible to investors. Within review, section-level feedback, severity, saved progress, and mandatory rejection reasons support a useful response.
Companies can begin without waiting; quality control remains at publication.
The admin review places section-level feedback beside the pitch, with saved comments and publication approval in the same workflow. The image is a focused view of the original public design board.03 / OUTCOME & LEARNING
Designed in six weeks. Built and live.
Design was completed in six weeks, with 45+ high-fidelity screens across three user types. Development is complete and the platform is live, with the product being presented to prospective clients. Adoption and commercial results are not yet reported.
MEASUREMENT PLAN
The measurement plan covers pitch completion, time from signup to submission, investor interest, return visits, and review turnaround. Results will be evaluated against these criteria as platform usage develops.
What this work reinforced
Privacy can guide a product’s architecture from the start. Here, the important choice was deciding what each person needed to know—and what they should never see.