What a good handoff looks like
Discovery produces a phased roadmap, role and permission model, integration boundaries, and acceptance criteria. The first release should let a customer and staff member each finish a meaningful task and see the correct status without relying on separate manual updates.
Try this before a consultation
Sketch a record for one customer request, including the staff owner, customer-visible status, approval history, and next action. Trace what happens when ownership changes or an attachment must be restricted. Use the sketch to define your first acceptance test.
Questions to ask before committing
How do I decide which existing systems to keep?
Identify the systems with reliable records, active integrations, or critical workflows. Keep the system of record where it already works and integrate selectively. Move a workflow only when the benefits justify migration, user training, and maintenance.
What belongs in a portal development quote?
Look for the included workflows, user roles, integrations, migration boundaries, acceptance criteria, and responsibilities for ongoing operations. Request a realistic demo of one end-to-end scenario before assigning value to a long feature list.
Related expert answers
Browse state and city service pages