Start with one client and learn the handoff
A small first implementation makes the request-to-completion pattern visible before a whole practice moves across.
Start with a real relationship
The first useful Duly setup is not a large import. It is one real client with a request that the practice already understands.
Bring across the client context, choose one recurring document request, set the period and due date, and make the owner visible. Then watch the work move through upload, review and delivery.
Learn from the handoff
The first client shows where the practice still relies on a private inbox, an old spreadsheet or a message thread. Those are not failures to hide. They are the places where a shared record can remove friction.
Expand when the pattern is clear
Once the team can see the request-to-completion loop, adding more clients becomes a repeatable operating decision instead of a large software project.
Start small. Make the work visible. Let the practice learn from the record.