![](data:image/svg+xml,<svg display="block" role="presentation" viewBox="0 0 22 22" xmlns="http://www.w3.org/2000/svg"><path d="M 0 0 L 0 19.127 L 8.709 22 L 8.709 5.347 C 8.709 0 0 0 0 0 Z M 5.532 19.142 L 3.177 18.371 L 3.177 2.631 L 3.592 2.759 L 4.224 2.953 C 5 3.192 5.532 3.934 5.532 4.776 Z M 18.741 6.199 L 18.741 0 C 18.741 0 10.031 0 10.031 5.347 L 10.031 22 L 18.74 19.127 L 18.74 8.753 L 14.529 10.058 L 14.529 13.606 L 15.564 13.306 L 15.564 18.371 L 13.208 19.142 L 13.208 4.776 C 13.208 3.934 13.741 3.192 14.517 2.953 L 15.564 2.631 L 15.564 7.251 L 18.74 6.199 Z" fill="rgb(0, 0, 0)" height="22px" id="iRPdBku8W" transform="translate(1.63 0)" width="18.740741374796762px"/></svg>)
MarkFilling started as an internal MVP built to validate Square's core trademark workflow.
Phase 2 set out to turn it into a public-facing SaaS product — and that meant designing an account experience that didn't exist yet.
Context
MarkFilling is a web portal built for Square to digitize core trademark-protection processes — prior-art search, classification, filing, and surveillance. An internal MVP validated the core workflow in Phase 1.
Problem
A technical-functional audit, commissioned by Square via Innovix Consulting, mapped what Phase 2 needed to turn that internal MVP into a public B2B SaaS product: self-service registration, a role-differentiated account area, and the supporting flows a purely internal tool never required. Working through Innovix Consulting, I used the technical-functional analysis as the starting point for the wireframing phase.
Wireframing: from V1 to V2
I designed the project's wireframes across two iterations. V1 defined the primary flows: sign-in and registration, a procedures dashboard, and the multi-step wizard for creating a trademark procedure. V2 evolved that foundation into a more complete, role-differentiated structure — separating the admin experience from the user's, and rounding out account settings, onboarding, and the public-facing pages.
