Company Roadmap Examples: 3 Views of One 12-Month Plan

What Makes a Company Roadmap Different

A company roadmap covers the whole business: product, sales, marketing, hiring and operations. A product roadmap only covers what the product will deliver. If you need that narrower view, see the product roadmap examples guide.

Three things are specific to a company roadmap, and they are why one plan needs three views.

• Several teams share one goal. The roadmap has to show how their work fits together.
• Dependencies cross teams. Sales cannot scale a channel before the product keeps new customers.
• Leaders need a different level of detail. They need results and risks, while teams need the month-by-month work.

The 12-Month Plan Behind the Examples

Goal: turn a small company with a working product into a focused, repeatable business within 12 months. The plan runs in six phases, each with its key steps and one milestone.

• Focus and direction (Month 1): write the goal, cut off-goal projects, set objectives and owners. Milestone: one-page goal and objectives signed off.
• Fix the core offer (Months 2 to 4): interview current and lost customers, ship fixes, rewrite onboarding. Milestone: top three customer complaints fixed and shipped.
• Build a repeatable sales motion (Months 4 to 6): pick one channel, write the sales process, track leads in one place. Milestone: written explanation of where new customers come from.
• Hire and structure the team (Months 6 to 8): hire for the role that blocks the plan, split into teams with leads. Milestone: every team has a lead and a written scope.
• Scale what works (Months 8 to 11): put more effort on the best channel, document processes, automate tasks. Milestone: each objective rated on track, at risk or off track.
• Review and plan next year (Month 12): compare results, list what to keep, stop and start. Milestone: next year's one-page goal approved.

Example 1: The One-Page Objectives View

This view answers "what are we trying to achieve, and who owns it?" It belongs on one page and changes rarely. Everyone in the company should be able to read it in two minutes.

Company goal: a focused, repeatable business within 12 months. Each objective below has a measure, an owner and the phases that serve it.

Not this year: a second product, a new market, a rebuild of the platform. This line is easy to skip, and it is the line that protects the plan. Write it in Month 1 and share it along with the goal. To link each objective to measurable results, see the guide on how to connect OKRs to your roadmap.

• Customers stay and recommend us: measured by retention rate, with the target set in Month 1. Owner: product lead. Main phase: fix the core offer.
• New customers succeed on their own: measured by the share of new customers who reach a first result without help. Owner: product lead. Main phase: fix the core offer.
• New customers come from a known source: measured by new customers from the main channel each month. Owner: sales lead. Main phases: sales motion and scale.
• The team runs without the founder in every decision: measured by each team having a lead and a written scope. Owner: CEO. Main phase: hire and structure.

Example 2: The Month-by-Month Swimlane View

This view is for the teams. Each team gets one lane, and the timeline runs in months. The four lanes here are leadership, product, sales and marketing, and operations and hiring. On a visual roadmap, each lane becomes a horizontal row.

• Month 1: Leadership signs off the goal, objectives and "not this year" list. Product pauses projects outside the goal. Sales and marketing pause campaigns outside the goal. Operations and hiring map current roles and gaps.
• Month 2: Leadership approves the interview plan. Product interviews current and lost customers. Sales and marketing share contacts of lost customers. Operations and hiring list tasks nobody owns.
• Month 3: Monthly review. Product ships fixes for the first two complaints. Sales and marketing ask active customers about the fixes. Operations and hiring list the roles that block the plan.
• Month 4: Monthly review. Product ships the third fix and rewrites onboarding. Sales and marketing pick one channel and set up one shared lead tracker. Operations and hiring choose the role that slows the plan most.
• Month 5: Monthly review. The new onboarding goes live. Sales and marketing run the channel test and write the sales process. Operations and hiring write the job description from the objectives.
• Month 6: Leadership reviews channel results. Product fixes gaps found in onboarding. Sales and marketing review results every two weeks and change one thing at a time. Operations and hiring interview candidates.
• Month 7: Monthly review. Product prepares the handover for the new hire. Sales and marketing document what works in the channel. The hire is made, with an onboarding plan ready.
• Month 8: Leadership approves the team structure. A product lead is named with a written scope. A sales lead is named and puts more effort on the best channel. Teams are split, each with one lead.
• Month 9: Mid-year check on every objective. Product automates one manual task. Sales and marketing scale the best channel. Operations documents weekly processes.
• Month 10: Monthly review. Product ships the next priorities from interviews. Sales and marketing refine the sales process. Operations automates one manual task.
• Month 11: Monthly review. Product gathers input for next year. Sales and marketing summarise channel results. Operations lists next year's hiring needs.
• Month 12: Annual review: keep, stop, start. Product, sales and operations each bring their input to next year's goal.

How to Read the Swimlane View

Follow one lane through the months to see one team's work. Read one month across all lanes to see the whole company at that moment. The real value is in that cross-team reading: in Month 4, product rewrites onboarding while sales picks a channel. Sales should not push the channel hard until the new onboarding is live in Month 5.

Write each cell as a result ("onboarding live"), not an activity ("work on onboarding"). You can build this view in Excel, as a slide in PowerPoint or on a board in Notion, as long as everyone looks at the same version.

Example 3: The Quarterly View With Outcomes and Risks

This view is for leadership meetings and board updates. It shows no tasks, only the result expected by the end of each quarter, the proof that it happened and what could stop it. If you report to investors, this view also works as the base of your update.

Leaders trust a roadmap more when it names its own risks. Update this view once a quarter, not every week, so it stays a stable reference.

• Q1: direction agreed, top customer problems understood and partly fixed. Proof: goal signed off, interviews done, first fixes shipped. Risk: customers decline interviews. Warning sign: few interviews booked by mid-Month 2. Response: offer a short call instead of a full interview.
• Q2: onboarding works without help and one channel is tested. Proof: onboarding live and a written sales process. Risk: the test channel brings no leads. Warning sign: no qualified leads after the first weeks of testing. Response: switch to the second-ranked channel and restart the test.
• Q3: key hire made, teams structured, mid-year check shared. Proof: every team has a lead and a scope. Risk: hiring takes longer than planned. Warning sign: no shortlist by the end of Month 6. Response: use a contractor to cover the role while hiring continues.
• Q4: best channel scaled, core processes documented, next year approved. Proof: next year's one-page goal signed off. Risk: the team spreads effort across too many channels again. Warning sign: new channel ideas appear in monthly reviews. Response: check each idea against the "not this year" list.

What About Now, Next, Later?

A very small team with no fixed dates can use a simple Now, Next, Later board in place of the swimlane view. Once two or more teams depend on each other's dates, the month-by-month view shows those links better. Founders who are still at that early stage will find a format closer to their needs in the related guides.

How to Keep the Three Views in Sync

Keep one source plan with the phases, steps and milestones. Build the three views from it. When something changes, update the source first, then each view.

For more detail on timing, read the guide on how often you should update your roadmap. A simple rhythm works for most small companies.

• Swimlane view: reviewed every month by team leads.
• Objectives view: checked every quarter, changed only if the goal changes.
• Quarterly view: updated at the end of each quarter, with new risks added.