142. Monthly Board/Advisor Update

A good monthly update builds trust before you need help.

It should be short, honest, and useful. The goal is not to look perfect. The goal is to help smart people understand where the company is, what changed, and how they can help.

Who it is for

Write the update for busy people who may help you later.

Reader	What they need
Existing investors	Truth, trust, risk visibility, and whether the plan is still credible.
Advisors	Specific context so advice is not generic.
Potential investors	A clean record of progress, learning, and founder judgment.
Mentors and supporters	Concrete asks they can forward or answer quickly.
Future you	A month-by-month memory of decisions, evidence, and mistakes.

Do not write a press release. Write an operating note.

Structure

Use this format:

1. One-line status
2. Highlights
3. Metrics
4. Customers and revenue
5. Product
6. Team and hiring
7. Cash and runway
8. Risks
9. Asks

Update versions

Not every reader needs the same depth. Keep the core truth consistent, but adjust detail.

Version	Audience	Length	Include
Short advisor note	Mentors, informal supporters	5 to 8 bullets	Status, one metric table, risks, asks
Investor update	Existing investors	1 to 2 pages	Metrics, cash, progress, risks, asks, next milestone
Potential investor forward	Warm leads	1 page	Narrative, traction, round timing, specific reason to talk
Board-style update	Formal board/advisory rhythm	3 to 5 pages	Operating review, financials, strategic decisions, risk register

Do not maintain four different stories. Maintain one story with different levels of detail.

One-line status

Example:

June was a strong learning month: activation improved after onboarding changes, but enterprise collections are slower than expected and we need two customer intros in logistics.

This is better than:

Great month, lots of progress.

Specificity creates useful replies.

Highlights

Share 3 to 5 bullets:

• Biggest customer win
• Important product milestone
• Key learning
• Hiring or team change
• Strategic partnership
• Fundraising progress

Avoid listing every activity. Highlights should explain what matters.

Metrics

Choose stage-appropriate metrics.

Example:

Metric	This month	Last month	Note
Revenue collected
Qualified pipeline
Activation
Retention
Burn
Runway

If a metric is weak, say so. Advisors cannot help with hidden problems.

Cash

Include:

• Cash in bank
• Monthly net burn
• Runway
• Revenue collected
• Major upcoming expenses
• Fundraising status, if relevant

Do not hide runway until it is urgent. Early visibility gives supporters time to help.

Customers

Cover:

• New customers
• Lost customers
• Expansion
• Top customer conversations
• Pipeline quality
• Key objections
• References needed

Customer truth matters more than vanity logos.

Product

Share:

• What shipped
• What improved
• What broke
• What customers used
• What is next

Tie product work to customer outcomes, not just features.

Hiring

Include:

• Open roles
• Critical hiring gaps
• Recent hires
• Candidate pipeline
• Specific referral asks

Ask clearly:

We need intros to senior backend engineers who have built multi-tenant B2B SaaS systems and are open to early-stage startups.

Risks

Name 2 to 4 real risks.

Examples:

• Sales cycle longer than expected
• Activation below target
• Founder bandwidth stretched
• Collections delay
• Hiring bottleneck
• Regulatory uncertainty
• Customer concentration

For each risk, add mitigation.

Asks

Good asks are specific:

• 3 intros to CFOs at Rs 50 crore to Rs 500 crore revenue companies
• Feedback on enterprise pricing
• Reference check on a VP Sales candidate
• Review of US GTM plan
• Intro to a CA/CS/lawyer with SaaS experience
• Customer intro in a named sector

Bad ask:

Let us know if you can help.

Ask priority

Limit asks to the ones that matter this month.

Ask level	Use when	Example
Critical	It affects survival, fundraising, hiring, or a major customer	”We need two CFO intros this week for paid pilot conversion.”
Important	It improves speed or quality	”Please review this pricing change before Friday.”
Optional	Useful but not urgent	”Send us examples of strong onboarding docs if you have them.”

Too many asks train readers to ignore all of them. Three strong asks beat twelve weak ones.

Ask bank

Keep an ask bank so updates produce useful replies.

