The Follow-Up Email Was Never the Hard Part. Knowing Which One to Send Was.

The message that pushed me into making templates was not dramatic. It was a DM from a college senior who had just finished a second-round interview and wanted to know whether "Thank you for your time" was too stiff, too late, too much, or somehow not enough.

That is the kind of question people think is small until it is their question.

When I worked around recruiting, I saw how much of job searching had nothing to do with whether someone was smart enough for the role. A lot of people were simply missing the invisible rules. How long do you wait before following up. How do you ask about salary without sounding difficult. How do you explain a gap year without turning it into a confession. How do you write back after an interview when every sentence feels like it might cost you the offer.

That is why my content started working. I do not make "career motivation" content. I make translation guides for rules that were obvious to people who grew up around office language and completely hidden to everyone else. A short Reel on how to answer "Tell me about yourself" for a first phone screen will do better for me than any generic productivity tip because the person watching is not looking for inspiration. They are trying to get through Thursday.

The comments tell me exactly where the pressure lives. Someone wants the follow-up email script. Someone else wants the salary negotiation checklist because they got the verbal offer and are suddenly terrified of sounding ungrateful. Another person wants the "gap year" answer frame because their parents are proud of them, they are scared, and every version they have typed sounds worse than the last one.

For a long time I handled those requests the way a lot of creators do when they care too much and systemize too late. I kept everything in Google Docs with names that made sense only to me. "Follow-up v3 final." "Negotiation script cleaner one." "Interview kit newest." Then a Reel would take off at exactly the wrong time, usually while I was doing client calls or halfway through the kind of admin work that makes you hate every notification sound. I would open Instagram after dinner and find thirty people asking for the same script, twelve more asking for the other one, and three who had replied again because their interview was the next morning.

The bottleneck was never writing the email. I already had the material.

The bottleneck was getting the right script to the right person while the moment still mattered.

That changed the way I think about Instagram. The comment is not the win. The comment is just the hand raise. If someone types RATE, or FOLLOWUP, or SALARY, they are not engaging for fun. They are asking for the next step while their nerves are still hot. If I send the script right then, it gets used. If I send it five hours later, they may already have guessed, panicked, or stayed quiet when they should have replied.

So my setup with StarLovin is intentionally plain. Someone comments FOLLOWUP, and the interview thank-you script lands in their DMs. SALARY sends the negotiation checklist. GAP sends the short answer framework for explaining a nonlinear resume without sounding defensive. I am not trying to build a giant funnel out of this. I am trying to make sure the person who asked for help at 9:12 p.m. gets the document before they talk themselves out of using it.

There is one category I do put behind an email gate: the fuller job-search kit. That one includes interview prep notes, follow-up scripts, a salary conversation framework, and a 30-60-90 day question list. It is more useful when I can send related updates later, especially when I publish a new script or revise a section based on what people keep running into. So StarLovin collects the email in the DM, validates it, and saves the contact. That is not because I want to turn every nervous job seeker into a marketing asset. It is because some material works better as an ongoing thread than as a single dropped link in a crowded inbox.

The part I still do myself is the part that actually requires judgment.

If someone says, "I got an offer, but it is from a company where I would be the first person in my family to work in that environment, and I do not know if the manager's tone is a red flag or if I am overthinking it," there is no keyword for that. If someone sends me their exact gap-year story and asks whether it is better framed around caregiving, part-time work, or recovery, that is not a script-delivery problem. That is a person trying to figure out how honest and strategic they can be at the same time. Those are the messages I want waiting for me in Social Inbox, with the context of what template they first asked for, so I can reply like a human being instead of pretending a checklist can carry all of it.

That distinction matters to me. A good template should lower the threshold for action. It should not pretend to replace discernment.

The people who follow my account are often carrying more than a job search. They are carrying family expectations, money pressure, visa timing, burnout, and the weird loneliness of being the person who has to learn the rules while also performing them. I cannot automate reassurance. I cannot automate judgment. I definitely cannot automate whether a role is actually right for someone.

What I can do is make sure the script arrives before the opportunity goes cold.

That turns out to matter more than making the script perfect.