DEV Community: Christina Revells

After the quote: the two replies that decide the job — silence and "too expensive"

Christina Revells — Tue, 20 Oct 2026 15:49:03 +0000

Freelancers past the beginner stage usually don't have a "getting started" problem anymore. The work is good, past clients exist, and referrals carry a chunk of the year. The struggle is the wobbling pipeline: a promising conversation stalls, a quote gets no answer, and suddenly next month is empty and nothing in your craft can fix it.

Look closely at where those pipelines actually die. Rarely at the first contact, and rarely at the work itself. They die in the two replies that come after a prospect is interested but not yet committed: the going-silent, and the pushback. Most freelancers improvise both. Here is the version you can run deliberately.

Part one: when the quote goes quiet

Silence feels like an answer, but it isn't one. "No news" carries no information — it means "not yet," "not interested," "buried," or "in a meeting," and nothing in the inbox tells you which. The fix is not persistence in general; it is a short, finite sequence where every message adds something, and where stopping is part of the design.

Three touches, then done:

Touch 1 — the quote or first email (day 0). One verified observation, one implication for their business, one clear ask. Short enough to read on a phone, easy to say no to.

Touch 2 — the value follow-up (3–5 business days later). Something useful, never a nudge: an answer to a question they asked that you never fully answered, a short example of the fix from work you've actually done (anonymized if needed), or one new fact — "since I sent the quote, [specific thing] changed; the offer holds if the timing moved." The test: if this prospect never replies and never hires you, is the message still worth having received? If not, delete it.

Touch 3 — the polite close (5–7 business days later). Say it out loud: "Following up one last time — it sounds like this isn't a priority right now, which is completely fine. I'll stop here. If [specific problem] becomes current later, you know where to find me." A close like this removes the obligation to respond — which is exactly why it sometimes reopens the door; people answer the sender who is clearly going to stop.

Then the stop rules, which are the actual system: any "no" is final and stops the sequence immediately. Any opt-out is processed the same day. Two follow-ups maximum — three total messages, ever. Silence after the polite close means the row is closed; don't reopen it because you had a good week. A "maybe next quarter" gets exactly one scheduled revisit, agreed with permission. And never send a follow-up that contains no new information — that rule alone retires most of what makes follow-up feel bad.

Fictional example (illustration, not a real client): a freelance designer sends a proposal, hears nothing, and — busy with a current client — improvises a "just bumping this" six weeks later. A designer running the three-touch shape instead would have sent one useful follow-up and one clean close inside three weeks, and the row would be closed either way: a decision on the record, or a door closed so kindly it can reopen without awkwardness.

Part two: when they push back

An objection is not rejection. It is the only reply that tells you exactly what stands between your work and the hire — if you can resist arguing with it. Nearly every pushback falls into one of four families, and each has one question that keeps the conversation honest:

Timing — "not right now." Usually real: the problem is believed, the month is full. Ask: "What would need to change for this to become current — a launch, a budget cycle?" Their answer is an event. Write it down; that event, with their permission to check back, is the follow-up date.

Money — "too expensive" or "no budget." Ask: "Is it the total or the timing?" That separates a value problem (make the outcome concrete — a smaller paid first phase often does this better than a discount) from a budget problem (the honest answer may be "not yet"). Never drop your price on the spot; an instant discount teaches the buyer your first number wasn't real.

Trust — "how do I know it will work?" Fair, and most common for people without a brand. The answer is never a better claim; it is something inspectable: a real sample of the work, a small paid pilot, a plainly written page about how you work. Show, don't insist — and never invent proof, because a fabricated result ends the relationship the moment it's checked.

Priority — "we already have someone." Don't run down the incumbent. Ask: "What does the current arrangement not cover yet?" Sometimes the answer reveals a real gap you can fill; sometimes it's a clean disqualification. Both are wins — one prospect learned something specific, and you didn't spend a month chasing a no.

Keep the log that makes next month easier

Five columns, kept honestly: objection in their words · family · what you replied · what happened next · did it repeat. After twenty conversations, the repeated objections are your positioning feedback. If "sounds like a lot of work" shows up five times from five people, that's not a reply problem — it's a page or offer problem, and no clever response will fix it.

Two or more people naming the same objection is a signal. One is an anecdote. Change one thing at a time, and note what happened.

AI disclosure: this post was drafted with AI assistance.

Research signals: how to tell "a reason to email" from "a thing you noticed"

Christina Revells — Tue, 20 Oct 2026 04:34:32 +0000

Two people send outreach the same week, to similar companies, with similar offers. One email reads like it was written by someone who did homework. The other reads like a template wearing a costume. The difference usually isn't effort, word count, or even quality of writing — it's whether the sender actually found a signal, or just a fact, and mistook one for the other.

