Role Guide
AI Strategist
What we expect from an AI Strategist at Rosedale: keep clients aligned and confident, turn vague requests into testable definitions of “done,” shape high-impact scopes, and communicate clearly with the team.
Expectations
How you work
1) You reduce client uncertainty
At any point, the client can answer, without guessing: “What are we building, why, what’s next, and what could change?”
You do not let confusion sit across weeks. If something is unclear, you treat it as a decision that needs to be made. The goal is to prevent surprises. For our team, and for our clients.
2) You define what will make our work good
Which means pushing the client to let us into the specifics of what they need. Asking for clear examples, rules, criteria that make the difference between ok work and work that helps them improve their business.
You do not allow “quality” to be subjective. You force it into something that can be checked.
3) You guide the scope of our builds
The AI Strategist is the extension of our intelligence to the outside world. The strategist’s job is to shape toward the highest impact work that is feasible with our constraints.
This will include prototyping, asking for specific examples, and highlighting higher impact projects we could pursue together with our clients.
You keep projects unblocked by getting decisions, inputs, and feedback from the client when we need them.
4) You create tasks (issues in Linear) that are buildable without back-and-forth
The tasks you create for our devs are clear, rich in the necessary context and leave no confusion on what criteria are needed to make the work successful.
You prioritize the work (see chapter 3 for definitions)
What you deliver
1) Predictable, complete communication
In call and async. Communication should elevate the quality of our work by being timely, and complete. Our communication should reflect back what was agreed, what has been done, what’s coming and by when.
2) A shared definition of done
At task and build level. You collect and refine client-approved, testable targets that prevent endless iteration
3) Scopes that are detailed enough to execute on
With clear boundaries, clear dependencies, and clear assumptions so we don’t have to guess what work will look like and what good work will look like.
4) Questions and prototypes that help us understand our clients
Your questions will help us uncover what the client really needs. Your prototypes will help us collect actionable feedback.
Required Reading
- 02How We Scope A New Build
Build Process
- 03How We Start Working On A New Issue
Build Process
- 04How We Estimate and Prioritize Issues
Build Process
- 05When Work Can Be Considered Done
Build Process
- 06How We Communicate With Our Clients
Client Communication
- 07Response and Escalation Standards
Client Communication
- 08How We Use Linear
Internal Systems