A subscription package is the moment a prospect becomes an investor. It is also, on most funds, the single worst-performing step in the entire relationship: the point where a committed LP goes quiet for three weeks because a PDF would not open on their phone. Related: What Goes in a Fund Subscription Package and Who Signs What.
It is worth being precise about what the package actually consists of, because "send the subs docs" hides at least four different jobs.
The four things a subscription package is doing at once
Collapsing these into one PDF bundle is what makes the process feel heavy. They have different audiences, different failure modes and, ideally, different interfaces.
- Collecting data. Legal name, entity type, tax residency, commitment amount, bank details, beneficial owners. Structured fields, not prose.
- Collecting consent. The subscription agreement itself, side letters, and the fund documents the investor is confirming they have received and read.
- Making disclosures. Risk factors, fee terms, conflicts. The fund's obligation, regardless of whether the investor engages with them.
- Establishing eligibility. Accreditation or professional-investor status, sanctions and PEP screening, source of funds.
Each of those has a different natural format. Data wants a form with validation. Consent wants a signature with an audit trail. Disclosure wants a document that is provably delivered. Eligibility wants evidence you can re-examine in three years.
The order that keeps people moving
The common sequencing mistake is asking for the hardest thing first. A package that opens with a request for a certified passport scan and a bank letter loses people before they have made any psychological commitment to the process.
A sequence that holds up better:
- Confirm the basics. Who is subscribing, as what entity, for how much. Two minutes, no documents, no uploads.
- Present the documents. Fund documents to read, with delivery recorded. The investor can stop here and come back.
- Sign. The subscription agreement, in the same session, on the same device.
- Verify. Identity, accreditation, source of funds. Now the investor is committed and the friction is tolerable.
- Fund. Wire instructions released only after acceptance.
Note that the wire instructions come last and are gated. That is not a workflow nicety; it is the single most important fraud control in the whole sequence.
Where investors actually stall
The entity question
"Are you subscribing personally or through an entity?" sounds trivial and is not. An investor subscribing through a family trust needs different signatories, different tax forms and different beneficial-ownership disclosure. If the form does not branch on this, someone in the back office reconstructs it by email later, which is where a week goes.
The joint-signature problem
Joint accounts, trusts with co-trustees, and entities with two required signatories all break a subscription flow built for one person clicking once. If your signature step cannot route to a second party and hold the package in a partially executed state, every one of those investors becomes manual.
Re-entry
Investors do not complete a subscription in one sitting. They start on a phone in an airport and finish on a laptop four days later. If the package does not persist partial progress against their identity, they start over, and a meaningful fraction simply do not.
What to keep after it closes
A subscription is a legal record, not a workflow artefact. When a package completes, what should survive is the executed document, the signature evidence (who signed, when, from where, against which version of which document), the disclosures delivered and acknowledged, and the verification evidence.
The version detail is the one people miss. "Investor signed the LPA" is not defensible on its own. "Investor signed the LPA, revision 4, hash abc123, on 4 March, having been shown that exact revision" is. If your document store overwrites files in place, you cannot make the second statement.
The test
Ask one question about your current process: if an investor who subscribed two years ago disputes what they were shown, how long does it take to produce the answer, and how many systems do you have to open?
If the answer involves an email archive, a shared drive and someone's memory, the package was a workflow. If it is one record, it was a subscription.