Finance Portal - Builder

Finance

2024–2026

Product Designer

I redesigned a month-end invoicing workflow that Finance had built workarounds around for years, reducing load time from ~60 seconds to <1 second and invoice creation from ~2 minutes to ~20 seconds.

Mobile views presenting a chat and a map view

Finance Portal - Builder

Finance

2024–2026

Product Designer

I redesigned a month-end invoicing workflow that Finance had built workarounds around for years, reducing load time from ~60 seconds to <1 second and invoice creation from ~2 minutes to ~20 seconds.

Mobile views presenting a chat and a map view
Mobile views presenting a chat and a map view

Finance Portal - Builder

I redesigned a month-end invoicing workflow that Finance had built workarounds around for years, reducing load time from ~60 seconds to <1 second and invoice creation from ~2 minutes to ~20 seconds.

Finance

2024–2026

Product Designer

Mobile views presenting a chat and a map view
Mobile views presenting a chat and a map view

Project summary

Challenge

The existing Builder was slow and fragmented, forcing Finance users to rely on multiple tabs, personal notes and repeated navigation to complete month-end billing.

My role

Product Designer working closely with Finance, Product and Engineering across workflow definition, interaction design, prototyping, technical trade-offs and implementation.

Solution

I restructured the experience around how Finance actually makes billing decisions, bringing actionable work, client context, invoice creation and final review into one connected workflow.

60×

Faster page load

15x

Faster to find a project

~83%

Faster invoice creation

Reframing the problem

Redesign the workflow, not just the Builder

Finance users weren’t struggling because information was missing. The workflow itself was fragmented, forcing them to rely on multiple tabs, personal notes and repeated navigation.

Creating an invoice and reviewing the final output also required different information and different focus.

Decision

Instead of redesigning the existing Builder screen by screen, I restructured the experience around the full billing journey and split it into two stages: Build — find work, understand context and create the draft. Review & Send — verify the final invoice, edit and deliver it. This created a clearer end-to-end structure and gave each stage one primary user goal, forming the foundation for the rest of the redesign.

Outcome

The redesign replaced a fragmented, multi-tab workflow with a connected billing journey. Users could move from identifying billable work to creating, reviewing and sending invoices without losing context.

Separating Build from Review & Send also meant each stage could prioritise the information and actions users needed, reducing unnecessary navigation and making the overall process easier to follow.

Search
Invoice Notes
Projects
Draft Invoice
PDF Preview
Edit Invoice
Send Email

Build

Find work → understand context → create invoice

Users start with Search to find the right client activity, then review invoiceable work and build the invoice.

Finding work

Show less upfront, get users to the right project faster

Finance users usually know which client they need to work on. Loading every entity and its invoiceable projects upfront added unnecessary information and slowed down the path to the work they actually needed.

Decision

I kept projects hidden until a user selects an entity, rather than surfacing all invoiceable work upfront. I also made Search active by default and surfaced recent searches immediately, so returning users could start searching — or jump back into a familiar client — without an extra click.

Outcome

Users can get from opening Search to the relevant project 15× faster.

Keeping context close

Bring billing knowledge into the product

Some of the most important client-specific billing knowledge lived outside the product.

Experienced Finance users knew how particular clients expected to be billed, what wording was required and what exceptions to look out for.

Much of this existed in personal notes or people’s memory.

Decision

I brought Invoice Notes directly into Builder and kept them accessible throughout the billing workflow. The notes persist at client level, show when they were last edited and stay attached to the entity as users move between tasks. This turned informal, individual knowledge into shared product context available at the point of decision.

Outcome

Billing knowledge became shared rather than person-dependent. Finance users could cover colleagues’ clients when they were away and get to invoice creation faster without reconstructing client-specific context.

Prioritising information

Show what changes the billing decision

Around 90% of clients are billed monthly, so at month-end Finance mainly needs to see what could block invoice creation, such as, warnings, missing case codes and project totals.

Decision

I prioritised these blockers and key amounts above the fold, while using Finance users’ typically wide monitors to surface additional context without compromising the information that always needs to stay visible. I also introduced keyboard shortcuts for bulk actions so users could keep their hands on the keyboard instead of repeatedly moving between selection and actions.

Outcome

Invoice creation became 83% faster, dropping from around 1 minute to 10 seconds per invoice. Keyboard shortcuts also reduced bulk creation from 2 clicks to 0 mouse clicks, while keeping key blockers visible before users build.

Adding projects into an invoice

Shift the focus from projects to the invoice

Once projects are selected, Finance shifts from deciding what to bill to checking whether the invoice has been assembled correctly. In the old flow, mistakes often meant deleting the invoice and starting again.

Decision

I kept invoiceable work and the Draft Invoice side by side, so users can immediately see what has moved and what remains. Projects can be moved or regrouped directly instead of rebuilding the invoice from scratch. Once a draft is created, it receives a unique, non-reusable invoice number for a clear audit trail. I also show only the first 3 projects by default, as project-level detail becomes less important once the invoice has been assembled.

Outcome

Users can correct grouping mistakes without deleting and recreating the invoice, reducing unnecessary rework and contributing to a lower invoice deletion rate.

2. Review and send

Review and send

Once the invoice is built, the focus shifts to checking the final document, making any last changes, and sending it.

Reviewing the invoice

Keep every draft in one review workspace

Finance often needs to review several draft invoices for the same client. Opening each one in a separate tab made comparison slower and important warnings easier to miss.

Decision

I introduced an invoice carousel so users can move between drafts without leaving the review workspace. The PDF stays live as changes are made, while relevant warnings remain visible throughout review.

Outcome

Users can review multiple drafts in 1 workspace instead of multiple tabs, with 0 extra preview step and billing warnings kept in view while navigating between invoices.

Sending the invoice

Working around legacy constraints

Recipient data came from the legacy system, so redesigning To, CC and BCC from scratch would have required disproportionate backend work. Finance also regularly needed to move existing recipients between fields before sending.

Decision

I worked with Engineering through several iterations to improve the interaction within legacy constraints. The final design lets users move existing recipients between To, CC and BCC without re-entering them, while keeping templates, Invoice notes and the PDF close to the send flow.

Outcome

Users can prepare and verify the email in 1 workspace when moving an existing recipient between fields.

Impact

Reduce the work around the workflow

The biggest inefficiency wasn’t one screen, it was all the extra work Finance had learned to do around the product, from waiting and switching tabs to rechecking context and rebuilding invoices.

Decision

Across the redesign, I focused on removing those workarounds rather than optimising isolated interactions: faster loading, clearer hierarchy, fewer context switches and a more continuous end-to-end flow.

Outcome

60× faster page load, 15× faster to find a project, 6× faster invoice creation, and month-end close reduced from 7–8 days to 4–5 days.

Reflection

Designing beyond Builder

Builder was one part of the wider Finance Portal, alongside Review, Tracker, Charge Management and other finance workflows. A decision in Builder could change what Finance saw later in Review or Tracker, so I had to think about handoffs and how billing information moved through the whole process, not only the screen in front of me.

The speed gains mattered. Month-end close went from 7–8 days to 4–5. But the change I think about most is where billing knowledge lives. Client billing rules used to sit in people’s heads and personal notes. Bringing invoice notes into Builder was the start of moving them into the product, and the Finance Portal now also logs billing cadence and invoice settings as structured data.

That opened a new question. If the product knows how each client is billed, how much of month-end does Finance still need to do by hand? I explored that in a concept for the Finance Portal in 2027, where agents prepare the routine work and Finance stays in charge of the decisions.

See the Finance Portal 2027 concept —>