Area	Strong ask
Customer discovery	”Can you introduce us to 3 finance heads in export manufacturing companies with 100 to 1,000 employees?”
Sales	”Can you review this enterprise objection and tell us what proof a CFO would need?”
Hiring	”Can you recommend one senior product engineer who has worked in early B2B SaaS?”
Fundraising	”Can you suggest 5 funds that like India-to-global SaaS at this stage?”
Compliance	”Do you know a CA/CS/lawyer who has handled SaaS cross-border invoicing and ESOPs?”
Strategy	”Which of these two ICPs looks more credible from the evidence below?”

Specific asks are a service to the reader. They reduce guessing and make help easier.

What to include only when useful

Do not make every update heavy. Add these sections only when they matter:

Section	Use when
Fundraising	You are preparing, actively raising, or runway is becoming tight
Hiring plan	A role is critical and supporters can help source or reference
Customer case study	A win explains ICP, value, or repeatability
Churn/postmortem	A loss teaches something important
Regulatory/legal	A material compliance issue affects timing or risk
Founder note	Energy, health, or co-founder dynamics may affect execution

Short and honest beats long and polished.

Update quality score

Before sending, score the update:

Question	Yes/No
Can a reader understand the company status in the first 30 seconds?
Are metrics comparable to last month?
Are customer/revenue signals separated from vanity activity?
Are risks named without drama or hiding?
Are asks specific enough to act on?
Is the update short enough that people will actually read it?

If fewer than four answers are yes, rewrite before sending.

Metrics discipline

Keep the same metric definitions month to month. If you change a definition, explain it.

Examples:

• Revenue booked is not the same as cash collected.
• Pipeline is not the same as qualified pipeline.
• Signups are not activation.
• Active users are not retained users.
• Runway based on current burn is not runway after planned hiring.

Investors and advisors lose trust when numbers move because definitions move.

Risk register

Keep a small risk register and show movement month to month.

Risk	Current level	What changed	Mitigation	Help needed
Slow collections	Yellow	2 enterprise invoices delayed	Founder escalation and payment-term change	Intro to finance leader for advice
Weak activation	Red	New users need too much setup	Simplify onboarding and add setup call	Review onboarding flow
Hiring bottleneck	Yellow	Engineering pipeline thin	Referral sprint	3 senior engineer intros

Risks should not appear as drama. They should appear as managed reality.

Reply management

The update creates work after sending. Manage replies deliberately.

Reply type	Founder action
Intro offered	Reply with a clean forwardable blurb within 24 hours.
Advice given	Thank, decide whether to use, and close the loop later.
Investor interest	Send memo/deck and propose a specific next step.
Concern raised	Answer directly; do not become defensive.
No response	Do not interpret silence too much; keep sending useful updates.

The fastest way to make supporters stop helping is to ask and then respond slowly.

India field notes

For India-based startups, include collection status when relevant. Many founders report revenue but do not show delayed payments, TDS/GST friction, or enterprise procurement drag. Supporters can often help only if they see the bottleneck early.

For cross-border companies, separate India revenue, global revenue, and pipeline by geography if the sales motion differs.

Email template

Subject: StartupBook update format example - [Company] [Month]

Hi all,

One-line status: [clear summary].

Highlights:

• [highlight]
• [highlight]
• [highlight]

Metrics: [small table]

Risks:

• [risk and mitigation]

Asks:

• [specific ask]

Thank you, [Founder]

Board update narrative spine

A monthly update should not read like a pile of facts. It should tell a clear operating story.

Use this spine:

Part	Prompt	Example shape
Status	What is the company state in one sentence?	”Demand is improving, but onboarding is slowing conversion.”
Progress	What changed since last month?	”Qualified pipeline grew from X to Y and two pilots converted.”
Learning	What did the team learn?	”The buyer is the CFO, but daily usage starts with ops.”
Constraint	What is the biggest bottleneck?	”Implementation takes too much founder time.”
Decision	What are you doing about it?	”We are narrowing ICP and productizing setup.”
Ask	What help do you need?	”Intro to two finance leaders who run implementation-heavy SaaS.”

This keeps the update from becoming “good news, good news, vague ask.” Supporters help more when they understand the real constraint.

Write the first paragraph last. After drafting highlights, metrics, risks, and asks, summarize the month in one honest paragraph:

“This month was [overall state]. The strongest signal was [signal]. The main concern is [risk]. We are responding by [decision]. The most useful help is [ask].”

