Orchard · Case study
SaaS CRM · Client reporting portal

Making paid media answer to revenue

Orchard is a portal a growth agency gives its B2B clients. It joins LinkedIn Ads and Google Ads with the client’s CRM, so a finance-minded buyer can follow a lead from the first ad click to a closed deal without asking anyone.

{{ m.k }}{{ m.v }}
app.orchard.co/overview
The problem

Clients saw clicks. They wanted to see deals.

Agency reports stop at the ad platform: impressions, clicks, cost per lead. The client’s CFO judges the agency on pipeline and revenue, which live in a different tool. Every month someone stitches the two together in a spreadsheet, and every month the same question comes back: is this spend actually working?

{{ p.n }}{{ p.t }}{{ p.d }}
Who it’s for

Two people, one set of numbers

{{ p.ini }}
{{ p.name }}{{ p.role }}

“{{ p.quote }}”

Needs{{ x }}
Key decisions

Six choices that shaped the product

{{ d.n }}

{{ d.title }}

{{ d.body }}

{{ t }}
{{ f.cap }}Try it →
System & accessibility

Built on Untitled UI, tuned for charts

Every colour, size and space is a named token with a Tailwind class, so a developer can build any screen without guessing. The one place I went beyond the kit was charts: nothing depends on colour alone.

View the design system
{{ a.t }}{{ a.d }}
Next

What I’d measure after launch

This is a concept, so there are no results to report yet. These are the signals I’d use to know it works.

{{ m.n }}
{{ m.t }}{{ m.d }}