Proofly

Turn what you did into proof.

Paste your raw work — tickets, commits, emails, wins — and get achievements you can use.

Import from GitHub

Your achievements

Example
  1. Rebuilt checkout pricing lookups behind a shared cache, cutting median checkout time from 1.3s to 0.8s (−38%) and p95 from 4.1s to 2.2s while closing 17 related timeout tickets.
  2. Wrote the cache-invalidation runbook and trained the on-call rotation on it, so cache incidents are resolved by whoever is on call rather than one engineer.
  3. Onboarded two new engineers by pairing on their first production tickets, getting both shipping independently within [N weeks], and reviewed about 40 pull requests for the payments squad.
    Needs a number: How many weeks until each new hire shipped their first change on their own?

This is the example's result. Paste your own notes and press “Write my achievements”. Click any line to edit it.

Turn all of it into a finished document.

A Proof Pack writes 8–15 achievements from everything you paste, then the document you need. Your notes come with you.

What a Proof Pack contains

Every line comes from your own notes. Sample lines below are written from the example above.

01

Resume achievements section

Five to eight bullets, ordered for the job you're going for.

Cut median checkout time 38% (1.3s → 0.8s) by moving cart pricing behind a shared cache; closed 17 timeout tickets in the process.
02

Performance review self-assessment

Your self-assessment, written in your voice, ready for the review form.

My biggest result this quarter was checkout speed: after I moved pricing lookups behind a shared cache, median checkout dropped from 1.3s to 0.8s.
03

Promotion case

The case your manager takes into the promotion discussion.

Ready for the next level: found, fixed and documented the team's largest checkout bottleneck, then trained the on-call rotation to own it.
04

Freelance case study

A portfolio case study a prospective client can read in two minutes.

The challenge: carts were timing out at peak. What I did: moved pricing lookups behind a shared cache. The result: p95 checkout fell from 4.1s to 2.2s.
05

Client proposal — proof section

The “why me” section you drop into a client proposal.

I've done exactly this before — on a live checkout I cut median response time by 38% and turned the fix into a runbook the whole on-call team uses.
06

LinkedIn achievements

An About paragraph, experience bullets and one post.

Faster checkouts are a revenue feature. This quarter I moved our pricing lookups behind a shared cache and median checkout time fell from 1.3s to 0.8s.

Notes

What to paste

Anything that shows work happened: ticket titles, commit or pull-request lines, release notes, a status update, a thank-you email, a before-and-after number from a dashboard. Rough bullet points are fine — messy is expected.

Numbers are never invented

Proofly only uses figures that are in your notes. Where a statement needs a number you haven't given, it leaves a highlighted gap like [X%] and tells you what to measure.

Privacy and limits

The free writer doesn't store your notes on our side; your browser keeps your draft. Packs live in your private account, and you can delete your account and data from Settings at any time. The free writer takes up to 6,000 characters; a pack takes up to 20,000.