When a decision-maker asks how long a marketing initiative will take, the literal question and the actual question being asked are often not quite the same thing. Answering only the literal version β a project timeline β frequently leaves the real underlying concern unaddressed, and that mismatch is a common reason otherwise solid plans lose confidence at approval time.
Why Timeline and Payback Are Different Questions
A project timeline describes when specific tasks will be completed. What a decision-maker usually actually wants to know is when they'll start seeing real results β when the investment starts paying for itself. These can be very different numbers: a project might be executed within a few weeks, while the actual business results it produces take considerably longer to materialize and compound.
Answering this question well should involve:
- Distinguishing clearly between execution timeline and expected results timeline in your answer
- Being explicit about how soon measurable payback is realistically expected, not just task completion
- Accounting honestly for factors that could extend the timeline, like resource availability or the need for iteration
- Avoiding the temptation to promise unrealistically fast results just to make the pitch more appealing
A Simple Framework
- Separate your answer into two distinct parts: when tasks will be executed, and when results should appear
- Be specific and honest about the second part, since that's usually the real underlying question
- Account for realistic factors that could extend either timeline, and mention them proactively
- Avoid promising an unrealistically fast payback purely to make the proposal more attractive upfront
> Tip: If you find yourself only prepared to answer the execution timeline and not the results timeline, that's a sign you haven't fully thought through the second, more important half of this question β and it's worth resolving before the pitch, not during it.
Example
Before: A proposal answering "how long will it take" purely in terms of task completion, leaving the decision-maker's real question about when to expect results unaddressed and unresolved.
After: The same proposal explicitly separating execution timeline from expected payback timeline, directly answering the underlying concern and building considerably more confidence in the plan.
Common Mistakes
- Answering only the literal execution timeline while ignoring the real underlying payback question
- Promising unrealistically fast results to make a pitch more immediately appealing
- Failing to account honestly for factors that could reasonably extend either timeline
- Treating this as a single question instead of recognizing it usually has two distinct answers
Tracking how results actually develop after a new initiative launches is the clearest way to validate whether your original payback estimate was realistic. SeoWolf's Cohort Tool can help visualize that trend as it unfolds.
"How long will it take" is rarely just about the calendar β it's usually a question about when the investment starts proving itself, and that's the answer worth preparing most carefully.