Quotejump

Quotejump is a live Power Purchase Agreement quoting tool, the first of its kind on the energy market.

Domain

Self-serve energy quoting

Responsibilities

Product strategy
User research
Information architecture
UX + UI Design

Team

1x Product Manager
1x Engineering Manager
2x Frontend Developers
3x Backend Developers

Overview

Detangled from outdated processes

A transparent optimisation process

Power Purchase Agreements (PPAs) are contracts to buy and sell energy, between a buyer (here, Limejump) and a generator (here, our customers). They are traditionally quoted through a series of emails, phone calls, and manual entries. It took on average a total of 8.5 days for an energy asset owner to finalise their standard PPA contract with Limejump.

We identified an opportunity for asset owners to quote their own PPAs, using our forecasting and pricing engines remotely. The resulting product was a finalist for ‘Product of the Year’ at Computing Technology Product Awards 2022.

discovery

From business to user centric

The problem to solve was first communicated to the CX team by business stakeholders, as an initiative termed “self-acquisition”.

To formulate the customer-centric POV, I reached out to and interviewed 8 businesses that had signed up to a PPA. The key pain point amongst all renewable generators was around asynchronicity:

Customer contracting journey compared to the sales person’s, against the volatility of the energy market
Ideate

Lead by UX Considerations

Similar to design principles, UX considerations helped me keep a set of reasoning flows in mind when designing for specific circumstances.

From a given technical constraint, a basic user story comes up. Design needs to mend the two in order to provide a minimally viable solution.

The 4 leading UX Considerations, or reasoning flows backing the MVP build
UX Consideration #1

Tactful design

Tackling this first principle meant we had to advocate for a restructure of “mandatory fields” in internal interfaces. The devs and I had to find out how to undo some dependencies between the CRM and the internal quoting tool (both in human habits and in code).

For the MVP, we had to stick with the current system demands. Their rigidity needed to be tackled in a different product initiative. Shame we couldn’t cut our pre-quote form in half, but we compensated (for now) with a big bold access to our privacy policy.

Our (untactful) systems require a single all-encompassing data submission to produce a quote
Accentuated privacy policy to compensate, while we adapt system demands as a separate initiative
UX Consideration #2

Conversational design

There’s rhythm to a conversation. Start smooth, but don’t let small talk drag either. Tackle what’s at the forefront of the person’s mind, and fill in the holes where questions don't have easy answers.

After the meaty forks in the questioning path, we end on a medium tone with easy, yet sensitive info (per UX consideration #1 where we can do even better).

Evolution of user mood through product journey from our POC to our MVP, per usability testing
API calls to third parties and autofills keeping the UI concise
UX Consideration #3

Transparent yet readable design

All 11 lines of the quote breakdown are necessary to show, but hard to grasp. Tooltips and intuitive categories were regularly refined through user testing.

We A/B tested a few options on how to lay them out. I negotiated with the Head of Business Development to ensure Limejump’s profit would be communicated as a distinct item to counterparties.

Landing vs. Expanded quote, showing complex breakdown clarified through tooltips
UX Consideration #4

Shortfall design

Users outside of the MVP target scope will run into obstacles. Instant system feedback was implemented so that these shortfalls are resolved right away.

Post-MVP updates include an additional user flow, where their info can be saved and Limejump is the one to reach out to them - not the other way around.

System feedback is triggered as the user touches out of an element, suggesting a prompt resolution
reflection

Problems solved

Quotejump gets on average 12 new quote requests per month, 86% of which are successful on our backend stack. This saves our Business Development team about 2 months in the year that used to be collectively spent on:


Quotejump gets on average 12 new quote requests per month, 86% of which are successful on our backend stack. This saves our Business Development team about 2 months in the year that used to be collectively spent on:

  • Entering customer info in CRMs (with some typos)

  • Fetching MPAN and company data

  • Refreshing and discussing quotes

Iteration

Next steps

This MVP was focused on successfully automating disparate parts of our existing quoting toolkit. This meant that the user flow remained quite system-bound. For future versions, I have prioritised the following with our stakeholders:

  • Segmentation of the form into steps that can be saved and come back to later

  • Functionality for energy brokers to quote on behalf of asset owners

  • Enable PPA dates comparisons directly from the quote, without the need to re-submit the form

  • Ability to quote more than one energy site at a time

sarhowww@gmail.com

LinkedIn

Back to the top