"The nature of our work is shifting. Not eventually — now. The questions we're being asked are getting more complex. The timelines are getting shorter. And AI tools are starting to show up everywhere, doing some of what we used to spend hours on."
I'm not going to pretend you haven't noticed. You have. So let's actually talk about it.
Some of what we do is changing faster than the job descriptions say
Some of you have already started using AI — and aren't sure if you should
Some of you are worried about what this means for your role
Let's Name the Concerns Upfront
What IS changing
How we produce first drafts (RFPs, architecture docs, summaries)
How fast we can turn around research and positioning
The baseline expectation for preparation before customer meetings
What "good output" looks like at scale
What ISN'T changing
Your judgment about what's technically right for a customer
Your relationships and trust built over years
Your ability to read a room and adapt in real time
The value of genuine curiosity and technical excellence
Your career here — this is about expanding what you can do
"This isn't about replacing you. It's about removing the parts of the job that were never the best use of your brain."
Where Your Time Will Actually Go
Before (Now)
Hours on RFP writing, slide creation, doc formatting
Hunting for the right internal reference or past deal
Repeating the same onboarding context to every new stakeholder
Context-switching between selling and building
After (What We're Building Toward)
First draft in minutes, your judgment sharpens it
Structured knowledge base that surfaces what you need
Consistent materials — focus on customization, not creation
More time in front of customers, solving real problems
"You'll spend less time writing RFPs and more time solving problems. That's the actual trade."
Concrete Roles. Honest Lines.
Solutions Architects (SA)
AI Handles
You Keep
First-draft architecture docs
Technical judgment + design decisions
RFP response drafting
Customer trust + relationship calls
Competitive positioning summaries
Live whiteboarding + discovery
Internal knowledge retrieval
Knowing when the standard answer is wrong
DSE
AI Handles
You Keep
Demo script generation + variation
Live demo delivery + improvisation
Feature documentation first drafts
Deep product expertise
Meeting prep briefs
Stakeholder reading + room navigation
Post-call summary generation
Deal context + strategic framing
"The line isn't fixed. We'll keep refining it based on what we learn together."
Here's When You'll Start Seeing the Difference
Phase 1
Days 1–14 We Listen First
Map where the real friction is in your workflow
You tell us what wastes your time — we don't assume
Two pilot volunteers identified
Phase 2
Days 15–45 We Build Together
Pilots test new workflows with real work, not demos
Weekly check-ins — honest feedback loop
If something isn't working, we say so and adjust
Phase 3
Days 46–75 We Learn Out Loud
Pilots share back what they found — good and bad
Lessons become a playbook the whole team can use
No mandatory rollout yet
Phase 4
Days 76–90 We Decide Together
Honest read: what worked, what didn't, what's next
Team input shapes what we scale
If pilots say "not worth it" — that matters
"This is a real experiment, not a top-down mandate with a pilot label on it."
A Team of Creative Builders and System Experts
The Creative Builder
Uses AI as raw material
Brings domain expertise + customer insight
Produces higher-leverage outputs, faster
Career path: specialist depth, customer-facing leadership
↔
The System Expert
Designs and maintains AI-assisted workflows
Bridges technical and go-to-market
Multiplies the whole team's output
Career path: COE lead, technical program, platform architect
"Both paths require the same foundation: curiosity, technical rigor, and the judgment to know when the tool is wrong."
"Neither path is a demotion. Both are deliberate bets on where this function is going."
I'm Not Asking You to Trust the Plan. I'm Asking You to Help Build It.
Early Adopters
"I need 2 people to be honest pilots. Not cheerleaders — testers. If something doesn't work, I want to know. The pilots shape the playbook."
Honest Feedback
"Tell me what I'm missing. If you see a gap in this, or something that worries you, I'd rather hear it in this room than in a skip-level in month 3."
Challenge the Process
"If a workflow we build is slower or worse than what you do now, say so. The goal is better outcomes, not AI for its own sake."
"We build this together or we don't build it well. I'm serious about that."
Your Turn
What questions do you have?
What did I miss?
Who's interested in being a pilot?
Notes from this session will be shared back to the team within 48 hours.