About ApplyStorm

Pro now costs $39 a month, or $105 every three months, and includes 75 applications, 40 submissions and up to 100 tailored résumés a month. Anyone already subscribed keeps the price they signed up at for as long as they stay subscribed, and any change to their limits comes with 30 days’ written notice and a prorated refund if they cancel before it takes effect.

• ·Two ways to pay: monthly, or quarterly at $105 (about $35 a month). Quarterly plans refund in full within 7 days of the charge and are otherwise non-refundable, with access kept to the end of the quarter. There is no annual plan on purpose — a search rarely lasts a year.
• ·Pro’s limits went up: 75 applications and 40 submissions a month, from 50 and 25. Tailored résumés are “up to 100 a month”, which is more than a 75-application month needs; existing subscribers keep unlimited tailoring until the written notice period has run.
• ·Existing subscribers are grandfathered. Nothing about their subscription changes; the earlier price stays on their account and is simply no longer sold to new customers.
• ·Every configured price is checked against Stripe before a checkout is created, so a wrong price can never be sold by mistake — checkout refuses and names the setting instead.
• ·The budget banner no longer mentions a “Premium” plan; there never was one to buy.

The application page now shows the résumé’s quality-check result beside Send to Chrome and Submit. A résumé that failed a check is not sent on one click: you see which checks failed, can edit the résumé, and confirm in so many words if you want to send it as it is.

• ·Above the Send and Submit buttons the résumé’s result is stated plainly: passed; could not be fully checked (a check did not run, so the résumé is unjudged rather than bad); not checked yet; or failed, with each failed check named — a claim the résumé makes that your own material does not support, say — and what it found.
• ·Sending a failed résumé takes a second, deliberate click. The first shows exactly what failed and what confirming means for the path you chose — handing it to your Chrome to fill the form, or submitting it with the résumé as written — and offers Edit résumé instead. Nothing goes out until you confirm you have reviewed it.
• ·A résumé that could not be fully checked, or has not been checked yet, still sends on one click, with the notice in view — you are the reviewer.
• ·On the Jobs and applications lists, the reason Auto-apply is unavailable now says which of those three it is, instead of “hasn’t passed the quality check” for all of them.
• ·Storm is unchanged: it never hands a résumé to your Chrome unless the check passed, whatever you confirm here.

Everything waiting on you now lives on the Storm page. Jobs shows a short summary of it and gets on with the job list, and the number in the top bar takes you straight to the queue.

• ·The Jobs page no longer lists every approval and question above the job list. A compact card says how many things need you and what kinds — "19 approvals", say — shows the two most pressing, and links to Storm for the rest. It is the same size whether one thing is waiting or a hundred.
• ·The "need you" number in the top bar is the way into that queue from anywhere in the product: it opens Storm at Needs your attention.
• ·On Storm, the queue is grouped — Approvals, Ready for your review in Chrome, Failed runs, Employer questions, Refused résumés — with a count on each. Large groups show five and fold the rest behind "Show all"; every approval stays on the page with its Approve and Decline buttons.
• ·A question from your specialist, or an interview email you have not answered, now appears on Storm too, so the number in the bar and the page it opens always agree on what is waiting.
• ·The word "robot" is gone from these screens. Storm is Storm.

Storm is now the first entry in the top bar: whether it is on, what it is working on, what it needs from you, what happened, and what actually got submitted — read from the same records the rest of the product uses, on one page.

• ·The header answers three things at a glance: is Storm on, paused or not yet enabled for you; does it ask before acting, and who clicks Submit; and is your Chrome extension connected, offline, unpaired or in need of an update.
• ·Needs your attention lists only what is waiting on you — an approval, a form filled and parked in Chrome for your review, a failed run you can retry, an employer question, or a résumé the quality check refused — each with the company and job, why Storm stopped, and one link to act. Approvals can be answered right there.
• ·In progress and Recent activity say what Storm and your browser are doing and did, in plain words: prepared, handed to Chrome, filling, waiting for you, quality check passed or refused and why, skipped and the rule, temporarily deferred.
• ·Recent outcomes labels every application with exactly how far it got. “Submitted” is shown only for applications an employer actually received; a filled form, a parked form and an approved handoff are never called submitted.
• ·The page refreshes itself while anything is moving, and says so when part of your data could not be read rather than showing an empty list.

