Ghost Writer

See what Ghost Writer gives you

This is the complete, real output from an actual Ghost Writer run on the sample notes below — nothing here is invented or shortened.

Sample notes (job recommendation, professional tone)

Letter for Jordan Kim (she/her), job recommendation, professional tone. Traits: leadership, communication, initiative, technical skills. I managed Jordan for 3 years as a product manager. She stepped in during a hiring freeze to run a stalled project with no formal authority over the engineers, and delivered it on time — two engineers later asked to work with her again. She also drove an onboarding redesign across design, engineering, and data that cut drop-off by 34%, run in a way that left every stakeholder feeling heard. Fintech startup context.

Real run, 2026-09-23 — the tool's own built-in example scenario, Narrative style.

The letter (narrative style)

There is a moment I think about when someone asks me what kind of product manager Jordan Kim is. We were eight weeks into a hiring freeze, a critical project was stalled, and the engineers assigned to it had no formal PM support. Jordan stepped in. She had no direct authority over the four engineers on that team — no reporting line, no leverage — and she never seemed to need it. She ran standups, cleared blockers, kept the roadmap honest, and delivered the project on time. I found out later that two of those engineers had specifically asked to work with her again. I managed Jordan for three years, and I will say plainly: her resume does not capture what she actually is. What she is, is someone who makes the people around her better — and does it so quietly that you only notice it when you look at what the team produced. The onboarding rebrand is another example worth naming. Jordan identified that our activation funnel was losing users at a rate that had become structural, not incidental. She drove the redesign of the onboarding flow end to end — working across design, engineering, and data — and the result was a 34% reduction in drop-off. What I remember most is not the number. It is that she ran the project in a way that left every stakeholder feeling heard. Nobody felt steamrolled. The outcome was significant; the process was clean. Jordan is also the person you want when something goes wrong. She does not perform calm — she is calm. In [NUMBER] years of managing product teams, I have worked with very few people who can hold a room steady during a real crisis without losing the thread of what needs to happen next. She is one of them. She is ready for a senior role. More than ready — she has been operating at that level for some time without the title. I would hire her again without hesitation, and whoever brings her in next will benefit from something that does not show up in a job description: a person who makes the work around her better, every time.

Personalize these parts

• Add the name of the project the engineers asked to work on again, if you recall it.
• Replace [NUMBER] with your actual years managing product teams.
• If there is a specific crisis moment you witnessed firsthand, name it — even briefly.

Fill in these details (3)

• [SPECIFIC CRISIS OR INCIDENT] — name the actual high-pressure event you have in mind (a launch that nearly failed, a sudden stakeholder shift, a production incident) so the reader sees a real situation, not a category.
• [WRITER'S CONTACT INFORMATION] — add your direct email and, optionally, a phone number if you are open to a call.
• [name of the onboarding project or product] — if the project had an internal name or the product line is something you can mention, adding it makes the claim verifiable.

Power phrases

• “She managed by earning trust, staying organized when the situation was not, and making sure credit landed where it belonged.”
• “She spent the first weeks of that project making sure the engineers and designers felt heard before she proposed a single solution.”
• “She calibrates without being told to.”
• “Her steadiness in those situations set the tone for everyone around her.”
• “Whoever hires her will benefit not just from what she delivers, but from what she draws out of the people she works with.”

Writing tips

• The 34% drop-off stat is your strongest hard evidence — make sure it appears early enough to anchor credibility, not just as a footnote.
• Avoid adding any accomplishments Jordan did not tell you about; the letter is already compelling without invention.
• Read it aloud once before sending — any sentence that sounds like a press release should be rewritten in your own voice.
• The fintech startup context rewards specificity about cross-functional coordination and comfort with ambiguity; both are already in the letter, but you can amplify them if you have a concrete example from a scrappy or under-resourced moment.

What happens with your notes

Give Ghost Writer the relationship, destination, and real examples you remember. It turns your evidence into a polished draft — in narrative, structured, or concise style — while keeping every claim grounded in what you actually supplied, and flags exactly what still needs filling in before you send it.

This is a real, complete tool run against realistic sample notes.