Corporate Strategy

Concept

The company-level choice of which customers to win, on what strength, and — just as much — what the company will not do.

Why it exists

A small company doesn't need to write down what it will work on. Whatever lands in front of you is the work, and when only one thing lands, that thing is the plan. Past forty people, with several kinds of paying customer in play, the arrangement stops holding. Sales asks for a feature only one large account will ever use, because that account is close to signing. Marketing spends its budget pulling in more individual users. Engineering takes both requests into the same quarter and gets each one halfway built. Everyone made a defensible call from where they sat, and the company as a whole is pointed nowhere.

Meetings in that period ended the same way every time. Someone would ask why a piece of work was on the list, and the answer would be that a customer asked for it. Nobody had grounds to argue with that, so every request went onto the list, and the longer the list got, the more the order was set by whoever spoke with the most conviction. Two quarters of that leaves you with eight features stopped at the halfway mark and a product that satisfies no particular customer.

Corporate strategy is the word for putting a standard in that empty spot. Most of the content sits on the "won't do" side rather than the "will do" side. When Pagedeck decides this year belongs to company accounts, that sentence also says no additional people go to the individual plan, and that individual users can ask for a feature as loudly as they like without moving up the order this year. A document with nothing excluded from it is a wish list. Saying the company will do everything is the same as saying no order has been set.

Once a standard exists, the question in the room changes. Instead of "is this a good feature," people ask "does this help at the spot we chose to win." The first question ends in a contest of taste; the second one has an answer. The person whose request got turned down also learns that it wasn't rejected for being bad — it didn't match this period's standard. Half of what strategy does in practice is deliver that explanation so nobody has to improvise it.

How this field breaks down

The terms under corporate strategy fall into five groups: direction, which writes down where the company is headed; choice, which picks what gets the resources inside that direction; analysis tools, which lay the situation out before anyone picks; strategy types, which are the answers common enough to have earned names; and structure, which describes how a chosen answer keeps turning on its own.

Direction holds two terms. A mission is one sentence on why the company exists. A vision is one sentence on what it wants to look like some years out. The tense separates them. A mission is true today and rarely changes; a vision isn't true yet, and once you reach it you have to write a new one. If Pagedeck's mission is "turn scattered documents into a team's shared memory," its vision runs closer to "within three years, half the software teams in the country write their meeting notes in Pagedeck." Neither sentence tells anyone what to do this week, but without them the next group has no yardstick for choosing.

Choice holds two terms, and this is where strategy actually cuts. Strategic priorities are the handful of pushes a company commits to for one period, and "handful" means around three. Write ten and the people and the budget split ten ways, and none of the ten finishes. Competitive advantage is the place where the company does better than its rivals, and it only counts as an advantage if rivals can't copy it easily. A prettier screen gets matched in a quarter, so it isn't one. Three years of a customer's documents already sitting in the product, plus a whole team trained on how search works there, is hard to match, so it is. Priorities are this quarter's answer; advantage is the reason that answer was chosen.

Analysis tools hold three terms, all of them ways to get scattered information onto one surface before anyone decides. None of the three produces an answer. Their job ends at gathering facts that different people held differently onto one page so the room is looking at the same picture, and a person decides what to do from there.

  1. SWOT analysis — sorts the situation into strengths, weaknesses, opportunities and threats. It's the simplest of the three, which is why it gets used most and why it so often stops at four filled boxes. The value shows up when you pair a strength against an opportunity and pull one sentence of action out of it.
  2. Porter's Five Forces — asks whether an industry is built to make money, using five pressures: new entrants, substitutes, supplier power, buyer power, and rivalry among the companies already there. A document collaboration market is cheap to enter and cheap to leave, so the first two press hard, and that's where the conclusion comes from that no single feature holds a position for long.
  3. PESTEL analysis — sweeps the world outside the company across political, economic, social, technological, environmental and legal factors. It isn't a tool for watching rivals; it's a tool for noticing the board itself shifting. Tighter data protection rules can turn "where is our data stored" into a purchase requirement overnight.

