Problem
Reliance on the pros
Healthcare marketers aren’t equipped with the tools that allow them to create and manage their own medically compliant, interactive content (Stories) without requiring external creative agencies and developers.
What’s fueling this project?
Market opportunity
There aren't content building tools, like Canva, targeting the pharma industry.
Goal
Provide the tools & reduce workloads
Create an ecosystem that healthcare marketers can immerse themselves in to create and manage interactive content (Stories) while still meeting medical compliance, pushing our business model towards a B2B SaaS approach
Expected outcome
A shifting business model
Aiming to move from a project-based model to B2B SaaS.
For added context
What is a “Story”?
Storysoft’s projects are referred to as Stories. A Story is an interactive experience built on a proprietary omni-channel advertisement framework designed to accommodate content that meets global pharmaceutical regulations.
Story = medically compliant & interactive content
What we want to accomplish
Deliverables
Create 3 B2B SaaS products
Create products for Story creation, asset management, and a client/analytics portal that utilize the existing Story framework.
Target users
Tailor to pharma brands
Incorporate common pharmaceutical features and requirements unlike existing content creation products.
UI/UX plan
Implement a design system
Adopt a design system for a consistent visual identity across products.
A deeper look at…
Studio products
Editor
Editor is home to Story creation. Users use this drag-and-drop builder to design and set up Stories within the framework defined by Storysoft and legal medical compliance.
Files
Files is an asset management solution that allows different users across teams to access reusable content & components. It's a folder based system that can be accessed from within Editor.
Studio’s Portal
A total redesign of our client reporting portal, Studio's Portal is the hub for all Stories, Users can access the analytic reports, Story paths, and channel drivers settings for all projects.
Design approach
Early discussions
Determining what features went where
Feature request were weighed against the goals and intentions of Studio, determining what would be included in the early wireframes.
Ideation & iteration
Strategic compromise & wireframe reviews
My first wireframes were filtered through department reviews, leading to compromises across function, features, and technical limitations.
Defining styles
Adopting a design system
By implementing the new design system to the refined wireframes, I created the first fleshed-out prototypes used for review.
Testing the prototypes
User feedback sessions
User feedback session were used to test refined features, workflows, and usability, then designs were updated accordingly.
Dev handoff
Annotated prototypes
I communicated detailed specs, flows, and design system updates for hand-off to the development team.
Review
300+ jira tickets
I worked closely with developers, supporting QA, making design adjustments, and answering any implementation questions.
Launch!
Refinement & client trials
I refined the MVP based on real usage and client feedback from the Otezla team with Amgen in a trial use of Studio.
Where users design, build,
and publish content
Studio Editor & Portal
Results & impact
Positive client reactions
We’ve received great reactions and feedback from clients surrounding ease of use and product uniqueness.
2nd largest source of revenue
The efficiency of Studio is bringing in new brands, increasing total sales and client retention, becoming Storysoft’s 2nd largest source of revenue.
Reduced internal workloads
With the release of Studio, some clients and their projects have completely shifted over, leaving less custom projects.
New opportunities & initiatives
With less bandwidth going towards individual client projects, team members explored new ideas and workflow improvements.
Landed some BIG clients
Large players in the pharmaceutical industry have Studio subscriptions including Amgen and Eli Lilly.
An Eli Lilly team member once said…
“This [Studio Editor] is pretty intuitive. With the way it’s designed, if I’ve never seen this before, I could still get a good result.”
How'd it go?
It went really well!
Now that Studio has launched, I can look back and say I’m really proud of how these products turned out. As the lead designer on this project, I was able to learn quite a bit, especially through working alongside other departments.
Studio will continue to grow and expand it's capabilities with ongoing regular releases, with a goal of quarterly updates.
An update
2026
As a few version updates have released, Studio has continued to be a success, on average bringing in 2-5 brands, and therefore more seats, per subscription.