A 45-minute walkthrough for design-partner GPs · 15 November 2026
We want to know whether zSign fits how your team actually runs closings before we build it. Nothing here is final. Please be blunt.
What to share with the customer:
prototype/ (open index.html),
user-guide/GP_User_Guide.html,
user-guide/Investor_Signing_Guide.html, and this kit. Keep
docs/, spec/ and scripts/
internal.
| Min | Screen | Ask them to… | Listen for |
|---|---|---|---|
| 0–5 | 01 Closing dashboard | Tell you what needs their attention first | Do the “why it’s stuck” reasons match reality? What’s missing? |
| 5–12 | 04 New packet — prefill review | Talk through what they’d check before sending | Trust in prefilled values; who reviews; field colors clear? |
| 12–18 | 03 Packet detail | Explain who’s waiting on whom | Joint, IRA, trust, entity routing; delegates; CC rules |
| 18–24 | 05 Bulk send | Decide whether to send | Is the objection forecast useful or noise? Would they opt in to using their history? |
| 24–30 | 08 Version manager | Roll out a counsel revision | Comfort with void-and-reissue when people already signed |
| 26–30 | Working prototype · Templates & fields | Add a dropdown and a checkbox to the subscription agreement, make one conditional, preview and publish | Is placing fields as fast as DocuSign? Which field types or properties are missing? |
| 30–35 | 09 AI review | Approve the hints as counsel would | Who approves; the “can’t hide high-priority obligations” rule |
| 35–40 | 11, 12, 14 Signer screens | React as one of their LPs | Would LPs find the briefing helpful? Too much? Tone? |
| 40–45 | 06 Countersign queue | Countersign and record admission | Batch countersign; separating signing from admission |
Use feedback_form.csv — one row per comment. Columns:
screen, persona (whose point of view), type (bug / confusing / missing /
like / question), severity (blocker / major / minor), comment, quote
(their words), follow-up owner.
Send the completed CSV to the Zive product team.