There's a meaningful difference between a tool that wraps a generic language model and calls itself an analysis product, and a tool that's genuinely anchored to a proprietary, accumulated dataset that nobody else has access to. The standalone tools planned for this platform's future are deliberately built around the second category — and specifically not the first.
Why proprietary anchoring is the requirement, not an option
A tool that simply passes a question to a generic model and formats the response is commoditised — any competitor with API access can build the same thing in an afternoon. A tool built on top of years of accumulated, validated signal history and a structured historical precedent library cannot be replicated that way, because the underlying data simply doesn't exist anywhere else.
Why these tools aren't being built yet
- The firm sequencing rule on this platform is: finish the core onboarding flow, launch, get real paying customers, observe how they actually use the platform — and only then extract standalone tools from genuine usage patterns
- Building speculative tools before understanding real usage risks building the wrong things, however technically interesting they might be to build
- Other candidates under consideration for this later stage include a Decision Assistant, a Precedent Timeline Viewer, and an Intelligence Digest Builder — each anchored the same way, to proprietary data rather than generic capability
What this means for the roadmap
None of these tools are available today. They represent a deliberately deferred phase of the roadmap — genuinely promising, and deliberately not prioritised ahead of proving the core platform works end to end for its first real subscribers.