Designing clarity from ambiguity

The Opportunity

The idea came from a simple observation.

The founder mentors startups through accelerator programs and repeatedly saw founders asking the same question:

"What's the best software for my business?"

The answers usually came from:

• sponsored comparison websites

• generic "Top 50 SaaS Tools" articles

• inconsistent rankings

• recommendations from other founders

Finding software had become a research project of its own.

Instead of creating another directory, we wanted to build a platform that made software discovery feel structured, trustworthy, and approachable.

My Role

As the sole designer, I owned the product from concept to launch.

This included:

• defining the product structure

• designing the complete user experience

• creating the visual identity

• establishing the design system

• building the website

• coordinating integration with our external platform partner

• leading QA and UAT before launch

While the founder focused on partnerships and business development, I focused on turning an idea into a usable product.

The Challenge

Building a marketplace isn't simply about listing products.

It's about helping people make confident decisions.

We also had several constraints:

• launch within two months

• team of two

• limited budget

• evolving product vision

• only 35 launch partners

• dependency on an external integration partner

Every design decision had to maximize clarity while keeping the product scalable as new providers were added.

Design Principle #1

Start with the problem, not the product

Most software directories immediately ask users to browse hundreds of tools.

I wanted users to first identify what they were trying to accomplish.

Instead of thinking:

"Which CRM should I buy?"

Users first answered:

"I need help managing customers."

Organizing discovery around business needs reduced cognitive load and made the experience accessible even to founders with limited technical knowledge.

Design Principle #2

Educate before asking users to choose

One early concept placed the searchable directory directly below the hero section.

While this reduced clicks, it also skipped an important step: helping users understand unfamiliar software categories.

I deliberately moved educational content earlier in the experience.

By giving users context first, they entered the directory with greater confidence and a clearer understanding of what they were actually looking for.

Decision

Rejected: Homepage-first directory

Chosen: Education → Discovery → Provider

Why: Confidence leads to better decisions than speed alone.

Design Principle #3

Turn learning into action

Educational content shouldn't become a dead end.

Every technology overview page concluded with a contextual call-to-action that opened a pre-filtered version of the directory.

For example, someone learning about attribution software could immediately continue exploring attribution providers - without restarting their search.

This small interaction shortened the distance between learning and decision-making.

Design Principle #4

Build trust through neutrality

The platform showcased dozens of unrelated SaaS brands.

Instead of competing with those identities, I designed a visual system that intentionally stepped into the background.

The interface used:

• generous whitespace

• approachable photography

• geometric illustrations

• subtle patterns

• modern typography

• restrained color usage

The result was a visual language that felt welcoming regardless of the provider or industry being showcased.

Trust wasn't communicated through copy alone.
It was reinforced by every visual decision.

Designing for Fast Scanning

Startup founders rarely read every word.

The interface was intentionally optimized for scanning.

Large headlines, oversized calls-to-action, highlighted keywords, and generous spacing helped visitors understand each section in seconds before deciding whether to continue reading.

Rather than asking users to search for information, every section answered a simple question:

"What should I do next?"

Beyond Design

One unexpected challenge emerged late in the project.

Our third-party integration partner struggled to deliver key functionality on schedule, creating friction between both companies and putting the launch timeline at risk.

Rather than allowing the partnership to break down, I facilitated discussions between both teams, documented outstanding issues, proposed a recovery plan, and introduced frequent QA and UAT checkpoints to verify progress.

The partnership recovered, the integration was completed, and we launched on schedule.

It reinforced an important lesson:

Product designers don't only create interfaces - they help teams move forward.

Outcomes

Although the startup didn't implement comprehensive product analytics, several outcomes validated the direction.

• Successfully launched within the planned timeline.

• Built a searchable directory spanning 35 SaaS providers across 16 categories.

• Became a recommended resource within two startup accelerator communities.

• Generated stronger-than-expected referral traffic from accelerator partners.

• Received positive qualitative feedback from accelerator coordinators, who reported founders were actively using the platform to discover software for different stages of growth.

While the product remained in its early stages, it proved that thoughtful information architecture and trustworthy positioning could create value even with a relatively small catalogue.

Reflection

If I were redesigning SaaSgenie today, I wouldn't start with a directory.
I'd start with a conversation.

Instead of asking founders to browse categories manually, I'd use AI to understand their business stage, goals, existing workflows, budget, and operational challenges before recommending a tailored software stack.

The opportunity extends far beyond software discovery.

SaaSgenie could evolve into an intelligent operating advisor - helping founders identify workflow gaps, recommend more cost-effective tools, improve internal processes, and guide smarter business decisions over time.

Looking back, that's the biggest lesson I took away from this project:

Design isn't about helping users find more information.
It's about helping them make better decisions.

Key Takeaways

• Translated an ambiguous startup idea into a launch-ready product.

• Designed the complete user experience, brand, and interface.

• Built a scalable marketplace architecture under tight constraints.

• Balanced education, discovery, and trust to reduce decision fatigue.

• Stepped beyond design to resolve integration risks and keep the launch on track.