If your submission path is the Chrome extension, a tailored résumé and cover letter are now generated automatically only for postings the extension can fill; every other strong match is still found, scored and ranked, and is tailored the moment you ask.

• ·Matches from aggregators, or on sites the extension cannot drive, no longer consume your generation allowance on their own. Open one and press Generate now — the documents are produced the same way, through the same quality checks, and the application appears ready for a manual submission.
• ·The job page says when a match was not tailored automatically and why, so a strong match without documents is never a mystery.
• ·The same posting reissued under a new listing is not tailored twice. Two openings that merely share a title and employer — a different city, a different description — are still treated as two.
• ·If your path is self-service or a specialist, nothing changes: every strong match is tailored automatically, as before.

When Storm prepares an application and stops because your settings say ask first, the question now appears in Settings → Autonomy with Approve and Decline beside it.

• ·Each waiting action says what Storm wants to do and to which job, when it asked, and when the question lapses if nobody answers.
• ·It also says what it will not do. Approving hands the application to your Chrome extension, which fills the form, uploads your documents and checks the result — then stops. You click Submit. Nothing reaches the employer until you send it.
• ·Approving releases the work Storm had already paused; it does not start something new. Declining is final for that application — Storm will not ask about it again.
• ·Only you can answer: the decision is recorded against your sign-in, and it applies to that one action rather than changing what Storm may do next.
• ·Questions that lapsed before you saw them say so instead of offering a button. Storm asks again the next time it reaches that step.

Three new pages you can read without an account: how it works, what it costs, and the questions people ask — with the same answers the help guide gives.

• ·How it works walks through the pipeline in order: finding roles, writing the materials, filing the application under your control, following employer replies, and preparing for the call.
• ·Pricing now has its own page — the Terms of Service had pointed to one for months. It states the free tier and the Pro plan side by side, with the monthly limits of each and how refunds and cancellation work.
• ·The FAQ publishes the customer half of the help guide, so what happens with CAPTCHAs, LinkedIn, the kill switch, recordings and your data can be read before you decide.
• ·Links to all three sit in the footer of every page.

Settings → Autonomy shows each thing Storm can do, whether it is Off, asks you first, or runs automatically, and why — and lets you make a time-boxed change.

• ·Every capability shows its level and where that level comes from: the product default, a choice you made, or a limit Storm tightened on itself.
• ·A temporary change lasts from one hour to seven days. Tightening takes effect immediately. Loosening is recorded as a request and changes nothing until you approve it in a second step that names the consequence — so nothing is ever sent without a deliberate yes from you.
• ·You can end a temporary change early, or withdraw a request you have not approved, at any time.
• ·If a setting cannot be read, the page says Unknown rather than guessing. It never shows a more permissive level than it can prove.
• ·Not yet: changing a permanent level from this page. It is shown honestly as not offered rather than as a button that does nothing.

Paste or upload an offer and the terms are read out — base, bonus, equity over four years — with anything read wrong yours to fix in two clicks.

• ·Find it under Interviews → Offers. Paste the offer email or upload the letter (PDF or Word); the terms appear as editable numbers with the original text kept alongside.
• ·Nothing is ever guessed: a term the letter does not state shows as a dash, not an invented “typical” value. A bonus stated as a percent is computed from the stated base — by arithmetic, not by the model.
• ·Each offer shows its 4-year value and what arrives each year — a vesting cliff delays money, it does not reduce it, and the math treats it that way.
• ·With two or more offers in the same currency, a side-by-side ranks them by net present value. It is labeled as arithmetic, not advice: the right offer weighs things no letter states.
• ·Every parsed offer can become a negotiation playbook: what to ask for first and the exact words to say it, a sendable email, the 60-second phone version, and replies to the pushback you will actually hear. No number appears in a script unless it came from the letter or from you.
• ·Then practise it out loud: one click seeds the recruiter’s pushback lines into Rehearsal, where your answers are scored on holding your anchor, arguing value rather than need, and never inventing a figure.

When an employer replies, ApplyStorm reads the outcome — and what it cannot decide alone, it asks you in one click.

