Feasibility & Pricing — Internal Decision Platform

Flagship Internal Product · B2B · Healthcare Research. Designing a core internal platform that enables teams to evaluate feasibility and generate accurate pricing — supporting confident decisions at scale.

Role

Product Designer

Industry

Healthcare Market Research

Duration

3 months

Overview

Before this project, there was no dedicated system for feasibility evaluation and pricing at Konovo.

Teams relied on:

• Excel spreadsheets to estimate feasibility and costs

• Salesforce to manually assemble client-facing quotes

While this approach worked at smaller scale, it became increasingly fragile as project volume and complexity grew.

I led the design of a new internal platform that unified feasibility assessment and pricing logic into a single, structured experience — creating a shared source of truth across Sales, Operations, and Finance.

Why This Was Needed

As the business grew, feasibility and pricing work became more frequent and more time-sensitive — but the process was still handled through spreadsheets and manual steps.

What used to work at a smaller scale started creating delays, rework, and risk. To support faster turnaround and more reliable decisions, the team needed a dedicated system.

The Problem

The spreadsheet-based workflow created several challenges:

• Important logic was spread across multiple files instead of living in one place

• Calculations were hard to review or explain

• Knowledge depended heavily on individual experience

• Small changes could lead to big differences in outcomes

As a result, feasibility and pricing decisions became inconsistent, time-consuming, and stressful under tight deadlines.

My Role

Product Designer · Project Lead

I led the end-to-end design of this platform, from early problem framing through launch.

My responsibilities included:

• Partnering closely with Product and Engineering to define scope and requirements

• Translating complex workflows and business logic into clear, usable interfaces

• Driving design decisions and trade-offs across iterations

• Aligning multiple teams around a shared system and workflow

This was a 0→1 project, and I worked closely with cross-functional partners throughout the process to ensure the solution was both usable and scalable.

Solution Overview

Instead of extending existing spreadsheets, we designed a dedicated internal platform that brings feasibility evaluation and pricing into a single, structured workflow.

The system guides users through key inputs, surfaces feasibility signals early, and generates pricing outputs that are clear and consistent. By centralizing logic and removing manual steps, teams can move from request to decision with greater speed and confidence.

At its core, the platform replaces fragmented, person-dependent processes with a shared system that supports repeatable decision-making as the business scales.

1: Feasibility Input

Users define audience, geography, survey parameters, and options before generating feasibility results and pricing.Feasibility Input:

Overview

Before this project, there was no dedicated system for feasibility evaluation and pricing at Konovo.

Teams relied on:

• Excel spreadsheets to estimate feasibility and costs

• Salesforce to manually assemble client-facing quotes

While this approach worked at smaller scale, it became increasingly fragile as project volume and complexity grew.

I led the design of a new internal platform that unified feasibility assessment and pricing logic into a single, structured experience — creating a shared source of truth across Sales, Operations, and Finance.

Why This Was Needed

As the business grew, feasibility and pricing work became more frequent and more time-sensitive — but the process was still handled through spreadsheets and manual steps.

What used to work at a smaller scale started creating delays, rework, and risk. To support faster turnaround and more reliable decisions, the team needed a dedicated system.

The Problem

The spreadsheet-based workflow created several challenges:

• Important logic was spread across multiple files instead of living in one place

• Calculations were hard to review or explain

• Knowledge depended heavily on individual experience

• Small changes could lead to big differences in outcomes

As a result, feasibility and pricing decisions became inconsistent, time-consuming, and stressful under tight deadlines.

My Role

Product Designer · Project Lead

I led the end-to-end design of this platform, from early problem framing through launch.

My responsibilities included:

• Partnering closely with Product and Engineering to define scope and requirements

• Translating complex workflows and business logic into clear, usable interfaces

• Driving design decisions and trade-offs across iterations

• Aligning multiple teams around a shared system and workflow

This was a 0→1 project, and I worked closely with cross-functional partners throughout the process to ensure the solution was both usable and scalable.

Solution Overview

Instead of extending existing spreadsheets, we designed a dedicated internal platform that brings feasibility evaluation and pricing into a single, structured workflow.

The system guides users through key inputs, surfaces feasibility signals early, and generates pricing outputs that are clear and consistent. By centralizing logic and removing manual steps, teams can move from request to decision with greater speed and confidence.

At its core, the platform replaces fragmented, person-dependent processes with a shared system that supports repeatable decision-making as the business scales.

1: Feasibility Input

Users define audience, geography, survey parameters, and options before generating feasibility results and pricing.Feasibility Input:

Key Design Decision #1

Designing a Guided System Instead of a Flexible Spreadsheet

The challenge

Spreadsheets offered maximum flexibility, but they also made outcomes inconsistent and hard to trust. Different users could approach the same request in different ways, leading to varied results and uncertainty around feasibility and pricing.

At the same time, the system couldn’t be overly rigid — teams still needed room to handle edge cases and nuanced scenarios.

