The setting
makes tools for teams at businesses and agencies to build and run websites. lets those teams deploy working web apps on their Webflow-hosted domains.
Keeping deployments available now puts apparently abandoned preview state at risk.
Capacity protection requires space immediately, while developers still depend on environments whose activity records look empty.
Who you’d be doing this for
“The reviewer finally replied this morning. That preview hasn't had visitors in weeks, but it's where I left all the test cases.”
Esmeralda Cruz · Agency application developer · a character in this brief
Maintains a preview containing staged application data while a client's legal reviewer approves the experience.
What is at stake
Application developers could lose preview state as storage runs out within 36 hours. You must weigh irreversible deletion against suspending new previews while existing deployments remain available.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- deployment continuity vs retained preview state
- affirmative consent vs a closing capacity window
- broad eligibility vs defensible evidence
- new project access vs reversible protection
Why Webflow
Applications mounted beside managed websites depend on preview environments that remain useful between infrequent stakeholder reviews.
Written with these in mind
Not your kind of problem? 40 more at Webflow, or browse every organization.
Where the organization context comes fromThe postings this brief was written from, and the reporting read before it.
The organization context comes from public information. The situation and characters are written for the brief.
Job postings it was written from
Public descriptions of the work at Webflow. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Staff Product Manager, AI (opens in a new tab)
- Agent Instructions give a project durable, governed steering, so every agent works from the same brand, structure, and business context instead of rediscovering it session by session.
- Teams across Webflow are building specialized agents on your platform, from site building and content to optimization and marketing.
- Senior Product Manager, Cloud Infrastructure (opens in a new tab)
- You can serve developers who need flexibility and less technical customers, including marketers, who need to get something live with confidence.
- Improve the deployment lifecycle, from shareable preview environments to promotion and rollback.
- Senior Product Manager, Developer Productivity · no longer posted
- This team owns the developer experience end-to-end: CI/CD, build systems, internal tooling, developer environments, observability, and the feedback loops that tie it all together.
- Partner with engineers, TPMs, and cross-functional stakeholders to scope and deliver platform improvements that reduce friction across CI/CD, build systems, developer environments, and observability.
- Principal Product Manager, AI · no longer posted
- Director of Product, Infrastructure and Developer Productivity · no longer posted
- We’re looking for a Director of Product Management for Infrastructure and Developer Productivity to help us meet the demands of a rapidly scaling business, directly shaping how fast our teams can build, how confidently our customers can rely on us, and how boldly we can innovate.
- Define and drive strategy for infrastructure and developer productivity, balancing long-term scalability with immediate needs to empower engineering teams across Webflow.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.
Where similar work appears
Other live briefs connected to this one, and what connects them.
Similar problems at other organizations
Like this one, each of these turns on crossing a deadline that can't be undone.
Deleted records now eat 31% of retention cost, and recovery is slowing in large bases before a fixed storage migration.
You have to cut the cost without removing data that customers expect to get back.
In 34% of workspaces, intermediate artifacts sit past the approved window, and regulated accounts are waiting to expand.
You have to set a default that cuts stored data without deleting what audits and recovery need.
Six weeks before launch, 34 of 500 deletion requests lack conclusive proof for at least one recovery or workflow path.
You have to judge whether the evidence is strong enough to turn the commitment on as promised.
The same setting, from another role
Each is set around Webflow’s Webflow Cloud, written for a different role. They’re separate briefs, not the same scenario.
Enterprise buyers are pausing agency-led Cloud purchases because nobody owns the application after handoff.
You must weigh a scalable partner package against clear operating boundaries for customers and agencies.
A $150,000 ACV deal is blocked because the CTO requires AWS-bound compute and the CMO needs faster agency handoffs.
You have to weigh a quarter-close commitment against a contract promise the delivery path may not support.
Six corporate evaluations worth $420,000 in potential annual contract value are stalled on cost predictability.
You must weigh a sharper commercial commitment against terms that still hold through technical discovery.
Other problems with a similar purpose
In each of these, as in this one, the aim is to make a hard-to-reverse product decision feel clear and defensible before customers are bound by its consequences.
Routing differs by region, so time to the right owner varies threefold, and the slowest paths enter the next filing peak unchanged.
You decide what must be true before launch, since the new path is hard to undo.
A migration review found 14,600 old invoices the new service calculates differently, 430 with conflicting exemption evidence.
You decide what counts as correct before a switch you cannot undo.
Customers can set retention windows, but records past the window pile up because cleanup is still done by hand.
You have to weigh what gets deleted automatically against legal holds and history nobody can recover.
