The setting
builds AI-powered tools for product teams. applies AI models to creative design tasks for professional creatives and designers.
A successful creative demo and a credible close date are different kinds of evidence.
Sellers need room for relationship context, and finance needs purchase expectations grounded in recorded commitments.
Who you’d be doing this for
“Our designers loved the demo. Then someone asked procurement for a signature date before I'd even sent them the business case.”
Paivi Nielsen · Design Director · a character in this brief
Sponsors a Mid-Market evaluation and depends on the seller to distinguish creative approval from readiness to purchase.
What is at stake
Mid-Market sellers carry 40 late-stage deals into review, but managers disagree about what successful demos prove. You decide whether AI flags missing purchase evidence or infers a conflict with the recorded close date for sellers and managers to judge.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- creative enthusiasm vs purchase commitment
- consistent milestones vs relationship context
- missing records vs contradictory evidence
- account coverage vs customer permissions
Why Figma
Creative demos link Figma source files with Weave outputs, but enthusiasm for generated assets does not establish a customer's procurement timeline.
Written with these in mind
Not your kind of problem? 59 more at Figma, 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 Figma. They are listed as sources, not as openings. The lines under a posting are its own words, where it meets this brief.
- Account Executive - Figma Weave (London, United Kingdom) (opens in a new tab)
- You will work closely with Figma Account Executives and cross-functional partners to understand customer needs, demonstrate relevant workflows, and guide opportunities from first conversation through close.
- Distribution Partner Manager, LATAM (opens in a new tab)
- Identify, evaluate, and execute new strategic opportunities for Figma that require complementary GTM partners
- Partner with Figma’s GTM teams to source, scope, and progress partner-influenced opportunities
- Account Executive, Enterprise (Bengaluru, India) (opens in a new tab)
- Account Executive, Mid-Market (London, United Kingdom) (opens in a new tab)
- Create and manage a pipeline of Mid-Market accounts from inbound and outbound activity to consistently meet or surpass sales targets
- Senior Account Executive - Figma Weave (opens in a new tab)
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 committing to a deal before it checks out.
Sellers and managers place 11 of 36 email expansion deals in different months despite reading the same activity.
You decide how far AI can turn conflicting Salesforce activity into a proposed next step before the seller and manager make the forecast call.
Partner-assisted deals carry close dates that recorded customer activity does not always support.
You decide whether an absent milestone warrants a forecast exception or a request for the seller to supply evidence first.
Discovery calls are leaving enterprise opportunities with inconsistent next steps and unanswered qualification questions.
You have to decide where the draft stops and the seller starts when a call's notes become a Salesforce next step the buyer may read as a promise.
The same setting, from another role
Each is set around Figma’s Figma Weave, written for a different role. They’re separate briefs, not the same scenario.
New enterprise customers remain active while their onboarding steps stall.
You decide whether AI can assign a stalled milestone from conflicting notes and activity, or must ask the CSM to establish the step first.
Six design customers need evidence that another creative tool earns its budget.
You weigh a comparable evaluation service against the customer-specific work needed to make its conclusions useful.
Eight design teams face a funding decision tomorrow, but only three have shown where generated assets shipped.
You must weigh broader continuity against a year of support promises that the available evidence may not justify.