Kiley Daniel Meehan
My apps

Tools I design and build for the way design teams actually work.

Two working products, built on one shared design system, each with its own accent.

01 · Service blueprinting

Blupi

See the whole service on one board: what the customer goes through, and everything behind it.

Open Blupi
A Blupi blueprint called Self-Serve Trial to Day-One Value. Phases run across the top, steps in columns below, each with stacked cards describing what happens at that step.
A future-state blueprint, with cards drafted by Claude from captured screens.Walkthrough video soon

Blupi is a collaborative service blueprinting tool. Teams lay out a customer journey as phases and steps, then stack what happens at each step underneath it: the touchpoint, the people and process behind it, the friction, the policy, the technology. The part customers see and the part they don’t end up on the same board.

I built it because blueprints usually die in a slide deck. In Blupi they stay alive. Teams edit together with live cursors, keep a current-state and a future-state version of the same journey and compare them side by side, and capture real flows straight from the browser with a Chrome extension. Claude drafts a first pass of the board from the captured screens, so the team starts with something to argue with instead of a blank wall.

02 · Design inspiration

SwatchBook

A design inspiration library that files itself, and that Claude can search while I work.

The SwatchBook library: a grid of saved design screenshots, with folders, tags and flows in the sidebar.
The library, with folders, tags and flows in the sidebar.Walkthrough video soon

SwatchBook is where my design inspiration lives. A Chrome extension saves screenshots and images from any page into an inbox. Claude looks at each one, tags it (typography, colour, layout, and so on) and files it into the right folder. Screens can be strung together into flows, so a whole onboarding sequence stays together instead of living as twelve loose files.

It also runs an MCP server, so Claude can search the library while I’m designing: asking for pricing pages or empty states pulls straight from what I’ve collected. It sits on the same shared design system as Blupi, with its own coral accent.