Every package, five documents
What you get for one posting.Built from your history, nothing invented.
Paste a posting, and Second Reader builds all five from the resume you uploaded. Every one passes the integrity check: claims the reviewer can’t find in your history are removed, and anything the posting asks for that you haven’t done is repositioned onto real experience or left out. The samples below are a fictional applicant.
Not a template. Your real history, reordered and reworded for one posting — the language the ATS scans for, the results a human wants to see.
- —Built from your uploaded resume and nothing else
- —Keywords from the posting appear where you actually did the work
- —Anything the reviewer can't find in your history is struck out, and you see what was removed
- —ATS score and report with every package; PDF download
Demand generation leader with six years building B2B SaaS pipeline programs. Grew qualified pipeline 2.4x in 12 months by pairing ABM with a rebuilt lifecycle nurture; owns budget, attribution, and the sales handoff.
Demand generation · ABM · Lead scoring · HubSpot · Salesforce · Attribution · Paid media · Events
Demand Generation Manager — Fernwood Analytics, Austin, TX (2021–2026)
• Built multi-channel demand generation programs that grew qualified pipeline 2.4x in 12 months.
• Partnered with a 12-person sales team on lead scoring and SLA definitions; cut lead-to-meeting time from 9 days to 3.
• Owned a $1.1M budget across paid, ABM, and events; cut CAC 18% year over year.
• HubSpot and Salesforce administrator; shipped weekly attribution dashboards used by the CRO.
Fluent in Mandarin removed — not in your history
Led a team of 40 removed — not in your history
The posting's requirements, one per row, with why each one matters to them and exactly where you meet it. Every row is a strength, evidenced from your own history — nothing in it works against you.
- —Every requirement pulled from the posting, not a generic list
- —Proof column cites your actual roles and numbers
- —No weakness rows: a missing tool becomes the adjacent tool you actually run
- —Spreadsheet download (XLSX) you can attach or paste into an email
| Job requirement | Why it matters | How they meet it |
|---|---|---|
| 5+ years B2B demand generation | Pipeline is the job. | 6 years; grew qualified pipeline 2.4x. |
| HubSpot + Salesforce | Their stack. | Admin on both; built attribution dashboards. |
| Manage a $1M+ budget | Accountability for spend. | $1.1M across paid, ABM, events; CAC −18%. |
| Regulated-buyer experience | Long cycles, compliance sign-off. | 3 years selling analytics into financial-services compliance teams. |
Four short paragraphs that answer the posting instead of introducing you. It names the problem they're hiring for, shows the one result that proves you've solved it, and closes on a specific ask.
- —Opens on their problem, not your career summary
- —One proof point with real numbers from your history
- —Never lists what you lack — it points to the closest real thing you have done
- —Letter-formatted PDF with your contact details
Northwind's posting asks for someone who can turn a demand engine from campaign-led to pipeline-led. That is the work I have done for the last five years, and it is the reason I am writing.
At Fernwood Analytics I rebuilt the lifecycle program around account-based plays and a shared lead-scoring model with sales. Qualified pipeline grew 2.4x in a year, CAC fell 18%, and the CRO started reading my attribution dashboard before his own. The posting's emphasis on HubSpot and Salesforce fluency matches how I work day to day; I administer both.
Selling into regulated buyers is where the Fernwood playbook came from. Legal and compliance sat inside every deal cycle, so sales and I built the lead-scoring model to survive that review, and the attribution dashboard had to hold up to an auditor before the CRO ever read it. That is the repeatable part, and it travels.
I would welcome twenty minutes to walk through the Fernwood playbook and where it would and would not apply at Northwind.
Dana Reyes
Most applications ask for it and most people write it last, badly. This one is written from the posting and your history together: what is specific about the company, why the timing suits you, and what you'd want to work on there.
- —150–250 words, ready to paste into the application form
- —Specific to the company's stage and the posting's language
- —Specific to this company's stage, anchored on work you've already done
- —Word document (DOCX) download
Northwind is at the stage I like most: the product is proven, the sales team is real, and the demand engine has not caught up yet. The posting reads like a team that wants pipeline it can defend in a board deck, not campaign vanity metrics. That is the exact problem I solved at Fernwood, and I want to do it again where the buyer is a health system and the review cycle is longer.
A short note to the hiring manager or recruiter, written to be read on a phone. Applies the same rule as everything else: two proof points and one ask.
- —Under 120 words; subject line included
- —Names your single strongest match to the posting
- —Two proof points, one ask
- —Copy-paste ready; Pro and coach plans
Hello Priya,
I recently applied for the Demand Generation Manager role at Northwind and wanted to reach out directly.
Short version: at Fernwood Analytics I grew qualified pipeline 2.4x in 12 months on a $1.1M budget, running HubSpot and Salesforce myself. Northwind's posting asks for exactly that mix.
One more number, the lead-scoring model I built with that sales team cut lead-to-meeting time from nine days to three. Fifteen minutes and I can show you how it was built.
I've included a job matrix for the role that maps each of your requirements to my experience.
Thanks for reading, Dana Reyes · dana.reyes@example.com
First one is free