5.1 The behaviors you're trying to create

• Work starts in the AI layer. Team members open Claude before they open individual tools. The connected workflow is the default starting point for deal prep, account reviews, reporting, and follow-ups.
• Nobody is copy-pasting context between systems and AI. If someone is still assembling information manually and pasting it into a chat window, they haven't made the Era 2 shift.
• Playbooks run after every customer interaction, not just when someone has time. The connected workflow makes consistency automatic rather than dependent on individual discipline.
• Managers review AI-generated outputs and focus their coaching on strategy and judgment, not on whether administrative work got done.
• The team identifies missing system connections as problems to solve. When a workflow would be better with data from another source, people flag it rather than working around the gap manually.
• People share connected workflows and improvements with the broader team. The organizational knowledge compounds.
• The connective tissue roles shift from manual data movement to workflow design and optimization.
• Presence and knowledge sharing increase because the cost of producing and distributing information is near zero. Silence becomes a signal.
• People resist the urge to over-engineer. They use connected workflows to deliver results, not to build systems for the sake of building systems.

5.2 Permission structures

The permission structure at Era 2 shifts from "it's okay to use AI" to "this is how we work now."

In Era 1, leadership gave permission to experiment. In Era 2, connected workflows need to become the expected way of operating. This is a harder message because it creates a real expectation, not just an invitation. The leader who says "we've connected these systems to Claude and this is how we're running deal prep going forward" is making a decision for the team, not offering them an option.

That directness is necessary. If connected workflows are optional, they won't be adopted universally. The people who are comfortable with their Era 1 copy-paste setup will stick with it because it works well enough. The value of Era 2 comes from organizational consistency, and you don't get consistency from optionality.

The build versus buy boundary needs to be explicit and public. Celebrate the people who experiment with building workflows. Thank them for validating the need. Then be clear that production workflows will be built on supported, maintained platforms. If someone builds a great workflow, acknowledge the contribution and explain that you're going to buy the proper version. This prevents resentment from the builders while preventing the accumulation of fragile custom infrastructure.

The hardest permission to give at Era 2 is permission to stop doing things the old way. Some people have built their identity around being great at manual execution. The CSM who prides themselves on knowing every account from memory. The RevOps analyst who can build any report in a spreadsheet. When you tell them the new way involves AI pulling the data and doing the first pass of analysis, it can feel like you're devaluing their expertise. Be direct about what you're actually saying. Your expertise is not being replaced. It's being applied at a higher level. You're moving from data assembly to data interpretation. From execution to oversight. That is a promotion, not a demotion.

“Your expertise is not being replaced. It’s being applied at a higher level. You’re moving from data assembly to data interpretation. From execution to oversight. That is a promotion, not a demotion.”

5.3 Enablement systems

The enablement challenge at Era 2 is more structural than Era 1. In Era 1, you shared prompts and let people figure it out. In Era 2, you need to teach people how to use connected workflows that involve multiple systems, and you need to do it without overwhelming them.

Start with live demonstrations using real data and real workflows. Not screenshots or hypothetical examples. Have someone on the team run a connected deal prep workflow in front of the group using an actual deal from the pipeline. Let people see the AI pull data from the CRM, reference the last call transcript, and produce a brief in real time. The visceral experience of watching it work is more persuasive than any training deck.

Build the connected workflows so they're easier than the old way. This is the single most important enablement principle. If the connected workflow requires more steps, more configuration, or more thought than the copy-paste approach, people will revert. The new way needs to be simpler, faster, and more reliable than the old way. Every friction point you leave in the connected workflow is a reason for someone to go back to doing it manually.

Create workflow templates that the team can use immediately. A deal prep workflow. A follow-up workflow. An account health scan. A pipeline review. Each one should be pre-configured and ready to run. People should be able to open the workflow and start using it without building anything themselves. The builders on your team can customize and improve these templates over time, but the starting point needs to be zero-configuration.

Keep the enablement ongoing. Era 2 workflows will evolve as your connections improve and your team develops new use cases. A monthly workflow review where the team shares improvements, surfaces problems, and demonstrates new approaches keeps the momentum going.

5.4 Measurement

The leading indicators at Era 2 shift from individual adoption to workflow adoption.

In the first 30 days, measure how many people have switched from copy-paste to connected workflows for at least one regular task. This is the adoption bridgehead. If fewer than half your team is using a connected workflow within the first month, the enablement or the workflow design needs attention.

In the first 60 days, look at consistency metrics. Are playbooks running after every customer interaction or just sometimes? Are follow-ups going out within minutes or are people still batching them at the end of the day? The value of connected workflows shows up in consistency, and consistency is measurable.

In the first 90 days, look at the same revenue indicators as Era 1 but with higher expectations. Pipeline velocity should show clear improvement over Era 1 levels. Forecast accuracy should be tightening. CSM risk identification should be happening earlier. RevOps reporting cycles should be visibly shorter.

Track the infrastructure rabbit hole explicitly. If you have people whose core metrics are declining while they spend time building workflows, that's a signal to intervene. The number is still the number.

Monitor the volume of internal artifacts being produced and shared. In Era 2, the cost of producing and sharing information drops significantly. You should see an increase in the volume of internal knowledge sharing. If you don't, people aren't using the connected workflows. If you see a massive spike that's creating noise without signal, you need to address the quality filter.

5.5 Resistance patterns

The most common resistance at Era 2 is "this takes longer than doing it myself."

Someone tries a connected workflow. It takes a few minutes to set up, the connection to the CRM is slow, and the output needs editing. They compare it to their well-practiced copy-paste routine that takes five minutes and produces a result they're happy with. The connected workflow feels slower because it's new and because the setup cost is front-loaded. The copy-paste approach feels faster because they've been doing it for months.

The answer is to acknowledge the learning curve honestly and point to the payoff. The first time you use a connected workflow, it takes longer. The tenth time, it's faster. And the fiftieth time, you've saved hours that you'll never get back from copy-paste. The setup cost is paid once. The efficiency gain compounds over every use.

The second resistance pattern is the infrastructure rabbit hole disguised as productivity. Someone has built an elaborate system of connected workflows and automations. They're proud of it. They can demonstrate it. They can explain why every piece matters. But they haven't closed a deal in three weeks. When you raise this, they'll defend the work by explaining the future value it will create. The response is straightforward. The number is the number. If the systems work is delivering results, great. If it's replacing results, it needs to stop. Use the build versus buy framework to channel this energy productively. Acknowledge the innovation. Replace the custom build with a supported solution. Get the person back on their primary job.

The third resistance pattern is quality sensitivity backlash. As AI-generated output increases in volume, people become more sensitive to the quality bar. They start noticing when something reads as AI-generated. They push back on receiving documents that feel formulaic or generic. This is actually a healthy signal. It means the team's quality standard is rising. The answer is not to suppress the feedback but to use it to improve the workflows. If the output from a connected workflow isn't meeting the team's quality bar, the workflow needs better context, better prompts, or better human review before the output gets shared.

The deeper risk at Era 2 is not resistance. It's the new normal problem. AI stops feeling magical. The initial excitement of Era 1, where every new prompt felt like a revelation, fades into routine. Connected workflows just become how work gets done. That's actually the goal. But it means the energy and enthusiasm that drove early adoption isn't there to push through the harder changes. Leadership needs to maintain momentum through results, not through novelty. Show the team what's improving. Show them the numbers. Make the connection between connected workflows and revenue outcomes visible and specific. The magic wearing off is fine. The results need to keep compounding.

“The magic wearing off is fine. The results need to keep compounding.”