Hiring teams at product companies read the same sentence over and over: "I have been using your product for a long time and I love it." It tells the reader nothing they can act on. The fact underneath it, that you genuinely use the thing they build every week, is the strongest personalization asset most applicants will ever hold, and nearly all of them spend it on one empty line.
It matters because it cannot be copied. Anyone can read the funding announcement and the engineering blog the night before. Nobody else can produce your last eighteen months of Tuesday mornings inside that product.
Lived use is not desk research
There is a separate job, researching a company before you write, and it means reading the changelog, the pricing page, the last three job postings, the founder's conference talk. That work is real and it has its own article. This is the opposite direction. Research pulls information in from outside the product; lived use is data you already own and could not have crammed the night before. The two do not compete, but they are not interchangeable, and the second one is far rarer in the pile.
What actually counts as evidence
Five concrete things turn "I use it" into something a reader believes.
- The workflow, named. Not "I use your product." Instead: "I run our freelance invoicing in it, one database, twelve contractors, closed on the last Friday of the month." A workflow has nouns in it. A compliment does not.
- The duration, anchored to a date. "Since March 2023" beats "for a while." A date is checkable, and it sets the weight of everything else you say.
- What you switched from, and why you stopped. The previous tool, the spreadsheet, the manual process, and the specific thing that broke.
- A moment it changed how you work. One before-and-after, small enough to be true. "I used to schedule a call to review drafts. Now I leave comments and the call does not happen."
- One friction point you have actually hit. The detail that proves the other four.
Most letters contain a version of nothing on this list. If you write even three of the five, you are already in unusual territory.
The switch story is the part they read twice
Every product team argues internally about why users leave the competitor. They have analytics on churn, and analytics give them the timing, not the reason. When you write that you moved off a shared spreadsheet after the same file got overwritten twice in one quarter, you hand a real reason to the person reading. That is the rare cover letter paragraph that is useful to the reader before you are hired.
Be precise about what you left. Naming the competitor is fine and usually welcome; saying the competitor is garbage is not, because half the team probably worked there. Describe the breaking point, not the verdict.
The friction point, handled carefully
This is the sentence that proves the rest of the paragraph, and it is also the one that can sink you. Anyone can praise from the homepage. Only a user knows where it rubs.
- Keep it to one. Two friction points read as a list of complaints from someone who has not been offered the job yet.
- Make it operational, not strategic. "It took me a month to find the bulk export, I kept looking in the wrong menu" is a user detail. "Your pricing is too aggressive for teams our size" is a verdict on a decision someone in that building fought hard for.
- Report what happened, not what they should do. You are not auditing them. You are showing that you were close enough to the product to bump into an edge.
- Say what you did instead. The workaround is often the most interesting half of the sentence.
The trap is obvious once you name it: you are writing to the people who built the thing. If your instinct is to explain how you would rebuild their onboarding, hold it for the interview, where you have actually been invited to have opinions. A letter that grades the product reads as arrogance from someone who has never seen the constraints.
How much of the letter this deserves
One paragraph. Four or five sentences, inside a letter that still has to argue you can do the job. That is the whole judgement call, and it is where people who follow this advice most enthusiastically go wrong.
If your use of the product takes half the page, the letter argues that you are an excellent customer. Nobody is hiring for that.
A shape that works: one paragraph on why this company, built entirely from lived use, one or two on the work you have done that maps to the role, and a short one on what you would want to get done in the first months. The use paragraph buys attention. The rest earns the interview.
Enthusiasm versus a user report
Register decides how this lands. Compare two openings. "I am so excited about what you are building and would love the chance to contribute." Versus: "I have run our month-end close in your product since March 2023, and the reason I stayed is the audit trail, which the tool I left never had."
The first is a feeling. The second is a report. Gushing reads as junior because it is what a person writes when they have nothing else to put in the paragraph, and readers know that. Cut the superlatives too. "The best tool I have ever used" cannot be checked and everyone says it, so it lands as noise.
There is a version of this that works for actual juniors, and it is not less enthusiasm but more specificity. A student who used the free tier to run a club's budget for two semesters has a workflow, a duration, and a switch story. That reads as a user, not a fan.
When the customer is your employer, not you
Business-to-business changes the material, usually for the better. You may have been the admin who rolled the tool out to forty people, the one who wrote the internal how-to, the one who filed the support tickets, the one who defended the renewal to finance. That is stronger than consumer use, because you saw adoption, training, and the objections people raised before they came around.
Two cautions. Do not leak commercial terms: not the discount, not the contract value, not what your finance director said during the negotiation. It is your employer's information and repeating it tells the reader exactly how you will treat theirs.
And if you are currently the account owner on your employer's account, say so plainly in the first line of that paragraph. They will see it in their own CRM within minutes of your application landing. "I am the administrator on our account, which is part of why I am writing" is a clean, slightly bold sentence. Being discovered after the fact is neither.
What to do before you write the paragraph
Open your own account, not their marketing site. Find the signup date in your billing history. Find the feature you touched most in the last month. Write down the name of the tool you stopped paying for when you started paying them, and the specific thing that made you stop. Then write five sentences containing those facts and not one word about how passionate you are.
A tool like Postulit can turn your LinkedIn history into a formatted CV in a couple of minutes, which handles the mechanical half of the application. This paragraph is the half nothing can generate for you, because the source data is in your account and your own memory of a Tuesday morning that went better than usual.