Tailoring to the Job Post
What to extract from a job post and how to turn it into a proposal that feels written for one person.
Template vs tailoring
These are two different things that work together. A template is your structure: the order of sections, your pre-written proof points, your standard CTA. Tailoring is content: the specific sentences you write for this job, this client, this post. You need both.
A freelancer with no template writes slowly and inconsistently. A freelancer with a template but no tailoring sends generic proposals that get ignored. The goal is to have scaffolding that never changes and a top section that always does.
What to extract from a job post before writing
Before you write a single word, read the post once and identify these five things:
- The exact problem. Not the category ("I need a web developer") — the specific problem ("our checkout flow has a 70% drop-off on mobile and we don't know why"). The specific problem is what you write about.
- The outcome they care about. Not what you'll deliver — what success looks like to them. "Launch before Q2" is an outcome. "Reduce support tickets by 30%" is an outcome. Mentioning their outcome in your proposal signals you understand what they're actually trying to accomplish.
- Specific tools, platforms, or constraints. If they mention Stripe, React, Shopify, HubSpot — note them. Referencing the exact tools they listed (rather than the category) shows you read carefully.
- Tone of the post. Casual and direct? Formal and detailed? Anxious and rushed? Their writing style tells you how they communicate and what kind of working relationship they're expecting. Caveat: nearly 9 in 10 posts are now AI-written, so tone is a weaker signal than it used to be — weight scope clarity and client signals more heavily.
- Any hidden concern. "We've had bad experiences with freelancers before" means: they need trust and reliability, lead with proof of both. "This is urgent" means: lead with your availability and turnaround time. "We have a tight budget" means: don't open with your premium positioning.
The 3-minute tailoring process
This is repeatable once you've done it a few times:
- Read the entire post once — don't skim.
- Underline mentally (or literally): the specific problem, the success metric they care about, and any tools or constraints mentioned.
- Write one sentence that references at least two of those three things. That sentence is your hook.
Example: a post says "We're rebuilding our onboarding flow in React — it needs to work on mobile and be done before our product launch in 6 weeks." Your hook: "I've built mobile-first React onboarding flows before and can work to a 6-week timeline — here's how I'd approach this one."
That's it. One sentence. It references the tool (React), the constraint (mobile-first), and the deadline (6 weeks). The client reads it and thinks: this person read my post.
Tailoring by job post type
Different post types call for different tailoring strategies:
Well-defined post
The client has listed clear scope, milestones, specific tools, and deliverables. They know what they want. Mirror their structure back to them — show you fit their exact spec. If they listed five requirements, address them in the same order. If they specified deliverables, use their language, not your own paraphrase.
Example hook: "You've outlined a clear scope: React frontend, Node API, PostgreSQL — with delivery in three phases. I've done this exact stack in a similar setup; let me show you how I'd handle phase 2 specifically, since that's where most projects in this space run into trouble."
Vague post
The client has a goal but no clear scope. Don't write a vague proposal back. Instead, briefly restate what you understand the goal to be and ask one clarifying question at the end. This does two things: it shows you've thought about their situation, and it separates you from the 30 other proposals that are also vague.
Example: "From what I can tell, you're trying to build a client portal that reduces your team's manual reporting work — is that the core goal, or is there a different outcome you're prioritizing?" One question. Not five.
Emotional or frustrated post
"Our previous developer disappeared mid-project," "we need this fixed immediately," "we've been burned before." Don't pretend the emotional context isn't there. Acknowledge it directly — briefly — then move to how you structure your work to prevent exactly that.
Example: "Sounds like you've been burned before — here's how I structure projects to prevent that: weekly check-ins, written scope confirmation before I start, and no invoicing for incomplete milestones." Specific process, not empty reassurance.
What not to do
| Common mistake | Why it fails | What to do instead |
|---|---|---|
| "I see you're looking for a React developer..." | Pastes the job title back — says nothing | Reference a specific detail from inside the post |
| Restating their whole post back in different words | Adds length, zero new information | Acknowledge their situation in one sentence, then move to your approach |
| "I'm very interested in this opportunity" | Every applicant says this; it's filler | Show interest by demonstrating you read and thought about the post |
| Using the same opening for every proposal | Clients recognize templated openers immediately | Write the first 2–3 sentences fresh for each job |
| Addressing concerns they didn't raise | Makes you seem defensive or off-topic | Address only what's in the post, plus the hidden concern if there is one |
Qualify before tailoring
Tailoring is worth it only when the job is worth applying to. Before spending 10 minutes on a tailored proposal, confirm: does this job match your niche, your rate range, and your available capacity? If not, skip it. A tailored proposal on the wrong job is still wasted effort. See Filtering for Quality Jobs for how to qualify quickly.