Every job search guide says the same sentence: follow up. It is good advice and almost useless as stated, because it treats following up as a trait. Some people are organised, some people are persistent, so some people follow up and the rest quietly do not. Building a peer product for the weeks after a layoff made that framing look wrong. The people who followed up were not more disciplined. They were the ones whose notes made the follow-up easy to write.
That sounds like a small distinction. In practice it changed what got built.
What was built
WUUUH at https://wuuuh.com is a peer community for people rebuilding after job loss, and the part of the build this post is about is the unglamorous layer underneath the community: a search log that treats every application as a record worth keeping properly the first time.
Each entry holds the role, the company, the date applied, the exact version of the resume that was sent, the posting text saved before it disappears, and one line on why this role looked like a fit. None of that is clever. The point is what it makes possible two weeks later. A follow-up written from that record takes four minutes, because the writer is not reconstructing anything. A follow-up written from memory takes forty minutes and usually does not get written at all.
Three choices mattered most. First, the posting text is saved at application time, because postings vanish and a follow-up that references the actual wording of the role reads differently from a generic check-in. Second, the follow-up date is set when the application is logged, not remembered later. A date chosen in advance survives a bad week. A date left to memory does not. Third, the log keeps silence visible. An application with no reply after the agreed window is shown as exactly that, plainly, so the next step is a decision rather than a worry.
What broke
The first break was over-tracking. The early version of the log had fields for everything: recruiter name, salary band, commute, interview stage, a confidence score. People filled it in faithfully for the first five applications and then stopped logging altogether, because each entry had become homework. The fix was cutting the record back to what a follow-up actually needs. Everything else became an optional note. Logging went back up within a week, which said more about the design than about the users.
The second break was the reminder tone. Early nudges were written like a coach: cheerful, urgent, a little loud. After a rejection, that tone landed badly, and people muted the reminders entirely. The rewrite was plain and factual. This application has had no reply in fourteen days. Here is the record. Here is a short draft if you want it. Muting dropped sharply. People did not need motivating. They needed the task to be small and the wording to respect the week they were having.
The third break was subtler. A follow-up system can quietly turn into a scoreboard, and a scoreboard in week six of a search is a cruel object. Counts of applications sent started to stand in for progress even when nothing was moving. The log now leads with a different question: what is the next single action on the oldest open application? One action, named, finishable today. The totals are still there, one tap away, but they stopped being the headline.
What the numbers look like
The honest measure here is not applications per week. It is the share of applications that received any follow-up at all. Before the log, in early peer sessions, people estimated they followed up on maybe a third of what they sent, and the estimate was probably generous, because the ones they remembered were the ones they had followed up on. With the record doing the remembering, follow-up became the default rather than the exception, and the replies that came back, even the no replies, were more useful than expected. A short, specific follow-up referencing the posting and the date applied drew answers from recruiters who had gone quiet, including honest ones: the role was filled, the team was paused, the shortlist had closed. Each of those answers ended a thread that would otherwise have stayed open in someone's head for weeks.
There is a second number worth naming: time to write. Four minutes against forty is not an efficiency detail. It is the difference between a habit that survives a discouraging month and one that does not.
What stayed
Keep the record at application time, set the follow-up date before motivation is required, and let the system carry the remembering so the person only has to do the writing. None of that requires a particular personality. It requires a log that respects how a search actually feels in week three and after.
The lesson that survived every revision is simple: persistence is mostly logistics. Build the logistics well and ordinary people follow up like organised people, because the organised part was never really about them.
