Classifying business structure upfront
By asking for the seller's legal structure first (sole proprietorship, LLC, or corporation), the flow hides irrelevant tax schedules immediately. A solo merchant never sees questions meant for a corporation.
Open for product design roles & research collaborations.
Simplifying legal compliance so new merchants can get approved and start selling quickly.
In a 36-hour sprint, I designed an adaptive onboarding flow for marketplace sellers navigating multi-state tax and entity requirements. The flow asks only for what is required for each business structure, supports multi-session document uploads, and was validated using an interactive prototype built with AI assistance.
A sole proprietor selling crafts from home has very different compliance requirements than an LLC with warehouse inventory across multiple states. When an onboarding flow attempts to cover both with a single rigid questionnaire, solo sellers get overwhelmed by corporate tax schedules, while larger businesses struggle to clarify physical versus economic nexus obligations.
By asking for the seller's legal structure first (sole proprietorship, LLC, or corporation), the flow hides irrelevant tax schedules immediately. A solo merchant never sees questions meant for a corporation.
Merchants rarely have every resale certificate or tax document ready at once. A dynamic checklist outlines exactly what is needed, shows current status (Ready, Pending, Missing), and allows merchants to save their progress and return later without starting over.
Tax IDs and bank routing numbers are validated inline as the merchant types. If a digit is missing or formatted incorrectly, clear guidance appears immediately, preventing days of delay caused by a rejected submission.
A consolidated review ledger displays entity details, confirmed tax jurisdictions, and payout accounts. Merchants can adjust any field directly in place without clicking back through previous steps.
In a 36-hour sprint, building an interactive prototype made it possible to test branching logic and state transitions without waiting on backend APIs. If taking this to production, the next priority would be observing how sellers handle multi-day document collection in usability sessions.