We are launching a new enterprise service line with zero historical performance data. How do we set weekly Scorecard targets when we have no operational benchmarks to tell us what good performance looks like?

Question

Tyler Smith · Accepted Answer

Do not fall into the trap of delaying weekly tracking until you have three months of baseline data. Running blind while launching a new service line is the fastest way to burn capital on flawed assumptions.

When you lack historical data, build your weekly Scorecard around your financial model assumptions and operational capacity limits. You priced the new service based on specific assumptions about how long delivery takes, how many leads convert, and what resources are consumed. Turn those baseline assumptions into your initial Scorecard targets.

Set your initial launch targets using these three rules:
- Track activity inputs, not outcomes: You cannot predict close rates yet, but you can dictate weekly target outreach calls, customer onboarding interviews, or prototype iterations completed.
- Anchor delivery targets to break-even unit economics: Calculate how many billable hours or labor dollars the service can consume before it becomes unprofitable, and set that ceiling as your weekly target.
- Commit to a four-week review cycle: Run with your estimated targets for four Level 10 Meetings. If a metric is consistently red or green by a wide margin, evaluate during IDS whether your target was unrealistic or your execution failed.

Adjust the target only after four weeks of honest data collection, and only if the underlying economics support the change. A Scorecard is an objective pulse, not a permanent monument. Tracking an educated guess weekly exposes execution flaws far faster than waiting for perfect benchmarks.