Reqst
A simpler way to collect, manage and complete requests.
Role:
Founder & Product Designer
Tools:
Figma, Cursor, Supabase, Vercel, Framer
Category:
Product Design, UX, Research, Design Engineering
Overview
Turning scattered requests into one simple workflow.
Requests often arrive through email, messages and different tools, leaving the person doing the work to organise everything. I designed and built Reqst to explore a simpler way to collect, manage and complete requests from one place.
Problem
The work wasn’t the only problem. Managing the request was.
A request might start in an email, WhatsApp message, Slack conversation or meeting. Details become scattered, priorities are unclear and requesters have little visibility once work begins. Existing project management tools can solve parts of this, but often introduce more complexity than a simple request needs.
Approach
Start with the request, not the project.
Rather than building another project management tool, I focused on the smallest useful interaction between the person requesting work and the person completing it. I reduced the experience to a simple loop: create a list, share it, receive a request, complete the work and keep the requester updated.
Solution
One link from request to completion.
Providers create reusable lists containing the work they offer and share them through a single link. Requesters select what they need, prioritise items and submit without creating an account. Each request then becomes a trackable workflow for both sides through to completion.
I started by sketching the requester journey at low fidelity, focusing on the simplest possible flow from selecting what was needed through to confirmation. Keeping this stage rough made it easier to test the structure before getting distracted by visual detail.
I then expanded the experience into a more complete product system, designing the provider dashboard, submissions, contacts and analytics alongside the public request flow. This helped define how both sides of the product connected and where each piece of information belonged.
The chosen direction refined the strongest parts of those explorations into a cleaner, more consistent interface. I focused on clearer hierarchy, reusable patterns and keeping the requester experience lightweight while giving providers enough structure to manage requests from start to finish.
Key Decisions
Small decisions. A simpler experience.
1
Remove the account barrier
Creating an account before making a request added unnecessary friction. I kept the requester experience account-free, allowing someone to open a shared link and submit what they need immediately.
2
Make the link reusable
Creating and sharing a new form every time would simply move the admin elsewhere. Each list therefore has one reusable link that can collect multiple requests while keeping every submission separate for the provider.
3
Make progress visible
Submitting a request shouldn’t create another reason to send follow-up messages. Requesters can track what is active and complete, while notifications provide updates as work progresses.
Outcome
From concept to a live product with real users.
I took Reqst from an initial idea through product definition, UX, interface design and development to a live product. It is now being used by its first users, giving me real-world feedback and behaviours to learn from. Moving beyond Figma has helped uncover usability issues, edge cases and product decisions that only became apparent once the experience was being used.
Results
3
Ready users onboarded
8
Different use-case categories
64
SEO templates published
6
Acquisition channels tested
And Beyond
Shipping the product was only the beginning.
Launching Reqst also meant thinking about how people would discover and understand the product. I built the marketing site, implemented SEO and AEO, set up Google Search Console and Analytics, and began testing acquisition through short-form content and building in public.
