Build a contract management system

You are a developer who builds legal software.
I work in Legal: a mid-sized law firm. This work matters to clients, partners and associates.

## Goal
Build a system to store contracts, track key dates and obligations, and manage approvals.

## What matters in Legal
- People involved: partners; associates; paralegals; clients; opposing counsel; courts and regulators.
- Rules and standards that usually apply: client confidentiality and privilege; bar council and professional-conduct rules; the law of the relevant jurisdiction; limitation periods and court deadlines; conflict checks; every output is a draft for a qualified lawyer, not legal advice.
- Numbers that matter: matter turnaround; billable utilisation; realisation rate; client retention; win or settlement rate.
- Common risks to plan for: missed deadlines; conflicts of interest; confidentiality breaches; citing wrong or made-up case law; fixed fees that run over.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Contract types and volume: [TYPES, NUMBER]
- Users and roles: [ROLES]
- E-signature tool: [TOOL]
- Stack: [STACK]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Summarise what you understood about the product, its users and the launch scope. Point out anything unclear or contradictory and ask before you guess.
2. Build the contract repository with metadata, versions and full-text search.
3. Build templates and a request workflow.
4. Build approval routing by value and type.
5. Integrate e-signature.
6. Track renewals, expiries and obligations with reminders.
7. Control access by role and matter.
8. Build reports on upcoming renewals and value.
9. Give a launch checklist covering security, performance, SEO, accessibility, backups and monitoring.
10. List what is deliberately out of scope for version 1 and what to build next.

## What to deliver
- Plan and data model
- Phase-by-phase build
- Approval workflow
- Reminder engine
- Security design

## Expert rules
- Build mobile first and make every screen work from 360px wide upwards, with labels, keyboard support and 4.5:1 contrast.
- Validate every input on the server, use prepared statements, hash passwords, protect forms with CSRF tokens and check roles on every admin action.
- Give complete files with full paths; never write "rest of the code stays the same".
- Respect client confidentiality, professional-conduct rules and jurisdiction (the output is a draft for a qualified lawyer to review, not legal advice). If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Start with the plan (stack, structure, data model, screens), then build in numbered phases.
- Use tables for data models and endpoint lists.
- End each phase with how to run and test it.

## Before you answer
Check your draft against this list and fix anything that fails:
- The answer is practical enough to use today without rewriting.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on matter turnaround and billable utilisation.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.