Real estate investment · United States
A document process turned into software
The back-and-forth between the firm and its investors is gone.
Stack
- Process modeling
- Document control flow
- Digital signature
- Client platform
- 2
- branches in the document flow: entity and individual
The problem
A US real estate investment firm raises capital from accredited investors, and every subscription was a document relay.
Screening, a subscription agreement, an accredited investor certification, terms acceptance, an operating agreement signed by each investor in the vehicle, and the final signed set returned to everyone.
Each of those steps was a round trip. The firm asked, the investor answered, someone checked whether the answer was complete, and asked again for what was missing.
Entities and individuals need different documents entirely — an entity brings formation documents, its tax ID, and beneficial ownership down to the ultimate owner; an individual brings identity and residency — and that branch was being handled by whoever happened to be on the thread.
The approach
I mapped the subscription circuit end to end and specified it as a document-control flow: every state an investor can be in, what the system asks for at each one, which branch applies to an entity and which to an individual, what has to be verified before the next document is generated, and which documents are produced, signed and returned at each step.
The specification covers the full chain: screening, identity and entity data capture, subscription agreement generation, accredited investor certification, terms acceptance, registration, project documentation release, digital signature, constitution of the operating agreement with participation percentages, and the signed set returned to every investor.
That specification was then built into the firm’s software.
The result
What used to be a chain of emails asking for one more missing document is now a sequence the platform drives: it asks for what it needs, in the order it needs it, on the branch that applies, and it does not advance until it has it.
A second version of the document-control diagram exists, so the flow was revised against reality rather than designed once and filed.
The transferable piece
Most document-heavy processes do not need AI to stop being painful. They need someone to write down what the state machine actually is.
Until that exists, every automation sits on top of a process nobody agreed on.