The challenge

A strong product, hidden behind the slides

The materials had everything investors and customers needed. The design made none of it easy to see.

Features before a thesis

The deck opened on product modules, so the story never had a reason to exist.

Text where visuals belonged

Workflows and architecture were described in bullets instead of shown.

Inconsistent product proof

Screenshots from three tools, three eras of UI, and no shared style.

No visual system

Default fonts, placeholder logo, and colors chosen slide by slide.

Before: founder's cover slideBefore: problem slideBefore: solution slideBefore: product slide with screenshot placeholder

Tables, not charts

A usage export and dashboard screenshots, read aloud line by line.

Built for a laptop

Dense layouts that fell apart on a boardroom screen.

No visual hierarchy

Every metric looked equally important, so none stood out.

Nothing reusable

No view the customer could lift into their own board report.

Before: hours saved slideBefore: tasks by departmentBefore: user adoptionBefore: top workflows

Moodboard

A visual direction that feels technical and warm

Enterprise buyers need to trust the product; investors need to feel momentum. The direction had to carry both.

Workframe moodboard: TBJ Artnik, Zalando Sans and Roboto type, soft 3D ribbon imagery, brand colors, line icons, and glass UI elements

#4A46F7

Primary

#D9F24A

Highlight

#F08A63

Alert and accent

#FFC000

Data accent

Soft 3D ribbons for warmth

Iridescent forms bring energy to an otherwise technical product.

One weight of line icon

A single stroke style keeps dense slides calm and consistent.

Glass UI as the proof layer

Frosted product cards sit over imagery, so the product always reads first.

Spotlight 01 · The problem slide

Enterprise work is scattered across 90+ tools

The problem was easy to state and hard to feel. We designed it as one real workflow instead of a list of tools.

Hand sketch of the problem slide showing one request moving through 11 tools

Step 1

Sketch the path

Map one real workflow: a single vendor request moving through 11 systems.

Grayscale structure wireframe of the problem slide

Step 2

Lock the structure

The request enters top left, stats sit where the path breaks, and it ends at +78 more.

Final problem slide: Enterprise work is scattered across 90+ tools

Step 3

Design the final

Real logos, coral alert markers at every handoff, and each stat on the part of the path it describes.

Before and after

Drag the handle to compare the client's version with the final slide.

After: problem slide finalBefore: the client's problem slide
‹ ›

Before

After

Spotlight 02 · The solution slide

The Workframe Fabric, built layer by layer

Architecture slides usually end up as plumbing diagrams. We built this one in the order an investor needs to understand it.

Sketch of the solution slideStructure wireframe of the solution slideFinal solution slide: The Workframe Fabric

Sketch

1 of 6

Step 1 · Sketch

Start on paper

Systems at the bottom, the outcome on top, and every verb wired to one layer between them.

Step 2 · Structure

Set the grid before color

Spacing and hierarchy locked in grayscale, so the diagram reads top to bottom in one pass.

Step 3 · Systems

Anchor it in what customers own

Ten systems of record sit at the base as recognizable logos.

Step 4 · The layer

Draw the layer, not the plumbing

One blue band carries what Workframe understands, from people to policies, instead of an architecture diagram.

Step 5 · Actions

Show the verbs

Real actions, from Update CRM to Route approval, wired straight into the layer.

Step 6 · Outcomes

End where the eye lands first

Find, Decide and Execute sit on frosted cards over ribbon imagery at the top of the slide.

Before and after

After: solution slide finalBefore: the client's solution slide
‹ ›

Before

After

Solution

18 slides. 4 clear chapters.

Built around how a Series A investor evaluates a platform: why now, what it is, whether it works, and what the money buys.

Chapter 01 · The shift

Why finding answers is no longer enough

An editorial grid, hairline rules and one gradient word per title set a calm, confident tone.

Client's version

Before
After
Series A slide 2: Cover: editorial split with ribbon imagery

02Cover: editorial split with ribbon imagery

‹
›

Chapter 02 · The platform

One product, designed as one product

Screens from three different tools rebuilt as a single UI language on frosted cards.

Client's version

Before
After
Series A slide 6: Solution: the Workframe Fabric as a single layer

06Solution: the Workframe Fabric as a single layer

‹
›

Chapter 03 · The proof

Metrics turned into visual objects

Glass rings for market size, a staircase for growth, and product cards for pricing.

Client's version

Before
After
Series A slide 12: Use cases: a product card for every department

12Use cases: a product card for every department

‹
›

Chapter 04 · The path

A close built on weight, not density

A gradient ring for the ask, portraits for the team, and one line to the plan.

Client's version

Before
After
Series A slide 16: Competition: a logo map with a clear top right

16Competition: a logo map with a clear top right

‹
›

UI as proof points

Product UI that does the persuading

Instead of claiming what the product does, the slides show it. We designed each UI element to prove one claim. Select one to see where it lives in the deck.

Series A slide 8

Series A slide 8

Answer card

Answer card UI element

Answer card

Proves answers are cited and actionable, not generated from thin air.

Slide 8

Run trace UI element

Run trace

Proves every agent step is logged, timed, and auditable.

Slide 9

Permission panel UI element

Permission panel

Proves access always mirrors the source system.

Slide 11

Action list UI element

Action list

Proves agents act inside real systems, not just summarize.

Slide 11

Account card UI element

Account card

Proves sales teams see renewal risk before the call.

Slide 12

Ticket inbox UI element

Ticket inbox

Proves support tickets resolve without a human.

Slide 12

Per-run billing UI element

Per-run billing

Proves customers pay only when agents finish work.

Slide 15

Department adoption UI element

Department adoption

Proves the platform expands team by team.

Slide 15

Data visualization

A customer QBR designed for the boardroom screen

Eight views, each answering one question a CFO asks before renewing, readable from the back of the room.

Presented by Workframe customer success

To Acme's VP of Finance Operations

45 days before renewal

Boardroom with a large display at the front of the room
QBR coverQBR view 1: Hours returnedQBR view 2: Outcome splitQBR view 3: Task flowQBR view 4: Workload mixQBR view 5: AdoptionQBR view 6: Department scorecardQBR view 7: Top workflowsQBR view 8: Expansion path

Acme Co. Q2 business review

Q2 2026 Business Review

Cover. The dark cover opens the room with one idea: this is a review of results, not a product demo.

Before
After

00 / 08

Scroll to present

Where the slides went

Designed for the rooms they were shown in

A deck is judged where it's used, not where it's made. Each format was designed for its setting from the first draft.

Series A cover shown on a laptop

The partner meeting

The Series A, presented live and left behind in the data room.

QBR Sankey shown on a boardroom display

The boardroom screen

The QBR on a large display, readable from the back of the room.

Acme Co. Board of Directors

Page 7

QBR scorecard printed in the customer's board report

The customer's board pack

Two QBR views, lifted into Acme's own quarterly board report.

Result

Two decks. One visual system.

18

Series A slides across four chapters.

8

Data visualization views for the customer QBR.

8

Product UI elements designed as proof points.

1

Visual direction shared by both decks.

For AI companies

Raising, or defending a renewal?

We design the deck investors fund and the review customers renew on.