top of page
Won agencies and enterprises building on WordPress and Drupal by treating website operations as a discipline distinct from either hosting or development — a category ('WebOps') it named and then owned.
1
MODEL
BUSINESS MODEL
Infrastructure Platform
model bm
HOW THEY BUILT IT
Founded 2010, built a managed platform for WordPress/Drupal with built-in Git-based version control and multi-environment (dev/test/live) workflows for agencies and enterprises managing many sites; coined 'WebOps' as a category term distinct from generic managed hosting.
HOW TO ARCHITECT IT
1) Build for the pain of managing many sites at once, not the single-site owner. 2) Coin your own category name distinct from 'hosting' to reposition the buying conversation. 3) Build Git-based, multi-environment workflows natively rather than leaving that to developers' own tooling.
DISTRIBUTION MODEL
Direct Sales
dm
HOW THEY OPERATIONALIZED
Direct sales to agencies, enterprises, and higher-ed institutions managing multiple sites; tiered subscription by site count, traffic, and workflow features.
HOW TO REPLICATE WHAT WORKED
Sell first to agencies managing many client sites on the pain of inconsistent environments and manual deployment, using 'WebOps' framing to justify a premium over commodity hosting.
| PATTERNS OF THIS MODEL
PATTERNS IN MANAGED PLATFORMS BUILT ON OPEN-SOURCE CMS:
1. SELL TO THE ORGANISATION MANAGING MANY SITES, NOT THE OWNER OF ONE. Agencies, universities and multi-brand enterprises have a governance problem; single-site owners have a hosting problem. Only the first supports a real ACV.
2. COINING A CATEGORY ("WebOps") IS A PRICING MOVE. It reframes the purchase from commodity hosting — where the comparison is $10/month — to an operations platform. Category names buy time and shortlist inclusion; they do not stop commoditisation, as Zuora's decade demonstrates.
3. DEVELOPER WORKFLOW IS THE SWITCHING COST. Git-based multi-environment dev/test/live pipelines embed in daily habit. Ripping that out means retraining every developer, not migrating files.
4. A SINGLE MEGA-ROUND CAN BECOME A CEILING. ~$198-200M raised, with the $100M Series E funded solely by SoftBank Vision Fund 2 at $1B+ in July 2021 — and no publicly disclosed round since. Five years growing into a 2021 mark, with a CEO transition reported (Zack Rosen to Sameer Kazi; sources disagree on current attribution).
5. YOUR ROADMAP IS SET BY THE FRAMEWORKS YOUR CUSTOMERS ADOPT. Adding Next.js alongside WordPress and Drupal (April 2026) is survival work: managed platforms must follow the frontend, or the frontend leaves.
Scale reference: ~700,000 sites, ~17B monthly pageviews.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — BUILD FOR MANAGING MANY, NOT MANAGING ONE.
Standard: the single-site owner is price-sensitive and low-value; the agency or enterprise running two hundred sites has a genuinely different problem — environments, deployment, governance, consistency. Same underlying technology, an order of magnitude more willingness to pay. In any category, find the operator who has your problem at N=100.
GOLDMINE 2 — COIN A CATEGORY NAME TO ESCAPE A COMMODITY COMPARISON.
Standard: "WebOps" moved the conversation away from hosting, where the buyer compares monthly price, toward workflow, where they compare capability. Renaming what you sell is the cheapest repositioning available to a challenger — and it works because buyers research categories before brands.
GOLDMINE 3 — MAKE THE DEVELOPER WORKFLOW THE RETENTION MECHANISM.
Standard: Git-based multi-environment dev/test/live workflows become the way a team works, not a feature they bought. Teams that rely on your deployment process do not leave for a cheaper server.
THE PIT — CATEGORY COINAGE IS NOT DEFENSIBILITY.
"WebOps" generated shortlist inclusion; it did not stop WP Engine, Kinsta or Cloudways from offering equivalent staging and Git workflows. If your defensibility slide says "we named the category," you do not have a defensibility slide.
THE SECOND PIT — YOUR FATE IS TIED TO SOMEONE ELSE'S CMS.
A business optimised for WordPress and Drupal inherits their trajectory. Headless architectures and AI-generated sites are both changing what a CMS deployment even looks like.
MOVE WITH CAUTION — THE AGENCY CHANNEL IS A CONCENTRATION RISK.
Agencies bring volume and they also churn in blocks: losing one partner removes dozens of sites at once. Track revenue concentration by agency, not by site count.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Fragmented Market
WHY THEY WON
WordPress/Drupal hosting spans budget hosts and premium single-site hosts (Kinsta, WP Engine). Pantheon won agencies/enterprises managing dozens of sites needing standardized workflows.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Pantheon entered directly building its own multi-site WebOps platform, targeting a fundamentally different buyer than single-site hosting incumbents.
FOOTHOLD STRATEGY
fs
Beachhead Strategy
The beachhead was web agencies managing multiple client sites needing standardized, Git-based dev/test/live workflows across their client portfolio.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
Coining and evangelizing the 'WebOps' category term through content and conference presence.
KEY LEARNING
If your product serves a fundamentally different need than the commoditized version of your category, name and evangelize a distinct category term to reposition the buying conversation.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: In a fragmented infrastructure category, do not sell HOSTING — sell the WORKFLOW that makes managing many instances survivable. The buyer with fifty sites has a fundamentally different problem from the buyer with one, and only one of them has real budget.
RULE 1 — SEGMENT BY PORTFOLIO SIZE, NOT BY TRAFFIC.
Budget hosts serve one-site owners on price; Kinsta and WP Engine serve premium single sites on performance. The unclaimed position is the agency, university or enterprise running dozens or thousands of sites who needs standardised environments, one dashboard and repeatable deployment. That is a governance product wearing a hosting label.
RULE 2 — DEV/TEST/LIVE, GIT AND CONTAINERISATION ARE SWITCHING COSTS DISGUISED AS CONVENIENCE.
Once a team's deployment process, CI and release discipline are shaped by your platform, leaving means retraining every developer and rebuilding every pipeline. The moat is the customer's own operating procedure, not your uptime figure.
RULE 3 — ARCHITECTURAL CHOICES MADE EARLY DEFINE WHO YOU CAN AND CANNOT SERVE.
Pantheon's container-based architecture and network filesystem deliver its scaling story and also impose constraints — for example, plugins that write outside standard directories do not work, and platform-level email is not sent directly. In infrastructure, every constraint that creates your advantage also disqualifies a segment. Name the disqualified segment out loud rather than discovering it in churn data.
RULE 4 — THE AGENCY IS A CHANNEL, NOT JUST A CUSTOMER.
Agencies standardise, resell, migrate client sites and recommend defaults. Winning an agency wins its whole book. Every durable player in this fragmented category is partner-led, and partner programmes compound far better than direct sales here.
RULE 5 — CMS-BOUND INFRASTRUCTURE INHERITS THE CMS'S RISK, INCLUDING ITS POLITICS.
A platform tied to WordPress and Drupal is exposed to those ecosystems' governance, licensing disputes and the headless/JavaScript shift. The strategic response is to extend beyond the CMS: Pantheon added Next.js support in April 2026, running CMS and modern frontends on one platform, and shipped a Content Publisher for Google Docs (public preview, September 2025) and an MCP integration for AI-driven workflows (2026).
EVIDENCE: Founded 2010 by Zack Rosen, Josh Koenig and David Strauss; venture-backed through Series E with investors including Scale Venture Partners; infrastructure runs on Google Cloud with regional data residency in the US, Europe, Australia and Canada; publishes a 99.99% uptime SLA. Sameer Kazi was appointed CEO in November 2024. Revenue, ARR and customer counts are not publicly disclosed, and the company remains independent as of mid-2026.
MARKET TYPE: Fragmented Market (managed WordPress/Drupal hosting), won by re-defining the category as WebOps for site portfolios.
| MARKET ENTRY PLAYBOOK
THE STANDARD: WHEN THE INCUMBENTS SELL TO THE SITE OWNER, ENTER BY SELLING TO THE PERSON WHO MANAGES MANY SITES. A different unit of account creates a different product, a different price and a different buyer.
RULE 1 — CHANGE THE UNIT FROM ONE SITE TO A PORTFOLIO.
Commodity hosting prices per site and per resource. Agencies, universities and enterprises run dozens to thousands of sites and need fleet-level governance, environments and deployment. That is not a hosting upgrade; it is a different category, and it is why the price ceiling is higher.
RULE 2 — SELL THE WORKFLOW, NOT THE INFRASTRUCTURE.
Dev, test and live environments, version control and one-click deploys are what the buyer is really acquiring. Infrastructure is the delivery mechanism, and treating it as the pitch drags you back into a price war with commodity hosts.
RULE 3 — THE AGENCY IS BOTH CUSTOMER AND CHANNEL.
One agency standardising on you brings its whole client roster. Partner programmes, margin share and multi-site management are entry requirements in this segment, not later additions.
RULE 4 — BUILDING ON OPEN-SOURCE PLATFORMS MEANS YOUR ROADMAP HAS A LANDLORD.
Serving WordPress and Drupal ties your addressable market to their trajectories and to their governance disputes. Write down what happens to the business if either platform's direction changes.
RULE 5 — "WEBOPS" IS A CATEGORY NAME, AND NAMING IS A COMPETITIVE ACT.
Coining an adjacent category moves the buying criteria off uptime and price and onto release velocity, where you are the only credible answer.
EVIDENCE: founded 2010; container-based platform for WordPress and Drupal aimed at agencies, higher education and enterprise multi-site operators rather than single-site owners; raised a $40M Series E in 2019 led by SoftBank, with total funding reported at over $160M. Current revenue and customer counts are undisclosed.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: SELL TO THE BUYER WHO BUYS ONCE AND DEPLOYS MANY TIMES. An agency, reseller or consultancy is not one customer — it is a distribution channel that pays you.
RULE 1 — Find the professional who makes the technology choice for OTHER PEOPLE.
Agencies pick the hosting, the CMS and the stack for every client they serve. Winning one agency wins its entire portfolio, and portfolios grow without any further sales effort from you.
RULE 2 — SELL THE AGENCY'S OWN OPERATIONAL PROBLEM, NOT THE CLIENT'S.
The agency's pain is inconsistency: every client site on a different host, with a different deployment process and a different failure mode. Standardisation across the portfolio is the pitch. The end client never hears it.
RULE 3 — IN DEVELOPER-ADJACENT SEGMENTS, THE WORKFLOW IS THE PRODUCT.
Dev, test and live environments with proper version control are what make a professional feel professional. Raw performance is table stakes; the workflow is what they cannot get from commodity hosting.
RULE 4 — AN ECOSYSTEM BEACHHEAD INHERITS THE ECOSYSTEM'S TRAJECTORY.
Building on one open-source CMS means your addressable market rises and falls with that CMS's share of new site starts. Diversifying across frameworks is expensive and usually late.
RULE 5 — AGENCIES CHURN WHEN THEIR CLIENTS CHURN, AND THEY NEGOTIATE HARDER EVERY YEAR.
A channel that consolidates your revenue also concentrates it. Model portfolio-level churn, not logo churn.
EVIDENCE: Pantheon built its foothold with web agencies managing many client sites on WordPress and Drupal, selling standardised Git-based dev/test/live workflows across a portfolio rather than single-site hosting. It raised a Series E in 2021 reported at around $100M with SoftBank participation, at a valuation reported near $1B. It has not disclosed revenue or customer counts, and no exit has been announced. The category around it has consolidated heavily — WP Engine took private-equity investment, and Newfold Digital absorbed multiple hosting brands.
CHECKLIST: (a) Identify who chooses the stack for others. (b) Sell their standardisation problem. (c) Make the workflow the differentiator. (d) Watch the underlying ecosystem's share of new builds. (e) Track revenue concentration by channel partner.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription
PRICING MODEL
Usage-Based Pricing
WHY THEY WON
Tiered subscription scaling by site count, traffic, and workflow/environment features; enterprise/agency-scale custom pricing.
Pricing scales primarily by site count and traffic tier, matching how agencies actually grow usage.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
Web development agencies, enterprises, and higher-education institutions managing multiple sites.
Committee-led procurement for agencies and enterprise/university IT teams evaluating standardized workflow tooling.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
THE STANDARD: Usage pricing works when the meter is something the customer's success produces automatically. In hosting, that meter is traffic — and traffic is the one number a marketing team is proud to report.
RULE 1 — PRICE PER SITE PLUS TRAFFIC, SO GROWTH IS BILLED WITHOUT A CONVERSATION.
Every successful campaign raises the bill. Nobody negotiates because the increase arrived alongside the result they wanted. This is the cleanest alignment available in infrastructure.
RULE 2 — SELL THE WORKFLOW, NOT THE SERVER.
Dev/test/live environments, version control and one-click deployment are what separate a managed platform from commodity hosting priced at a tenth of the rate. Without the workflow you are selling compute and will be compared to it.
RULE 3 — THE AGENCY IS YOUR REAL CUSTOMER AND NEEDS ITS OWN PRICE STRUCTURE.
Agencies deploy many client sites and re-bill your fee. Multi-site management, white-labelling and partner economics matter more than any feature. Price so the agency's markup is comfortable, and they become your salesforce.
RULE 4 — TRAFFIC SPIKES ARE A TRUST EVENT, AND OVERAGES DECIDE WHETHER YOU SURVIVE THEM.
The customer's best day should not produce a punitive invoice. Soft overages, alerts and grace periods cost margin and buy renewal. Hard cutoffs during a traffic surge end relationships permanently.
RULE 5 — YOUR CEILING IS THE CHEAP HOST AND YOUR FLOOR IS RAW CLOUD.
Managed platforms live in a narrow band between commodity hosting and DIY infrastructure. Both edges compress you. The defence is uptime during a launch, which is worth far more than a rate card.
THE WILLINGNESS-TO-PAY INSIGHT: A marketing team is not paying for hosting — they are paying so the site does not go down during the campaign they have already spent the budget on. Willingness to pay in infrastructure is a function of what is already sunk into the event your product must survive.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
THE STANDARD: Infrastructure priced on traffic and site count inherits its customers' web traffic. When AI search removes 20-40% of that traffic, your pricing metric shrinks and your customers start questioning the premium at the same time.
RULE 1 — PREMIUM-PRICED HOSTING IS THE FIRST LINE AUDITED WHEN TRAFFIC FALLS.
Customers publicly describe paying $60,000+ a year for two low-traffic sites and downgrading. When the value story is performance-at-scale and the scale disappears, the price becomes indefensible.
RULE 2 — SUPPORT QUALITY IS THE ACTUAL PRODUCT IN MANAGED HOSTING, AND COST CUTS DESTROY IT VISIBLY.
Customer and employee reviews through 2026 consistently describe support degradation following headcount reduction. In a category where the premium is justified by service, cutting service converts a margin fix into a churn engine.
RULE 3 — GROWTH HAS ALREADY FLATTENED.
Third-party estimates put revenue near $124M with roughly 10,000 customers and headcount down to about 413 (from 432). Approximately $200M raised against that scale means the venture path is effectively closed.
RULE 4 — DRUPAL CONCENTRATION IS A DECLINING BASE.
A meaningful share of the installed base sits on a CMS losing share to WordPress and headless architectures. Category decline is churn you cannot sell against.
RULE 5 — CONTENT-PLATFORM DEMAND IS BEING RESHAPED BY AI, NOT JUST REDUCED.
If fewer sites are built and more content is delivered through answers rather than pages, the unit being priced — hosted sites and visits — is the wrong unit for the next decade.
NOT DISCLOSED: Pantheon publishes no official revenue, ARR or retention. Figures above are third-party estimates and should be treated as such.
Where the model can break
4
MOTION
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Market Development (New Customer Segments)
HOW THEY EXPAND
Expanded from web agencies into enterprise and higher-education segments managing large, distributed multi-site portfolios.
Focus Strategy
HOW THEY COMPETE
Rather than compete with Kinsta/WP Engine for individual site owners, focuses on multi-site operational workflow needs.
GROWTH ENGINE
GTM
ge n gtm
Partnership Growth
Loop: an agency onboards its portfolio for standardized workflows → recommends the platform to new clients → each new agency brings its own existing portfolio. Depends on continued agency satisfaction relative to newer entrants.
Direct sales, category-defining content around 'WebOps,' and partner programs incentivizing agencies to standardize entire portfolios.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
Once an agency has standardized its entire client-site workflow around Pantheon's tooling, migrating even a portion means retraining the whole team on a different workflow.
| MOAT INTELLIGENCE
THE STANDARD: Managed infrastructure is only defensible when it removes a RISK the customer's team cannot carry — not when it removes work they could do themselves more cheaply.
RULE 1 — SELL THE UPTIME LIABILITY, NOT THE SERVER.
Hosting is a commodity with brutal price competition. Guaranteed availability during traffic spikes, automated security patching and a supported upgrade path for a CMS the customer cannot afford to break — that is a liability transfer, and liability transfers command real margin.
RULE 2 — THE WORKFLOW IS STICKIER THAN THE HOSTING.
Dev/test/live environments, one-click clones, version control integration and multi-site dashboards become how an agency's engineers work. Migrating means changing not the server but the team's habits and their client delivery process.
RULE 3 — AGENCIES ARE THE HIGHEST-LEVERAGE CUSTOMER AND THE HIGHEST-CONCENTRATION RISK IN THIS CATEGORY. One agency brings dozens of sites; one agency loss removes dozens at once. Track site-level and agency-level retention separately or you will be blindsided.
RULE 4 — YOUR MOAT IS TIED TO THE FATE OF THE CMS YOU SPECIALISE IN.
A platform built around WordPress and Drupal inherits their trajectory. Drupal's enterprise decline and the governance turbulence in the WordPress ecosystem are exogenous risks no amount of product quality offsets.
RULE 5 — HEADLESS AND COMPOSABLE ARCHITECTURES ARE THE STRUCTURAL THREAT, because they move the hosting decision to the front-end layer where Vercel and Netlify compete, leaving you hosting only the back end.
EVIDENCE (with limits stated):
- Pantheon is a WebOps platform for WordPress and Drupal, providing managed hosting plus a development workflow — dev/test/live environments, containerised infrastructure, global CDN and multi-site management — sold to agencies, higher education, government and enterprise marketing teams.
- I DID NOT VERIFY CURRENT FUNDING, VALUATION, ARR, CUSTOMER OR SITE COUNTS IN THIS PASS. Publicly circulating figures date from a 2021 round and are not current. Confirm before citing.
- Competitive reality: WP Engine (private-equity backed, and party to a high-profile dispute with WordPress leadership), Acquia (Vista-owned, Drupal-focused), Kinsta, Cloudways (DigitalOcean), plus AWS/Cloudflare at the infrastructure layer and Vercel/Netlify at the composable layer.
- The exogenous risk is real and specific: the WordPress ecosystem experienced significant governance conflict from late 2024 onward, and Drupal's share of new enterprise CMS selections has been declining for years.
THE SIGNAL TO COPY: Pantheon's durable asset is that agencies build their delivery process inside it. But a moat tied to a single open-source ecosystem is a moat with someone else's hand on the tap. If you specialise in a platform you do not control, your strategic risk register starts with that platform's governance, not with your competitors.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — SELL THE INFRASTRUCTURE THE AGENCY HATES MANAGING
Target the professional who is forced to be a sysadmin against their will — here, agencies and developers running WordPress and Drupal sites for clients.
Make the workflow the product: dev, test, live environments with one-click deploys and rollbacks. Hosting is the commodity; the workflow is the purchase.
Sell to the agency, not the end brand. One agency relationship carries dozens of sites.
REFUSE: competing with cheap shared hosting on price. You are selling engineering time, not disk space.
$1–5M ARR — PRICE PER SITE, LAND WITH ONE
Charge per site so revenue grows automatically as the agency wins clients, with no new sales conversation.
Build free developer sandboxes; the person who evaluates you is not the person who pays.
Instrument migration: an importer from the customer's current host is a sales tool, not a feature.
WATCH: sites per account, month over month.
$5–10M ARR — MAKE THE ECOSYSTEM YOUR SALES TEAM
Sponsor and staff the open-source communities you depend on. In CMS ecosystems, contributor credibility converts into agency preference in a way advertising does not.
Add performance, security and compliance as paid tiers — the enterprise CMS buyer purchases risk reduction.
DECIDE: whether you serve agencies or enterprises. They want opposite things from the same product.
$10–50M ARR — MOVE UPMARKET WITHOUT LOSING THE DEVELOPERS
Sell to enterprise marketing and IT on governance across hundreds of sites, which is a problem no agency-scale competitor addresses.
Keep the developer experience unchanged as you add enterprise controls; losing developer preference removes the reason you get shortlisted.
WATCH: revenue concentration in your largest accounts.
$50–100M ARR — DEFEND AGAINST THE PLATFORM SHIFT, NOT THE COMPETITOR
Assume the underlying CMS market moves — headless, composable, static, AI-generated front ends — and build for the architecture that follows, not the one that funded you.
Raise growth capital only against a specific expansion. Pantheon raised a large late-stage round in 2021 with SoftBank participation at a reported valuation around $1B; treat the figure as reported rather than audited.
WATCH: net revenue retention as agencies consolidate.
$100M+ ARR — NOT CONFIRMED: SAY SO
State it plainly: Pantheon does not disclose ARR and no reliable third-party figure exists placing it in this band. Its funding stage implies scale but implies is not evidence.
The durable lesson for founders is the one from the first band: in infrastructure sold to professionals, the workflow is the product and the ecosystem is the channel. Whoever owns the deploy owns the account.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: In global payroll, the software is the wedge and the MONEY MOVEMENT is the business. Own the regulated payments layer or you are a reporting tool sitting on someone else's rails.
HOW TO COPY — THE SEQUENCE:
1. Target the buyer with a problem no domestic vendor solves — companies paying people in 10+ countries, where the finance team has no single view of workforce spend.
2. Lead with the CFO's analytics, not the HR admin's workflow. Workforce spend reporting is a finance purchase with a finance budget.
3. Use a self-serve cost calculator as top-of-funnel lead generation in a category where every competitor hides behind a demo.
4. BUILD THE REGULATED PAYMENTS LAYER YOURSELF. Papaya's licensing work (including direct SEPA access as an EMI in Europe) is what makes it structurally different from a payroll aggregator.
5. Publish core plan rates openly — rare at this price tier and a genuine trust advantage.
WHAT WORKED:
- Explosive early growth on the remote-work tailwind: 300%+ year-on-year revenue growth for three consecutive years to 2021, taking the company from $1.2B (Series C, March 2021) to $3.7B (Series D, $250M led by Insight Partners, September 2021) in months.
- A native payments layer no direct competitor matches, plus coverage across 140-160 countries and enterprise logos including Intel, Microsoft, J&J and Toyota.
- Modular packaging (EOR, payroll, contractor, payments, workforce management) so the same customer expands without a new sales cycle.
WHAT DID NOT WORK / THE CAUTIONS:
1. THE $3.7B MARK IS FROM SEPTEMBER 2021 AND HAS NOT BEEN RESET. Third-party ARR estimates around $145M (2024) against roughly $440-450M raised imply the business has spent years growing into a peak-cycle valuation. Sources disagree and none are company-confirmed.
2. THE TAILWIND REVERSED. Growth that arrives from an external shock is borrowed; headcount underwritten to 300% growth is the problem when the rate normalises.
3. REGULATED PAYMENTS IS A PERMANENT COST CENTRE, not a feature — licensing, safeguarding and compliance across 100+ jurisdictions never becomes cheaper.
4. DEEL AND RIPPLING SET THE PACE. In a category where one competitor is materially larger, differentiation must be structural (payments licensing) rather than functional.
bottom of page