Fundraising operating notes for founder-led rounds.
Practical writing on keeping investor conversations warm, choosing the next move, and turning messy fundraising context into momentum.
Latest articles
Ideas, systems and field notes for running the work between investor meetings.
The highest-leverage fundraising work is boring
The work that decides a round is the boring upkeep: stale intros, late follow-ups, unanswered objections, and open diligence requests.
10 min readRound operationsA fundraise is a sales pipeline with worse feedback loops
Pipeline discipline transfers to fundraising, but investor silence and warmth lie unless you retune the stages.
11 min readRound operationsWhy founder-led fundraising breaks after the first 30 investors
Founder-led rounds break when active investor threads exceed what your head can hold, not when you stop working hard.
9 min readRound operationsThe round doesn't start when you email investors. It starts when you structure memory.
A founder who can recall the exact state of every investor conversation outcompetes a founder with a better deck.
8 min readRound operationsYour fundraise is not a CRM problem. It is an execution problem.
Rounds stall when the next move stays unclear for too long, so a founder needs a daily operating system that produces moves, not another database that stores them.
8 min readGuidesHow to export a WhatsApp chat for RoundOS
WhatsApp does not give you one clean fundraising archive. Export the investor and connector chats that matter, one conversation at a time, then upload each TXT or ZIP to RoundOS.
4 min readGuidesHow to download your LinkedIn archive for RoundOS
Export the larger LinkedIn data archive, wait for the complete email, and upload the ZIP to RoundOS so your fundraising memory starts with real relationship context.
3 min read