Round operations
Systems for running a live raise: memory, pipeline state, next moves, stale threads, and follow-up timing.
What founders should automate in fundraising, and what should stay judgment work
Automation should carry lookup work, not relationship judgment. Use the task map to split automate, assist, and founder-only decisions.
Round operationsThe raising founder's calendar design
A reactive fundraising calendar interleaves prep, pitching, recording, and company work. Batch the week by energy instead.
Round operationsThe 5 fundraising stages founders actually need
Most fundraising trackers copy sales CRM stages. These five stages encode investor state, whose move it is, and the next action.
Round operationsThe meeting note format that makes future follow-up obvious
A six-field decision note turns an investor call into a follow-up you can write in two minutes, even three weeks later.
Round operationsHow to run a round without losing your company for two months
A founder-led round expands into every undefended hour. Use a fixed weekly calendar container so the company keeps moving while you raise.
Round operationsWhat should happen after every investor meeting
A good investor meeting decays unless you capture the exact objection, proof requested, owner, and deadline.
Round operationsThe difference between an investor database and your investor list
A database tells you who exists. A real investor list tells you who to pitch, in what order, and why.
Round operationsThe round retro: how to learn from every pass
A single pass is noise. A classified set of passes is the market telling you what to fix next.
Round operationsMeeting notes that matter three weeks later
Fundraising notes should preserve the next decision, not replay the meeting transcript.
Round operationsHow to run your fundraise like sales without becoming cringe
Sales discipline belongs in the back office of your raise. Sales tactics do not belong in the investor's inbox.