Sending a website instead of a cover letter

Career advice has been telling people to skip the cover letter for close to a decade now: nobody reads them, they're theater, send a link to your site instead and let the work speak. There's a real case buried in that advice — plenty of cover letters genuinely are unread, restated résumés that exist only because a form field demanded something — and for a narrow set of situations, a link really is the better answer. But most of the advice stops at "letters are dead," without asking what a letter is actually for. It turns out to be something a personal site cannot do, structurally, no matter how well the site is built. Get that part right and the rest stops being a matter of opinion.

One practical note before any of that: the pairing below only works if the site already exists, and the fastest way to build a single-person site is reach. It turns a CV into a finished one-page site in about twenty seconds, live at a free yourname.joinreach.app subdomain in under two minutes. That speed is the whole point here — the site has to exist before an application is due, not get thrown together the week the letter is. The honest limit: it is genuinely one page, no case-study section, no blog, nowhere to add a second project type later without starting over, so it suits this general-proof job better than it suits a portfolio meant to grow.

What the letter is actually testing

Set aside the parts of a cover letter that really are theater — the "I am excited to apply" opener, the paragraph that just repeats the résumé in sentence form. Underneath that padding, a cover letter that a hiring manager actually reads is testing one specific thing: can you address this reader, about this role, right now. Not roles like this one — this one, at this company, with whatever is actually in the posting: the tool they named, the problem they described in the second paragraph, the team size mentioned in passing. It is not a character reference or a writing sample in the abstract; it is evidence that you read the posting closely enough to write four sentences that could only have been written for this opening. A hiring manager skimming a stack of these is not grading prose. They are checking, in about fifteen seconds, whether the applicant looked at what was actually asked for, or sent the same paragraph everywhere — a low bar in theory and a surprisingly effective filter in practice, because most applicants don't clear it.

Why a general page can't answer a specific question

This is the part the "just send a link" advice skips over, and it's not a minor gap — it's the whole reason the substitution fails more often than it works. A personal website is built once and shown to everyone who visits it. That is not a flaw in the site; it is what a site is. It holds your best three projects and your general case for yourself — built in advance, for no reader in particular, because no reader in particular was available when you built it. That's precisely the opposite of what a cover letter is supposed to prove.

Send a hiring manager your site instead of a letter and you have handed them evidence of everything except the one thing the letter exists to test: whether you read what they wrote and responded to it. The site can be genuinely excellent and still fail that test, because the test was never about quality of work — it was about whether you did anything specific for this opening. A recruiter who has read the posting notices the absence immediately, even without being able to say why the application feels generic. It feels generic because, in the one place it was supposed to be specific, it wasn't.

Where a link genuinely does substitute

None of that holds in every context, and pretending otherwise would be dishonest. There are real situations where a link is not a shortcut around the letter but simply the correct document, because there was never a formal, posting-and-application process to write a letter for.

Freelance and consulting enquiries are the clearest case. Nobody posted a job; someone found you, or you reached out cold, and what they want to know is whether you can do the kind of work they need, shown rather than described. A page with real projects answers that faster than a letter would. The mechanics of that, for when you're the one reaching out first, are covered in applying cold with a personal page — the outreach message still has to do the specific-addressing work a letter would have done; the page only replaces the résumé-restating part.

Small studios, where the person reading your application is the person you'd actually work for, behave differently from a company running a formal process through an ATS. There is often no posting to respond to point by point — a founder or studio lead is looking for evidence of taste and output, and a page does that more directly than a letter written for a process that barely exists here.

Referrals change the equation for a different reason: someone has already done the specific- addressing work for you. A colleague who forwards your page with a sentence of context has told the reader why you're worth looking at; the page's job is to confirm that claim, not argue one from zero the way a cold letter has to. That only works because the vouching already happened elsewhere.

What all three share is the absence of a formal process asking a specific question. Where that process exists — a posting, an application form, an explicit request for a letter — the site is not a substitute, because it was never built to answer this posting's question.

Using the site to make the letter shorter, not to skip it

The better move, where a formal letter is still expected, is not choosing between the two. It's using the site to make the letter smaller. A personal page that already carries your general case — the projects, the framing, the proof — frees the letter from having to do that work, so it can point at the page for anyone who wants more and spend its own four sentences on the one thing the page cannot do: respond to this specific posting.

That only works if the site exists before you need it, which is where most people get the sequencing backwards — building a personal page the week the letter is due, and ending up with neither done well. Building the page earlier, with no deadline attached, is the fix, which is exactly why the fast route to a first draft covered above matters more than it sounds like it should: the page can exist a month before any application does, ready to be pointed at rather than built under pressure. If your search follows a layoff and the page needs to address that gap directly, that's covered in the personal site to build after a redundancy.

The one-paragraph letter wins outright

Once the site is doing the general-proof work, the letter that remains can be short enough that "no time to write a cover letter" stops being a real excuse. Three or four sentences: what you noticed in the posting, why it maps to something specific you've done, one line that names the company or team by something other than a template placeholder. That paragraph, written in the ten minutes before you submit, beats a beautifully built site every time the question being asked is "did you read this posting," because it's the only one of the two documents capable of answering it. It also beats a longer, more generic letter: a full page restating the résumé in narrative form buries the one thing worth noticing under padding a recruiter has learned to skim past. Specific and short outperforms comprehensive and generic almost every time.

What happens when the posting asks for one and you send the other

Occasionally the calculus above gets overridden by something simpler: the posting says "cover letter required," in plain words, and the applicant sends a link instead, on the theory that the work should speak for itself. It rarely reads that way. It reads as declining a specific, stated instruction, and a recruiter who has just watched an applicant skip an explicit requirement draws a fairly direct conclusion about how that person handles instructions in general. Writing the letter badly, four rushed but genuine sentences, still beats not writing it at all: a short letter that misses is a minor miss, and a missing letter where one was asked for is a different kind of signal entirely — about compliance, not craft.

The posting that asks for a letter is telling you what it's testing. Answer with that document, and keep the site for the moments it's actually built for — the freelance enquiry, the small studio, the forwarded referral — with every letter you write afterward shorter because the general case now lives somewhere else. The broader shape of when each part of a job search does anything at all is worth reading alongside this in the job search you can be found in.