Services

Each engagement produces a system you own and operate: a template set, a version history, an approval path, and written instructions for running it.

Send enquiry Fee schedule

Governance document systems
One authoritative set of governance documents, versioned, with a register that stays current.
Terms and template libraries
One library, one current version, a log of every variation you have agreed to.
Employment document systems
Role-based document sets, issued consistently, with a record of what each person holds.
Property document management
A register of every premises, every document, and every date you cannot afford to miss.
Transaction document coordination
Data room structure, checklist discipline and version control while a transaction is running.
Fractional legal operations
A monthly engagement that runs the system after it is built, so it does not decay.
Document assessment
A full inventory of what is actually in circulation, with the differences marked up.
Contract intake desk
One place requests go, with tracked status and somebody chasing the approval step.
Contractor IP assignment audit
A register of who produced what, and whether the assignment paperwork exists.
Retention and disposal schedule
What you keep, for how long, and who is allowed to delete it.
Post-acquisition document integration
Two document systems collided. This is the engagement that merges them.
Board and minute book systems
A minute book that is current, and a checklist for the things that change it.

Fees

What moves the number

A fee is quoted against a written scope, so the honest question is what makes a scope bigger. These are the things that actually do it, and they are established in the first conversation rather than discovered halfway through.

How many versions are already in circulation: The inventory step scales with what exists, not with the size of the business. Four sets of terms and forty are different engagements.
Where the documents currently live: One shared drive is quick. Documents spread across personal drives, inboxes and a departed employee’s account take longer to collect than to organise.
How many people issue documents: The approval matrix and the distribution step scale with the number of roles that touch a document, not with headcount.
Whether a register already exists: Extending a register that is partly maintained is cheaper than building one from nothing and reconstructing its history.
Whether the system has to move tooling: Structuring documents where they already live costs less than migrating them somewhere new. Migration is scoped and quoted separately.