If you cannot write that paragraph, the update is not yet clear.

Decision requests

Do not ask advisors to “share thoughts” on everything. Ask for decisions or targeted judgment.

Use these request types:

Request type	Example
Decision feedback	”We are choosing between self-serve onboarding and founder-led onboarding for the next 30 days. Which risk do you see?”
Intro request	”Can you introduce us to CFOs at export businesses with 100 to 500 employees?”
Pattern recognition	”Have you seen enterprise pilots stall at security review? What usually unblocks them?”
Hiring help	”Who is a strong first sales hire for founder-led B2B in India?”
Fundraising feedback	”Does this milestone sound seed-fundable, or should we prove one more sales cycle?”
Customer reference	”Can we speak to one operator who owns this workflow?”

Make every ask forwardable. A good intro request includes:

• Who you want to meet.
• Why that person is relevant.
• What you will ask them.
• Why it will be a low-effort conversation.
• A short blurb the advisor can forward.

Weak ask:

“Please introduce us to any enterprise customers.”

Better ask:

“Could you introduce us to finance or operations leaders at Indian logistics companies with 200+ employees? We are learning how they handle invoice reconciliation and payment follow-up. A 25-minute discovery call is enough.”

Investor memory log

Monthly updates compound when they create memory. Keep a simple log of what you told supporters each month.

Month	Main signal	Main risk	Main ask	Promise made	Follow-up sent

Use the log before sending the next update:

• Did we close the loop on last month’s ask?
• Did we explain what happened to last month’s risk?
• Did we change metric definitions?
• Did we promise a milestone that is slipping?
• Did someone help us and not hear the result?

Supporters remember patterns. If every update has a new story with no continuity, trust weakens. If the founder shows progress, admits misses, and closes loops, trust compounds even before the metrics are perfect.

For fundraising, the memory log becomes especially valuable. An investor who has watched three honest updates often understands the company better than an investor seeing a cold deck for the first time.

Ask follow-through system

A monthly update is only useful if asks turn into action. Track every ask like a mini pipeline.

Ask	Sent to	Date sent	Needed by	Status	Follow-up
				Open / accepted / declined / done

Use different follow-up styles:

Situation	Follow-up
Advisor offered help	Send a forwardable blurb within 24 hours.
Intro was made	Reply quickly, thank both sides, and close the loop later.
Advisor did not respond	Follow up once with a narrower ask.
Ask became irrelevant	Tell them it is no longer needed.
Help produced value	Report the result in the next update.

Forwardable blurb:

Pushkar is building [company/product] for [specific customer]. He is trying to speak with [specific profile] about [specific problem]. A 25-minute call is enough, and this is for learning/customer development, not a sales pitch.

Replace the text with the real company and ask. The discipline is to make helping easy. Advisors are busy; vague asks die quietly.

Evidence quality by stage

The update should show the right evidence for the stage of the company. A founder can lose trust by reporting late-stage vanity metrics when early-stage learning is the real work.

Stage	Weak update says	Strong update says
Idea/discovery	”We got great feedback"	"We spoke to 18 target buyers; 11 had the problem this month; 4 agreed to a follow-up with current workflow data”
MVP	”Product is almost ready"	"5 of 8 target users reached first value; setup still needs founder help; next bottleneck is onboarding”
First revenue	”Customers are interested"	"3 paid pilots started, 2 invoices collected, 1 stalled at procurement, average sales cycle is 27 days”
Repeatability	”Pipeline is growing"	"Qualified pipeline by ICP, stage, next step, owner, and close risk”
Scaling	”We hired and launched channels"	"CAC/payback/retention/support load by channel or segment, with decision on what to scale or stop”

Your update should make it obvious whether progress is real, repeatable, and tied to the next milestone.

Cash and runway wording

Founders often soften cash language until it is too late. Use clear wording.

Situation	Say this
Runway healthy	”We have X months runway at current burn; planned hiring changes this to Y.”
Collections delayed	”Booked revenue is ahead of cash. Rs X is overdue, and founder escalation is underway.”
Fundraising soon	”We expect to start conversations in [month] and need to prove [milestone] first.”
Runway tight	”Runway is X months. We are choosing between [cut/raise/bridge/revenue push] by [date].”
Burn changing	”Burn increases from X to Y after [hire/tool/office]; this is tied to [milestone].”

