How to use Viewfield: three mornings in Webflow's market
In this note
The plainest way to show what Viewfield does each morning is to run it on one market, start to finish. We picked one that is public, busy and familiar to anyone who runs a B2B website: Webflow's.
Webflow is not a Viewfield customer, and nobody at Webflow saw or used this workspace. We set it up on 3 October 2026 the way any team does, from the company's public website, and let it run for three days. Everything below is what the workspace showed, drawn from public pages, posts and AI answers. Where it suggests something Webflow could say, that is the workspace's suggestion, not advice Webflow asked for. Read it as you would read your own: the brand at the center is the one whose positioning does the filtering, and in your workspace that brand is yours.
1. Start from the website
We gave Viewfield one address, webflow.com. Within about half an hour the engine had read the site and drafted the four things every later judgment depends on.
What the company sells, in a paragraph: a visual web platform for building, managing and optimizing websites, with a CMS, hosting, A/B testing, personalization and AI-search optimization, bought mainly by marketing and design teams.
Who it sells to. Three audiences, with marketing and design teams at mid-market B2B SaaS and enterprise companies as the primary one, beside marketing leaders and web marketers, and designers and freelancers.
Who it competes with. Six companies, each with a class and a reason a person can read. Contentful, Framer, Wix and WordPress came back as direct rivals, read every day. Squarespace came back as adjacent and is read once a week, because "its primary buyer is small businesses and creators, not mid-market B2B marketing teams". Wix Studio was set aside with four words: "Same company as Wix."
What it claims. Five positions, each a single sentence drawn from the site. One of them: "Webflow turns a visual canvas into clean, production-ready code, so designers control layout without hand-coding." A sixth, about team governance, was proposed from what the engine observed and is waiting for a manager to accept or reject it. Nothing changes a team's positioning on its own.
This is the step worth ten minutes. A rival in the wrong class, or a claim you would never make, bends every morning after it. Correct them once. A class a person sets stays set, and nothing the engine does later overwrites it.
2. Read your positions before you read the news
Each position gets a short read: what buyers are asking, which rivals claim the same ground, and what proof the brand has. Two of Webflow's, as the workspace read them.
On design control, "no tracked competitor is claiming clean code output for itself", and independent reviews and AI answers already credit Webflow with precise layout control and clean code. Among the rivals the workspace tracks, nobody else stands there.
On AI search visibility, marketing leaders are openly asking how to get seen in AI answers, Contentful has written AEO-ready content into its core promise, and Webflow makes the claim "but you hold no proof yet". The read names the proof that would change that: a documented customer site that gained AI-answer visibility after being built in Webflow.
The second read is the useful kind of uncomfortable. A claim without proof is a promise, and the promises are the claims a rival can take. For your own team, this is where the content plan starts.
3. Read the morning Brief
Overnight, Viewfield reads competitor pages, community threads, trade press, newsletters and posts. Over three days the Webflow workspace stored 480 signals from 268 different sites. For each morning, an edition weighed the day's candidates against the positions above and kept the ones worth a look: 25 of 146 on the first night, 15 of 154 on the second, 19 of 162 on the third. Each morning's Brief then carried three items. Nine items in three days.
Here is one from the first morning in full, because the shape of an item is the point. It was titled "A 2,500-page Webflow team asks who moved to Framer and came back", and it was written for marketing and design teams at mid-market B2B SaaS and enterprise companies.
- Fact: on 2 October, a team on r/webflow running about 2,500 pages, mostly CMS-driven, asked who had moved to Framer and come back, and how a large CMS and custom code fared.
- Meaning: a switching question from a large CMS team is a live buying moment for teams like it. The post lists custom code, tracking scripts and HubSpot forms beside the CMS, so the question covers how the whole site runs, not only where its content lives.
- Position: the all-in-one workspace claim is contested, because a team weighing a move lists its CMS, scripts and integrations together.
- What this opens: a blog post, "Moving a big CMS site? Judge it by what keeps running", arguing that a platform move for a CMS-heavy marketing site should be judged on the tracking, consent and form scripts that keep working after launch, not on how fast the content moves across.
- How sure: medium. "One poster on one forum carries this; replies from teams that moved and returned would show how widely the question is shared."
Two things in it are worth expecting of any read you pay for. It says how sure it is and what would change its mind, so you know how much weight to put on it before the meeting. And the advice is in the brand's own frame. The rival's name is in the story, but the suggested piece is about what a buyer should judge, which is ground the brand can own. It is not a rebuttal.
Another item that morning joined six moves in twenty-one days into one pattern. Squarespace's Blueprint AI now takes a brand personality and previews several pages, Figma saves motion styles that coding agents can read, and a developer on r/webflow reports that Webflow's own MCP server is now good enough to build most of a site. The read: buyers ask less whether AI can make a site and more whether the result keeps brand and engineering standards, and whether the team can still edit it. Its suggested piece: "The agent built the page. Can your team still edit it?"
4. Let the week add up
On Monday the workspace wrote a Weekly Brief, which reads the week's mornings together instead of adding another list. Its opening for Webflow's market: "AI site building is now a given, and buyers judge it on brand fidelity and production quality. Meanwhile, AI search visibility is becoming a score marketers track, and cost predictability is shaping platform choices."
Under that it set out what the week added up to, the pattern that changed, what to watch next week, and what changed on the brand's own pages, which for this fortnight was nothing. It also counted what the team had done with the week: six items across two mornings, none acted on, all still open. No team reads this workspace, so the zero is accurate. On a real team, that is the line a head of marketing reads first.
5. Check what AI answers say about the category
Every day the workspace asked ten buyer questions of ChatGPT, Claude and Gemini and recorded who each answer named, in what order, and which pages it cited. The questions were drafted from the site and the audiences, for example "As a marketer at a mid-market B2B SaaS company, which visual website builder platforms should I consider?" and "What are the best alternatives to Framer among visual website builder platforms?"
Over three days the answers leaned Webflow's way. It was named in all 89 answers the workspace counted, and its average place was 1.5. Framer, the next most named, averaged 2.4.
The exception is the more useful number. Asked which visual website builders are the most popular in the United States, the answers put Squarespace, WordPress and Wix ahead of Webflow on average. On the questions written closest to Webflow's own claims, a shared workspace for design, content and optimization, or shipping campaigns in hours and showing up in AI answers, it came first or close to it, and its own pages were cited more often than on any other question. A brand is usually strongest where buyers already use its words. The gap is on the plain, popular question.
Then the sources. The answers carried 2,112 citations from 412 domains. On ChatGPT the most cited domain was reddit.com, with 310 citations to webflow.com's 127. Across the three platforms, the Webflow page cited most was its enterprise page, ahead of the home page, the CMS feature page and the pricing page.
For a team, that is a short list of work. The pages AI answers already cite are the first ones to keep current. A forum that outranks your own site in ChatGPT's answers is a reason to check that your pages answer the buyer's question in the buyer's words. On your own workspace, Viewfield suggests the next step for a question that leaves you out: a change to a page you already have, or the post that is missing. With your CMS connected, it saves the change as a draft beside what is live, and a manager decides whether to publish it. We did not connect a CMS here, since the site is not ours.
6. Act on one item, or on none
Every item in a Brief offers the same four actions. Create draft writes the piece the item suggested, in the brand's voice, and opens it in the editor with the item's evidence beside it, where the team comments on the sentence in question and reads any rewrite before keeping it. Create brief writes a fuller Brief on that one subject. Explore opens a chat about the item. Position adds a claim the team wants to own. A draft leaves Viewfield as text, a Word file, a Google Doc or a draft in the team's own CMS. Nothing posts on its own.
Doing nothing is a real outcome too. Each item can be marked Important, Interesting, Archive or Delete, and the next mornings learn from it. Three days after a decision, Viewfield reads what moved around it: what customers started saying, what competitors did next, what AI answers say. It reports that as an association, never as a cause.
What three mornings come to
For Webflow's market the routine would have been ten minutes on the first day correcting rivals and claims, then three items each morning, each with its reasons, its confidence and a suggested piece. A team that acted on two of the nine would have had drafts of a blog post on judging a site move by what keeps running and one on whether a team can edit what an agent built, both in the brand's own frame and both written from evidence anyone can check.
Not every item was certain. Where one source carried an item, it said so and named what would firm it up, and a person still reads each one before acting on it. The read makes the deciding quicker. It does not do the deciding.
To run the same three days on your own market, start with your website. The trial is fourteen days with no card: start here.