• ·An interview invitation or an offer from a verified sender moves the application forward automatically, so your pipeline reflects reality without you doing anything.
• ·A rejection is never applied automatically. It appears on the application as a one-click question — “this email looks like a rejection, is that right?” — with the exact phrases that made us think so. Rejections are final, so a human decides.
• ·You can now record what happened off-platform: a screening call, an interview, an offer, an acceptance or a rejection — straight from the application page. Phone calls and hallway offers count too.
• ·The KPI page now shows the whole journey: how many applications reached screening, interviews, offers — and the median days spent in each stage. Percentages appear only once there is enough data for them to mean anything.
• ·Every resume is tagged with how it was generated, so once enough applications resolve, the page can tell you which resume approach actually gets conversations. Until then it honestly says “collecting”.

The number beside Messages now tells you what kind of message arrived, not just how many — and there is a searchable guide to everything the product does.

• ·Amber means an employer, cyan means your specialist, violet means a notice from us. Several kinds waiting shows small dots so you can tell which, without opening anything.
• ·Nothing is shown when nothing is unread — the badge appearing means something genuinely arrived.
• ·Help now has a searchable guide covering every feature. Search the words you would actually use: “stuck”, “captcha”, “delete my account”.
• ·Replying to an employer from Messages works again — replies had been failing to send, and now keep the conversation threaded properly on their side.

Employers close postings without warning. When that happens you now see it said plainly, instead of a failure that looked like something had gone wrong on our side.

• ·A job that has been removed is recognised in about a second and labelled as closed, rather than timing out.
• ·A run of closed postings no longer pauses automatic applying — it used to look like a fault and stop the jobs queued behind them.
• ·You are not notified for these. A posting being taken down is not something you need to do anything about.

When the other person asks you something, the shape of an answer appears on screen — which of your experiences to reach for, and the two or three beats to hit.

• ·Turn it on with its own tick when you start a recording. It is off unless you choose it, and only for that one interview.
• ·It reads only the other person’s side of the call, only while you are recording, and none of it is kept.
• ·It writes the framing itself, drawing on your résumé and saved answers — but it will not put a number or a company in front of you that is not already yours.
• ·If nothing of yours fits the question it still helps, with a structure to fill rather than nothing at all.
• ·Withdraw permission at any point and it stops sending immediately.
• ·The panel shows how long each answer took to arrive, so you can judge for yourself whether it is fast enough to be worth a glance.

After an interview is transcribed, you now get a written review of it: what you were asked, what you said, what either side promised, and what to do next.

• ·Every question you were asked is listed with the time it came up, so you can jump straight to that moment in the recording.
• ·Your answers are scored against the same criteria the Rehearsal Studio uses, so practice and the real thing are directly comparable.
• ·Anything you did not really answer is called out — and those questions are added to your future practice sets, so you get another go at them.
• ·Commitments are recorded: what they said they would send you, and what you said you would do.
• ·A follow-up note is drafted for you, referencing something you actually discussed. It is a draft — nothing is ever sent for you.
• ·You can record how each interview turned out, which is what lets your dashboard show which kinds of interview actually convert.
• ·Phone interviews are supported properly: choose "a phone call" and you will not be asked to share a screen there is no point sharing.
• ·You can upload an interview you recorded somewhere else — a voice memo, a Zoom export — and it goes through exactly the same steps.
• ·We do not predict whether you will be hired, rate you as a candidate, or assess your personality. The review records what was said; it does not judge who said it.

You can now delete your account yourself, from Settings. It removes your files first and then every record we hold about you — and you have a week to change your mind.

• ·Settings → Account has a Delete your account section. You confirm by typing your own email address rather than clicking a dialog, because the mistake worth preventing is being on the wrong account, not clicking too fast.
• ·Deletion runs 7 days after you confirm, and you can cancel at any point during those 7 days. Until then nothing is removed.
• ·When it runs it removes your uploaded résumés, generated documents, employer messages and attachments, interview and practice recordings, and transcripts — the stored files first, then every record.
• ·Billing records are kept for 7 years because tax law requires it. That was already in the Privacy Policy; it is now also stated on the deletion screen itself, where it is actually read.
• ·Only the account owner can start or cancel a deletion.

Roles now come from employers well beyond the tech company boards — universities, banks, healthcare systems, government contractors — and each one is tailored from the full job posting.

