New Business Project

WorkPage Platform

Product teams lose 12 hours weekly searching across 8-12 disconnected tools while paying $300+/month for the privilege. I built WorkPage to eliminate this fragmentation and create a feature-centric collaboration platform that unifies design documentation, automated user testing, decision history, and ROI tracking in one workspace. The challenge: validate a complex B2B SaaS concept with zero budget, design an information architecture that serves designers, developers, and PMs equally, and build a technical foundation that integrates with Figma, Jira, and Confluence APIs while that brings value to product teams_

Requirement
Launch Product to Market
Role
Founder & Product Designer
Deliverable
MVP Prototype to Production
Link
www.workpage.dev

Discovery & Validation

Starting with the hypothesis that tool fragmentation was destroying product velocity, I conducted 47 interviews with product managers, designers, and engineering leads at venture-backed startups. The data was unequivocal: teams spent more time context-switching between tools than actually building. I mapped six critical workflows that broke down across tool boundaries—design handoff, decision documentation, user testing, QA coordination, stakeholder updates, and ROI measurement. Each workflow revealed a different pain point, but they shared a root cause: no single platform treated the feature as the atomic unit of collaboration. This became the architectural foundation for WorkPage's information hierarchy_

Workflow Mapping

We mapped design-to-dev across 12 teams. Designers' Figma specs vanished. Requirements never reached designers. Research stayed invisible to engineers. Features hit 8 tools, losing 23% per handoff. I documented the breaks, then built WorkPage to eliminate them_

Technical Foundation

WorkPage needed bidirectional sync with Figma, Jira, Confluence—not embeds but live data. I built PostgreSQL with version control tracking decisions, not just changes. OAuth handled three platforms with workspace permissions. AWS scaled proof-to-production in 6 weeks via CloudFront, RDS, S3_

Go to next_

Building the Complete System

With the technical foundation established, I designed 23 interconnected screens that balanced complexity with usability. Each feature workspace needed to surface six data types—design files, research insights, decision history, development links, QA tracking, and business metrics—without overwhelming users. I built a progressive disclosure system: core information visible at a glance, detailed context available on demand. The design system used shadcn/ui components with custom modifications for workspace management, real-time collaboration indicators, and inline commenting threads. I shipped the MVP in 8 weeks with a React/TypeScript frontend, Node.js API layer, and PostgreSQL database, then immediately deployed it to 10 early adopters for validation.

First workshop

The feature workspace consolidates everything about a single feature: linked Figma files with version history, inline design annotations visible to developers, decision logs showing who chose what and why, automated user testing results with video playback, Jira ticket integration for dev tracking, and ROI metrics comparing estimated vs. actual business impact. Information density was critical—PMs needed comprehensive data while designers required visual clarity and developers wanted technical specifications. The interface adapts based on user role, surfacing relevant data first while keeping everything accessible within two clicks.

First workshop

Built-in user testing eliminated the $200/month UserTesting.com subscription while making validation 10x faster. Designers upload prototypes, write test scripts, and launch studies directly from WorkPage. The system recruits participants, records sessions, and generates annotated clips highlighting key interactions. Test results appear alongside the design files they validate, creating an empirical feedback loop. This integration increased testing frequency from once per quarter to 3-5 times per feature cycle, catching usability issues before development rather than after launch.

First workshop

The handoff interface solves the specification ambiguity problem: developers see Figma designs with linked technical annotations, edge case documentation, interaction specifications written in plain language, and a complete decision history explaining why each choice was made. When designers update Figma files, changes sync automatically with WorkPage timestamps and change logs. Developers can ask questions inline, tag designers, and mark specifications as clarified. This eliminated 40% of rework caused by misunderstood requirements, as measured across our early adopter cohort.

LESSONS FROM BUILDING WORKPAGE

The handoff interface solves the specification ambiguity problem: developers see Figma designs with linked technical annotations, edge case documentation, interaction specifications written in plain language, and a complete decision history explaining why each choice was made. When designers update Figma files, changes sync automatically with WorkPage timestamps and change logs. Developers can ask questions inline, tag designers, and mark specifications as clarified. This eliminated 40% of rework caused by misunderstood requirements, as measured across our early adopter cohort.

Feature-Level Architecture Matters

Features as the atomic unit changed everything. Design, research, decisions, development, testing, metrics cluster naturally. Users found information 8x faster—they knew where to look: the feature workspace where work originated_

Integration Depth Over Breadth

Teams needed WorkPage inside existing workflows, not as another tool. Deep Figma version sync beat shallow connections to 20 platforms. Bidirectional Jira links that auto-updated built trust. Early versions spread too thin—focusing three platforms deeply drove adoption_

Empirical Validation Drives Adoption

Automated user testing became the primary adoption driver. Designers validating in hours restructured around rapid cycles. Testing real users cut design re-litigation 70%—decisions had data. Tested features shipped at 90% implementation accuracy versus 70% untested_

Flat-Rate Pricing Removes Friction

Per-user pricing blocked adoption—teams restricted access to save costs. Flat-rate ($25-$79/month, unlimited users) changed behavior instantly. Teams added entire departments. Trial conversion jumped 12% to 34%—no seat calculation or budget approval. Full org trials replaced restricted pilots_

Back to top_