PeoplePerHour proposal examples for small fixed-scope jobs

PeoplePerHour buyers often post small, fixed tasks: a landing page tweak, a logo refresh, a spreadsheet cleanup, a short video edit. The job looks simple, but your inbox competes with sellers who paste hour packages or generic intros that never mention the deliverable box.

On fixed-scope posts, the winning proposal usually does three things in the first screen: names the exact output, states what is not included, and offers a price or a tight range tied to assumptions you are willing to defend. This page gives copy-ready examples you can adapt in minutes, plus variations, mistakes, and a short pass before you send.

If the brief is vague, pair these patterns with short job post proposals. Before you submit, run the same discipline as our proposal checklist.

How buyers skim on PeoplePerHour

Most clients are not hiring a “relationship” on the first message. They want:

• Proof you read their task wording, not your gig title.
• A deliverable list they could forward to a colleague.
• Timeline with one assumption (access, assets, approvals).
• Price posture that does not dodge the post budget when they named one.

Length helps only when every line adds a decision. For micro-jobs, short and boxed beats a career essay. For slightly larger fixed boxes (e.g. “5 product pages + mobile check”), use the medium example below.

Example 1: Ultra-small task (under 2 hours of work)

Use when the post says “quick,” “small,” or lists a single artifact (fix header, resize banners, format CSV).

Hi [Name],

I can deliver [exact deliverable from their post] as described.

You will receive

• [Artifact 1, e.g. updated header on staging + live after approval]
• [Artifact 2, e.g. exported PNGs at 1x and 2x]
• [Handoff, e.g. 3-minute Loom showing what changed]

Not included in this fixed scope

• [Boundary, e.g. new illustrations, copywriting, extra pages]

Timeline: [X hours / same day / next business day] once I have [access / source files / brand PDF].

Price: [Fixed fee matching or slightly above their stated budget, with one line why if you are above].

If you confirm [one missing detail], I can start immediately.

Best,
[Your name]

Why this shape works: the client sees a closed box before they scroll to your profile. “Not included” prevents the classic PPH dispute where “small fix” becomes “redesign the site.”

Example 2: Fixed bundle (half-day to 2-day scope)

Use when they want a set of outputs (3 social templates, 10 SKU descriptions, WordPress plugin config).

Hi [Name],

Your post asks for [restate outcome in one sentence using their words]. Here is how I would deliver it as a fixed package:

Deliverables

1. [Deliverable with measurable boundary]
2. [Deliverable with measurable boundary]
3. [QA step, e.g. test checkout on mobile + desktop]

Process

• Kickoff: you share [folder / admin login / brief doc] by [day].
• Draft delivery: [date] for your review.
• Revisions: [1-2] rounds on [what is revisable: copy, spacing, colors within brand guide].

Assumptions (if any change, I re-quote before extra work)

• [Assumption, e.g. content is final in Google Doc]
• [Assumption, e.g. theme is already installed]

Timeline: [X business days] from kickoff.
Investment: [fixed price] for the package above.

Optional: we can start with [paid micro-milestone, e.g. first template only] if you want to validate style before the full batch.

Best,
[Your name]

Link fixed bundles to fixed-price project proposal pricing when you need to defend a number above the post budget without sounding argumentative.

Example 3: Post budget is tight but you still want to bid

Use when the listed budget is low but the task is real. You are not begging; you are shrinking scope to match.

Hi [Name],

I read your brief for [task]. At the budget listed ([amount]), I can offer a reduced fixed scope that still solves the core need:

Included at [budget]

• [Smallest viable deliverable]
• [One revision round on that deliverable only]

Available as add-ons (quoted separately before work starts)

• [Add-on 1]
• [Add-on 2]

If the full list in your post is required, my fixed price for the complete box is [higher number] with [timeline]. Happy to do either path; tell me which outcome matters most this week.

Best,
[Your name]

This pattern respects how to respond when the job post budget is clearly too low without a lecture. You give them a yes at their number and a clear upgrade path.

Example 4: They did not list a budget

Use when the post omits money. Anchor on deliverables first, then a range.

Hi [Name],

I can handle [deliverable] with the following fixed scope:

• [Bullet deliverables]
• [Revision rule]
• [File formats / access handoff]

Timeline: [range] after I receive [assets].
Investment: typically [range] for this box on PPH; final quote after you confirm [one variable: page count, number of SKUs, length of video].

Two quick questions so I do not misquote:

1. [Question tied to scope]
2. [Question tied to deadline or access]

Best,
[Your name]

See also what to write when the client did not list a budget.

Personalization checklist (5 minutes)

• Replace every bracket with text that only fits this job.
• Mirror one phrase from their post in the first two lines.
• Count deliverables: if they asked for 4 items, list 4, not “and more.”
• Match currency and fee style they used (fixed vs hourly mention).
• Read aloud: if it sounds like your gig description, cut half and add a client noun.

Mistakes that waste connects on small fixed jobs

Pasting your full offer catalog. Buyers asked for one box; showing twelve packages signals you did not read.

Hourly-only language on a fixed post. “My rate is X/hour” without a cap makes risk-averse clients skip.

No boundaries. Small jobs become scope creep. One “not included” line saves refunds later.

Fake urgency. “I am online now!!!” without deliverable clarity feels spammy.

Identical openings across ten bids today. Clients and platforms pattern-match; vary the first sentence and the deliverable list, not just the name field.

For tone that still feels human under pressure, compare freelance proposal examples that sound human.

After they reply

Keep the first reply aligned with what you promised. If they ask for more scope, quote an add-on in a new line item before you start extra work. Our first reply after the client messages you templates help you stay consistent without renegotiating in panic.

When not to use these examples

• Long discovery-heavy builds where milestones matter more than a single box (use milestone language from propose milestones when the client never mentioned milestones).
• Posts that are clearly scams or unpaid tests (unpaid test task requests).
• Jobs where you cannot verify access or legality of the task.

Final pass

Fixed-scope PPH posts reward clarity over charisma. Send a proposal that a busy buyer could forward internally and still understand what they are buying. Personalize the brackets hard, keep boundaries visible, and price the box you actually intend to deliver.

If you want the same structure without rewriting from scratch each time, keep one master template per niche (design, dev, admin) and only change the deliverable bullets and assumptions per post.