
Overview
Formstack made it easy to build custom forms without code. But once teams collected data, it was hard to turn that data into useful documents. Creating custom exports often required technical skills or extra tools, like third-party integrations. This limited how enterprise teams could use their data.
PDF exports were an important part of the product, but limited customization and usability reduced their value and adoption.
I redesigned the export experience to match how customers actually use their data. This made exports more flexible and opened up new ways for teams to use them.
This work:
The exported PDF file looks even worse. I can’t believe it is not possible to even see my logo in the submitted forms. There should be a way to make it look decent. I can’t just hand this to a customer.
Overview
Customers needed to generate professional, branded PDFs from form data, but the existing experience was rigid, unattractive, and difficult to customize.
This created friction for:
The existing PDF export experience created friction at a critical moment in the workflow:
A core feature meant to extend the value of collected data was instead creating friction and limiting how customers could use Formstack in real workflows.
To understand how exports fit into broader workflows, I combined product analytics signals (feature requests and votes) with qualitative research:
This helped identify usability issues and gaps in how Formstack supported downstream data usage.
Across interviews and competitive analysis, a pattern emerged: PDF exports were a primary way customers communicated data to others. Usability and customization weren’t “nice-to-haves,” they were essential for real-world use.
Fun Fact:
By using psychology, nudge techniques, and personalizing each email, I achieved a 100% response rate to my email invitations for user interviews. One participant, who was on vacation during our interview period, insisted on speaking with us the week he returned.
To guide the redesign, I defined a set of design principles based on research insights. These principles ensured the solution addressed the broader role PDFs played in customer workflows.
1. Design for control without complexity
Research showed enterprise customers needed:
I focused on enterprise readiness, not just feature parity.
Late-stage feature gating introduced pricing complexity.
Challenges
Not a feature, but a system-level shift:
Results
Results
This work: