PESTEL analysis: the six factors, a worked example, and how to turn a scan into decisions

A PESTEL analysis is a structured scan of the six outside forces that can change your market without your permission: Political, Economic, Social, Technological, Environmental and Legal. It is useful when it ends in a register of decisions, each with an owner, a trigger to watch and a review date. It becomes box ticking the moment it ends in a slide with six boxes of general observations. The discipline that separates the two is simple: every item must name the specific effect on your business, say which way it points, and state what you would do differently if it happened.

This page explains the framework, works through an example, and shows how to turn a scan into decisions. For the internal half of the picture, see a guide to SWOT analysis.

The six factors, and what actually belongs in each

Factor	The question to answer	Where the evidence comes from
Political	Which government decisions change our cost, access or demand?	Government and ministry announcements, trade body briefings, budget documents
Economic	What is happening to our buyers budgets, borrowing costs and currency?	World Bank data, OECD data, central bank statements, national statistics offices
Social	How are buyer habits, demographics and expectations shifting?	Census and labour statistics, industry surveys, your own customer interviews
Technological	What change alters how we deliver, or how buyers find and choose us?	Vendor roadmaps, patent and standards activity, search interest trends
Environmental	Which physical, climate or resource factors affect supply, cost or reporting?	Regulator guidance, insurer requirements, customer procurement rules
Legal	Which rules on contracts, data, employment or product change what we may do?	Statute and regulator sites, official statistics for context, your own legal counsel

Two habits keep the rows honest. Attach a source to every item, because an unsourced claim in a strategy document gets repeated for years. And write each item as a sentence with a direction: "fuel duty rising increases our delivery cost per order" rather than "fuel prices".

PESTEL, PESTLE, PEST and the rest

PESTEL and PESTLE are the same six factors in a different letter order, so either name is fine as long as you cover all six. PEST is the older four factor version without Environmental and Legal, which is thin for anything regulated or physical. STEEPLE adds Ethical. Pick one, name it on the document, and spend the time on the content rather than the acronym.

A worked example

Take a payroll software company, forty staff, selling to small employers in one country, now considering a second country next year. Here is what a useful scan looks like. Notice that every line names an effect and an action, and that the figures it depends on are deliberately left to be sourced from the national statistics office and the regulator rather than guessed.

• Political. Payroll rules follow government policy directly, so a change of administration in the target country can reset our product roadmap. Action: confirm the next scheduled budget or policy event in that country and treat it as a release milestone.
• Economic. Our pricing is per employee, so our revenue moves with our customers headcount. Action: model the plan against employment data for the target market from the national statistics office, and set a trigger if employment in our target sectors declines two quarters in a row.
• Social. Remote and contract work is changing who counts as an employee, and our product assumes a traditional contract. Action: add contractor handling to the roadmap before launch, not after.
• Technological. Accounting platforms in the target market have their own app marketplaces, and small employers choose payroll from inside the tool they already use. Action: treat the integration as a launch requirement, not a later phase.
• Environmental. Low direct exposure, with one real item: larger customers now ask suppliers for environmental reporting in procurement. Action: prepare a short supplier questionnaire response before the first enterprise deal needs it.
• Legal. Payroll involves personal and financial data crossing a border, so data residency and retention rules shape the architecture. Action: get written legal advice on data residency before engineering commits to a hosting region.

That scan took an afternoon and produced six decisions, two of which change the engineering plan. A scan that produces no decisions did not need doing.

Turning the scan into a register

Score each item on impact and likelihood, give it a time horizon, and name one person. The register is the deliverable, not the six boxes.

Factor  Item                              Impact  Likely  When    Owner  Trigger to watch
Legal   Data residency rules for payroll   High    High    Pre-launch  CTO   Regulator guidance update
Tech    Accounting marketplace integration High    High    Pre-launch  Head of Product  Partner API changes
Econ    Customer headcount drives revenue  High    Medium  Ongoing     CFO   Sector employment, quarterly
Pol     Policy change resets payroll rules Medium  High    Annual      CTO   Budget date in target country
Social  Contractor and remote working mix  Medium  High    6 months    Product  Share of contractor queries
Env     Procurement environmental asks     Low     Medium  12 months   COO   First enterprise RFP

Review: quarterly. Anything High/High goes in the plan now.

Three rules make the register last. Only items with a named owner stay on it. Anything scored high on both impact and likelihood becomes a line in the current plan rather than a note. And set the review date in the calendar when you write it, because an annual scan is where this framework usually goes to die.

When it is genuinely useful

• Entering a new country or sector, where your instincts from the home market do not transfer.
• Before a large, hard to reverse commitment: a factory, a licence, a multi year contract, a platform rewrite.
• In regulated markets, where the Legal and Political rows are the business rather than background.
• When a market has changed and nobody can say how, because the six headings force the conversation past the one factor everybody is already arguing about.
• As the input to a plan, directly feeding the opportunities and threats half of a SWOT.

It becomes a box ticking exercise in three recognisable ways: when it is done because a template asked for it, when the items are generic enough to apply to any company in any industry, and when nobody is named against anything. If you can swap your company name for a competitor and the document still reads correctly, it is not an analysis of your situation.

How it fits with the other frameworks

Framework	Looks at	Use it for
PESTEL	The outside forces acting on a whole market	Scanning an environment you do not control
Porter five forces	The structure of competition in an industry	Judging whether the industry can be profitable
SWOT	Your own strengths and weaknesses against outside factors	Deciding what to do, using the other two as input

The sequence that works: PESTEL and five forces first to understand the ground, SWOT second to decide, and the register to make sure the decisions get done.

What gets asked about PESTEL analysis

What is a PESTEL analysis in marketing?

It is the outside half of your market research: the political, economic, social, technological, environmental and legal forces that change what your buyers want, what they can afford and what you are allowed to say. In marketing it usually feeds positioning, pricing, channel choice and campaign timing.

What is the difference between PESTEL and PESTLE?

Only the order of the letters. Both cover the same six factors, so use whichever name your organisation already uses.

How often should it be refreshed?

Review the register quarterly and redo the full scan once a year, or immediately when something large changes, such as a new regulation, a new market or a change of government in a country you sell into.

How many items should go in each factor?

Three to five that genuinely affect you. A row with twelve general observations is a reading list. If a factor really has nothing material, write "low exposure" and the one thing you are watching, then move on.

Who should take part?

Somebody from sales, somebody from operations and somebody who reads the regulation, plus one person who writes it all down. Sales brings the buyer signals, operations brings the cost reality, and the register needs a single owner.

Is PESTEL useful for a small business?

Yes, in a shorter form. An afternoon, six headings, three items each, one owner per item. The value for a small team is in noticing the one change that would hurt early enough to act.

One item worth adding to your technological row

There is a change in buyer behaviour that belongs in the Technological row of most scans written this year and is rarely there. Buyers increasingly start by asking ChatGPT, Gemini, Perplexity, Claude or Google AI Overviews who the suppliers are for the problem they have, and act on a paragraph that names two or three companies. Whoever is named enters the shortlist, and whoever is not is never compared. The assistants answer the same question differently, so this is a specific, checkable item rather than a general trend: write down the questions a buyer in your category would ask, leave your own name out of the wording, and record which companies come back. That gives you an item with a direction and a trigger to watch, which is what the register needs. AI Knows Us runs those checks across the assistants.