Most lists of company goal examples are lists of things nobody would put on a wall: “increase revenue”, “improve customer satisfaction”, “be more innovative”. They’re accurate, but nobody could tell you on a Thursday afternoon whether the company was closer to them, which is the only test that matters for a goal.
The examples here are written the way I’d write them with a leadership team, as one line with a rough when that names an outcome, and most come with what will be true when it’s done, how you’ll know and the constraint that usually turns out to be holding a goal like it back. None of them will fit your company exactly, and they shouldn’t, but they’re a useful starting point and a check on whether your own goals are doing their job. If you want the method behind them, I’ve set it out step by step in how to write good company goals.
What makes a company goal worth copying
Before the examples, a quick test. A good company goal is memorable, so people can say it without looking it up; it’s an outcome, not a piece of work, so “launch a partner programme” becomes “get a third of new customers through partners by the summer”; it matters, so hitting it changes the company’s revenue, survival or position; and it has a rough when, so the team feels the clock without every small slip becoming a crisis. The precise numbers belong underneath, in how you’ll know, where they can change as you learn without rewriting the goal.
Revenue and growth goals
These are the most common company goals, and the easiest to write badly, because a revenue number on its own says nothing about how the company will get there or what’s in the way.
| Goal | What’s true when it’s done | What usually holds it back |
|---|---|---|
| Get to £1m in annual recurring revenue by the end of next year | We’re growing every month from customers who found us, not just from the founder’s network | Sales still depends on the founder being in every deal |
| Double monthly revenue from existing customers by Q3 | Customers grow with us, and expansion is a normal part of the year rather than a lucky break | Nobody owns expansion, and there’s nothing obvious to upgrade to |
| Make the US a third of new revenue by the end of the year | We sell in the US without flying someone out for every deal | No proof that US buyers want the same thing UK buyers do |
| Get a third of new customers through partners by the summer | Partners bring us deals they’ve already qualified, and we close them faster than our own leads | Partners don’t know how to explain what we do |
| Win our first five enterprise customers by March | We have the references, security answers and contracts to sell to large companies repeatably | The product isn’t ready for a security review |
| Grow revenue by half again without growing the sales team | Most new revenue arrives through the product, referrals and partners | Free users don’t see the value before they’re asked to pay |
| Halve the time from first call to signed contract, by Q3 | Buyers who want us can say yes quickly, and the pipeline is easier to forecast | Every deal needs a custom proposal and a call with the founder |
Customer and retention goals
Customer goals tend to be the ones that compound, because keeping a customer for twice as long is often worth more than winning twice as many, and they’re usually where a growing company’s real constraint is hiding.
| Goal | What’s true when it’s done | What usually holds it back |
|---|---|---|
| Find 20 customers who’d be genuinely upset if we disappeared, by the end of Q1 | We know exactly who our best customers are and why they buy | We’re selling to anyone who’ll buy rather than to the people who need it most |
| Keep nine in ten customers past their first year, by next summer | Renewals are a formality, and customers tell us what they want next before we ask | Customers never get past setup to the moment it becomes useful |
| Make onboarding something customers finish in a week, by the end of Q2 | New customers are live within days and support isn’t flooded with setup questions | Setup needs data the customer doesn’t have to hand |
| Get every customer using the product weekly by the autumn | The product is part of how customers run their week, not a monthly login | Only one person at each customer uses it |
| Be the obvious choice for agencies in the UK by the end of the year | Agencies recommend us to each other without being asked | Our product and messaging still try to serve everyone |
Product goals
Product goals are the ones most likely to be written as activities, because the work is so visible, so it helps to ask what the launch or feature is for and make that the goal.
| Goal | Instead of | What usually holds it back |
|---|---|---|
| Get new users to their first real result in under ten minutes, by Q2 | Redesign onboarding | The first result depends on data users haven’t added yet |
| Make the product something a team can buy without talking to us, by the summer | Launch self-serve | Pricing and setup still need a conversation to explain |
| Ship weekly without breaking anything customers notice, by the end of the quarter | Improve engineering velocity | Releases are manual and nobody trusts the tests |
| Have half of our customers using the new reporting by September | Launch the reporting feature | Customers don’t know it exists, or why they’d want it |
| Be ready to pass an enterprise security review by March | Get SOC 2 | No one owns security, so it competes with every feature |
People and leadership goals
People goals often matter most and get written least, because they feel soft; written as outcomes, they’re as concrete as any revenue goal.
| Goal | What’s true when it’s done | What usually holds it back |
|---|---|---|
| Build a leadership team that runs the company without the founder in every decision, by the end of the year | Each area has a leader who owns its results, and the founder spends most of the week on strategy and customers | The founder hasn’t written down how decisions get made |
| Build a sales team that closes deals without the founder by September | Deals close at the same rate whether or not the founder is involved | The pitch lives in the founder’s head |
| Hire the five people we need for next year by the end of Q1 | Every key role is filled by someone who’s already productive | We don’t agree on what good looks like for each role |
| Get every new hire doing their best work within their first month, by the summer | New people know what matters, who to ask and how their work fits from day one | Onboarding is whoever happens to be free that week |
| Make this a place people recommend to their friends, by next summer | Most new hires come through referrals | People don’t know where the company is going or how their work fits |
Profitability, cash and fundraising goals
These goals change how every other decision is made, so they’re worth writing down explicitly even when they feel obvious, because a team that knows the company is aiming for profitability will make different trade-offs from one that thinks it’s aiming for growth at any cost.
| Goal | What’s true when it’s done | What usually holds it back |
|---|---|---|
| Be profitable every month from Q3 onwards | The business pays for itself and we choose when and whether to raise | Costs grew ahead of revenue and nobody owns the margin |
| Be ready to raise our seed round by September | We’re choosing between investors rather than chasing them | Traction is real but the story doesn’t explain why now |
| Have eighteen months of runway by the end of the year | Decisions are made on what’s right, not on what keeps the lights on | Revenue is lumpy and hard to forecast |
| Get gross margin above 75% by next spring | Every new customer makes the business healthier | Delivery still involves a lot of manual work per customer |
AI and operations goals
A growing number of companies are setting goals about how they work, not just what they sell, and these are the goals most at risk of turning into a list of tools bought rather than a change in how the company runs.
| Goal | What’s true when it’s done | What usually holds it back |
|---|---|---|
| Every team doing its routine work with AI by the summer | People spend their time on judgement and customers rather than admin | Teams were given tools but not time to change how they work |
| Run customer support with half the hours by the end of the year, without customers noticing | Most questions are answered instantly and the hard ones get more time | Answers live in people’s heads, not anywhere AI can use them |
| Grow revenue by half without growing headcount at the same rate, by next year | Output per person rises every quarter | Nobody has mapped which work could be done differently |
| Close the books in three days instead of three weeks, by Q2 | The leadership team has last month’s numbers in the first week | Data sits in four systems that don’t talk to each other |
Team goals that serve a company goal
Here’s where most examples go wrong. Rather than giving every department its own goals, which tends to set teams optimising against each other, it usually works better to keep one company goal and give each team the constraint it’s best placed to clear. The examples below all sit under the same company goal, “Get to £1m in annual recurring revenue by the end of next year”, so you can see how each team’s work connects to it.
| Team | The constraint it owns | A team goal that serves it |
|---|---|---|
| Sales | Sales depends on the founder being in every deal | Close half our deals without the founder by the summer |
| Marketing | Too few of the right companies hear about us | Get 40 qualified conversations a month from content and partners by Q2 |
| Product | Trials stall before a second person joins | Get most new trials to invite a teammate in their first week |
| Customer success | Customers stop using it after the first month | Keep nine in ten customers active after their third month |
| Finance | We can’t see which customers are profitable | Know the margin on every customer by the end of Q1 |
| People | We can’t hire fast enough for the plan | Fill the four key roles by March |
Each team goal makes sense on its own, but more importantly each one is tied to a named constraint on the company goal, so if the constraint changes, the team goal changes with it, and nobody keeps working on a target that has stopped mattering. That’s the difference between a set of department goals and a company that’s actually aligned, which I’ve written about in more depth in the strategic alignment guide.
Company goals by stage
- Pre-seed
Prove someone needs it
“Get ten paying customers we didn’t already know, by the spring.” The constraint is usually focus: selling to anyone who’ll take a call rather than the people who need it most.
- Seed
Make growth repeatable
“Get to £50k in monthly recurring revenue before the raise, with most of it not from the founder’s network.” The constraint is usually that the founder is still the sales team.
- Series A
Build the team that scales it
“Have a leader in each area who has owned their results for two quarters running, by the end of next year.” The constraint is usually that decisions still aren’t written down.
- Established SME
Grow without growing pains
“Make our second product line a quarter of revenue by next year.” The constraint is usually that the team and the sales process are still built around the first one.
Mistakes to avoid when you borrow an example
- Taking too many. These are examples, not a menu; pick the one or two that matter most this year and leave the rest, because every extra goal splits attention.
- Copying the wording without the reasoning. A goal is only right for your company if it addresses the thing that would make the biggest difference to you, so start from that question rather than from a list.
- Putting the numbers in the goal. “Increase MRR by 18.5% quarter on quarter” is precise and forgettable; keep the line simple and the 18.5% in how you’ll know.
- Stopping at the goal. The constraint column is the most useful part of every table above, because a goal without an agreed view of what’s holding it back is a wish, and the team will each work on a different version of the problem.
If you’d like to try writing your own, the free goal writing tool takes you through it in a few minutes with no account needed, and once the goal is written, the goal tracking tool guide covers how to keep it moving.
Questions
What are some examples of company goals?
“Get to £1m in annual recurring revenue by the end of next year”, “Keep nine in ten customers past their first year, by next summer”, “Build a leadership team that runs the company without the founder in every decision, by the end of the year” and “Be profitable every month from Q3 onwards” are all good company goals, because each names an outcome, fits in one line and has a rough when.
What are the most common types of company goal?
Revenue and growth, customers and retention, product, people and leadership, profitability and cash, fundraising, and increasingly AI and operations. Most growing companies need one or two of these at a time, not one of each.
How many goals should a company have?
As few as possible: usually one goal for the company, or one for each team working on something genuinely distinct, and rarely more than a handful in total. Every extra goal splits attention and gives the team another place to drift apart.
What is the difference between company goals and team goals?
A company goal is the outcome the whole company is working towards; a team goal is a team’s part in it. Team goals work best when each one is tied to a specific constraint on the company goal, rather than cascaded down the org chart as a separate target.
Should company goals be SMART?
Not in the wording. Keep the goal short enough to remember and put the specific, measurable part into the evidence you track underneath it, so the numbers can change as you learn without rewriting the goal everyone knows.