Solutions Router — Persona-Based Site Navigation
Purpose
Route users to the /solutions/:slug page that best matches their professional role and use case. Different personas have substantially different needs from a legal AI platform — a law-firm partner cares about billing efficiency and matter-quality; an SME founder cares about self-serve contract review without legal fees. The solutions pages make the value proposition concrete and persona-specific, improving conversion from "I found this tool" to "this is for me."
Solution pages — persona map
| Persona |
URL slug |
Primary audience |
Key value proposition |
| Lawyers (private practice) |
/solutions/lawyers |
Law firm associates, partners, counsel |
Faster drafting, research, matter triage; AI as leverage for billable output |
| In-house counsel |
/solutions/in-house-counsel |
Corporate legal department teams |
Contract volume management, risk triage, faster turnaround to business clients |
| Law students |
/solutions/law-students |
LLB/JD students, trainee lawyers |
Research tool, drafting practice, moot/exam prep |
| SME founders |
/solutions/sme-founders |
Startup founders, small business owners |
Self-serve contract review, template access, reduce lawyer spend on routine matters |
| Enterprises |
/solutions/enterprises |
Large corporate legal and procurement teams |
Bulk contract review, compliance monitoring, integration with enterprise systems |
| Consumers (B2C) |
/solutions/consumers |
General public, individuals with legal questions |
Legal information, document preparation, access to justice |
Routing logic
Detection inputs (in priority order)
- Explicit persona statement: user says "I'm a lawyer", "I'm a startup founder", "I'm in-house at a bank" → direct route.
- Profile data: user is authenticated and profile records their role → route to matching solution.
- Navigation context: user arrived via a lawyers-specific campaign URL (
?utm_campaign=law-firms) → route to /solutions/lawyers.
- Behavioral signals: user searches for "eFirm", "billing", "matter management" → lawyers; "contract review for my company" → in-house counsel; "student", "moot" → law students.
- "Is this for me?" query: explicit question about fit → show persona options and route to best match.
- No signal: show all six solution options on the
/solutions/ index page.
Routing rules
1. Detect persona from inputs (see above).
2. Map to solution slug:
- "lawyer", "solicitor", "advocate", "barrister", "law firm", "partner" → /solutions/lawyers
- "in-house", "GC", "legal dept", "corporate counsel" → /solutions/in-house-counsel
- "student", "law school", "LLB", "bar prep", "trainee" → /solutions/law-students
- "founder", "startup", "SME", "entrepreneur", "CEO", "small business" → /solutions/sme-founders
- "enterprise", "procurement", "legal ops", "large company" → /solutions/enterprises
- "individual", "personal", "my case", "help me" (no professional context) → /solutions/consumers
3. Route to /solutions/[slug] with tracking parameters.
4. Track persona identification + page view for conversion analytics.
In-app usage
"Is this for me?"
When a user asks directly whether the platform suits their role:
- Ask one clarifying question if role isn't clear: "Are you a practicing lawyer, in-house counsel, law student, or using this for your own business?"
- Route to matching solution page.
- Offer to continue helping with their task.
Sales-intent conversations
When a user is clearly evaluating the platform for purchase or trial activation:
- Identify persona.
- Surface the solution page URL.
- Offer to demonstrate the most relevant features for that persona.
- Link to pricing page if appropriate.
Marketing-page to in-app link
Solution pages on the public site should deep-link into the app at the most relevant starting point for that persona:
- Lawyers → in-app contract review or research start.
- In-house counsel → in-app contract intake or clause library.
- SME founders → in-app NDA or service agreement template.
- Consumers → in-app legal information chat.
Critical constraints
Messaging consistency
The solutions pages must match actual product capabilities for that persona. Do not:
- Promise features that don't exist for that persona.
- Use lawyer-audience messaging on consumer pages (and vice versa).
- Claim jurisdiction coverage that the product doesn't have.
Disclaimer placement
- Consumer page (
/solutions/consumers): must include the legal-information-not-advice disclaimer prominently.
- Lawyers page (
/solutions/lawyers): no general disclaimer needed (they are the qualified professionals); a brief note on AI verification obligations is appropriate.
See [[safety-no-legal-advice-disclaimer-rules]] for disclaimer surface rules.
Related skills
- [[site-feature-router]] — feature-specific routing that may follow persona routing
- [[site-ai-feature-router]] — routing to specific AI feature pages
- [[site-legal-document-router]] — document library routing (often persona-filtered)
- [[site-compare-us-router]] — competitive comparison pages (often accessed by lawyers evaluating)
1---2name: site-solutions-router3description: Solutions Router — Persona-Based Site Navigation4---56# Solutions Router — Persona-Based Site Navigation78## Purpose910Route users to the `/solutions/:slug` page that best matches their professional role and use case. Different personas have substantially different needs from a legal AI platform — a law-firm partner cares about billing efficiency and matter-quality; an SME founder cares about self-serve contract review without legal fees. The solutions pages make the value proposition concrete and persona-specific, improving conversion from "I found this tool" to "this is for me."1112## Solution pages — persona map1314| Persona | URL slug | Primary audience | Key value proposition |15|---------|---------|-----------------|----------------------|16| Lawyers (private practice) | `/solutions/lawyers` | Law firm associates, partners, counsel | Faster drafting, research, matter triage; AI as leverage for billable output |17| In-house counsel | `/solutions/in-house-counsel` | Corporate legal department teams | Contract volume management, risk triage, faster turnaround to business clients |18| Law students | `/solutions/law-students` | LLB/JD students, trainee lawyers | Research tool, drafting practice, moot/exam prep |19| SME founders | `/solutions/sme-founders` | Startup founders, small business owners | Self-serve contract review, template access, reduce lawyer spend on routine matters |20| Enterprises | `/solutions/enterprises` | Large corporate legal and procurement teams | Bulk contract review, compliance monitoring, integration with enterprise systems |21| Consumers (B2C) | `/solutions/consumers` | General public, individuals with legal questions | Legal information, document preparation, access to justice |2223## Routing logic2425### Detection inputs (in priority order)261. **Explicit persona statement**: user says "I'm a lawyer", "I'm a startup founder", "I'm in-house at a bank" → direct route.272. **Profile data**: user is authenticated and profile records their role → route to matching solution.283. **Navigation context**: user arrived via a lawyers-specific campaign URL (`?utm_campaign=law-firms`) → route to `/solutions/lawyers`.294. **Behavioral signals**: user searches for "eFirm", "billing", "matter management" → lawyers; "contract review for my company" → in-house counsel; "student", "moot" → law students.305. **"Is this for me?" query**: explicit question about fit → show persona options and route to best match.316. **No signal**: show all six solution options on the `/solutions/` index page.3233### Routing rules34```351. Detect persona from inputs (see above).362. Map to solution slug:37 - "lawyer", "solicitor", "advocate", "barrister", "law firm", "partner" → /solutions/lawyers38 - "in-house", "GC", "legal dept", "corporate counsel" → /solutions/in-house-counsel39 - "student", "law school", "LLB", "bar prep", "trainee" → /solutions/law-students40 - "founder", "startup", "SME", "entrepreneur", "CEO", "small business" → /solutions/sme-founders41 - "enterprise", "procurement", "legal ops", "large company" → /solutions/enterprises42 - "individual", "personal", "my case", "help me" (no professional context) → /solutions/consumers433. Route to /solutions/[slug] with tracking parameters.444. Track persona identification + page view for conversion analytics.45```4647## In-app usage4849### "Is this for me?"50When a user asks directly whether the platform suits their role:511. Ask one clarifying question if role isn't clear: "Are you a practicing lawyer, in-house counsel, law student, or using this for your own business?"522. Route to matching solution page.533. Offer to continue helping with their task.5455### Sales-intent conversations56When a user is clearly evaluating the platform for purchase or trial activation:571. Identify persona.582. Surface the solution page URL.593. Offer to demonstrate the most relevant features for that persona.604. Link to pricing page if appropriate.6162### Marketing-page to in-app link63Solution pages on the public site should deep-link into the app at the most relevant starting point for that persona:64- Lawyers → in-app contract review or research start.65- In-house counsel → in-app contract intake or clause library.66- SME founders → in-app NDA or service agreement template.67- Consumers → in-app legal information chat.6869## Critical constraints7071### Messaging consistency72The solutions pages must match actual product capabilities for that persona. Do not:73- Promise features that don't exist for that persona.74- Use lawyer-audience messaging on consumer pages (and vice versa).75- Claim jurisdiction coverage that the product doesn't have.7677### Disclaimer placement78- Consumer page (`/solutions/consumers`): must include the legal-information-not-advice disclaimer prominently.79- Lawyers page (`/solutions/lawyers`): no general disclaimer needed (they are the qualified professionals); a brief note on AI verification obligations is appropriate.8081See [[safety-no-legal-advice-disclaimer-rules]] for disclaimer surface rules.8283## Related skills8485- [[site-feature-router]] — feature-specific routing that may follow persona routing86- [[site-ai-feature-router]] — routing to specific AI feature pages87- [[site-legal-document-router]] — document library routing (often persona-filtered)88- [[site-compare-us-router]] — competitive comparison pages (often accessed by lawyers evaluating)