What a startup measures in the first month.

The first month of marketing ends and someone asks what it produced. A few sign-ups, some traffic, a post that did well. Nobody can say whether any of it was caused by the marketing, because the work started a few weeks ago. The temptation is to report whatever number went up.

Outcomes are not readable in month one.

Most marketing takes longer than a month to show results a founder can trust. Search takes months to index and rank. Content needs time to be found and shared. Paid channels produce clicks quickly, but a handful of sign-ups from a few weeks of spend is too small a sample to tell signal from luck.

Reporting outcomes from month one invites the wrong decisions. A channel is killed because it produced nothing yet, or celebrated because of one lucky week. Both are reactions to noise. The honest report says what was set up, what was done and when the first real read is due.

Measure whether the setup works.

The most useful thing to verify in month one is that measurement itself works. Is analytics installed on every page and recording visits? Does the form record each submission with the page it came from? Do tagged links show up as their own source? Is there one place where every lead lands with its date and origin?

These checks sound basic, and they are where many early setups fail quietly. A form that has not been recording its source for two months leaves the team with two months of results it cannot read. The measurement stack a startup actually needs covers what that one place should be.

The fastest check is to do it yourself. Click a tagged link from a phone, submit the form with a test name and confirm the record shows the right page and the right source. If any step is wrong, fix it before the first real lead arrives, because a lead recorded wrong cannot be corrected later. Repeat the test whenever the site or the form changes.

Measure the inputs you control.

Beyond setup, month one can track the work itself. Pieces published. Posts made. Outbound messages sent. Experiments started, with their start dates and the date each will be read. These are inputs, not results, and that is fine. They show whether the plan is being carried out, which is the only thing a team controls in the first weeks.

Inputs also make later results interpretable. If month four shows a jump in inbound demos, the team needs to know what changed in months one to three. A simple log of what was done and when is the cheapest analysis tool a startup will ever have.

Pick the number that comes later.

Month one is also when to choose the outcome marketing will answer to once results are readable: qualified demos, trials that reach a first real session, paying customers from a named source. The number a startup's marketing is accountable to covers how to choose it.

Writing it down now prevents the drift that happens when results arrive. Without an agreed number, every report highlights whatever moved, and over a few months the team loses track of what marketing was supposed to deliver.

Say plainly when the first read is due.

The month-one report should end with a date. Setup verified, these pieces and experiments are running, the first read of the accountable number is in month three. That sets expectations with the founder, the board and anyone else waiting for proof.

It also protects good work from early judgment. A channel that needs three months to show anything deserves its three months, and a written date is what stops a nervous week from cutting it short. Marketing attribution for a startup with no data team explains how the sources get read once there are enough leads to read.

A month-one report that says little is not a failure. It is an accurate description of month one, and a team that gets used to accurate descriptions early will trust the numbers when they finally mean something.

Verify the setup, log the inputs, choose the number and put a date on the first real read.

Tell us what you're building.

Blog