The Relationship Starts After the Wire

Founders spend six months learning to pitch and then go quiet the week the money lands. Six months later they need a bridge, an introduction, or a supplier reference, and they are emailing people who have not heard from them since the closing. Those emails do not work.

The monthly investor update is the cheapest instrument on the cap table. It costs forty-five minutes, it keeps twenty people informed enough to help on short notice, and it is the reason a follow-on check takes two weeks instead of two months. Hardware founders need it more than software founders do, because hardware progress is invisible from outside. A software investor sees the product ship. A hardware investor sees nothing for nine months unless you tell them what is happening.

Cadence: Pick One and Never Miss It

Monthly is the standard for pre-seed through Series A. Quarterly is acceptable after Series A when a board meeting covers the detail. Anything less frequent is not a cadence, it is occasional contact.

Send on a fixed date. The first Tuesday of the month, every month, whether or not anything dramatic happened. The value is in the reliability, not the content of any single message. Investors learn to expect it, and its absence becomes a signal in itself. The month you skip because the news is bad is the month everyone notices.

Send to everyone: leads, followers, angels, advisors with equity, and the two people who passed but asked to be kept warm. That last group is a genuine pipeline. Founders regularly close their next round with an investor who passed the first time and watched twelve monthly updates go by.

What Belongs in Every Update

Five to eight hundred words, scannable in ninety seconds, same structure every month so readers can compare.

  • Headline. One or two sentences on the single most important thing that happened. Not a summary of the whole email.
  • Cash and runway. Cash in bank, monthly burn, months of runway at current burn. Every serious investor scrolls to this first. Hiding it does not work and destroys credibility when it eventually surfaces.
  • Key metrics. Three to six numbers, same ones every month, with last month's figure beside each. For a pre-revenue hardware company these are development metrics: units built, cycles on test, defects open, BOM cost at target volume, letters of intent signed. What counts as a meaningful number at your stage is the same question addressed in what counts as traction for investors.
  • Progress against the plan. What you said you would do last month, and what actually happened. This is where credibility accumulates or evaporates.
  • Product and manufacturing status. Where you are in the build sequence, in terms investors recognize: prototype, engineering build, pilot production run, mass production. Naming the stage is more informative than describing the work.
  • Team. Hires made, hires open, departures. Departures go in the update, not the rumor mill.
  • Lowlights. A named section. More on this below.
  • The ask. Also below, and the part most founders drop.

Keep the format identical month to month. An investor who reads thirty of these a month should be able to find your runway number in two seconds.

How to Report Bad News

Hardware generates bad news on a schedule. A mold trial comes back with warped parts, a certification lab fails your radio, a contract manufacturer misses a date, a key component goes to a fifty-two week lead time. None of this is unusual and none of it ends a company. Concealing it can.

Report it in the update where it happened, in the format: what went wrong, what it costs in time and money, what you are doing about it, and when you will know if the fix worked. Four sentences.

"Tooling trial two produced sink marks on the top housing. Two-week steel correction, $4,200, paid by the molder under the tooling agreement. Trial three is scheduled and we will report results in the next update." That reads as competence. The same news delivered six months later during a bridge conversation reads as concealment.

The pattern that actually damages founders is silence followed by a crisis. An investor who has watched you handle four disclosed problems well will fund the fifth. An investor who learns about all five at once will not. This is also how a supply disruption should be surfaced, well before it forces the kind of scramble described in planning a product around component shortages.

The Ask at the Bottom

End every update with two or three specific requests. Not "let us know if you can help." Specific:

  • "Looking for an intro to a buyer at a regional hardware chain, ideally private label."
  • "Need a referral to an EMC test lab in the Midwest with capacity in the next six weeks."
  • "Hiring a firmware engineer with BLE experience. Job description linked."
  • "Anyone with experience negotiating tooling ownership with a Shenzhen molder, twenty minutes would help."

Named, bounded requests get answered. Investors want to be useful and mostly do not know how. Give them a task that takes one email and a meaningful fraction will do it. Over a year that is a dozen introductions you would otherwise have chased cold.

The Update Is Quiet Preparation for the Next Round

Twelve consecutive monthly updates are a documented operating history. When you open the next round, existing investors already know the metrics, the burn, and how you handle problems, so the internal conversation is a decision rather than a diligence project. Cutting weeks out of the process matters more than founders expect once they see how long a round actually takes.

The updates also become raw material. The metrics you have been publishing monthly feed straight into the financial model and populate the data room without a reconstruction exercise. Founders who never sent updates spend three weeks rebuilding a history they lived through.

Turning Engineering Progress Into Something Investors Can Read

The hardest part of a hardware update is translating engineering status into language a generalist investor understands without dumbing it down. Projects House works with founders on the technical sections of investor reporting: build stage definitions, cost-down tracking, certification timelines, and honest schedule risk. Reach us through our contact form.