Most cover letters are the resume with different formatting, which is why nobody reads them. This method builds the letter from the same evidence and spends it on the one claim a resume cannot make.
A paragraph of duties from a slightly different angle reads worse than no letter at all, because it spends the reader's patience restating what they just finished reading.
A cover letter is not read carefully. It is scanned for one thing — why this person, for this role — and if it does not surface that in the first two sentences it is skimmed for the name and signed off. A letter that summarises your career has spent its only moment of attention on information the reader already has.
Almost every generated cover letter is a prose version of the resume: same roles, same duties, slightly reworded, with a paragraph about being enthusiastic. It reads as padding, and it makes the resume look redundant rather than reinforcing it. What makes a letter worth reading is material that is not in the resume at all.
A tool that invents a figure on a resume gets caught in a technical interview. A tool that invents enthusiasm, motivation, or a reason for wanting the role gets caught in the first human conversation, and it is much easier to catch, because the reader already has their own motive in mind and yours is visibly borrowed.
Copy it into Zaira with your resume and the posting. It finds the gap between what you have and what they need, then spends the whole letter on that gap.
Three outcomes, one loop. You get a letter worth reading rather than skimming, every claim in it traces to your resume so you cannot be caught out, and you stop resending one letter to every posting.
Step 1 finds the one requirement where the posting wants more than your resume shows, and the letter is about that. It is the only part of an application a resume structurally cannot deliver, so it is the only thing worth a reader's second look.
Step 2 collects the material a resume cannot carry — what you did that you left out, why this role, what you want next — and refuses to invent any of it. Invented motivation is the easiest thing for a human reader to catch and the hardest to recover from.
Step 4 removes any paragraph that could go without losing something the resume does not already carry, and Step 6 caps the letter at 220 words. The length is enforced rather than suggested, which is what stops the output drifting back into a prose resume.
The questions people ask before trusting an agent with a document that gets read by a human.
Much less often than the advice implies, and in most cases the honest answer is that the posting will not be read closely enough for a good letter to matter. It is worth writing when the role is one you actually want, when the posting names something specific you can address, or when a human is likely to read it — a referral, a small company, a recruiter who emailed you. For a high-volume application to a large employer, the time is better spent tailoring the resume.
No, and that is the mistake most generated letters make. The reader has just read your resume, so a letter that restates it in prose gives them nothing and spends the attention you were given. The letter should carry what the resume cannot: why this role, what you have done that the resume left out, and what you are looking for. Step 4 enforces this by deleting any paragraph whose removal loses nothing the resume does not already say.
It will if you let it, and the cause is that a tool asked to write a cover letter without your reasons will produce the one thing every applicant writes: enthusiasm. That is why this method asks you for your reasons in Step 2 and refuses to invent them, and why the opening has to earn its two sentences before the rest of the letter gets written. A letter with a specific reason in the first line does not read as generated, because a generated one cannot get there.
About two hundred words, and that limit is the most useful part of the constraint. The letter has one job — say why you, for this role — and that fits in a short opening, three short paragraphs and a two-sentence close. The practical effect of a hard cap is that it forces a choice about which evidence to use, and that choice is the whole reason a reader keeps going.
Then do not attach one, and the method's audit is still worth running because it forces you to answer the same questions before you submit the form. A surprising number of applications are decided in a free-text box that most people fill with three sentences of enthusiasm. The gap analysis from Step 1 is exactly what that box should contain instead, and it takes the same work.