The contract is stalled between broader publishing access and a package finance can defend.
Marketing needs faster site changes, while security and procurement need clear control and predictable cost.
Who you’d be doing this for
“Finance asked me why we need these seats, and I’m still rebuilding the answer slide by slide.”
Pooja Jain · Director of Web Design
Leads the design team at the prospective corporate customer and must justify both access decisions and website delivery speed.
What is at stake
A $90k annual contract is paused because procurement cannot separate access needs from cost. You must weigh a simpler package against the publishing control the buying committee expects.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- broader collaborator access vs. defensible cost
- faster marketing updates vs. publishing control
- contract momentum vs. accurate forecast
- initial simplicity vs. expansion potential
Why Webflow
Webflow Designer sits where branded website speed, collaborator access, and governed publishing meet.
Written with these in mind
Not your kind of problem? 32 more at Webflow, or browse every organization.
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.