The decision

I designed a guided workflow that structures how inputs are collected and how decisions are made, while still allowing flexibility where it matters.

Rather than asking users to “figure it out,” the system leads them step by step, making key assumptions visible and reducing opportunities for error.

Why this mattered

This approach shifted the work from manual problem-solving to informed decision-making:

• Teams spent less time figuring out how to calculate

• More time understanding why a result made sense

• Outcomes became more consistent across users and teams

The platform didn’t remove human judgment — it supported it with clarity and structure.

Key Design Decision #2

Making Complex Outcomes Understandable — Not Just Accurate

The challenge

Feasibility and pricing results depend on many variables working together. While the system could generate accurate outputs, those numbers alone were not enough — users needed to understand why a result looked the way it did in order to trust it and explain it to others.

Without clarity, even correct results could feel risky or arbitrary.

The decision

I designed the experience to surface key drivers behind each outcome, rather than presenting a single final number.

Instead of treating feasibility and pricing as a black box, the system makes underlying assumptions visible and groups information in a way that helps users quickly see what is influencing the result.

Why this mattered

This approach helped users move from simply accepting outputs to actively understanding them:

• Users could quickly identify which inputs were driving feasibility or cost

• Conversations shifted from “Is this number right?” to “What would change it?”

• Teams felt more confident sharing and defending decisions across functions

By prioritizing explainability over compression, the platform supported better decision-making — not just faster calculations.

2A: Feasibility Results Table

Feasibility results are presented in a structured table, allowing teams to compare scenarios and identify potential risks before moving forward.

2B: Panel Details Popup(check icon click)

Clicking into a scenario reveals how feasibility is calculated across internal and partner panels, helping teams understand and trust the results.

Key Design Decision #3

Building a Scalable System From Day One

The challenge

This platform was built from scratch to replace a fragmented workflow that previously relied on spreadsheets, Salesforce exports, and manual quote adjustments. From the beginning, it was clear that feasibility and pricing needs would continue to evolve as the business grew.

Designing only for current use cases would quickly recreate the same fragmentation the team was trying to move away from.

The decision

I designed the platform around flexible structures and reusable patterns, rather than hard-coding logic for a single scenario.

Inputs, rules, and outputs were organized so that new audiences, countries, and pricing logic could be added without changing the core workflow or user experience.

Why this mattered

Starting with a scalable foundation allowed the platform to grow without constant redesign:

• New use cases could be supported without rebuilding the system

• Teams could adapt to change without relearning the workflow

• The product avoided drifting back toward spreadsheets and manual work

By treating scalability as a first-class requirement, the platform was able to support long-term growth instead of becoming a short-term solution.

3A: Pricing Input

After feasibility is confirmed, teams configure pricing inputs within the same system, defining deliverables and parameters that shape the final quote.

Impact & Outcome

The new platform replaced a fragmented, manual workflow with a single source of truth for feasibility and pricing.

Teams were able to move faster and work more consistently, with clearer visibility into how decisions were made and why. By centralizing logic and reducing manual steps, the platform lowered the risk of errors and rework at the earliest stage of the project lifecycle.

Most importantly, feasibility and pricing shifted from being person-dependent tasks to a shared, repeatable system — enabling teams to make confident decisions as volume and complexity increased.

4A: Pricing Report / Summary

The platform generates a structured pricing summary with clear cost breakdowns and margins, replacing manual spreadsheet-based quoting.

All numbers and values shown are illustrative.

What I Learned

Designing this platform reinforced that internal tools are ultimately decision-making systems, not just interfaces.

I learned the importance of structuring complexity so users can understand and trust outcomes, especially when decisions carry real business risk. Building from scratch also highlighted how early design choices around flexibility and scalability can prevent long-term fragmentation as a product grows.

Impact & Outcome

The new platform replaced a fragmented, manual workflow with a single source of truth for feasibility and pricing.

Teams were able to move faster and work more consistently, with clearer visibility into how decisions were made and why. By centralizing logic and reducing manual steps, the platform lowered the risk of errors and rework at the earliest stage of the project lifecycle.

Most importantly, feasibility and pricing shifted from being person-dependent tasks to a shared, repeatable system — enabling teams to make confident decisions as volume and complexity increased.

4A: Pricing Report / Summary

The platform generates a structured pricing summary with clear cost breakdowns and margins, replacing manual spreadsheet-based quoting.

All numbers and values shown are illustrative.

What I Learned

Designing this platform reinforced that internal tools are ultimately decision-making systems, not just interfaces.

I learned the importance of structuring complexity so users can understand and trust outcomes, especially when decisions carry real business risk. Building from scratch also highlighted how early design choices around flexibility and scalability can prevent long-term fragmentation as a product grows.

Other projects

Copyright 2026 by Jie Liu

Copyright 2026 by Jie Liu

Copyright 2026 by Jie Liu