How to write a one-page signal brief

A one-page signal brief is not a mini white paper. Its job is to make one signal legible enough that another person can decide what to do with it.

Quick answer. Write it in four blocks: what changed, why it matters now, what still needs checking, and what you want to do next.

Block one, what changed. State the observable movement in plain language.

Block two, why it matters. Explain why the change could matter before the market catches up.

Block three, what still needs checking. Say what is still uncertain so the brief stays credible.

Block four, next action. End with one recommendation: watch, outreach, deeper pass, or drop.

If the brief cannot survive on one page, the thinking is probably still too fuzzy.

The four blocks are not arbitrary. They map directly onto the discipline of separating timing from verification. Block one, what changed, is the signal. Block two, why it matters now, is the thesis. Block three, what still needs checking, is the verification gap stated openly. Block four, next action, is the decision. When the brief keeps these four separate, it stays honest about what it knows and what it does not.

Make the what changed block concrete. GitDealFlow surfaces observable movement in commit velocity, contributor growth, and repository expansion from public GitHub activity, so there is a specific change to name. Write it in plain language, without unexplained metrics. A brief that says a repo accelerated is weaker than one that says which metric moved and how that compares to the name's own prior pattern.

The why now block should lean on lead time rather than enthusiasm. Breakout teams tend to surface 3-6 weeks before a fundraise announcement, so the honest reason to act now is that the movement is early and the market has not caught up yet. That is a stronger sentence than vague excitement, and it gives the reader a reason to believe the timing, not just the direction.

Keep the open questions block visible. Stating what still needs checking is what makes the brief credible, because it signals you are not dressing an opinion up as a fact. A brief with no open questions usually means the writer is hiding uncertainty. A brief with one or two sharp questions reads like the work of someone who actually looked.

The ninety-second test is the real bar. A partner should be able to read the brief and know exactly what you want to do next without hunting through attachments. If the brief cannot survive on one page, the thinking is still fuzzy, and the fix is to sharpen the four blocks, not to add a fifth page.

The brief inherits its credibility from the signal method, which has been validated against a set of startup-period observations and published as a preprint. That means the what changed block can point to observable movement rather than a feeling, and the reader can trust that the movement is not invented. A brief built on a real, validated signal reads differently from one built on a hunch.

The most common failure is not length, it is overconfidence. Writers drop the open questions block because it feels weak, and the brief hardens into a pitch. Resist that. A brief that names its uncertainty is the one a partner can act on, because the partner knows exactly what still needs confirming before money or time moves.

The one-page limit is the discipline, not a formatting preference. It forces you to rank the four blocks by importance and leave out the rest. Anything that does not fit was probably not essential to the decision, and cutting it is the point. A brief that earns its single page has already done most of the thinking.