The things people ask before we talk. If yours isn't here, email me at erica@layeradvisory.com.
Most teams start in one of two ways. In executive partnership I work with the leader first, getting AI into their own week so they can see what it could mean for the organization and decide where the team starts. In the Foundations workshop I start with conversations with the leadership and an anonymous survey of the whole team, then run two sessions shaped around what comes back, where the team sees what AI can do for its work and writes its own agreement on how they'll use it, with the guardrails and security built in.
From there, some teams go deeper with me: a team capacity program, a discrete build of one process, or a six-month Embedded AI Partner engagement.
It depends on the engagement. Executive partnership is $1,250 a month at the founding rate, month to month. Team capacity starts at $15,000, with three to four hours a week per person while it runs. A discrete build is a set price for a defined scope, starting at $5,000. I quote Foundations and the Embedded AI Partner engagement for your team, because they depend on its size and what we'd build.
The TEMPO cohort for individuals is $1,000, or $2,000 for TEMPO Guided, which adds a direct line to me and up to four 30-minute one-to-one sessions on your own system.
The best next step is a free 15-minute call. If there's a fit, I'll follow up in writing with what I'd suggest and what it would cost.
Involved, and that's the point. This work only lasts when your team takes it on and has the time to keep using it after I'm gone, which is why I need a leadership team that wants it and people on the team I can build alongside.
For team capacity, plan on three to four hours a week per person. For a build, most of the time comes from the person who owns the process, since I build it with them and they're the one running it afterwards.
I teach and build with Claude, alongside tools like Lovable, Supabase, and n8n when a system needs them. Everything I build and teach is made for Claude, so for team capacity and the Embedded AI Partner engagement your team needs to be on Claude or to have decided to move to it. The systems won't run on Copilot, ChatGPT, or Gemini as they are.
Claude licenses are a separate cost, paid to Anthropic. I'll help you work out which plan your team needs. If you haven't settled on a platform yet, that decision is often where we start.
Before anything is connected, we decide together what AI is allowed to touch, who can see what, and where a person on your team makes the call. In Foundations, your team writes that into its own agreement. Anything that shouldn't go near AI stays outside what we connect.
Work with them. The goal of every engagement is a team that can run and extend what we built after I'm gone. I build your team's capacity alongside the systems themselves, through training, playbooks, and often a private team program, so the capability stays with you.
Purpose-driven founders and leadership teams at startups, small businesses, and nonprofits, usually growing faster than their systems can keep up with. I work best with leaders who already want AI in how their organization works and a team that's curious about what it makes possible.
An automation expert automates a process you already have. I start from the business objective, reimagine how the work could run with AI in the loop, build the system, and then train your team to use it and keep building on it.
I come to this as an operations leader who builds (I'm not a developer), so I work with the same tools and constraints as the people I'm helping.
It can, and the research is worth taking seriously. Studies from MIT, Microsoft, and Wharton have all found the same pattern: people who passively accept what AI produces get worse at thinking, catch fewer errors, and feel more confident while it happens. But the outcome depends on how the AI is designed and used. In a Harvard trial, students working with an AI tutor built to make them think learned more than twice as much as students in a regular class, and in less time.
I build for that second way of working. Every system I build has a human decision at every point that matters, and everything I teach starts from you setting the direction and judging the result. If a system makes your team's thinking lazier, it's a bad system, and I'd tell you to turn it off.
Yes, this is agentic AI. The way you'll build these systems means agents do a significant amount of the work with you: reading, drafting, organizing, and running the routine pieces of your day. You set the direction and make the calls, and the agents carry the work between your decisions.
Yes. A lot of what I now build and teach I first worked out inside organizations, as a CEO and then as a fractional COO. My fractional COO practice is full right now, so I'm not taking on new clients for it. If you want me inside your team, the Embedded AI Partner engagement is six months working alongside your COO and leadership team, on the systems and on your team's ability to run them.
No. TEMPO is built specifically for non-technical professionals. No coding is required. Everything I've built, I built without an engineering background, and TEMPO teaches you to do the same, starting from the system I use every day and shaping it around how you actually work.
A Claude Pro subscription ($20 a month) or access through your organization's enterprise Claude plan, running Claude Code in the Claude desktop app. You'll also need a computer you're comfortable on (Mac or Windows), an email and calendar you can connect, and a meeting notes tool. Copilot, ChatGPT, and Gemini can't run the system.
The cohort runs over six weeks, live and fully recorded. Plan on up to four hours a week for the live session and that week's build, plus the time you spend using the system day to day.
The fastest way to know whether there's a fit is a short conversation.
Whatever the engagement, the idea underneath is the same: adopt AI deliberately, so it strengthens your thinking, in service of work that matters. That's what I mean by AI on purpose.