Career & Job Search

Verified against ChatGPT · 2026-08-09

Write a cold application to a company with no open role posted

Produces a cold-outreach application email that makes a case for creating a role or considering you for a future one, built around a specific problem you'd solve rather than a generic 'I'd love to work here.'

ChatGPT (GPT-5.1)3 fillable variables

The prompt

Ready to copy — highlighted parts are example details you can swap.

You are writing a cold application email to a company that has not posted an open role matching what I do — this is a speculative outreach, not a response to a job listing, so it has to earn attention on its own.

PHASE 1 — IDENTIFY THE HOOK
From the company context below, identify one specific, plausible problem or gap this company likely has that matches what I can do. Do not invent a fact about the company you weren't given — if you're not confident in a specific problem, say so and ask me to confirm one rather than guessing at their internal challenges.

COMPANY CONTEXT
They just launched in a new country and their careers page has no listed operations or localization roles.

MY RELEVANT CAPABILITY
I ran market-entry localization for a similar-sized company's launch into three EU markets, cutting time-to-first-revenue by six weeks.

WHO I'M ADDRESSING THIS TO
Head of International Expansion — likely the actual decision-maker, not just HR.

PHASE 2 — DRAFT THE EMAIL
Open by naming the specific problem or gap, not by announcing that I'm job-hunting — the email should read like it's about their situation first. State my relevant capability as evidence I could help with that specific problem, using one concrete result rather than a list of skills. Explicitly acknowledge that I don't know whether they have budget or headcount for this right now, and frame the ask accordingly — not "are you hiring," but a smaller, answerable question like whether this is a problem worth a short conversation. Keep it to under 150 words in the body.

PHASE 3 — SUBJECT LINE
Write a subject line that names the specific problem or opportunity, not "Application for [Role]" or "Interested in opportunities at [Company]" — those read as mass-sent and get filtered accordingly.

WHAT NOT TO DO
Do not attach a resume-summary paragraph that lists job titles and years of experience — that's what the actual resume is for, not this email. Do not use "I've always admired your company's mission" or similarly unfalsifiable flattery. Do not ask them to "keep me in mind for future openings" as the primary ask — that's too passive to prompt a reply.

OUTPUT FORMAT
1. Subject line.
2. Email body, under 150 words.
3. A one-line flag if any part of the company context you were given felt too thin to build a credible hook from, so I can supply more before sending.

Customize

Optional — swap in your own details for the highlighted parts above.

Why this works

The explicit instruction against guessing at unconfirmed facts about the company matters because cold applications live or die on credibility in the first two sentences, and GPT-5.1 will otherwise happily fabricate a plausible-sounding company challenge from thin context, which reads as confident until the recipient — who actually knows their own company — spots the guess and discounts the whole email. Naming the problem before announcing the job search reframes the email from a request (give me something) to an offer (here's something useful), which changes which mental bucket a hiring manager sorts it into on first read; unsolicited job requests get filtered fast, unsolicited useful observations get a reply more often because they cost the recipient nothing to consider. The under-150-word constraint is load-bearing rather than arbitrary — a cold email to someone who didn't ask for it competes against a full inbox of email people did ask for, and length itself signals whether this is worth opening now or archiving for later. Asking a small, answerable question ("is this worth 15 minutes") instead of the large, effort-shifting "are you hiring" respects that most recipients cannot honestly answer a headcount question on the spot but can answer a scoped yes/no about whether a problem is real. Separating the resume-summary content out entirely stops the email from duplicating the resume's job, which is the single most common reason cold applications read as generic — they restate a background instead of making a case for why this specific background matters to this specific, named problem right now.

What you get back

Subject: Localization gap in your new market launch Hi Marcus — I noticed your recent expansion announcement doesn't have a listed localization or in-market operations role yet, which is usually the first hire that determines whether time-to-revenue is 3 months or 9. I ran that exact function for a similarly-sized company's EU launch and cut time-to-first-revenue by six weeks by fixing the localization handoff early. I don't know if this is a gap you're actively solving for right now — worth a 15-minute call if it is?

Verified against

ChatGPT GPT-5.1 · 2026-08-09

Changelog

  • 2026-08-09 Initial publish, verified against ChatGPT GPT-5.1.

Need this built into your business?

If a prompt isn't enough — what Scult builds, built and maintained for you — that's Scult's day job.

EXPLORE WHAT SCULT BUILDS
All Career & Job Search prompts

Check your AI visibility

One URL in, a 0–100 score and the exact fixes out.

RUN THE CHECK

Browse all the tools

15 tools across six categories
13 of them never send your data anywhere

Free · No signup · No trial clock

SEE THE DIRECTORY