Public request links
Clients complete files, links, notes, approvals, and changes from one polished page.
Overview
Role
Founder · Product Strategy · UX · Brand Direction
Platform
Web SaaS for client-facing teams
Status
Live product direction · launch preparation
Deliverables
UX flows, UI system, pricing, positioning, Notion workflow
Tools & systems
Product strategy, HTML prototypes, Notion workflow mapping, Supabase-ready product logic
One clean place to ask, receive, review, and approve.
Chasepad turns the most invisible part of client work — waiting for assets, comments, approvals, replacements, and final sign-off — into a structured request workflow.
The product is designed for teams who do not need another bloated agency operating system. They need a focused way to make client requests clearer, track what is still missing, and move work forward with less chasing.
Founder Insight
Most project delays do not start with the work. They start with the wait.
Across client-facing work, the actual task is often ready to move, but the project stalls because someone is still waiting for a file, a link, a comment, a replacement, or a final yes.
The product idea was simple: make the request feel as polished as the work itself. One link. One clear checklist. One calmer way to collect, review, remind, and sign off.
Product Highlights
A focused system for the part of client work everyone feels, but rarely designs.
The interface needed to prove that Chasepad is not just a request form. It is a focused workflow system around asking, receiving, reviewing, and closing the loop.
Approval states
Waiting, overdue, ready-to-review, approved, and changes-requested states make progress visible.
Notion visibility
A connected status layer helps Notion-based teams track requests where they already work.
Reminder flow
Lightweight follow-up support reduces awkward manual chasing when something is missing.
Challenge & Solution
The opportunity was not more software. It was less chasing.
The design direction had to keep Chasepad narrow enough to be instantly understood, but strong enough to feel commercially useful for agencies and client-facing teams.
The challenge
- Client inputs live across email, folders, WhatsApp, Notion notes, and random message threads.
- Teams lose time checking what is missing, who replied, what needs review, and whether sign-off is final.
- Clients need clarity, but they rarely want another complex workspace or login-heavy tool.
The solution
- One clean public request link for every client-facing ask.
- Practical status states that show what is waiting, overdue, ready to review, or approved.
- A Notion-connected layer for teams who want visibility without rebuilding their internal system.
Workflow System
A simple request loop designed around momentum.
For Chasepad, the real design system is the workflow logic: every screen supports the same product loop — ask clearly, collect cleanly, review quickly, and close the decision.
Request
The team creates a clear page with the exact files, links, copy, approvals, or notes needed.
Submit
The client completes everything from one polished link, with no new workspace to learn.
Review
The team sees what arrived, what is missing, and what is ready for review.
Approve
Work is approved, sent back for changes, or kept waiting with a clear next action.
Sign off
The request closes with a cleaner record of what was received, reviewed, and agreed.
Product Decisions
The choices that kept the product focused.
Every major decision was designed to protect Chasepad from becoming bloated. The strongest product wedge is the moment where work is waiting on a client response.
Focused before feature-heavy.
The product direction avoids trying to replace every tool agencies use. Instead, Chasepad gives teams one clear layer for the part that repeatedly causes friction: client requests, feedback, approvals, reminders, and sign-off.
Client simplicity
The client side stays lightweight: one link, plain instructions, and a clear route to submit what is needed.
Team visibility
The team side focuses on urgency: what is waiting, overdue, ready to review, approved, or blocked.
Notion as a bridge
The Notion layer supports teams that already plan in Notion, without making Notion a requirement for clients.
Plan clarity
Pro and Agency share the same core experience while Agency expands for teams, workspaces, and higher-volume operations.
Final Screens
Key moments in the Chasepad experience.
These interface moments tell the product journey: a team creates a request, a client completes it from one link, and the team reviews progress without digging through scattered channels.
Dashboard overview
A clear view of what is waiting, overdue, and ready to approve, so teams can act without hunting through threads.
Client request page
A polished public page where clients complete files, links, notes, approvals, and changes without needing another workspace.
Approvals and changes
A focused review flow that separates approved work, requested changes, and outstanding decisions.
Notion-connected status
A live request widget that gives Notion-based teams visibility without rebuilding their workflow.
Launch Direction
Built around a specific, expensive bottleneck.
Chasepad is strongest because the problem is easy to recognise and hard to ignore. Client-facing teams already feel the cost of stalled projects, scattered approvals, and awkward reminders; the product gives that bottleneck a clearer name, a calmer workflow, and a sharper commercial promise.
Product category
Client workflow SaaS
Primary audience
Agencies, studios, consultants, client-facing teams
Commercial direction
Pro and Agency subscription tiers
Distribution angle
Notion users, agency teams, founder-led launch channels
Key Takeaways
What this project clarified.
Chasepad reinforced that good product design is often about choosing a painful, repeated moment and making it feel calm enough to trust.
Design the waiting state
Delays are not just operational. They are an experience. Chasepad gives waiting a status, a place, and a next action.
Clients need simplicity
The client-facing side must feel lighter than the team-facing side. The public link is the product promise.
Focused beats bloated
A narrow workflow can feel more valuable than a large platform when the pain is specific and frequent.