The expansion depends on proving delivery value without turning included AI into a pricing promise.
Procurement needs a defensible spend case while programme leaders need relief from delayed cross-agency handoffs.
Who you’d be doing this for
“My deputy asked which handoff we’d actually speed up, and I didn’t have one clean answer.”
Omolara Sackey · State Programme Manager
Runs cross-agency initiatives whose milestone updates depend on project owners across multiple departments.
What is at stake
A $420,000 expansion is stalled because procurement cannot connect included AI tools to a defensible delivery outcome. You have to weigh a faster commercial narrative against evidence the programme sponsor can stand behind.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- procurement certainty vs. AI-led value
- fiscal-window urgency vs. defensible assumptions
- workflow activity vs. delivery outcomes
- near-term expansion vs. long-term adoption
Why Asana
AI Teammates and Dash now sit inside the paid plan, making realized workflow value central to enterprise expansion conversations.
Written with these in mind
Not your kind of problem? 28 more at Asana, 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.