What kinds of custom software can Bosseo discuss with a Waverly law firm?+
Bosseo’s public page gives examples including client status portals, intake tools, internal dashboards and referral trackers. It also describes tools for removing operational bottlenecks. Whether a particular tool is feasible depends on the firm’s workflow, data and systems.
Does Bosseo support the systems my firm already uses?+
The public page describes connections with a firm’s website, intake and dashboard and discusses integrations. It does not establish support for every CRM, case-management, billing or other system. Bring the exact systems to the consultation and ask for confirmation.
Do I need a technical requirements document before contacting Bosseo?+
Bosseo says a firm can describe the bottleneck in plain English and that its team will ask questions and scope the build. You can prepare more effectively by bringing the current workflow, users, data fields, permissions and desired acceptance tests.
How will access be handled?+
Access should be decided during scope. Identify each user role and what that role may view, create, edit, export or delete. Bosseo’s public page does not publish one universal permissions model for every custom build, so ask for the proposed model for your tool.
What should we ask about hosting and recovery?+
Bosseo says it hosts, monitors and maintains the software it builds and refers to backed-up infrastructure. Ask for the specific backup, restoration, retention, export and incident procedures that would apply to your proposed tool. Do not infer recovery times or infrastructure locations that have not been confirmed.
How do we know whether custom software is better than an existing product?+
Compare the actual workflow with the available product. Custom software may warrant consideration when a defined bottleneck requires repeated workarounds or disconnected systems. An existing product may be preferable when it already meets the firm’s requirements. Bosseo’s consultation should be used to scope the decision, not to assume that custom is always necessary.