Bartlesville · office visit
Bville visit — Cowork game plan
Job
Listen → clarify → navigate. Not own their build.
One line: I'm here to help you think it through — not take it home.
Meeting spine
- What problem hurts most?
- What does good look like?
- What have you already tried?
- Where does the data live / who owns it?
- What's the smallest safe next test?
Consultant moves
- Ask before you answer
- Mirror: So the pain is ___
- Offer 2–3 paths — don't pick their winner
- I don't know yet + how you'd find out
- End with their next step
Don't sign up
Boundaries
Point ≠ build.
Follow-up ≠ own it.
Ownership push: Your team owns it with IT — I can advise on the first cut.
Ready lines
Open
Dan pointed me your way — happy to hear the use case and help navigate options.
Boundary
I may not have the perfect build answer today. I can help frame the problem and a first safe test.
Close
Here's what I heard… Here's what I'd try next… You own the call from here.
If they ask "what can Cowork do?"
Pattern-level — not a build promise
- Repeatable skills / templates
- Fixed landing shape so outputs are auditable
- Human approve before anything scales
- Small experiment first — sanitized examples only
Overthinker rule: Brain spinning? Back to question 1 until it's crisp.