What types of custom software can Bosseo build for a Haslett law firm?+
Bosseo’s public Custom Software page describes client portals, intake tools, internal dashboards, speed-to-lead tools, referral trackers, document intake flows, calculators and integrations between existing systems. Whether a particular build is appropriate depends on your workflow and the systems involved.
Do I need a technical requirements document before contacting Bosseo?+
Bosseo says you can start by describing the operational annoyance in plain English. You should still bring enough detail to explain the current steps, users, data involved and desired outcome. Bosseo’s review can then determine whether custom software is appropriate and what should be scoped.
Can custom software connect to our existing systems?+
Bosseo describes tools connected to a firm’s website, intake and dashboard, and gives examples involving CRM, case-management and marketing systems. Do not assume your specific systems or connection method are supported. Ask for a direct review of your current tools, access requirements and data rules.
How should we evaluate permissions and backups?+
Ask who can view, edit, export or delete each category of information; how access changes when staff roles change; how backups are handled; and how restoration would work. Bosseo says it hosts custom software on dedicated servers and uses monitored, backed-up infrastructure, but your firm should confirm the terms that apply to the proposed build.
How is the cost determined?+
The public Bosseo page says scope and investment are defined up front on the call and that the amount depends on what is being built. Request a written scope that separates the initial build from any later work and identifies the hosting or maintenance terms that apply.
Who maintains the tool after launch?+
Bosseo says its team hosts and maintains the custom software it builds, including updates, fixes and improvements. Confirm the exact maintenance responsibilities, response expectations, change process and any boundaries for your proposed tool before proceeding.