For UX/UI designers
'Redesign the app' isn't a scope. Flows, fidelity and handoff are.
UX work is sold to people who often can't picture the deliverable. A founder or product manager asks for a redesign, you scope discovery, research, flows, wireframes, high-fidelity screens and a prototype, and they hear 'Figma files'. When the research recommends cutting a feature, or engineering asks for every edge-case state, the fight is about what was promised.
ApeiroCraft sends the proposal as a link with research activities, the flows in scope, prototype fidelity, design-system work and what handoff includes. You see when it's opened and reopened — handy when a product manager is selling it internally — it's signed in the browser, and each milestone is invoiced from the accepted proposal.
Where UX projects grow without the fee.
Screens multiply
Ten screens become forty once empty states, errors, loading, mobile breakpoints and admin views appear. If the proposal counted screens, every state is a debate.
Research gets cut, then blamed
The client trims research to save time, then questions the design decisions research would have settled. Without the trade-off written down, you carry both.
Handoff without an end
Developers keep asking questions for months after delivery. 'Support during build' was never defined, so it's either free or awkward.
From discovery call to dev handoff.
Scope by flow and fidelity
List the user flows in scope — onboarding, checkout, settings — and the fidelity for each: wireframe, high-fidelity, interactive prototype. Clearer than a screen count, and harder to dispute.
Know when it's being sold internally
Opens and re-opens are recorded on the link. A burst of opens before a roadmap meeting tells you it's being discussed — and when to offer a walkthrough.
Signed in the browser
The signature records name, email, IP address and a UTC timestamp, and the signed proposal can't change — the flows, rounds and handoff terms are fixed on record.
Milestone invoices
Convert the accepted proposal to a draft invoice, set it to the discovery milestone and send with your payment link. Convert again at wireframes, final designs and handoff.
What a UX/UI design proposal has to include.
The deliverable is a set of decisions as much as a set of files. These sections make both concrete.
Research activities
If it's left vague
'User research' could mean five interviews or a full study with recruitment.
With ApeiroCraft
Name the methods, number of participants, who recruits them and any incentive costs.
Flows and states in scope
If it's left vague
Edge cases, error states and responsive layouts appear as new requests.
With ApeiroCraft
List flows in scope, which states are designed, and the breakpoints covered.
Revision rounds
If it's left vague
Stakeholders keep reopening approved wireframes once high-fidelity begins.
With ApeiroCraft
State rounds per phase and that approved phases are only reopened as a change.
Design system and components
If it's left vague
The client expects a full design system from a single-flow redesign.
With ApeiroCraft
Say whether you're using their system, extending it, or building components — and how far.
Handoff and build support
If it's left vague
Developer questions continue indefinitely after delivery.
With ApeiroCraft
Define what handoff includes and a support window or hours for build questions.
- Milestone invoices from one accepted proposal.
- Team notes for research findings and decision logs.
- Kanban tasks for each flow, shared with collaborators.
Common questions.
How do UX designers usually price freelance work?
Common models are a fixed fee per phase (discovery, design, prototype, handoff), a day or week rate for embedded work, a monthly retainer for ongoing product design, and occasionally value-based pricing tied to a business outcome. Phased fixed fees with milestone payments are common for projects. ApeiroCraft holds the model you use and invoices it; it doesn't recommend rates.
What does a UX proposal look like for a SaaS onboarding redesign?
A problem statement from the discovery call; five user interviews recruited by the client; an audit of the current onboarding; two flows — sign-up and first-project setup — at high fidelity, desktop and mobile, with empty and error states; an interactive prototype; two rounds per phase; handoff with annotated files and a two-week question window. The product lead reopens it the morning of their planning meeting, signs, and you invoice discovery.
When is ApeiroCraft not the right fit for a UX designer?
If you bill hourly against tracked time, you'll need a time tracker alongside — ApeiroCraft has none. It's also not a research repository or a design-review tool. It fits the commercial side: getting the scope signed and the milestones invoiced, with the client record and notes in one place.
Can I propose a paid discovery phase first?
Yes. Send discovery as its own proposal, invoice it once signed, and send the design proposal once you know what you're designing. Many designers find a discovery proposal is an easier first yes.
Who owns the design files?
Whatever you agree. Write it in the proposal: when ownership or a licence transfers (often on final payment), whether working files are included, and whether you can show the work in your portfolio.
Scope the flows before the first wireframe.
Start from the web design template and adapt it to your UX phases.
Start freeStill deciding? Talk to the founder
Keep reading
Free template
Web design proposal template
Goals, scope boundaries, week-by-week process, and staged pricing that stops scope creep.
Solution
ApeiroCraft for freelance designers
See when the client opens your proposal, get it signed, and bill the deposit from it.
Solution
Proposal tracking, explained
Timestamped opens on the proposal itself — not an email pixel, not a guess.