Case Study - Pixsprint: Building living media kits for creators
Pixsprint starts with the irritating fact that a media kit can be polished when it is sent and stale by the time it is opened. It gives creators and creative teams one shareable workspace for selected work, fresh audience context, public or private brand links, and the signals that show what happens next. Instead of a static attachment, the kit becomes a living link built for an actual brand conversation.
I built Pixsprint to replace the stale PDF-and-spreadsheet routine of sending tailored media kits with a living workspace that keeps creator proof current and shows what happens after a brand opens the link.
- Client
- Pixsprint
- Year
- July 2026 – Present
- Service
- End-to-end product build
Overview
I’m a photographer before I’m a product person. I travel with a full-frame Sony A7R V and three heavy lenses—because apparently one camera and one lens would be too sensible. After travelling across every continent, I kept running into the same problem: sending a tailored media kit meant rebuilding the same work, audience data, and links while all of them were already changing.
Pixsprint is the product I wanted on the road: a living workspace that keeps a creator’s work and audience context together, helps build the right kit for a brand, supports public or private sharing, and shows what happens after the link is opened. I built the MVP to make collaboration easier and the admin a lot less heroic.
What I did
I took Pixsprint from the product idea and UX through the full-stack application, landing site, sharing flows, analytics, and cloud deployment.
I’m a photographer, so the pain was personal: I still had to wrestle a stale media kit into shape whenever I wanted to collaborate. Pixsprint automates the repetitive part—building tailored kits from current data and showing whether people actually viewed them—so the next step can be a conversation, not another spreadsheet.
- React
- React Router
- Next.js
- TypeScript
- Tailwind CSS
- Node.js
- Express
- MongoDB
- Prisma
- Clerk
- Google Cloud Storage
- Google Cloud Tasks
- Cloud Run
- Stripe
- OpenAI
- Resend
- Sanity
- Framer Motion
- Puppeteer
- Sharp
- Docker
Project snapshot
- Role and ownership
- Founder and product engineer; took Pixsprint from product idea to deployed MVP.
- Product surface
- A living media-kit workflow for creators: curate work and audience context, build tailored kits, share public or private links, and see what happens after a brand opens them.
The problem
A creator’s proof does not stay still. Selected work changes, audience context moves, campaign examples spread across tools, and a static media kit gives little indication of what happened after a brand opened it.
The current public Pixsprint product brings the kit, the share, and the follow-up into one workflow. The product challenge is to make that progression understandable rather than present a collection of unrelated features.
Implementation - Implementation and product highlights
- Product ownership across the workflow. I took Pixsprint from product idea and UX through the full-stack application, sharing flows, analytics, and cloud deployment.
- Curated proof in one workspace. The public workflow brings together photos, videos, campaign examples, services, audience context, and proof points for a brand conversation.
- Controlled sharing and follow-up. The public product presents public kits, private brand-specific links, and custom domains alongside signals such as views, clicks, messages, and download requests.
