CONTENTS
0%

"Where are our leads?"

I led the design of Ignition’s answer, a sales pipeline that gave customers visibility and spurred action. The result? A 52% increase in accepted proposals.

About

Ignition is?

A SaaS platform serving accounting and professional services firms.

What's Ignition do?

They help accountants and service firms spend less time chasing admin and more time running their business by automating everything such as proposals, billing, payments, and workflows to improve efficiency and profitability.

What did I focus on?

The proposal editor ecosystem—improving visibility, adoption, and the transition between the new and classic editors.


PRODUCT

ROLE

Lead product designer

MY Contribution

Product design

User research and testing

Stakeholder management

User experience design

Prototyping

Interface and interactions

TIME

12 wks | 2021

TEAM

Belle - PM

Gareth - TL

Walid - BE

David - BE

Moe - FE

Toby

Problem

We’d split the product and user base in two—supporting both a legacy and new proposal editor until the newer one reached feature parity and adoption. This created friction on both sides. Users loyal to the old editor were hesitant to switch, while early adopters were hitting gaps and raising support tickets. The challenge became clear: how might we motivate the hesitant to switch, fix frustrations for those who already had, and ideally solve both with one coherent solution within the project’s scope?

Why it mattered

The coexistence of two editors increased operational complexity, created user confusion, and flooded support with tickets. Visibility gaps made tracking proposals difficult, eroding user trust and adoption.

What we identified

Two major opportunities emerged: Billing Management and Proposal Visibility, we prioritised Proposal Visibility for its user impact and simply because proposals come before billing, (and we didn't have the appetite from the business to tackle both).

sentiment_very_dissatisfied

the new proposal editor proposals do not show in this list???

sentiment_very_dissatisfied

You cannot drill into any of the dashboard revenue or payments reports so it’s hard to be able to make client decisions from this limited view.

sentiment_very_dissatisfied

This feels like unnecessary extra steps to see basic reporting information.

sentiment_very_dissatisfied

NPE - Drafting proposals NO longer appear under DRAFT - which is unacceptable. The placeholders are almost all gone from the Terms section which is also a big downgrade.

sentiment_very_dissatisfied

“We can only export accepted services in the services report. The proposal export doesn’t give a list of services.”

sentiment_very_dissatisfied

“Feels like Ignition did a hard pivot… feels a bit like living on a building site.”

sentiment_very_dissatisfied

After 4–5 proposals we switched back… too difficult to get an overview of proposals.

sentiment_very_dissatisfied

"In general, it is not easy to sort proposals by who’s a new client, what’s outstanding, etc."

sentiment_very_dissatisfied

"I want to filter which proposals I see in the dashboard and have them organised better."

sentiment_very_dissatisfied

“It’s not easy to pull data for this firm, and with hundreds of employees, their biggest needs are seeing proposals sent most recently.”

sentiment_very_dissatisfied

want to filter which proposals I see in this section of the dashboard (see e.g. Awaiting, 100 Accepted or Archived).

sentiment_very_dissatisfied

Two steps forward... one step back.

sentiment_neutral

Love it but… not being able to see a list of proposals issued is a nightmare…

sentiment_very_dissatisfied

Please keep a list view of proposals so we can see what proposals were sent out and filter them.

sentiment_very_dissatisfied

"We need NPE reporting in-app. We can't operate a business blind."

Goals

Through feedback analysis, support tickets, 20 user interviews, and analytics we defined three measurable goals for our solution to address.

Visibility

Enhance NPE visibility to address usability challenges and drive higher customer satisfaction.

1

Support relief

Alleviate support team workloads by addressing recurring pain points and reducing customer reliance on workarounds.

2

Adoption friction

By achieving goals 1 and 2, we aim to make the NPE not just worthy of adoption, but truly irresistible.

3

Visibility

Enhance NPE visibility to address usability challenges and drive higher customer satisfaction.

1

Support relief

Alleviate support team workloads by addressing recurring pain points and reducing customer reliance on workarounds.

2

Adoption friction

By achieving goals 1 and 2, we aim to make the NPE not just worthy of adoption, but truly irresistible.

3

Solution

Ignitions Pipeline

A unified view of all proposals across clients and editors reduced task times by up to 75% and boosted user satisfaction.

Segments tailored

Quick Filters streamline workflows by embedding best practices, going beyond simple status segmentation. User testing showed expiring engagements were often missed, so we introduced a filter to surface them instantly, ensuring critical tasks aren’t overlooked.

Precision filtering

‘More Filters’ adds precision, enabling users to tailor their experience with attributes aligned to their workflows. Dynamic options simplify common tasks while providing full control when needed.

Classic + New editor

Combining the datasets into a unified view proved unfeasible within the project’s timeframe and performance constraints, especially for a limited user subset. As a compromise, we organized the data into two tabs, enabling quick switching—an effective solution given the limitations.

Bulk actions

Post-release, bulk actioning of proposals became a top request. Fortunately, initial concepts created during shaping allowed us to deliver this feature soon after. Takeaway: While bulk actions were fast, managing errors, progress indicators, and state was complex. Shoutout to Dale (front-end) for simplifying it with a delightful surprise—progress indicators that persisted even after closing and reopening the tab. <3 @Dale!

Post-release, bulk actioning of proposals became a top request. Fortunately, initial concepts created during shaping allowed us to deliver this feature soon after. Takeaway: While bulk actions were fast, managing errors, progress indicators, and state was complex. Shoutout to Dale (front-end) for simplifying it with a delightful surprise—progress indicators that persisted even after closing and reopening the tab. <3 @Dale!

Making visibility more visible!

Initially the segmented views shared data, but not all information was relevant to each segment causing gaps, the redesign fixed this by ensuring each view only had data that was useful and relevant.

Status badges were removed where unnecessary (e.g., drafts only contains drafts) reducing visual density.

Contextual actions to each proposal aiding users with only relevant possible next steps and enabling this without opening the proposal.

Quick Filters were also re-designed with order and grouping to reflect real world sequencing.

Key results

User Engagement

Within the first year, daily engagement among active users reached 47%, surpassing our 25% target.

Operational Efficiency

Support requests related to NPE/Proposal visibility dropped from 30% to 5%, enabling KAMs to focus on higher-impact work.

Accepted proposals

Streamlined tools and full proposal visibility drove a 53% increase in accepted proposals, from 650,000 to 1 million in a year, those additional proposals were valued at $1.3 billion to our users.

In depth process can be found below in 3 stagees Discovery, Shaping and Delivery + Release combined.

Note: It's quite the read and can take around 25-30 minutes.