Webflow told you it was repositioning. In public.

There is a moment in every company's repositioning where the strategy is fully visible on the website and nobody outside the company has noticed yet. Webflow had a long one.

For years the pitch was legible in a sentence: visual development for designers who wanted real HTML and CSS instead of a template. Then, gradually, the pages stopped saying that. Not with an announcement — with the slow substitution of nouns. "Website builder" became "website experience platform." Individual designers moved down the pricing page. Enterprise moved up. Three new product names appeared where there had been one.

None of it was secret. All of it was sitting on pages a competitor could have read on any Tuesday.

The pricing page stopped selling websites

Pricing pages are where positioning gets expensive to fake. Marketing can write anything on a homepage; the pricing page has to survive contact with the sales team, the billing system, and the support queue. When it changes, something real changed behind it.

Webflow's pricing did two things worth noticing. First, it split — site plans on one axis, workspace plans on another. That split is not cosmetic. It means the company decided the unit it sells is no longer "a website" but "a team that makes many websites," which is a completely different buyer with a completely different budget. Second, capabilities that would once have been features became separately priced products: localization as an add-on, optimization as its own line, analytics as its own line.

Unbundling a feature into a priced SKU is one of the loudest signals a pricing page emits. It says the company believes there is a standalone budget for that thing — and usually that a competitor already proved there is. Localization pricing in particular is worth reading closely; we've written before about how what a competitor chooses to translate is a better roadmap than what it ships. Webflow charging for localization tells you which customers were asking loudly enough to pay.

The marketplace is where the roadmap leaks

If you want to know what a platform thinks it's becoming, count the extension points.

Webflow University came first and is the least interesting — every tool with a learning curve builds one eventually. The Apps marketplace is the interesting artifact. A template gallery says "we sell a tool." An apps marketplace says "we sell a substrate, and we intend other people to build revenue on top of it." Those are different companies with different five-year plans, and the second one is much harder to displace.

Read the app categories rather than the app count. Categories are a company's own taxonomy of what its customers do all day, published in public, updated whenever the taxonomy stops matching reality. When e-commerce, analytics, CRM sync, and localization categories appear next to design utilities, the platform is telling you its users are running a business function, not decorating a page. The same logic applied to Zapier's app directory, which is effectively a live census of which SaaS categories are consolidating.

The other tell: which apps are first-party. When a platform ships its own app in a category that already has third-party apps, it has decided that category is strategic enough to own. That is a competitive move you can see in a directory listing weeks before it shows up in a press release.

Careers and docs corroborate — or contradict — the story

Marketing pages state intent. Job postings and documentation reveal capacity. The gap between them is where you learn whether a repositioning is real or aspirational.

Three things to check. Job titles: a company moving upmarket hires solutions architects, security and compliance engineers, and enterprise support before it hires more designers. Locations: an enterprise motion needs a sales footprint in specific geographies, and the postings say where. Team names in the postings themselves — often the org chart leaks through phrases like "you'll join the Optimize team," naming an internal group that doesn't appear anywhere on the marketing site.

Docs corroborate differently. Enterprise buyers ask for SSO, SCIM, audit logs, role-based permissions, data residency, and uptime commitments. Those requirements arrive as documentation pages long before they arrive as marketing copy, because the docs are written for the customer who already signed. If a company claims an enterprise move and its docs have no SCIM page, the move is a slide deck. If the SCIM page shipped six months ago, the move happened and the marketing is catching up.

A trust or security page belongs in the same read. Compliance certifications have long lead times — a newly listed one means the work started a year earlier. It's one of the cleanest lagging indicators of a strategy decision, and one of the most commonly skipped surfaces on our list of pages almost nobody checks.

What a competitor should have done with this

Here's the uncomfortable part. Every signal above was public, permanent, and free. The pricing split, the new SKUs, the marketplace categories, the enterprise job postings, the SCIM docs. Any competitor could have assembled the picture in an afternoon.

Almost nobody did, because nobody was assigned to look on the day each change landed. The pricing page changed once, quietly, and the person who would have understood it read that page four months later — by which point it was ambient reality rather than news. A competitive signal loses most of its value the moment it stops looking like a change and starts looking like the way things have always been.

This is the narrow thing Seeto is actually for. It watches public surfaces — pricing, docs, careers, marketplaces, changelogs — and reports what changed between one check and the next as a discrete event with a timestamp. It won't tell you that a pricing split means a move upmarket; that judgment is yours, and it requires knowing the market. What it removes is the failure mode where the judgment never gets a chance, because the change was never surfaced to a human while it was still a change.

The repositioning was announced. It just wasn't announced in a blog post.