Get a baseline before you set goals

Annual sales goals get written in the first two weeks of January, which is the one moment of the year when nobody has current data. December's numbers are holiday-distorted. Last January belongs to a different list, a different message, and probably a different rep. So the targets get set from ambition, a board conversation, and a number that felt right in a planning meeting. A goal without a baseline under it is a wish with a deadline attached, and the difference announces itself around March.
Two weeks of honest measurement
The alternative costs fourteen days. Before the annual targets get inked, run the motion normally, at the input standards you set last week, and measure everything that happens without editing any of it. What an ordinary day of dialing actually produces once meetings and admin take their cut. How often a dial becomes a live conversation on your current list. What share of conversations turn into a booked meeting, and what share of booked meetings actually get held. None of this requires new tooling. It requires two weeks of logging what is true, including the parts that are unflattering, because the unflattering parts are the entire point of the exercise. A baseline padded to look healthy is a wish with extra steps.
Two weeks is a floor, not a study. The sample is small, and small samples wobble, so treat the result as a first sketch that the following months will sharpen rather than a physical constant. But a rough number measured this month beats a precise number imagined in a kickoff deck, and it is enough to catch order-of-magnitude fiction, the plan that quietly requires triple the conversations your team has ever produced.
Goals become multiples, not inventions
With a baseline down, goal-setting changes character. The question stops being what number would look good and becomes what multiple of the current reality you can justify. A team holding meetings at its measured rate can commit to an improvement with a mechanism behind it: a better list, a sharper message, more protected calling hours, and each mechanism has a plausible size. Twenty percent more conversations from fixing the list is an argument. Three times more meetings from the same inputs is a hope wearing a spreadsheet. Baselines also make the mid-year conversation survivable. When the numbers disappoint in May, a team with a January baseline can see which stage moved and which did not. A team without one just knows it is behind, which is information nobody can act on.
The measurement is also the plan
There is a compounding benefit hiding in this. The two-week baseline forces the logging habits, honest counting, stage-by-stage visibility, that the rest of the year runs on, and it does so in January, when, as the backward calendar made clear, the quarter is mostly set anyway and the real work is building the machine for the quarters that are not. You lose almost nothing by measuring first. You lose the whole year's steering by skipping it.
Every CommandVA engagement starts this way by construction: the funnel is measured and reported to the client weekly from the first Friday, so a baseline exists within weeks and every later claim about improvement has a number under it. If your annual targets are about to be written on a clean whiteboard with no data behind them, book a strategy call. We will show you what a measured baseline looks like for an ICP like yours, and what honest multiples of it look like by summer.
One dedicated, full-time SDR inside a complete outbound system. Written meeting SLA, weekly reporting, month-to-month. A 30-minute call tells you if it fits.
Book a strategy call