Skip to content

100 Job Strategies · 3 of 100

The Unsolicited Audit

Stop asking them to evaluate you. Hand them something already finished.

3 viewsHigh effortPays off in 1-3 weeksFreshersCareer switchersDesigners and marketersAnyone with no referrals
Share

In short

An unsolicited audit is a one-page teardown of something a company owns — their signup flow, their ad copy, their warehouse layout, their onboarding email — sent with no pitch attached. It inverts the hiring conversation: instead of claiming you can do the work, you have already done a piece of it. Response rates are far higher than any application because you are giving rather than asking.

The situation

You apply for a role. Your resume says you are a detail-oriented UX designer with five years of experience improving conversion. So does everyone else's.

The hiring manager cannot verify any of it. They can only decide whether to spend 30 minutes finding out. Most of the time, they don't.

Now imagine a different message arriving. No resume, no cover letter, no "I am writing to express my interest". Just a single page: here are four things costing you signups on your onboarding flow, with screenshots, and here is what I would change.

They can verify that in 90 seconds, because it is about them.

Why this works

Hiring is a risk-reduction exercise disguised as a selection exercise. Nobody is trying to find the best candidate in the world; they are trying to avoid hiring someone who cannot do the job. Every step of a normal process — resume screen, phone screen, take-home, panel — exists to reduce that uncertainty.

An audit collapses the whole ladder. It is a work sample about their actual business, produced unprompted. It answers "can this person do the work" more convincingly than four rounds of interviews, because interviews measure how well you talk about work and an audit is the work.

There is a second effect that matters just as much. Giving something away changes the social dynamic. An application asks the company for something — time, attention, a job. An audit gives them something they can use whether or not they ever reply. People respond very differently to the second kind of message, and the ones who do reply arrive already predisposed to like you.

How to run it

  1. 1

    Pick one narrow surface

    Not "your marketing". One specific thing: the signup flow, the pricing page, the abandoned-cart email, the shift handover sheet. Narrow is credible; broad reads as a template.

  2. 2

    Actually use the thing

    Sign up. Buy something. Call their support line. Walk the store. Your audit must contain details that only someone who genuinely went through it would know — that specificity is the entire proof.

  3. 3

    Find three to five real problems

    Not fifty. A long list reads as criticism; a short list reads as judgement. Each problem should be something a reasonable person would agree is a problem once you point at it.

  4. 4

    Write the fix next to each problem

    A problem without a fix is a complaint. For each item: what is happening, why it costs them, what you would do instead. Two or three sentences each, maximum.

  5. 5

    Keep it to one page and make it beautiful

    One page, screenshots where useful, their name on it. If your discipline is visual, the document itself is a second work sample — make the artefact prove the skill.

  6. 6

    Send it with no ask

    This is the part people get wrong. Do not attach a resume. Do not ask for a call. Send it, say you made it because you found the problem interesting, and stop. Let them ask the next question.

What to say

Copy, then make it yours
Hi Dana, I signed up for Northwind last week to see how the onboarding worked, and ended up making notes. They turned into this — four things I think are costing you activations, with what I'd change for each. No agenda here, it's yours either way. I've spent three years doing exactly this kind of work on onboarding flows and yours was genuinely interesting to pull apart. If any of it is useful, happy to talk through the reasoning. If not, ignore me entirely and good luck with the launch. — Tom [one-page PDF attached]

When it does not work

  • Being rude about their work. Someone in that building built the thing you are critiquing, and they may be the person reading your email. Write as though you respect the constraints they were working under — because you do not know what those were.
  • Auditing something you cannot actually see. An outsider cannot audit their data pipeline or their hiring process. Stick to surfaces you have genuinely experienced as a user, customer or visitor.
  • Attaching a resume anyway. The power of this move is that it does not ask. The moment a resume is attached it becomes an application with extra steps, and it gets filed like one.
  • Confusing volume with value. A 20-item list looks like you ran an automated scan. Three sharp observations with fixes beat twenty generic ones every time.
  • Expecting a fast reply. Audits often get forwarded internally before anyone responds to you. A reply three weeks later saying "we passed this around" is a normal and good outcome.
The takeaway

Applications ask a company to imagine what you could do. An audit removes the imagination step entirely — and costs them nothing to accept.

Questions

Is it rude to send a company criticism they did not ask for?

It depends entirely on tone and framing. An audit that reads as "here is everything wrong with what you built" will land badly, and deservedly so. One that reads as "I found this interesting enough to pull apart, here is what I noticed and what I would try" is received as generosity, because that is what it is. Assume every choice you are questioning was made by a smart person under constraints you cannot see, and write accordingly.

What if I do not have professional experience to back up my suggestions?

The audit itself is the credential, which is precisely why this works so well for freshers and career switchers. Nobody checks your years of experience against a document that visibly demonstrates the skill. What matters is that your observations are correct and your fixes are sensible. If you can spot four real problems in someone's onboarding flow and explain how to fix them, you have proven more than a degree does.

Who should I send it to?

The person who owns the surface you audited, not a recruiter and not a general inbox. If you audited the signup flow, that is usually a head of product, growth or design. If you audited ad copy, it is marketing. At smaller companies it is often a founder. Recruiters cannot act on an audit and will most likely redirect you to the careers page, which wastes the advantage you just built.

How long should the audit take me to make?

A few hours for a focused one-page teardown, assuming you genuinely use the product first. If it is taking days you have chosen too broad a surface — narrow it. The time cost is real, which is why this is a strategy for a handful of companies you seriously want rather than something to run at scale. Three excellent audits will outperform thirty applications.

Find verified jobs from 100,000+ companies
Share

More from 100 Job Strategies

See all 25 in this series