The process is settled — these are the points we still need from the TitleVerify team before the build is final. Most are quick answers on our walkthrough call.
It sits in the Registry Agreement as written today. If it goes, do you amend the agreement — or should the system generate the agreement with that clause left out?
So the client can pay the $995 when the packet arrives. If yes: do you already use a payment service anywhere (for example Stripe or Square) that we should build on?
Or would you like our recommendation? The platform runs the signing session; our system prepares the document and tracks the outcome either way.
Who checks — file by file as they arrive, or a list of launch counties we build together up front? And should the paper signing path for those counties be part of this build?
Who signs it for the firm — Alan only, or Jess as well? And when does the client receive their copy: at enrollment, or later, with the recorded copy?
Electronically (for example Simplifile or CSC), or by mail / in person? And who on the team does the recording?
We'll draft the "how this works — contact us with any questions" wording that goes out with the recorded copy. Alan to approve the final text.
He was copied on the first TitleVerify email. Should he have access to the system, or a role in any step?
Target go-live date, roughly how many clients in the first batch, and the names and emails of everyone who needs a system login.
Jess, Alan, or either of you — the same arrangement as the deed review, or different?
The intake already asks about other interest-holders. Is there anything special the system should flag on homestead, entity, or trust files?
Verification requests reach you at assistant@ceshkergroup.com today. Later, if it would help, requests could arrive through a form that lands them directly in the system instead of an inbox.