Log what you did
A line or two a day. Freeform, voice, whenever. AI tags the project, the tech stack, the impact.
Most people rebuild their resume from memory once a year and quietly lose four years of good work. Write down what you did today — the rest is our job.
Free to use. No card. Your journal is encrypted, never sold, never used to train anything.
The journal is live and free. Resume building, tailoring and job matching are being built in the open, and the changelog is the honest record of what has actually shipped.
Writing now is the point. Everything later is built from what you write today, so an empty journal in six months is the only thing that cannot be fixed.
Two minutes of setup, then it is two sentences a day.
A line or two a day. Freeform, voice, whenever. AI tags the project, the tech stack, the impact.
A structured master profile built from real entries — not from what you can remember in March.
Paste a job description. Every line in the tailored version traces back to something you actually logged.
Matched roles arrive daily. Found, tailored, applied, interview — each linked to the exact resume you sent.
You write two sentences about today
That's the entire ask. Voice works too.
Your record builds itself
Tagged, searchable, numbers kept while they're fresh.
Every application gets a true, tailored resume
AI rephrases your facts — it never invents.
You watch the pipeline, not a spreadsheet
Every role linked to the exact PDF it received.
No templates to pick, no fields to configure. Open it, write a line, close it. The structure is built from what you wrote, not asked for up front.
Start your journalThe number you hit today is gone by Friday unless you write it down before you get home. So the app opens straight into the composer, the optional fields are one tap away, and logging something takes about as long as sending a text.
Both builds are in review. Start on the web today — the journal is the same one, and it will be waiting when the app lands.
The tailoring engine can only rephrase facts that already exist in your journal. It cannot add a framework you never used or a number you never hit. If a claim can't be traced to an entry, it doesn't get written — which is the only way to walk into an interview able to defend every line.
↑ the entry behind the bullet, kept and shown
No, and that is enforced in code rather than asked for in a prompt. Every generated line has to cite the journal entry it came from, and output that cannot name a real entry is rejected before you ever see it. It is the difference between a promise and a property of the system.
You. Access is enforced inside the database with row-level security keyed to your account, so a forgotten filter in application code cannot leak someone else’s entries — the database refuses. It is tested in both directions: the owner reads their row, a stranger reads zero. Entries are never sold and never used to train models.
Two sentences. Skip the weeks where nothing happened. There are no streaks, no reminders and no score, because a journal you feel guilty about is one you stop keeping — and an empty journal is the only thing here that cannot be fixed later.
The journal is free and stays free. You pay only when you are actually job hunting, and the limits are visible in the product before you hit them rather than after.
Yes. It is your writing. Export is plain text and JSON, with no lock-in and nothing held back to make leaving harder.
iOS and Android, sharing one codebase with the web app. The phone is where most entries actually get written — on the way home, while the number is still fresh.
Two sentences about what you did. In eight months it is a resume bullet you can defend in an interview, because you wrote it yourself.
No streaks, no reminders, no guilt. Write when something happened.