Do we need a technical requirements document before speaking with Bosseo?+
Bosseo’s public Custom Software page says no requirements document is needed to start; describing the annoyance in plain English is enough for the initial conversation. You should still bring the current workflow, systems involved, user roles and desired outcome so the discussion can be concrete.
What kinds of tools can a law firm consider?+
Bosseo’s public examples include speed-to-lead tools, client status portals, referral trackers, internal dashboards, document-intake flows, calculators and connections between existing systems. These are examples of possible categories, not a guarantee that a specific request or integration will be accepted.
Can the tool connect to our existing systems?+
Bosseo describes custom tools that connect with a firm’s website, intake and dashboard, and gives CRM, case-management and marketing examples. The specific systems, permissions, data definitions and technical connection must be reviewed before any integration is promised.
Who hosts and maintains the software?+
Bosseo’s public page says its team hosts and maintains the tools it builds on its dedicated servers and describes updates, fixes and improvements as part of the relationship. Ask during consultation about access, backups, recovery, documentation, change requests and any service terms that apply to your scope.
How should we decide whether custom software is better than an off-the-shelf product?+
Buy an existing product when it matches the firm’s actual problem and operating requirements. Consider custom software when a narrow workflow gap creates repeated work or when several tools require manual bridging. The consultation should be able to conclude that custom software is not necessary.
What should staff test before adopting the tool?+
Test the agreed workflow with representative records and common exceptions. Confirm data accuracy, required fields, permissions, assignment or notification behavior, correction paths, reporting needs and recovery procedures. Staff onboarding and post-launch refinement should be discussed as part of the scope.