Strategy types hold four terms — answers that enough companies have chosen that they now travel as a single word in a meeting. Blue ocean means building a market where nobody is competing yet instead of fighting inside a crowded one. Vertical integration means taking over a step of the chain currently handled by someone else, such as moving payments in-house after years of renting them. Diversification means spreading into several lines of business, which keeps the company standing when one line stumbles but makes it hard to lead in any of them. Focus strategy is the opposite: pour everything into one narrow area, and it's usually the answer available to a forty-five-person company. The same market supports different types depending on how much you have to spend. Having a name attached doesn't make a type something to pick off a menu. Each one is the label on a road other companies already walked, so it's worth borrowing only as far as their situation overlaps yours. Choose the label first and start bending the company to fit it, and what customers actually want drifts away from what the document says.

Structure holds one term. A flywheel is a business loop that picks up speed on its own once it starts turning. The more documents a team has stored, the more useful search becomes; the more useful search is, the more other departments put their documents there; and that makes it more useful again. Once the loop turns, user growth needs less advertising behind it. Strategy types describe what to choose. Structure describes why that choice gets stronger with time.

The five groups run in one direction. Direction sets the yardstick, analysis tools put the current situation on the table, choice picks this period's answer from what's on it, the answer takes a name from the strategy types, and if it's designed to compound it becomes a structure. The order gets reversed often enough to be worth naming: companies that start with analysis, produce a thick document, and attach a direction afterward. Documents built that way send every reader home with a different conclusion.

How it sounds at work

"Company accounts are the priority this year, so the individual-plan rework moves to next year."

Work that isn't on the priority list is being taken out of this period.

"Does this thicken our competitive advantage, or is it just a nice feature?"

A request to separate good ideas from the ones that belong in this quarter.

"That's a target, not a strategy. It doesn't say how the revenue doubles."

Sending back a document that has numbers in it but no choices.

At Pagedeck the phrase came up most in the first quarter after the Series A. Grace closed the year-end meeting by committing to teams of twenty or more and to company accounts, and that one sentence changed three things at once. Sofia pulled time away from five-person inquiries and put it on accounts above thirty seats. Ravi moved advertising budget off individual users and onto material written for the person evaluating tools for a company. Mia dropped four consumer features from the roadmap and moved permissions management and audit logs up.

The pushback came from the individual side. Long-time users had been asking for the same features for six months with nothing to show for it, and the support channel filled with people asking why it had gone quiet. Grace refused to delete those requests from the list and had them tagged as untouched this year instead. A deleted list has to be rebuilt from scratch the next time; a tagged list can be pulled out whole on the day the standard changes. When strategy shifts, the items that were held back move to the front, and the team that kept the reasoning moves faster at that moment.

Grace settled one more thing in the same meeting: the standard gets revisited every quarter and never mid-quarter. When a large account arrives with a different demand, the pull to adjust the standard on the spot is strong. But a standard that moves whenever it's convenient only costs the people who trusted it and set their own work aside.

What people get wrong

The most common mistake is measuring strategy by the thickness of the document. The format people have seen runs to dozens of slides, so the association sets early. What actually gets used fits on one page: who the company is going after, on what strength, what it will do this period, and what it won't. Four lines is enough to quote in a meeting. A forty-slide deck takes two months to build, nobody but its author reads it to the end, and an unread document never gets cited at the moment a decision splits. A strategy that isn't used in decisions sits in the same place as no strategy at all. If one page looks thin, keep the supporting material in a separate document behind it. Bundle the page people quote in meetings together with the pile of evidence and both of them go unread.

Confusing strategy with targets is nearly as common, helped along by the fact that both get announced at the same year-end meeting. "Double revenue next year" is a target, and a target names a destination while leaving the route blank. Strategy picks the route. Doubling by adding company accounts, doubling by raising what existing customers spend, and doubling by entering another country lead to different hires and different features. Set the target and leave the route empty, and each team quietly picks whatever route looks best from its own desk. Those routes point in different directions, so the year passes with the resources split. What's left in December is a number that wasn't hit and no way to explain why.

Easily confused with

TermWhat it decidesHow it differs
Product strategyWhat the product will and won't buildIt runs one level down. Corporate strategy picks which customers to serve; product strategy picks what gets built for them

Where to go next

  • Strategy

    see where strategy meets the company's other decisions

  • Mission

    look at the sentence strategy uses as its yardstick

Sub-terms

Last updated 2026-09-16