LawVu · Ecosystem · Product Discovery
The opportunity space for the SharePoint, Google Drive, and Box sync integrations, built from the Pendo feedback export using Teresa Torres' continuous-discovery framework: one outcome, opportunities, solutions, and assumption tests.
Desired outcome
Why this outcome: a customer-behaviour outcome, not a feature checklist. It captures setup failures, adoption blockers, and trust erosion in one metric, reflecting the integration's core promise: a single source of truth without disrupting existing workflows.
The opportunity space
Counts are feedback items mapped to each node. Branch B is recommended as the target opportunity — it carries the strongest commercial evidence in the dataset — and is expanded into solutions and assumption tests below.
“Matt has to go to Box, create the same folder name as the matter (this could have a typo issue) and then hop back into the LawVu matter.”
“Customers taken by surprise that they have to create a folder in GDrive in advance of syncing.”
“It is quite time consuming trying to scroll through all the folders… we have to scroll through them all.”
“Being able to search for folders beginning with 'W' rather than having to scroll all the way down through A, B, C…”
“It's quite fiddly when we have to do the files and then each contract separately. It would be good if we can do the whole matter at once.”
“Customer would like the sync button on a matter to sync all linked contracts.”
“Would love our integration to automate (by convention) the creation of folders for new matters and contracts, and to initiate syncing without a manual step.”
“Others assume there would be an option to get everything syncing… ensure everything is backed up.”
“Once sync is turned on it only works for those added after… if someone forgets the step, there may be extra work to have the files in two places.”
“Capital One's IT governance… is done at a Drive level, meaning they typically never have humans in the mix… they would need to create an exception from a governance point of view.”
“Can't force all business users to live in LawVu or our SharePoint site — they use their own sites and we need to be able to link to those.”
“Complex organizations may have LawVu users across multiple sectors with different GDrives… cited as a pain point for a $304,670 RFP expansion that we lost.”
“There is no functionality to sync articles from the Knowledge Base… would improve accessibility and searchability in SharePoint.”
“The actual contract itself is not synced. To have a complete record in the external DMS, this should occur.”
“A way for the sync to utilize the data fields in the contract, not just the document names, in SharePoint.”
“Some files in a matter are confidential — only for the members of the matter. Other files should be synced live to a shared gDrive. Our current integration simply syncs ALL files.”
“Customer would like the ability to sync a single file or folder to SharePoint rather than everything in the files tab.”
“We would like to be able to sync just one file / or folder, not the whole matter.”
⚠ Sharpened by the current model: permissions are not synced, so over-syncing is a real exposure path, not just clutter.
“There is no way to identify which matters/contracts have been synced, so users need to open individual records… time-consuming and inefficient.”
“It would be helpful if there was an automatically created tag or populated field on which I could filter in grid view (‘synced = yes’).”
“Is there a log where we can check the syncing and spot any error? …I think the sync only works when we link the folder, but then it only goes one way.”
“When you delete a file in LawVu… it does not get deleted in SharePoint, and there is no popup to let the user know. Our users will not necessarily be aware of the limitations.”
“Is there any way to copy over the DOC ID field too while syncing the files to SharePoint site?”
“The option to open their SharePoint instance directly from LawVu, enabling users to browse folders when needed… would make the user experience much smoother.”
“Easily access the synced GDrive folder within the Files tab… and from other areas of the matter.”
“Need ability to make edits in real time on SharePoint-type system.”
“It is lacking some of the functionality that SharePoint has for team integrated working, and can be a little clunky at times.”
“When adding a comment and trying to tag a colleague, no user options appear… works via the SharePoint integration but not Word Online.”
“Link from a matter to open directly to Google Docs. Or even better, native editing in LawVu in a Google Docs format.”
“Integration with G-Suite is incredibly slow.”
“The platform has better functionality for Microsoft users… the intake process isn't automated or seamless as we had hoped.”
Target opportunity · deep dive
Chosen as the target because it's the only branch with direct commercial evidence — a lost $304K RFP expansion (2022), an active enterprise POC blocker (Capital One, 2026), and the same "one root doesn't fit" pain recurring across four years and both Microsoft and Google estates. The other branches are friction; this one is a wall. Per Torres, solutions are generated only for this target — three candidates, deliberately different in shape, set up for compare-and-contrast rather than whether-or-not.
The narrower sub-opportunity being targeted is B1: “one root folder / one drive doesn't match our governance.” B2 (content scope: KB articles, contract metadata) is real but smaller and independent — it can be picked up separately without touching the connection model.
Admin nominates several roots (sites / libraries / shared drives); the sync modal asks "which root?" before the folder picker. Smallest change to the current model.
| Desirability | Assumes multi-BU orgs want legal to reach into per-BU sites rather than centralising. Test → interview 5 enterprise admins (incl. the two named multi-site accounts): map their actual site/drive topology. |
|---|---|
| Feasibility | Assumes Graph/Drive consent granted once can span multiple roots without re-consent per root. Test → 2-day API spike: enumerate + write across 3 libraries / 2 shared drives under one consent. |
| Viability | Assumes single-root is a recurring deal blocker, not a one-off. Test → sales review: tag last 24 months of lost/stalled enterprise deals for root-model objections. |
| Usability | Assumes users can pick the right root without mis-filing to the wrong business unit. Test → prototype the two-step picker; watch 5 users route matters for 3 fictional BUs. |
| Ethical / risk | Assumes wider write scope doesn't widen the existing permissions-not-synced exposure. Test → security review of blast radius per added root before any build. |
Each team or matter type carries a default destination (site / drive / folder convention); sync destination is inferred, and combined with auto-initiation this also collapses much of branch A.
| Desirability | Assumes destination is predictable from matter attributes in most orgs. Test → in the same admin interviews: "for your last 20 matters, could a rule have picked the folder?" |
|---|---|
| Feasibility | Assumes matter-type/team metadata is populated reliably enough to drive routing. Test → data pull across active orgs: % of matters with type + team set at creation. |
| Viability | Assumes convention-based routing differentiates vs. competitors in enterprise evaluations. Test → probe in the next 3 active evaluations / POC conversations. |
| Usability | Assumes users trust an inferred destination they didn't pick. Test → fake-door "synced automatically to X — change?" banner in prototype; measure overrides. |
| Ethical / risk | Assumes a wrong rule mis-files at scale rather than one matter at a time. Test → design review: dry-run/preview mode and undo story before commitment. |
Attacks Capital One's actual stated blocker: their governance forbids human-managed folder permissions. LawVu's service account applies an org-defined permission template to each folder it creates, making folder-level delegation acceptable to drive-level-governance IT.
| Desirability | Assumes IT would approve folder-level exceptions if applied programmatically + audibly. Test → take a one-page concept back to the Capital One POC team: would this clear governance? |
|---|---|
| Feasibility | Assumes provider APIs allow the service account to set ACLs at folder grain in Shared Drives / libraries. Test → API spike alongside S1's; these share a consent investigation. |
| Viability | Assumes governance-blocked enterprises are a segment, not one logo. Test → CSM canvass: which accounts raised governance in security review? (target n≥3) |
| Usability | Assumes admins can express their policy as a template without a services engagement. Test → paper-prototype the template config with 2 admins. |
| Ethical / risk | This is a permissions feature: a template bug is a confidentiality incident. Test → threat-model first; define audit log + rollback as acceptance criteria, not add-ons. |
Tensions the tree surfaces
Trojan Energy and others want zero-touch, sync-by-convention; Linktree and Pew want file-level control because some matter content is confidential. These aren't contradictory requests — they're two segments (completeness-driven vs. confidentiality-driven), sharpened by the fact that permissions don't sync. Any auto-sync solution needs an exclusion story on day one, or branch A's solution creates branch C's incident. A good interview question for every discovery call: "if every new matter synced automatically, what would worry you?"
The product intentionally doesn't propagate deletions (SharePoint: neither direction; Drive: one-way; Box: undocumented). Customers don't experience that as a safety feature — they experience silent divergence. The cheapest unit of trust here may be honesty in the UI (warn at delete-time) rather than building deletion sync, which carries its own risk profile.
NerdWallet's detractor comment says functionality "isn't living up to the expectations set during our demos." Before investing in co-editing parity, check what the sales and onboarding narrative promises about the Google experience — a positioning fix is cheaper than an engineering one, and the Drive-side performance complaints (Snowy Hydro, NPS 0) deserve a profiling spike regardless.