Our work
Proof we ship.
We build our own products with the same hands and the same rules we use for clients. The first one is live.
Case study · 2026
Pagemoor
Save the post. Keep the note.
The problem
People save dozens of carousels a week and never open them again. The useful part, the text on the slides, is locked inside images on a platform that does not want it to leave. Every existing tool either scraped the platform, which breaks its terms and gets an app rejected, or asked people to type the notes themselves.
What we built
- A share-sheet-first progressive web app: share a post from any app and it is filed in seconds
- Carousel screenshots and screen recordings read on the device, one settled frame per slide
- One structured note per post: slide-by-slide text, takeaways, action items, links found, link back
- Grounding: any number or link not seen in the slides is dropped, never invented
- Export as Markdown or an AI pack; sync across devices when signed in; delete everything in one tap
- No scraping. The app only ever sees what the person shares with it
How it is made
- Client
- Vite, React, React Router, Tailwind, installable PWA with a custom service worker
- On device
- Tesseract.js OCR in a web worker, frame sampling for recordings, perceptual-hash dedupe
- Backend
- Supabase (Postgres, Auth, row-level security) and a small Hono API
- Notes
- Anthropic's Claude through a provider-agnostic layer, with Zod-validated structured output
- Delivery
- GitHub Actions, Cloudflare Pages, a managed server for the API, zero-cost launch
Real screenshots of the app, taken from its production build. The example slides are Pagemoor's own test cards, not anyone's post.
Next
More to come.
Client work is shown here only with the client's agreement, so this page grows slowly. If you would like to see something closer to your own project, write to us and we will walk you through it.