Do not hide cash behind vague phrases like “managing burn carefully.” Good supporters can help only when the founder is specific early enough.

Update anti-spin checklist

Before sending, remove spin.

Draft phrase	Replace with
”Lots of interest”	Number of qualified conversations, follow-ups, and paid next steps
”Strong pipeline”	Pipeline by stage, buyer, next step, and close probability
”Product is improving”	Activation, retention, support load, or time-to-value change
”Hiring going well”	Candidate sources, qualified candidates, offers, blockers
”Fundraising conversations are positive”	Number of investor calls, next steps, objections, and timing
”We are exploring”	Decision date and evidence needed

The best updates are not pessimistic. They are clean. They give readers enough truth to help without forcing them to decode founder optimism.

Board/advisor packet

For a formal board or serious advisor call, send a packet 24 hours before the meeting.

Section	Include
One-page update	Status, metrics, risks, asks
Decisions needed	1 to 3 questions where you want judgment
Metric table	Comparable month-by-month metrics
Cash view	Cash, burn, runway, receivables, planned spend
Customer evidence	Wins, losses, quotes, churn reasons, pipeline quality
Hiring/team	Critical roles, risks, team load
Appendix	Deck, memo, product screenshots, pricing notes, legal/accounting questions if relevant

Ask board/advisors to respond to the decision questions, not to every detail. A good packet turns a meeting from a founder performance into a useful operating conversation.

Bad-news update protocol

Send bad-news updates earlier than feels comfortable. The point is not to dramatize problems. The point is to protect trust and create time for help.

Use this structure:

Part	What to say
Fact	What happened, with date and number if possible.
Impact	Why it matters for customers, cash, team, product, or fundraising.
Cause	What you know, what you do not know, and what is still being investigated.
Response	What you are doing now.
Decision	What choice must be made and by when.
Ask	What specific help would change the situation.
Next update	When you will report back.

Example:

Two enterprise invoices worth Rs [X] are now more than 45 days overdue. This reduces practical runway from [A] to [B] months unless collected by [date]. The issue is not product usage; it is finance approval and PO mismatch. I am escalating to the buyer sponsor this week and changing future pilot terms to collect upfront. The useful help: one intro to a finance leader who has handled similar collection delays in Indian B2B SaaS. I will update by Friday.

Do not bury bad news in the last paragraph. If the issue affects runway, customers, legal risk, team trust, or fundraising, put it near the top.

Update cadence by stage

Choose a cadence that matches company risk.

Stage	Suggested cadence	Why
Discovery	Monthly or every 6 weeks	Enough time to show learning patterns.
MVP/pilots	Monthly	Supporters can help with customers, product judgment, and proof.
Active fundraising	Every 2 to 4 weeks to close advisors/investors	Momentum and objections need fast follow-up.
Runway under 6 months	Every 2 weeks to key stakeholders	Cash, cuts, collections, and fundraising cannot drift.
Crisis or shutdown risk	Weekly to the small relevant group	Decisions and communications need tight coordination.
Stable growth	Monthly or quarterly depending on governance	Focus on metrics, risks, and strategic asks.

Do not send updates so often that they become noise. Do not send them so rarely that supporters only hear from you when you need a rescue.

Update archive

Keep every monthly update in one folder.

Archive item	Why it matters
Sent update	Shows what was communicated.
Metric table	Preserves definitions and trends.
Ask tracker	Shows who helped and what follow-up is owed.
Decisions	Records why the company chose a path.
Risks	Shows whether risks were noticed early.
Investor replies	Helps future fundraising and relationship memory.

Before fundraising, reread the last 6 updates. They will reveal whether the company story is actually compounding or just changing language.

Common mistakes

• Sending only good news
• Reporting activity instead of progress
• Making vague asks
• Hiding cash concerns too late
• Sending long updates that nobody can act on

Done when

The update is useful when:

• A busy advisor can understand the company in five minutes
• The asks are specific enough to forward
• Metrics are comparable month to month
• Risks are named with mitigation
• The founder feels clearer after writing it

Related chapters

• 86. Company Operating System
• 80. Investor Memo
• 151. Operations Templates