1. Start with the workflow, not the feature list
A custom build should begin with the work your team performs, not with a list of fashionable features. Describe where information enters the firm, who touches it, where it is copied, which decisions require approval and what happens when a step is missed. Bosseo’s public Custom Software page describes a discovery conversation based on the firm’s actual workflow and says a requirements document is not required to begin that conversation. That makes the first evaluation practical: identify one recurring bottleneck and explain it in ordinary language.
Recommended approach
Bring one process to the consultation. For example, you might review how an inquiry moves from receipt to assignment, or how a client-status request is answered. Treat those as illustrative process categories, not claims about your firm. A useful scope should state the starting event, the people involved, the records changed, the exceptions and the desired stopping point. Naperville is recorded as a municipality in DuPage County and Will County, but that geographic fact does not establish a particular operational need. Use your own staff’s experience to define the problem.