The format wars are over. PDF versus proposal software versus an email quote, fine, pick one. The bigger question almost nobody asks is whether the thing renders on a phone, because that’s where it’s getting opened first.
Watch a prospect’s inbox for a week. The notification dings. They tap. They scroll for 20 seconds. They either say “this looks interesting, I’ll read it tonight” or they put their phone down and never open it again. That first tap is where proposals get killed silently.
Most freelancers have never opened their own proposal on a phone. Try it right now. Pull up the last proposal you sent on your phone. Scroll through it. Notice how it feels.
The mobile read pattern
Mobile reading isn’t desktop reading at smaller size. People hold the phone differently, scroll faster, and skim with one thumb. The mental model is closer to scrolling Instagram than reading a document.
What this means for proposal design:
- The first screen has to communicate “what is this and what does it cost”
- The second screen has to communicate “what do I get for it”
- The third screen has to communicate “what’s the next step”
- Everything after that is for the desktop deep-read
If a prospect has to scroll past five screens of intro fluff to find the price, they’ve already lost interest. The phone read is the trailer. It either makes them want to come back for the movie or it doesn’t.
The common mobile-killers
These show up in roughly half the proposals I’ve seen freelancers send.
Multi-column tier layouts. Three pricing tiers laid out side by side look great on a 14-inch laptop. On a phone, they either shrink to unreadable or stack into a confusing wall. If you must use three tiers, design them to stack vertically on mobile with clear separators and the recommended tier called out at the top.
Small body type. Anything under 16px on mobile is a problem. Designers default to 14px because it looks tight and professional on desktop. On a phone in sunlight, 14px is genuinely hard to read. Bump it up.
Light gray body text. “Sophisticated” gray-on-white body copy is a desktop trope. On a phone screen in a bright cafe, light gray on white is invisible. Use near-black for body text. Save gray for de-emphasized supporting elements.
Price hidden on page 4. A surprising number of proposals bury the total price three or four scrolls down, after the “about us” section and the “our process” section. On mobile, this is fatal. The prospect skims, doesn’t see a number, assumes the proposal is incomplete or overpriced, and closes it. Put the price near the top.
Tables that don’t reflow. A scope table with five columns becomes garbage on mobile. Either redesign tables as stacked lists for mobile or accept that they need horizontal scroll, which is annoying but readable.
CTAs below the fold. The “accept” or “book a call” button shouldn’t be only at the very bottom. Repeat it after each major section so a mobile reader can act whenever they’re ready.
A simple mobile readability checklist
Run your proposal through this list on your phone:
| Check | Pass / Fail |
|---|---|
| Can I see the project name and the total price within 2 screens of scrolling? | |
| Is the body text at least 16px and dark enough to read in sunlight? | |
| Does every section header stand out clearly when I scroll past it fast? | |
| Are pricing tiers stacked vertically, not crammed into columns? | |
| Is there a CTA button visible within every 3 screens of scrolling? | |
| Can I read the whole proposal in under 8 minutes without zooming? | |
| Does the proposal feel finished, or does it feel like a desktop document I’m intruding on? |
If you’re failing more than two of these, your proposal has a mobile problem.
The structure that works
Here’s a proposal structure that works on mobile and reads well on desktop:
Screen 1. Project name, your name and a sentence about what this is. Big, clean.
Screen 2. The total price. Or the recommended tier price. Don’t hide it. Put it in big type, not a footnote.
Screen 3. The scope summary. Five to seven bullets, not a paragraph. What’s included.
Screen 4. Timeline. One sentence and a small calendar visual or week-by-week list.
Screen 5. Your process. Brief. Three or four steps.
Screen 6. Tier breakdown if applicable (stacked vertically).
Screen 7. Terms and the CTA. Accept button or call-booking link.
That’s roughly 7 mobile screens. About 4 to 6 minutes of phone reading. Enough to make a yes-or-no judgment without exhausting the reader.
Anything more belongs in an appendix the desktop reader can dig into.
The font and spacing rules that actually matter
You don’t need a design degree to fix mobile proposal readability. A few specific rules cover most of it:
- Body type: 16px minimum, 17 or 18 is better
- Line height: 1.5 to 1.6 times the font size
- Section headers: at least 22px, distinct color or weight
- Price numbers: 28 to 36px, bold
- Margin between sections: at least 32px on mobile
- Bullet spacing: 12 to 16px between items
- Color: body text within 20 percent contrast of full black against white background
Most proposal software has these as defaults. Most custom PDF templates do not.
The “open on a phone first” test
The fastest way to find your mobile problems is to do what your prospects do. Email your last proposal to your own personal email address. Open it on your phone exactly the way a prospect would, tap the notification, no zooming, no rotating.
Then ask yourself:
- Within 30 seconds, do I know what this proposal is and what it costs?
- Would I bother to come back to this on desktop?
- Does it look professional, or does it look like a desktop document forced onto a phone?
If you’re embarrassed even a little, your prospects feel it too. They just don’t tell you. They quietly close the tab and move on.
PDF specifically: how to make it less terrible on mobile
PDFs are the most common offender because they don’t reflow. The page layout you designed for letter size or A4 becomes a tiny scaled-down version on phone.
If you’re committed to PDF, design it differently:
- Use a vertical, narrow page format (something close to a 9:16 aspect ratio)
- One column only, no side-by-side anything
- Large type as if the document is being printed at 4x6 inches
- Short pages, lots of them, rather than dense pages with small text
- Test the actual file on your phone before sending
This is essentially designing a mobile-first PDF, and it works. It looks slightly weird on desktop (lots of white space on the sides), but mobile readability jumps significantly. Trade you’ll usually want to make, since mobile is the first open.
Proposal software defaults
If you use proposal software (Waco3, Proposify, PandaDoc, etc.), most of the mobile rendering is handled for you. But not all of it. A few things still go wrong:
- Custom images or embeds that don’t resize
- Tables that don’t stack
- Embedded videos that auto-play and chew data
- Custom fonts that fall back to ugly defaults on mobile
Send a test proposal to yourself, open it on your phone, and check.
What this is really about
Mobile readability isn’t a design preference. It’s a deal flow issue. If half your proposal opens are happening on phones, and your proposal isn’t designed to convert at that first mobile glance, you’re losing deals before the prospect ever sees the real version on desktop.
The fix isn’t expensive. It’s mostly discipline: shorter, larger, cleaner, prices early, CTAs repeated, one column.
The proposal that wins on mobile usually wins on desktop too, because the discipline of mobile design forces you to cut the parts of the proposal that nobody was reading anyway.
Open your last proposal on your phone right now. Honestly look at it. Then fix the worst three things you see.
Ready to send stronger proposals?
Build, send, and track proposals in one place so follow-up is easier.
Start your free trial →
