Investment Readiness
Why is our funding round taking so long?
Shafneed5 September 20264 min read
In short
Most of the delay is not the investor deciding. It is the gap between a question being asked and being answerable. Raising in India commonly takes three to nine months, and the portion you control is almost entirely how quickly you can evidence what you have already claimed.
This question usually arrives around week eight, when the enthusiasm of the first meetings has settled into a slow exchange of document requests and follow-up questions, and nobody has said no but nothing is moving.
It helps to know where the time actually goes, because the parts you can influence are not the parts founders usually worry about.
Where the weeks go
A raise here commonly runs three to nine months end to end. Roughly, the time divides into:
- Conversations and interest, which move fast when they move at all.
- Diligence, which is the longest and most variable phase, and the one this question is usually about.
- Documentation and closing, which is largely legal and moves at the pace of the slowest party.
Diligence stretches because investors have become more thorough about validating whether early traction is real and repeatable rather than accepting reported numbers. More questions, more reconciliation, more requests for the data underneath a headline figure.
The delays you cause
These are the ones worth fixing, because they are entirely yours:
- A question is asked that requires you to build something before you can answer, rather than retrieve it.
- Two documents disagree, and resolving it means going back through history rather than pointing at a source.
- The cap table does not reconcile to the resolutions, so approvals have to be obtained retrospectively from shareholders who are not waiting by the phone.
- An IP assignment or a contract was never executed, and the counterparty has no urgency about signing it now.
- A metric is defined differently in two board packs, and now every number derived from it has to be re-derived.
Every one of these turns a question into a project. That is the actual mechanism of delay: not scepticism, but latency.
The delays you inherit
Some of it is not about you at all, and it is worth recognising these so you do not over-correct:
- Investment committee calendars, which run on their own cycle regardless of your urgency.
- A fund raising its own next vehicle, or reaching the end of its deployment period.
- Market conditions shifting mid-process, which changes what the committee wants to see.
- Legal counsel on either side working through a queue.
You cannot compress these. You can avoid stacking your own delays on top of them, which is where the controllable portion lives.
What to do when it stalls
- 01Ask directly what is outstanding, in a list. Vagueness is usually politeness, not evasion, and a list converts it into work you can do.
- 02Separate what you can answer today from what needs building, and send the first group immediately rather than waiting to send everything at once.
- 03For anything that needs building, give a date and hold it. A predictable founder is easier to underwrite than a fast but erratic one.
- 04Fix the source, not the answer. If two documents disagree, reconcile them properly rather than explaining the discrepancy, because the same discrepancy will surface again in the next request.
- 05Keep running the company. Rounds that stall while the business also stalls tend not to recover.
When slow means no
Not every stalled round is recoverable, and reading it correctly saves you weeks you could spend on other conversations.
- Slow but specific is usually alive. Detailed questions, however tedious, mean someone is still doing work on your file.
- Slow and vague is usually not. Requests that stop being specific, or repeated deferrals without a named next step, generally mean the internal champion has lost the room.
- A long gap after a full data request is ambiguous. It can mean committee scheduling, and it can mean a quiet no. Asking directly is better than waiting, and the answer costs you nothing you still had.
If you conclude it is a no, treat the diligence work as reusable rather than wasted. The reconciled accounts, the defined metrics and the organised documents carry straight into the next conversation, which is one reason preparing properly the first time compounds.
What delay actually costs
Time is the visible cost. The more expensive ones are quieter.
Every week of delay consumes runway, and runway is what gives you the ability to walk away. A founder with four months of cash negotiates differently from one with ten, and both sides know it. This is the real argument for starting the process at nine to twelve months of runway rather than six.
Delay does not just cost time. It transfers leverage, one week at a time.
There is also a compounding effect within the process itself. Each unanswered question tends to generate more questions, because an investor who has found one gap reasonably assumes there may be others and looks harder. Closing the first gap quickly is worth more than its own weight.
None of which is an argument for rushing. It is an argument for arriving with the answers already assembled, so that the only delays left are the ones you were never going to control.
Who wrote this
Shafneed is the founder of Simplify, a finance clarity and investment readiness practice working with founders across India. He writes about the questions founders bring before a decision, not after it.
Preparing to raise?