1. Start with the Montgomery workflow, not a feature list
A custom build should begin with the work your team performs, not with a catalogue of screens. Ask where a matter begins, who records each fact, which system becomes authoritative and where a handoff can fail. A Montgomery firm may serve people in the township, throughout Somerset County or across New Jersey; those are different operating scopes. The software should not silently treat a municipal location as the boundary of your client base. Write down the actual users, matter types and jurisdictions that the process covers.
Recommended approach
Bring one recurring bottleneck to the consultation. Describe the trigger, the people involved, the information collected, the decision that follows and the desired result. Bosseo’s public Custom Software page says the process starts with describing the bottleneck in plain English, followed by design, build, feedback and continued maintenance. Ask Bosseo to restate the proposed workflow before approving scope.
