galenry.Real constraints, measured outcomes
We are early, so this is a short list rather than a long one. Each entry states the constraint the client was under, what we shipped, and what changed, with figures we can stand behind.
The record
2 case studies · every figure sourced and dated
- Delivered
- 1
- Built, shipped and running
- Prototyped
- 1
- Screens agreed, build not started
Each one, read in full
The constraint and the outcome here; the build, the screens and the delivery facts on each page.
Told in the order we work
Diagnose, design, deliver: every case study follows it, so they can be compared side by side.
Diagnose
The constraint the client was under before we started, in their terms. It comes first because a result means little until you know what it was up against.
Design
What we built, listed in plain terms beside the screens it produced. Real screenshots from the product or the prototype, not illustrations.
Deliver
The facts of delivery and one headline figure, each with where it came from and when it was counted.
The rules every entry follows
A short list is only worth reading if each entry can be checked.
Every figure carries its source
The headline number on each case study is printed with where it was counted and when, so you can ask us to show it.
No result we cannot support
A business figure goes up only with its period and baseline. Where we do not have one yet, we publish something we can count instead.
Prototypes say so
Work that has not been built is labelled pre-development on every card and page, and carries no delivery facts, because there are none yet.
Real screens first
Screenshots come from the live product or the agreed prototype. The abstract mockup only appears where no screenshot exists.
A short list, honestly presented
We would rather show work we can talk about in detail than a wall of logos we cannot. Ask us about anything here and you will get the version with the difficult parts left in.
Ask about an engagementTell us what you’re trying to build
An idea, a stalled project, or a system that has outgrown its architecture. Send it over and we’ll tell you where we would start and whether we’re the right team for it.
- Response time
- Within one business day
- First call
- 30 minutes, no deck
Prefer to write first? Send the brief and we’ll come back with questions before we come back with a proposal.