TransitionBinder Book a demo

Home / About the author

Jimenez Julien, the person behind TransitionBinder

Founder of MLJ, SASU, and the one who answers the email when a coach writes at 9 p.m. because a summary export will not attach.

Portrait of Jimenez Julien
Role
Founder and product lead, MLJ, SASU
Focus
Software for independent practices in family transition work
Reach him
jimenezjulien42@gmail.com

Why this product exists

TransitionBinder started with a conversation I did not expect to turn into software. A divorce coach in Rhode Island described her Sunday routine to me: she would clear the kitchen table, empty a paper accordion file, and rebuild a client packet from scratch because the attorney had asked for one and there was no single place the documents lived. She had been coaching for eleven years. She was excellent at the work. And roughly a fifth of her working life was spent reassembling things she had already touched once.

That is a structural problem, not a discipline problem, and I have seen the same shape in other trades. The file is not messy because the practitioner is careless. It is messy because documents arrive through channels the practitioner does not control: a photo by text, an attachment from an ex spouse's attorney, a portal download that expires, a form the client filled out on her phone in a parking lot. Every one of those arrives at a different moment in a different format, and no calendar or note tool is built to catch them and hold them together.

So I built the binder. Not a CRM with a documents tab bolted on, and not a case management suite aimed at law firms with a paralegal to run it. A binder: dividers, a deadline list with a name on every line, a dated log of what the client decided, and one export that turns all of it into something counsel can read without asking questions. The product does one job, and it is the job that eats the evenings.

Experience and expertise

I have spent my working life building small, durable software for people who run their own businesses, and MLJ, SASU is the company I publish it through. My background is product and engineering rather than family law, which is exactly why the design work started with listening instead of assuming. Before writing a line of the binder, I sat in on intake calls, read anonymized packet structures, and asked two family law attorneys what they actually want to receive from a coach. The answer was consistent and unglamorous: an index, a date, and a clear statement of scope.

What I learned about this trade shaped the product more than any competitive analysis could have. Divorce coaches and family mediators work at the point where administrative failure has emotional consequences. A missing statement is not a missing statement, it is a delay in a hearing, which is another six weeks in a living situation someone is trying to leave. That is why deadlines here carry owners and escalation windows rather than a simple due date, and why reminders are worded plainly enough for a client who is reading them in a hard week.

I also learned where not to go. Coaches were clear that they do not want a tool that starts drafting language for them, because the moment software suggests a position, the scope line between coaching and legal advice gets blurry. So TransitionBinder organizes and records. It does not advise, it does not generate arguments, and it puts the scope banner on the cover of every summary it produces.

How I work with operators in this vertical

Every practice that joins gets a real conversation with me or with someone on the team who has done the migration work before. We open a binder from one of your live files during the call, because a demo built on invented data proves nothing. After that, I read every support message myself. When a coach in Boise tells me the parenting divider is in the wrong order for how mediation actually runs in her county, that goes on the list, and I write back with a date.

How this product is built and maintained

The editorial and product standards here are simple and I hold myself to them. Every number on this site comes from our own usage records or from practices that agreed to be quoted, and if a figure changes, the page changes. Testimonials are from named people at named businesses who read their quote before it went up. We do not publish a feature until it works for the whole caseload, not just the demo file. Client content is never used to train models, never sold, and never shared with a third party for advertising.

Releases go out on a predictable rhythm and anything affecting your data is announced before it ships, not after. Security work is not treated as a project with an end date: encryption in transit and at rest, per binder access logging, and seat level restrictions are core behavior, and the access log cannot be edited from inside an account, including by us. If something breaks, we say what happened in plain language and what we changed so it does not happen again.

I am accountable for all of it: the accuracy of what this site claims, the availability of the service, the handling of the files inside it, and the answer you get when you write in. That accountability has a name and an email address on every page, which is not something you can say about most software your practice depends on.

Published articles

Everything I have written for The Divorce Practice, the TransitionBinder magazine for divorce coaches and family mediators, is listed here in the order it was published.

Contact the author

Questions about the product, the roadmap, a migration, or something on this site you think is wrong: write to jimenezjulien42@gmail.com. Requests for a demo are better placed through the request form on the home page, because it gathers what we need to make the call useful.

TransitionBinder is published by MLJ, SASU. Read the legal notice or return to the home page.