When you build a specialized legal tech platform, one of the hardest decisions isn’t the tech stack or the UI — it’s deciding what belongs in the self-service product and what should stay in direct consulting engagements.
At first glance, the temptation is to make everything available in software. It feels generous, scalable, and client-friendly. But in practice, this can create real problems — for both the client and the business.
Over the past few months, I’ve been shaping my Legal Deadline Engine with two clear “lanes”:
Lane 1: SaaS (Self-Service)
These are the core features every subscriber can access:
- Standard legal deadline calculators
- Clear, exportable reports
- Simple replay and history tools
- Regular automated rule updates
- Team collaboration with basic role management
These features are predictable, repeatable, and valuable without requiring deep customization. They’re designed for speed, consistency, and accessibility.
Lane 2: Consulting (Custom & Premium)
These are reserved for direct engagements with firms:
- Custom calculators for niche or multi-jurisdictional needs
- Certified forensic reports and expert analysis
- Tailored workflow integrations into firm-specific systems
- Advanced analytics and risk scoring
- Priority access to new or experimental features
These aren’t “locked away” to force upsells — they’re separated because they require expertise, judgment, and close collaboration to get right. Delivering them as consulting ensures accuracy, compliance, and client-specific adaptation.
Why This Matters
In legal tech, not all complexity should be automated away. Some problems are too nuanced, too context-dependent, or too high-stakes to hand off to a self-service tool. By drawing a clear line between SaaS and consulting:
- Clients get the best of both worlds — instant access for common tasks, expert help for the edge cases.
- The platform stays reliable and focused.
- My consulting work retains its value as a premium, high-touch service.
The lesson here? Innovation isn’t about doing everything in software. It’s about knowing what software should handle — and when a human expert should step in.
If you’re curious about what your firm could achieve with the consulting lane, let’s talk.
Thanks for reading!
About the Author
My name is Paul A. Jones Jr., and I am a software engineer and legal tech founder developing tools for professionals in law and other regulated industries. I write about systems thinking, modern workflows, and SaaS applications at PaulJonesSoftware.com. Follow me on Twitter: @PaulAJonesJr.


Leave a comment