• ·A broad job-market source that had been quietly returning nothing is now live. In its first hours it brought in over a thousand roles, from employers the company-by-company boards were never going to cover.
• ·Résumés and cover letters are written from the complete job posting. Previously, roles from that source arrived as a short preview — a few hundred words — and everything was tailored from that. The full text is now pulled in first, averaging roughly five times more to work from.
• ·Where only a short posting is available, the résumé review page says so plainly, so you know why a draft reads more generally than usual instead of guessing.
• ·A source that fails once mid-run no longer throws away everything it had already found.

Record an interview and get a transcript — with permission handled properly, because the other person on the call did not sign up for anything.

• ·Recording is per interview, never a setting you leave on. Permission expires after four hours and you can withdraw it mid-call.
• ·Before your first recording you are told the part that catches people out: in much of the world, recording a conversation is only lawful if everyone on it has agreed. You confirm you will tell them.
• ·A recording indicator stays visible the whole time, including in the browser tab title when you are looking at the call instead of us.
• ·Audio is transcribed on ApplyStorm’s own servers by default and deleted after 30 days. The transcript is kept for a year. You can delete either yourself at any time.
• ·Audio by default, with screen video as a separate opt-in that is off unless you tick it. You pick which tab carries the call and tick “Also share tab audio”; while you record, the panel shows which sources are actually live so you cannot end up with only your own half of the conversation.
• ·Audio recordings have no player and no download link — they exist to become a transcript, then they go. Where you recorded the screen, the video is playable on the transcript page, because a screen recording cannot be read as text.

Talk to the specialist working your applications, and read employer mail as conversations instead of a wall of messages.

• ·Messages is now two places: a private conversation with your specialist, and your employer mail. They are kept apart on purpose — a note to your specialist should never be one keystroke away from a reply to a hiring manager.
• ·When your specialist needs something before they can submit an application, the question now appears where the notification sends you, and you can answer it there. Answering it releases the application.
• ·Your specialist can see when you have replied, so a question you have answered stops holding things up.
• ·Your email is grouped into conversations, so a reply sits with the message it answers rather than somewhere else in the list. It covers everything that arrives at your application address — employers, recruiters, agencies and job boards — not employers alone.
• ·If more than one specialist works your account, every message says who wrote it, in one shared conversation rather than several you would have to keep track of.
• ·Unread mail is marked as unread, with a filter for it and a count on the tab. Opening a conversation marks only that one read.

Practise interview questions written from the job you actually applied to, answer them out loud, and get scored on what an interviewer would be listening for.

• ·Questions are generated from the job description, the résumé that was actually submitted for it, and your own match-score rationale — not from a generic question bank.
• ·Every question traces to a specific line in the posting or your résumé. Anything the system cannot trace is discarded rather than shown.
• ·Answer out loud. Recordings are transcribed on ApplyStorm’s own servers by default; audio is never sent to a third party unless you are explicitly moved to one.
• ·Each answer is scored against a rubric built for that question type — behavioural, technical, system design, case, and role-specific each get different criteria.
• ·Feedback cites its evidence. Every "what was missing" point quotes the phrase from your own answer that prompted it, so you can check it rather than take our word.
• ·Answers you are happy with can be saved to your Answer Bank and reused when filling out real applications.
• ·Practice mode allows unlimited retries per question; full mock gives you one attempt each, the way a real interview does.

Mail from employers now arrives in the product, is matched to the application it belongs to, and can be replied to without leaving the dashboard.

• ·Each account gets its own address for applications, so replies come back somewhere the product can see them.
• ·Incoming mail is classified — confirmations, rejections, interview invitations — and linked to the right application.
• ·Reply to an employer directly from Messages, with proper threading so it lands in the same conversation on their side.
• ·Attachments employers send are stored and downloadable, never opened or rendered in the browser.
• ·Correspondence is kept for 365 days and then deleted automatically.

A managed service line where a trained rep works your application backlog on your behalf — with your explicit consent, and a full audit trail.

• ·Nothing happens without you opting in first. Consent is required before any rep can see your material, and revoking it closes their access immediately.
• ·Every action a rep takes on your account is recorded and visible to you.
• ·Reps never see your EEO information; it stays encrypted and out of their view entirely.

Free and Pro tiers, with usage caps enforced in the pipeline itself.

• ·Monthly caps on applications, submissions and résumé tailoring, applied where the work happens rather than only in the interface.
• ·Trial codes for early access.