Turning research into results: The full journey of content-first design in SaaS
Published by: AT Studio
Published:
Summary: This blog walks through the full process of creating a content-first website for a SaaS product, from research to copywriting to design execution. Using Flowbit as a case study, it shows how aligning strategy, structure, and storytelling leads to conversion-focused design. You’ll learn how to define user goals, map them into content, translate the content into design, and ensure every decision supports clarity, consistency, and results.
In this Article:
- Introduction
- From Research to Structure: Building the Foundation
- How I convert the research into content
- 1. Define the purpose of each page
- 2. Understand the viewer’s psychology on each page
- 3. Write the copy
- Result example: The web content I wrote for Flowbit
- How I convert the content into design
- Establish Visual Hierarchy to prioritize content
- Add secondary information without disrupting the flow
- Organize the Typography and Whitespace
- Create reusable components
- Colorize the website
- Fill out the empty space with illustrations
- Conclusion
Related Topics
Introduction
Design isn’t about drawing pretty pictures. It starts with a purpose. Whether it’s increasing sales, promoting environmental action, or encouraging daily use, web design begins with a clear goal. This goal defines whether the site should be content-first or visual-first.
In most cases, especially for SaaS, your website must be content-first. If you want people to try your product, trust your team, and eventually convert into paying customers, then content becomes your most powerful tool.
Great designers don’t just decorate. They guide users with intention, clarity, and focus, ensuring nothing distracts from the message.
In this article, I’ll walk you through how I turned research into strategic content and then translated that content into a result-driven design for Flowbit, a SaaS product.
From Research to Structure: Building the Foundation
To ground the design in real user needs, I followed this SaaS web design research guide and collected data on competitors and user behavior.
Click here to see the research data of Flowbit
Based on that, I mapped out five key user tasks and structured the website around them:
Task 1: Understand what Flowbit does → Home
Task 2: Explore key features → Features
Task 3: Evaluate pricing → Pricing
Task 4: Decide to trust the team → About
Task 5: Ask final questions → Contact
This formed the core of the sitemap and user flow, aligning content with user intent and guiding visitors from awareness to conversion.
How I convert the research into content
Once the purpose is clear, writing content becomes much easier. It’s all about aligning your message with your audience’s psychology. Here are the three steps I used to write copy that resonates, followed by a real example from Flowbit.
1. Define the purpose of each page
Every page exists for a reason. You need to ask: What should this page achieve?
For example, on the Home page, I’m not trying to hard-sell. I’m warming up the audience, making them feel welcome, and focusing on benefits rather than features. Product details are saved for the Feature page, but even there, the copy stays benefit-driven.
2. Understand the viewer’s psychology on each page
Next, step into the user’s mind: What are they thinking when they land here? That shapes your tone and language.
Think of it as walking into a store. Visitors are interested but not ready to buy. So the homepage showcases your best and cleanest messaging, solving their pain points and grabbing attention with benefits first. Once they are hooked, you explain how it works. This gives them a clear signal that they can benefit from your product without putting in much effort. After that, you build trust through testimonials or logos from credible partners. Every page should simulate this mental journey and guide the user smoothly forward.
3. Write the copy
With a clear purpose and user mindset, all the job left for you is expressing it in words that match their stage in the journey.
Let’s say your SaaS helps users write copy. A homepage headline might be: “Get AI-powered copy that boosts conversion by 3% in just 3 seconds.” This follows a clear format: (what you do) + (benefits) + (timeframe
Result example: The web content I wrote for Flowbit
With the sitemap and user flow mapped out, I wrote the content to guide users based on what they would likely think and feel at each step. Here is the reasoning behind each page:
Home
The homepage is the first touch point, so the message needs to be professional, approachable, and focused on benefits. Instead of listing features, I highlight how Flowbit helps users. I then invite them to learn more via the Feature page or try it for free.
Structure: Hero → Benefits → How it Works → Testimonials → CTA
This hooks interest, builds trust, and encourages action.
Features
Users who are truly interested in the product will visit this page, so this page goes deeper. I present the five core features and explain how each solves common problems. I also include personalized sections for different user segments: freelancers, remote workers, and busy individuals. The page ends with a tailored CTA aligned with their mindset at this stage.
Pricing
Visitors here are close to buying but may have cost concerns. The copy is direct: three pricing cards with clear comparisons. The goal is clarity and fast decision-making.
About
People click here to build trust. This is not a sales page. It is about showing who is behind Flowbit and how the team is committed to solving real user problems. It helps them feel connected to the people behind the product, not just the product itself.
Contact
Visitors here may have final questions or need support. I keep it simple: a short form, a contact message, and an FAQ section to reduce unnecessary submissions.
Click here to see the full website content of Flowbit
How I convert the content into design
The structure of a website is often formed while writing the content. By this stage, you should already have a sitemap, user flows, and a finalized copy. From there, design becomes the tool to guide users visually, helping them focus on key content and navigate the site with ease.
Establish Visual Hierarchy to prioritize content
In this article, I explain how visual hierarchy helps guide the user’s eye through the page in a specific order of importance. It is about arranging design elements so that the most important parts stand out first.
With insights from How Users Read on the Web by Jakob Nielsen in mind, I placed the key messages in high-contrast areas such as headlines and CTAs. CTAs are often styled with background colors, while headlines use large font sizes to grab attention.
I also apply findings from How People Read Online to map out the eye-tracking path. This helps me design layouts where users do not jump around the screen or zig-zag from left to right too frequently. Here’s an example of how I applied these principles in Flowbit’s hero section:
Add secondary information without disrupting the flow
Once the main content is visually prioritized, I begin inserting supporting content, usually short paragraphs or subheadings. These are placed along the natural eye-tracking path, providing context for users who want to dig deeper without overwhelming those who scan quickly. The following example continues from the previous design:
Organize the Typography and Whitespace
Once the hierarchy is in place, I fine-tune typography and spacing. Good typography reinforces branding, and well-managed whitespace allows the content to breathe.
Both typography and whitespace reduce visual fatigue and improve focus. They create rhythm, making the experience more enjoyable while enhancing legibility. Here’s the setup I used:
Create reusable components
Design is not just about aesthetics. It is also about a system. Repetitive elements such as buttons, navigation links, and cards need to be consistent. So, I convert them into reusable components.
Reusable components ensure consistency and speed up future development. More importantly, they help users stay in the flow without friction. Here’s how I structured these components:
Colorize the website
I always colorize the website after the structure, typography, and spacing are set. Visuals, especially colors, carry strong psychological weight. If they are added too early, they can distract you from judging the layout clearly.
I use color to recharge the user’s attention, reduce monotony, and guide focus back to the content. A little color at key points makes the design feel more lively without stealing the spotlight. Here’s a before-and-after comparison:
Notes: Use color sparingly. The goal is to support the content, not overshadow it. A minimal color palette keeps attention on your message and improves conversions.
Fill out the empty space with illustrations
Finally, I added meaningful illustrations—product screenshots, real photos, and graphic lines—to support the message. These visuals enhance comprehension, create an emotional connection, and reinforce credibility.
This is the final homepage design for Flowbit:
Click here to see the full design.
Conclusion
A result-driven SaaS web design doesn’t happen by chance. It’s the result of a rigorous process—from research and strategy to content and design execution.
If you're looking for a reliable partner to accelerate this process, AT Studio helps SaaS founders turn insights into conversion-focused design.