Most "personalization" advice says "find something about them." That's the root of the problem. There are three different things you can find about a prospect, and only one of them is a reason to write today.

A fact, a signal, and a reason are three different things

A fact is verifiable and true, but says nothing about timing. "They're a 12-person company." "They sell to dental clinics." "Their HQ is in Rotterdam." Facts are necessary — you have to know who you're talking to — but a fact alone produces emails like "I saw you're a 12-person company," which is the corporate equivalent of "nice weather we're having."

A signal is a recent, observable event: a new hire in a role that touches your problem, a changelog entry revealing a workflow you improve, a pricing page that changed, a public complaint in their own community. Signals have a date and a direction.

A reason is the connective sentence between them: because this signal happened, the problem you solve just became slightly more urgent for this company than it was last quarter. The signal is the news; the reason is why the news is theirs.

Fictional example (illustration, not a real success story): a founder selling docs tooling notices a company's help center. Fact: they have a help center. Signal: last month's job posting says "first technical writer." Reason: a team about to hire its first writer is about to formalize docs workflows the same month. The email writes itself from that one sentence — and no amount of "loved your recent post" could have produced it.

Outreach that stacks all three lands differently because it proves a human looked. Outreach that stops at facts proves only that a scraper worked.

The five tests every claimed signal must pass

Before a "signal" earns a place in your first line, run it through five quick tests:

Recency. Can you date it to the last few months? "They raised a Series A in 2023" is history, not news. If you can't find when it happened, you don't have a signal — you have trivia.
Ownership. Is this the recipient's problem, or the company's? A Head of Support owns a support-tooling signal; the CEO of a 12-person company owns nearly everything, which is both an advantage and a reason their inbox is a war zone. If the change clearly belongs to someone else's function, write to that person — or don't write.
Relevance. Does this specific change touch the specific problem you solve? "They launched a new product" is only a signal if launching products creates the workflow you improve. A genuine but unrelated signal is small talk with a timestamp.
Specificity. Could your first line quote it back in one sentence? "I saw your changelog" fails; "your September changelog says the migration tool moved out of beta" passes. If you can't phrase it concretely, you haven't read it closely enough.
Verifiability. Can you name where you saw it, today, if they reply "where did you see that?" No source, no email. This one rule quietly eliminates most invented "signals."

Four or five passes: strong signal — build the email around it. Two or three passes: usable as a quiet opener, not as a headline claim. One pass: context for your notes, not for your inbox.

Noise that dresses up as signal

The most common failures are things that feel researched:

Awards and press mentions. Usually months old, and relevant to the marketing team at best — and they've heard the congrats already.
Podcast guest spots without a dated connection to your problem. If their episode said something that is your problem, that's a real signal. If the episode was about their vacation rental hobby, it's not.
Hiring in general. "I saw you're hiring!" is not a signal. "You posted a first-ever lifecycle marketing role eleven days ago" is.
Funding with no strategic angle. A raise only matters if it changes something your offer touches — headcount plans, a new market, a tooling budget.
Anything outside work. Where they vacationed, what their kids do, posts from years ago. The line is simple: use what they'd happily tell a work acquaintance; never use what they'd be startled a stranger knows.
The recycled "signal." If your last five first lines could each swap into the next email unchanged, you don't have signals — you have one sentence with different names typed in.

And then there are disqualifiers — observations that should end the research, not start the email: the wrong buyer role entirely, no plausible budget path, or any indication you'd be the third person this month to pitch the same obvious angle. Skipping a bad-fit prospect costs you one email; sending anyway costs you the address.

Signals have a shelf life

Because a signal is a dated event, it decays. A trigger that was sharp three months ago is now backstory — useful for understanding the company, useless as a "noticed this week" opener. Two practices keep your work honest:

Write the signal down with its date and source the day you find it. A one-line ledger per prospect — signal · date seen · where · why it matters to them — beats a folder of browser tabs you'll no longer trust next month.
Never reuse a stale observation in a live email. If the only signal you have is old, say so quietly and honestly ("I've been following your docs since the spring migration") rather than repackaging it as fresh — or fall back to a non-time-based observation you can still verify today. What you must never do is invent urgency that the record doesn't show.

The payoff, either way

Run this filter and one of two things happens consistently. Either the email gets built on a reason a busy stranger can verify in four seconds — which is the entire competitive advantage available to a sender with no brand — or you skip the prospect and save an hour. Both outcomes beat what most outreach does: turning facts into noise at scale, at speed.

AI disclosure: this post was drafted with AI assistance and reviewed by me before publishing.