Enterprise DNA

Instead of juniorPartner

Moving on from juniorPartner? Own the system your firm runs on.

We build your version around how your firm opens files, records time, chases debtors and keeps its diary, bring your juniorPartner history across, and look after it for you. Your trust account stays in a dedicated audited system.

juniorPartner publishes no price. It is bought module by module with a Maintenance and Support agreement on top, and firms changing to it are told to contact the vendor for a figure.

Get your version built See it working
  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

What the licence pays for

With juniorPartner you buy modules, then keep paying to stay current

Every client, file and time entry in juniorPartner was keyed in by your own staff. What the firm pays for is the module set that shows it to them, and the agreement that keeps that software updated.

request_quote

No figure until you ask

The website lists no prices at all. Its own advice to a firm thinking of changing over is to contact them for a price.

view_module

Five modules, bought one at a time

Time and invoicing, accounts rendered and GST, trust, management reports and mortgages are separate purchases. The management reporting partners want is its own module.

handshake

Updates tied to an ongoing agreement

Updates and helpdesk support are covered by the firm's Maintenance and Support agreement.

school

Training that runs out

Two hours of online training per module comes with the purchase. Onsite sessions and training for new staff are charged on request.

dns

A datafile on the office network

juniorPartner runs as installed Windows software sharing one datafile, and its technical page lists the machine settings that must be changed to avoid data loss.

logout

Help getting in, silence on getting out

The vendor offers to convert data from older systems into juniorPartner. Its pages say nothing about exporting your files and time history to something else.

What your firm gets instead

One place every partner can question

Diary

The diary that never forgets a date

Settlements, filings, hearings and limitation periods sit in one list with a daily countdown, alongside every undertaking a lawyer has given to another firm.

  • check Limitation periods always shown ahead of routine diary entries
  • check Each undertaking logged with its exact wording, the recipient and the due date
  • check A morning list of the files that need someone today, the riskiest first
  • check A file stays open until every undertaking on it is discharged

New files

Conflict checks on every new file

Each name on a new instruction is searched against every client and opposing party the firm has recorded, and the client care paperwork is tracked from day one.

  • check Searches cover closed files as well as open ones
  • check A hit holds the file until a lawyer records the decision
  • check Engagement terms, fee information and customer due diligence tracked on each file
  • check Every check points to the rule behind it

Lock-up

Unbilled work and debtors, without a reports module

Time goes in as people describe it, and the questions a managing partner asks about cash come back answered, without buying another module to see them.

  • check Unbilled time on each file, oldest entry first
  • check Lock-up per client: work not yet billed plus bills not yet paid
  • check Recovery per fee earner after write-offs, at the rate actually achieved
  • check An early warning when a file is heading past the client's estimate

Ownership

No datafile to babysit, no agreement to renew

Run it on one laptop with nothing to install, or on a shared database for the whole firm. The records stay readable by any tool, whatever happens to any vendor.

  • check No modules to buy: diary, time, lock-up and conflicts all come together
  • check Your juniorPartner clients, files and time mapped across by Enterprise DNA
  • check File types and stages named the way your firm already talks
  • check Open source under the MIT licence, with nothing to renew

Make it yours

Design your own juniorPartner replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from juniorPartner. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your juniorPartner replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your juniorPartner data across and run it for you.

Switching

How to switch from juniorPartner

