Own the account context for selected Creative Operations and Systems / Process Design clients: stakeholders, priorities, history, open questions, risks, decisions, and follow-ups.
Run the client operating rhythm so meetings, updates, actions, blockers, decisions, and handoffs do not drift or depend on memory.
Turn vague client requests into clear next steps, questions, owners, dependencies, and decision points.
Become highly capable with AI tools and workflows for account management: meeting preparation, account research, stakeholder mapping, summarisation, action tracking, client-ready drafting, QA, and reusable account memory.
Use AI to make your client work sharper, not just faster.
Make clients feel well looked after: clear communication, good energy, strong follow-up, useful questions, and the confidence that you are properly on top of their account.
Write clear client-ready summaries that make messy work understandable without overpromising or hiding uncertainty.
Maintain stakeholder maps, account notes, decision logs, follow-up trackers, and reusable context so Storm can manage the relationship professionally.
Work closely with Account Management, Creative Operations, AI Operations, and technical colleagues to keep client work moving.
Spot when a client ask is really a workflow, visibility, approval, stakeholder, or operating-rhythm problem.
Help internal teams avoid overbuilding, underscoping, or saying yes before the client need is clear.
Improve the way account knowledge is captured, summarised, shared, and reused over time.
High agency. You do not wait for every next step to be handed to you, but you know when to escalate early.
Structured thinking. You can break ambiguous work into users, inputs, outputs, owners, statuses, risks, decisions, and definitions of done.
A serious interest in becoming an expert at AI-enabled account management.
Strong client presence. You are warm, confident, curious, responsive, and naturally good at making clients feel understood.
Comfortable working around workflow and collaboration tools such as Airtable, Monday.com, Notion, Asana, spreadsheets, Slack, Teams, or similar systems.
Enough systems/process literacy to understand what is being built, why it matters, where the risks are, and how to explain it to non-technical stakeholders.