About Jimenez Julien, Founder of PaperKeepsake

Why I built a tool for photo organizers

PaperKeepsake started in a dining room in 2023, on a table covered with someone else's grandmother. A friend of the family had been hired to sort a house full of prints, slides and loose negatives, and she was doing brilliant work with a legal pad, a kitchen timer and a spreadsheet with forty two columns. What struck me was not the volume. It was how much of her expertise was being spent on bookkeeping that had nothing to do with photographs: which box she was in, which folder the assistant had exported, whether the count on page three still matched reality.

I asked to sit with her for a week. By the third day I had filled a notebook with the vocabulary of the trade: containers, batches, derivatives, circa dates, provenance notes, the difference between a client and the adult child who actually pays. By the end of the week I understood that the profession did not need a photo editor, a cloud drive or another general purpose project tracker. It needed a record of a client archive project that matched the physical reality on the table, and that could turn that record into something a family could read.

So I built the first version around four objects that already exist in every practice: the container, the batch, the person and the date. Everything else in the product hangs from those. The container is what the client hands you. The batch is what goes through the scanner. The person is who appears in the frame. The date is the honest answer, including the ranges and the guesses marked as guesses. Once those four things live in one place, the index, the reconciliation, the intake sheet and the profitability report all fall out of the same record instead of being assembled by hand at midnight.

What I learned about this trade

Three things, and they shaped the product more than any feature request did. First, organizers are not disorganized. They are running a manufacturing line with irreplaceable inputs, and every workaround they use exists for a reason worth understanding before you replace it. Second, the hardest part of the job is not scanning, it is identification, and identification happens in conversation with a client who is often elderly and often grieving. Software that interrupts that conversation is worse than no software. Third, the deliverable is not a hard drive. It is the moment a daughter finds her father at nineteen and can tell you where he was standing.

How I work with organizers

Every walkthrough I run uses a real project from the person on the call, not a demo account full of pretty sample images. I sit in on intake days when I am invited, and I read every support message myself. When an organizer tells me that a rescan queue does not match the way her assistant works, that goes into the notes and usually into a release within a few weeks. I have no sales team, so nothing gets promised in a call that engineering has not already agreed to build.

What I am accountable for

Uptime, export integrity and honest pricing. If a catalog export is incomplete, that is a defect I will fix at any hour. If a price changes, existing customers hear it from me before it appears on this page. And if PaperKeepsake is not right for your practice, I will say so on the call rather than sell you a plan you will cancel in March.

Experience and expertise

Eleven years building and shipping web software for small operators, working solo and in small product teams.
Founder of MLJ, SASU, the French company that publishes PaperKeepsake and handles its billing and support.
Direct field observation of client archive projects across print, slide, negative and album formats.
Working knowledge of IPTC Core, XMP and the metadata practices archivists rely on for long term description.
Hands on with consumer and production scanning hardware, including feed scanners used for high volume print work.

How this product is built and maintained

Releases go out on a fortnightly cadence, with a written changelog sent to every account. Nothing ships to customers without a restore test of the backup path first, because the material in these projects cannot be recreated. Copy on this site is written by me and reviewed against the product before publication: if a sentence describes something the software does not do today, it does not go up. Statistics quoted here come from anonymized aggregates of accounts in the system, recalculated each quarter, and I remove any number I cannot still defend.

Support is answered by a person, usually within one business day and always by someone who can read the code. Feature requests are logged publicly to the account that asked, and declined requests get a reason rather than silence. Security updates are applied within seventy two hours of a supplier advisory. No customer image is used for training, marketing or any purpose other than delivering the project it belongs to.

Contact the author

Write to jimenezjulien42@gmail.com with a question about a project, a pricing decision, a bug or a request for a walkthrough. If you would rather see the product on your own containers first, use the enquiry form on the home page.

Jimenez Julien, the person behind PaperKeepsake