A move like this involves checking what your juniorPartner installation can export, mapping the records you choose to bring, and reviewing them before you rely on the new system.

  1. 1

    Export your records

    juniorPartner does not publish an export process. Take the export while your Maintenance and Support agreement is current, and check with juniorPartner about what your installation can produce. Start with clients, files and time, then decide which history you need. Matters does not replace trust accounting, so keep trust records in a dedicated trust accounting system.

  2. 2

    Load a test import

    Map the records you have chosen to bring into Matters for Claude Code. The import supports plain CSV, and a test run is available before records are loaded for real. Have Enterprise DNA help identify which juniorPartner fields match the new records, then review the test before proceeding. Do not rely on an import until you have checked what came across.

  3. 3

    Review gaps and warnings

    Read the import results and follow up on anything flagged before relying on the records. Imported clients have no CDD date and imported matters have an empty client care file, so check what needs to be backfilled. Give diary dates and undertakings a careful pass by hand rather than relying on an import to get them right.

  4. 4

    Run both systems briefly

    Keep juniorPartner available while you use Matters for Claude Code on live work for a short period. Compare the records and work you rely on, including files, time, key dates and undertakings, and correct anything that is missing or mapped incorrectly. Keep trust accounting in its dedicated system throughout. Use this overlap to confirm the new setup fits your practice before you switch.

  5. 5

    Switch off juniorPartner

    Once you have checked the imported records and are satisfied that the new setup is ready for the work it is meant to hold, make Matters for Claude Code your practice system. Keep your dedicated trust accounting system in place for trust money. Do not switch off juniorPartner until you have confirmed that any work or records you still need from it have been dealt with.

construction

Where the real effort goes

The main work is usually mapping your own fields and rules, then deciding how much history to bring. Diary dates and undertakings need a careful manual pass, and you will need to review gaps such as missing client care information or CDD dates. If you have Enterprise DNA install and run Matters for you, Enterprise DNA handles the mapping and test import with you.

Not ready for a call?

Get your juniorPartner switch plan by email

We will send you the step-by-step plan for moving your business off juniorPartner, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Two ways to run it

Try the free version, or let us build and look after yours

Open source

Run it yourself

Free

  1. 1 Clone the repo from GitHub
  2. 2 npm run demo, then open the folder in Claude Code
  3. 3 Type /attention to see what the demo firm owes today
  4. 4 Point it at a shared database when the whole firm moves
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA build and run it

One setup fee, then a monthly retainer

  • check We map your juniorPartner history across and check the diary and undertakings with you
  • check We fit it to your practice areas, legal aid work and partner reporting
  • check We connect it to your email, documents and accounting
  • check It runs inside Omni, our managed Command Centre, beside the rest of your practice
Book a discovery call

Questions

Instead of juniorPartner, answered

juniorPartner runs our trust account. Does this replace that? expand_more

No, and on purpose. Trust money belongs in a dedicated, audited trust accounting system that meets the Law Society's trust account rules. You keep that job in a trust system built for it, and this holds the practice around it: files, conflicts, time, lock-up, diary dates and undertakings. We help you plan that split.

Can we get our history out of juniorPartner? expand_more

juniorPartner does not publish an export process, so we work out with you what your installation can produce and map it across with a test run before anything is relied on. Diary dates and undertakings get one careful pass by hand. Take the export while your Maintenance and Support agreement is still current.

We bought juniorPartner years ago. Why change now? expand_more

If it still does what you need, keep it. Firms look at moving when the office datafile becomes a worry, when partners want answers the module set does not give, or when the next renewal comes round. The difference here is that the system is yours: no modules to add, and changes are a conversation, not a feature request.

Does it handle legal aid files? expand_more

The free version records time and fees on any file. Fitting it to how your firm bills legal aid work, with your own file types and reports, is part of what Enterprise DNA builds into your version.

Is the compliance checking legal advice? expand_more

No. It checks your own records against a written rule book, covering client care, conflicts, undertakings, the AML/CFT Act and the Limitation Act, with each rule citing its source. Your firm reads the sources, changes the rules to suit its practice and keeps the judgement.

Find out what your firm would own instead

30 minutes with Sam. We look at which juniorPartner modules your firm actually uses, what you would keep, and what your own version would look like. If it fits, we build it and bring your history across. If not, the free version is yours to run.

Book a discovery call Get the free version

Matters for Claude Code is free and open source, published by Enterprise DNA.

Done paying for juniorPartner?

Get your version built