Weekly meetings, a scorecard, quarterly priorities. I help your team build an AI chief of staff into the rhythm you already have, starting with one useful workflow.
The weekly meeting, the priorities, and the scorecard work. The prep, the follow-through, and the "where are we on that" still live in scattered notes, inboxes, and someone's memory. Meanwhile AI shows up as one-off experiments that never become part of how the team runs.
The fix isn't more AI tools. It's one useful workflow, built into the rhythm you already have.
A founder or operational leader running EOS, Scaling Up, Shape Up, or Agile, with fragmented information, repetitive coordination work, and an internal owner who can put changes into practice.
A founder or product leader with the same problem, when the standard scope fits. Product teams can start with customer evidence instead.
It's the routine I run every day. We start with the morning brief, and once it's useful, the debrief closes the loop and the Sunday plan sets the week.
Your top three, active workstreams, meeting prep, and the decisions waiting on you, ready before you sit down.
Decisions logged, commitments filed, workstreams updated, and tomorrow's short list written.
Last week scored against your goals, one bottleneck named, and next week's top three set.
The chief of staff is where most teams start, but the same engagement works for other parts of your rhythm.
Begin with a paid 30-day engagement. Continue monthly when there's a valuable next objective, or conclude at the month-end review.
We identify the recurring problem, the internal owner, your tools, access needs, and the baseline.
We map the workflow together and build its first version.
Your owner runs it on real work and records what worked and what failed.
We fix what broke, document ownership, and set the review routine.
We compare results with the baseline, then agree on the next objective or conclude.
My morning brief, end-of-day debrief, and Sunday plan all read from one source of truth: my daily notes, my active workstreams, and my goals. I built a software company past $500K in monthly recurring revenue, and today I lead product at SalesAi. What I set up with your team is the routine I depend on every day.
See the routine run on a fictional company: watch the demo.
Takes about three minutes. I read every application myself.
I'll review it within two business days. If it's a fit, you'll get a link to book a 20-minute fit call.
No. Any team with a regular planning cadence, a set of priorities, and a scorecard or key metrics is a fit, whether that's EOS, Scaling Up, Shape Up, or Agile. Small software teams with the same coordination problem are a good fit too.
Yes. It's the default because it pays off fastest, but we can start with meeting follow-through, metrics commentary, shared knowledge, or another recurring workflow. Same scope, same price. For something bigger, like a company-wide rollout, email me and we'll talk it through.
We build the first version together in our working sessions, and your internal owner runs it. This is guided implementation, not custom software development or a done-for-you rollout.
The tools your team already runs on: your calendar, email, team chat, meeting notes, and project board. We connect them in stages, starting with what the morning brief needs, so each piece is useful before the next one goes in.
At the month-end review we compare results with the baseline. If there's a valuable next objective, we continue monthly. If not, we conclude and you keep everything we built.
No. We set a baseline and an agreed success measure up front and review against it honestly. I don't promise savings, headcount reductions, or business outcomes.