INTERNAL TOOLS / PRODUCT THINKING / DEVELOPMENT

Designing a more useful interface for QuoteWerks

An internal front-end project intended to reduce friction in everyday quoting work.

CASE 05 / LEO ANDRADEIn development

THE WORK AT A GLANCE

I have been entrusted with building a custom front end for QuoteWerks to make an internal workflow easier to use. It is a practical build project and remains in progress.

01 / THE CONTEXT

Why this
mattered.

Quoting involves customer context, products, service details, pricing, and the steps different people need to take to get a reliable proposal out the door. Software that technically works can still create friction when the workflow is difficult to follow.

A useful interface should be based on how people actually work—not just on what buttons an application exposes.

02 / MY ROLE

Where I
contributed.

I am taking ownership of the custom interface project, learning unfamiliar technical details as needed, and working toward a system that makes the team's quoting work more approachable.

The goal is practical usefulness. I am not presenting this as a deployed commercial product or claiming time savings that have not been measured.

03 / THE WORK

What that
involved.

  • 01Understand current quoting tasks and recurring sources of friction
  • 02Translate those tasks into an interface and workflow model
  • 03Build the front end and work through implementation details
  • 04Validate the result against real internal use before claiming impact
04 / THE EVIDENCE

What I can
stand behind.

  • The project is active and has been entrusted to me.
  • No completion date, public codebase, or performance metrics are asserted.
  • Screenshots and implementation details remain unpublished pending organizational approval.

Ongoing internal project. Product branding is used to identify the existing quoting platform, not to imply affiliation or endorsement.

05 / WHAT I LEARNED

I like this kind of work because it connects technical learning, user experience, and business process. A better system isn't defined by how sophisticated it looks; it's defined by whether the people using it can get their work done.
← All selected workAbout my approach ↗

CONTINUE EXPLORING

Another piece of
the bigger picture.

Connecting what customers need to what a team can deliver — Creating the materials, questions, and commercial context that support technical service decisions.

Read the next case