Skip to main content
Payflow logo
Payflow

A finance workspace for answers you can check

I designed Payflow’s workspace so finance teams could inspect the evidence behind Luca’s answers before taking a recommendation to the board.

  • Finance
  • Accounting
  • AI Workspace
  • Design Engineering

Project overview

  • Overview

    Would you take Luca’s recommendation to the board?

    In a Payflow prototype report, Luca recommends shifting 8% to 10% of paid marketing spend into referrals. The CFO needs to know what the $27.42 acquisition figure counts before acting on it.
  • Role

    Product designer and design engineer

    I designed the workflow from choosing inputs to reviewing a report and built the responsive prototype through Plastive.

    Team: Payflow product and engineering

  • Problem

    The source has to travel with the answer

    Finance needs to check the source, period and calculation behind a figure. That work gets harder when the answer moves from a chat thread into a board packet.

  • Solution

    Keep the report open to review

    I kept the question and report together so an analyst could inspect a chart, see the files in scope and ask a more precise follow-up.

What each finance role needed to verify

Payflow’s April customer meetings exposed three jobs in that workflow. The team captured them in its May 2025 roadmap notes.
Customer needDesign response
FP&A wanted to try questions with known answers, such as vendor spend or invoice counts.Show which inputs Luca will use before the analyst sends the first question.
Finance operators wanted to explore a chart without creating a dashboard.Build the report alongside chat and let dense tables expand.
A CFO wanted executive highlights, detailed tables for finance and a path to the exact ledger entry.Put the recommendation first and make the route to the underlying data clear.
Payflow customer meetings, April 2025. Product roadmap draft, May 7, pp. 3–8.

A connected account and a file belong at different moments

I proposed a short setup flow. Product pointed out that accounting, HR and CRM use different connectors. A controller connects those systems once. An analyst might add the budget workbook weeks later.
Early wireframe with Budget and Actuals files attached to Luca’s composer

Budget versus actuals · Early wireframe

Show the two workbooks before send

In June, the team asked where search would fit after an @mention. I kept selected files visible in the composer so the analyst could correct the inputs before sending.

Payflow Connections shows each connector’s status, last sync and record count

Prototype · Connections

Confirm whether data has synced

Connection status belongs at the account level. The report still needs to identify the records it used.

Payflow Context page with upload area and a library of documents

Prototype · Context

Add the file when the work calls for it

A finance operator can keep a budget or policy file available and choose it for the relevant analysis.

The report needs to survive the next question

A thread works for the first answer. The variance review needs a stable place for charts, tables and source files while the analyst asks about a specific line.
Variance report wireframe with chat on the left and charts, analysis and source workbooks on the right

Budget versus actuals · Report canvas

Keep the question and the report visible

The split keeps follow-ups anchored to the figure. Expanding the report frees room for wide tables but moves the thread out of sight.

Nine wireframes from first question to report review

Start with a known finance question

Suggested prompts help the analyst try a question they can check.
Early design studies. Open any screen to inspect the original notes.

Can history open without interrupting the review?

The three-pane sketch exposed a width tradeoff. In December I explored where history could fit once a report stayed open.
December option A replaces the chat pane with search and dated history beside the report

December design exploration

A. Put history in the chat pane

The report stays visible for comparison. Narrow previews truncate and the composer yields its space.

December option B places a searchable history dialog over the current report and chat

December design exploration

B. Open history in a dialog

Wider previews help distinguish similar questions. The dialog covers the report while the analyst searches.

For active review I’d start with the pane and test whether analysts can find a prior answer without losing track of the current figure. Search already existed. These studies explored where it should live.

A trend and a comparison answer different questions

Three banks’ balances on a shared time axis with period controls

July study · Bank balance trend

When did cash move?

Treasury can spot accounts moving at the same time. The selected interval and exact balances need to be accessible.

Grouped monthly bars for revenue and cost of goods sold with a common dollar scale

July study · Revenue and cost comparison

Where did revenue and costs diverge?

FP&A can compare the two amounts in the same month. A table supports reconciliation and a point note can explain a material change.

Payflow desktop dashboard with revenue, margin, cash and expense widgets

Prototype · Dashboard

Let the reader follow up from the figure

The dashboard gives executives a quick read. Questions attached to a chart let finance investigate without restating which metric they mean.

The reported figure is cost per signup

The sample CSV supports the cost-per-signup calculation. To justify the budget shift, finance would need paying-customer counts and evidence that added referral spend brings in incremental customers.
Payflow Inbox showing Luca’s acquisition recommendation and $27.42 labeled Paid CAC

Prototype · Acquisition report

The prototype exposes the channel data

The reviewer must infer the denominator from the channel breakdown or CSV. The corrected label and review note below make that judgment visible.

Paid search cost per signup

May 2026 · Prototype sample data

$27.42Down 31% from May 5
May 5, $39.74May 12, $34.60May 19, $30.45May 26, $27.42

Proposed review note

Hold the budget shift

$10,200 ÷ 372 signups = $27.42

The file ends at signup. Ask for paying-customer counts and evidence that added referral spend brings in incremental customers.

Download sample CSV

The December audit showed comments attached to a whole chart. I’d pin a note that disputes one figure to its metric, period and report revision, so the reviewer can tell when refreshed data needs a second look.

Open the acquisition report in Payflow

Return to the work after the meeting

I kept named analyses and recurring reports visible. The team discussed folders and favorites and wanted to learn how people actually organized their work before investing in them.

Start a new question

An analyst can begin with vendor spend, the Q4 board update or revenue by segment.
Responsive prototype captures. The desktop gallery shows one screen at a time.

On a phone, review one task at a time

I gave the question, report and source check separate screens on mobile. The phone supports a quick check. Comparing two workbooks still needs the desktop canvas.
Payflow phone home with the Luca composer
Ask a new question
Payflow phone workspace list
Return to a workspace
Payflow phone dashboard with stacked KPI cards
Scan the metrics
Payflow phone inbox with the acquisition insight
Open the relevant insight
Payflow phone document library and upload control
Add a source document
Payflow phone integration status and sync times
Check the last sync

One chart renderer across three product views

Payflow’s engineering team selectively reused the chart work from the December UX branch.
Chart families integrated into main
9
Product views using the renderer
3
Workspace scenarios on the UX branch
8
December 2025What changed
18 · UX branchStorybook covered workspace states including narrow and wide chat.
19 · Client mainThe shared chart renderer entered dashboard tiles, expanded charts and Luca Insights.
22 · Starter promptsThe team updated prompt examples to match the supported charts. Regional sales switched from radar to bar.
Client frontend history. Customer adoption and time saved remain unmeasured.

What I’d test next. Give analyst and CFO pairs matched packets with a faulty denominator in one. Measure correct accept or hold decisions, time to a verified answer, and whether the reviewer can cite the source.

The interaction patterns behind the prototype

These specimens recreate the prototype’s chart, composer and source controls. An assumed input, a connected system and a reporting period each need their own label.

Shipped with

  • Product design and design engineering

    Workspace structure, interactions, chart studies and responsive prototype

  • Product and engineering

    Customer discovery, technical constraints and integration into the client frontend

  • Finance operators

    Workflow context and product feedback

Notes

3 references
  1. Note
    Payflow product roadmap draft, May 7, 2025, pp. 3–8. April demos and customer meetings.
  2. Note
    Payflow design archive. Budget-versus-actuals wireframes, July chart studies and December 9 chat-history mockups.
  3. Note
    Payflow client frontend. December 18 UX branch, December 19 chart integration (#1174), and December 22 prompt updates (#1201).

More work