Aligning AI Initiatives With Business Goals

Aligning AI Initiatives with Business Goals

A conversation with Tim Seamans, VP of Business Transformation, AI Acceleration at Mimecast.

ai transformation

Executive summary

Mimecast’s AI transformation program is not a pilot. It is a company-wide operating system shift run by a small central team reporting to the Chief Digital Officer, with board-level sponsorship and clear commercial targets. In the first 80 days of a major go-to-market initiative, the team directly attributed 2 million dollars in expansion revenue and 30 million dollars plus in pipeline by consolidating signals, standardizing processes, and pairing predictive models with generative tools at the point of action.

Today, every department uses generative AI and more than 60 percent of employees hold a gen-AI certification, supported by a structured AI fluency program embedded into new-hire induction. The program measures outcomes across acquisition, expansion, retention, and productivity, with security and governance built in from the first pilot.

Below is the complete playbook from Tim Seamans, VP of AI Transformation at Mimecast, on how to design the charter, win stakeholder alignment, fix data, implement governance, measure results, and step toward agentic AI.

The Mandate and Where the Function Sits

Mimecast placed AI Transformation under the Chief Digital Officer who also oversees IT. That created proximity to platforms and data, without burying the team as a pure infrastructure group. The model works because the mandate is explicit and backed by the CEO and the board.

Charter in one line

  1. Embed AI in how the company works to improve productivity and efficiency.

  2. Govern AI across product, operations, and customer interactions.

  3. Build proprietary AI capabilities for durable advantage, not just tool parity.


“We went from something we might do if we had the right expertise to something we have to do. We are driving our business using AI.” — Tim Seamans

The Team: Small, Specialized & Outcome Focused

We asked Tim about how his team is currently structured. Here’s his breakdown:

Core capabilities:

  • Engineering and Architecture. Owns build vs buy, data and model architecture for scale.

  • Data Science. Four specialists across predictive modeling and generative techniques.

  • Program Management. Orchestrates cross-functional delivery and partner ecosystem.

  • AI Fluency. Strategy owned by the transformation team, executed with Enablement and L&D.

AI Fluency as a Business Capability

Mimecast made fluency non-optional. A three-level program powers adoption and safe use.

  • Level 1: Foundations for everyone. What AI is, how to use it safely, and where it fits in your job. Delivered in new-hire induction with a short certification.

  • Level 2: Builders. Power users who design task assistants and simple workflows.

  • Level 3: Data scientists and advanced builders. Rolled out after Levels 1 and 2 saturate.


“People using AI will replace your relevance. The bus is already moving. Get on it or get left behind.” — Tim Seamans

Adoption funnel:


Applicants to Level 1 → Certified users → Level 2 builders → Team-embedded champions → Program mentors

How GTM Value Was Created and Measured

The GTM program combined machine learning signals with generative tools at the moment of action. The team unified disparate workflows around outcomes, not around a single mega-platform migration.

Case snapshot: Expansion motion

  • What changed: Signals from CRM, product usage, and recent acquisitions were unified into a single expansion workflow that suggested what to sell, to whom, and why.

  • How it worked: Predictive propensity + recommended offers + gen-AI for messaging and objection handling.

  • Outcomes in 80 days: $2M in directly attributed expansion, $30M plus in pipeline.


“We brought everything together based on outcomes. Signals, the right opportunities, and gen-AI assistance for the conversations.” — Tim Seamans

What is actually measured:

  • Top line: New logo acquisition, expansion rate and mix, retention and churn avoidance.

  • Productivity: Hours saved translated to dollars only when tied to a business outcome.

  • Adoption: Assistant usage, recommendation acceptance, win-rate deltas, time-to-first-action.

  • Leading vs lagging: Recommendation acceptance and assistant usage are leading indicators. Retention is lagging and requires patience.

GTM AI KPI Framework Template:

LayerMetricDefinitionCadenceOwner
AcquisitionSQLs influenced by AIOpportunities created where AI flagged ICP fit or crafted outreachWeeklyMarketing Ops
ExpansionAttributed expansionClosed-won revenue tied to AI recommendation IDsWeeklySales Ops
RetentionRisk mitigations executedPlays launched from risk models with case IDsMonthlyCS Ops
ProductivityTime to first actionMinutes from recommendation to customer touchWeeklyTeam Managers
AdoptionAssistant usage rate% users above threshold weekly sessionsWeeklyEnablement
QualityRecommendation precision% of accepted recs that lead to stage advancementMonthlyData Science

Stakeholder Alignment: Start with Goals, Not Tools

The team begins every engagement with a simple sequence:

Goal → Pain → Option.

  1. Ask business leaders to state their goals in commercial terms.

  2. Map pain points that block those goals.

  3. Decide build vs buy and define a thin slice to prove value.


“If you start with technology, you will likely have a longer road. Take a thin slice, prove value, then scale with champions.” — Tim Seamans

Checklist: Thin-slice pilot readiness

  • Specific goal with a numeric success threshold

  • Data access path documented

  • Process owners signed up to change work patterns

  • Governance controls defined before any user touches the tool

  • Instrumentation for adoption and outcome attribution

Data Strategy: Fix Availability, Standardize, Then Expose

The biggest friction is not algorithms. It is data availability, fragmentation, and security constraints, especially after acquisitions and product evolution.

What Mimecast did:

  • Standardized core entities and created data that did not exist where needed

  • Built secure pipelines into the CRM for contact and buying committee context

  • Used a governed data store as the truth source for customer and prospect insights

  • Accepted that some product feature telemetry still needs work and built a plan to fill gaps

Governance & Security: Parallel to Innovation, Not After It

Compliance, legal, security, and procurement are in the room from day one. The goal is to move fast with minimum viable governance, then scale safely.

Governance controls in practice

  • Approved tool list with monitoring for shadow AI

  • Instructional guardrails for assistants and agents

  • Red-teaming and hallucination checks before scale

  • RACI for policy updates when assistants cannot answer

  • Vendor review criteria built for gen-AI risks

AI Agents: From Task Assistants to True Agentic Coworkers

Internally, assistants handle repetitive tasks with a human in the loop. The next horizon is fully agentic systems that complete actions across tools with verified outcomes.


“Think of true AI coworkers that collaborate across every function. The integration and security layers are the hard part, not the models.” — Tim Seamans

Agent taxonomy:

  • FAQ assistants. High-confidence answers for policies, routed to humans when unknown.

  • Workbench copilots. Research, summarization, draft generation with source grounding.

  • Decision aides. Rank opportunities, propose offers, suggest next best action.

  • Action agents. Execute steps across systems, propose changes for approval, log evidence.

Agent Design Canvas Template:

ElementDescription
Business outcomee.g., reduce time-to-first-meeting by 30 percent
Task scopeSystems to touch, actions to perform, stop conditions
Knowledge sourcesDatasets, embeddings, retrieval policies
GuardrailsAllowed actions, red-team tests, audit logging
Human in loopApproval points, reversibility, rollback
MetricsTask success rate, precision, cycle time, user NPS

Build vs Buy: A Portfolio View

Mimecast builds where proprietary advantage matters, and buys where the goal is speed and enablement. The decision hinges on data gravity, differentiation, and control.

Decision Matrix:

  • Build if: high differentiation, sensitive data flows, need custom workflows, long shelf life

  • Buy if: commodity capability, low switching cost, tight vendor security posture, short time to value

Finance Partnership & How to Talk About Value

Finance is involved from scoping to post-mortem. The team converts time savings into commercial impact only when tied to outcomes, and sets expectations on lagging measures like retention.

Pull quote
“Do not lead with cost cuts. Focus on top line levers and productivity. Cost will follow on a realistic transition curve.” — Tim Seamans

CFO One-Pager for Each AI Initiative Template:

  • Business goal and baseline

  • Expected lift with confidence ranges

  • Time to first value and dependencies

  • Opex and capex profile, including model and infra costs

  • Adoption plan and training load

  • Measurement plan with leading and lagging indicators

Lessons Learned

  • Start with business problems. Translate to a thin slice that can show value quickly.

  • Invest early in culture and fluency. Adoption follows understanding and safety.

  • Instrument everything. You cannot prove value without usage, acceptance, and outcome IDs.

  • Bring control partners in early. Governance cannot be bolted on later.

  • Expect data gaps. Document them, create interim features, and keep shipping.

  • Treat assistants like products. Version, monitor, deprecate, and support them.

  • Communicate reality on timelines. Expansion and acquisition show faster. Retention takes time.

90-Day AI Rollout Plan for a GTM Use Case

Days 0–15

  • Goal definition with numeric threshold

  • Data access and feature map approved by Security and Legal

  • Success instrumentation added to workflow

Days 16–45

  • Pilot assistant with 20 users

  • Daily office hours and fix-fast loop

  • Metrics: adoption, time-to-first-action, acceptance rate

Days 46–75

  • Expand to 100 users

  • Add objection handling scripts via gen-AI with retrieval

  • Introduce auto-logging to CRM

Days 76–90

  • Scale decision and enablement package

  • CFO readout with early commercial impact

  • Backlog for agentic actions

Frequently Misunderstood

Tim debunks some myths and fears surrounding AI and its implementation:

“AI will replace me.”
Not immediately. People fluent in AI will outpace peers. Mimecast solved this with certification and hands-on building.

“The value is time saved.”
Only if time saved converts to a measurable commercial outcome. Usage and acceptance must link to pipeline and revenue.

“We need a single platform.”
You need a single workflow around the outcome. The team unified signals and actions without forcing a monolith migration.

“We can measure retention lift next month.”
Retention is lagging. Set the expectation early and measure the upstream actions now.

A Practical Starting Sequence for Enterprise Leaders

  • Pick one revenue lever. Expansion is usually fastest to show impact.

  • Map the data you have and the data you need. Close only the critical gaps.

  • Ship a usable assistant in weeks that puts guidance where work happens.

  • Instrument adoption and outcome attribution on day one.

  • Train a cohort to Level 1, then Level 2. Reward real usage.

  • Publish a CFO one-pager and review biweekly.

  • Add guardrails as you scale. Prepare for agentic steps with human approvals.

AI Impact at Mimecast

  • 2 million dollars in directly attributed expansion within 80 days.

  • 30 million dollars plus expansion pipeline created in the same period.

  • 95 percent of employees using generative AI in daily work.

  • 60 percent plus certified in generative AI.

  • Small central team with engineering, data science, program management, and fluency.

Want to hear more stories from revenue leaders? Subscribe to The Revenue Lounge podcast to never miss an episode!

More Resources

A 30-60-90 Day Guide for First-Time Directors of Revenue Operations

A 30-60-90 Day Guide for First-Time Directors of Revenue Operations RevOps 10 min Starting a new job as a Director of Revenue Operations is an exciting opportunity to make a significant impact on a company’s revenue growth. To ensure success in this role, it’s essential to have a strategic plan that guides your actions during the crucial first three months. Here’s a 30-60-90 day plan that will help you strategically manage revenue operations and drive sustainable growth. We recently spoke to Hassan Irshad, Director of RevOps at FEVTutor. He shared his approach to this powerful framework, demonstrating how each phase (30, 60, and 90 days) builds strategically upon the last to deliver alignment, trust, and sustained improvement. By breaking down complex goals into achievable milestones, the 30-60-90 day approach empowers RevOps leaders to initiate meaningful change without overwhelming teams. For all the RevOps leaders, it’s a way to approach change with purpose, driving measurable impact and laying the groundwork for long-term success.  The 30-60–90 day framework must be an indispensable tool and here is how you can implement progressive, sustainable growth strategies from day one. First 30 days for a Director of Revenue Operations The purpose should be to gather insights and understand the organization, especially the needs and challenges of different teams. 1. Goals for first 30 days:   i. Meet Key Stakeholders Meet with cross departmental teams like Finance, HR, and Sales to understand their goals, challenges, and priorities. ii. Document Everything Create a “lay of the land” document summarizing findings on different team goals, challenges, and processes.   iii. Understand the Product Take product demos, listen to sales calls, and use tools that show how the product is sold. This helps in understanding the customer needs better. iv. Dive into Your CRM Understand your CRM (whether Salesforce or HubSpot) to assess how the data is organized. This is to check whether it’s easy to use, and identify immediate improvements. The CRM should be the central source of truth, with other tools supporting it. The data should be unified with easier adoption for the teams. v. Build Trust Internally Establish trust within your teams by listening carefully, asking questions about how RevOps can help, and addressing quick fixes to show you’re there to help. Having this trust shows them that you’re here to support their success. Quick wins, such as small fixes that make people’s jobs easier, helps in establishing credibility early. 2. Establish Clear KPIs   i. Understanding Team KPIs It is important to ask you stakeholders about the KPIs that matter to understand their goals and what their expectations are. ii. Aligning KPIs Across Teams Different departments oftentimes work in silos. RevOps should strive to align these departments and check if these KPIs match the overall business objectives. Gaps must be closed if their KPIs don’t align. iii. Setting RevOps KPIs As you approach the end of the first 30 days, start establishing RevOps-specific KPIs that match company goals, which may involve metrics like revenue increase, conversion rates, or improvements in overall efficiency. 3. Tech Stack Audit Deep dive into the existing tools that your company is using. Identify all redundancies, and find opportunities to streamline the entire tech stack. i. Map Out Tools Compile a list of all tools used by teams, noting their purpose and how they work with the CRM. ii. Evaluate Use and Cost Determine if tools are actively used or if there are duplicates. Look for cost-saving opportunities by consolidating tools when possible. https://www.youtube.com/watch?v=sVDJ9KI1tGw&t=869s Next 30 days – Alignment and Control The next 30 days marks a shift from discovery to alignment. The goals should be to create cohesion between departments (e.g., Sales, Marketing) and laying down effective controls. The improvements need to be implemented without overwhelming the teams. This phase combines further exploration with actionable improvements with the primary task being bringing the teams into sync.   1. Ways to bring your teams together i. Encouraging cross-team collaboration by addressing silos and ensuring all teams work toward shared quarterly or company-wide goals. ii. By creating alignment, you help teams see RevOps as a support system rather than an enforcer. This keeps communication channels open and creates buy-in. iii. Based on your findings, introduce controls wherever needed to improve workflow. Example: If close dates aren’t being recorded properly, this could skew reports. Meet with sales, identify the root cause (e.g., manual data entry that is taking too much of a reps’ time), and provide solutions or tools to make their tasks easier. Ensure that controls are practical and developed with the trust built in the first 30 days. Foster internal consensus within teams so that these improvements are adopted seamlessly. 2. Navigate Organizational Politics (i) Barrier Removal Larger organizations may have internal politics or ingrained processes that resist change. Find an internal “sponsor” who trusts and supports RevOps initiatives and can authorize actions to navigate any resistance. (ii) Trust and Consistency As you implement changes, make sure your efforts consistently demonstrate how RevOps can make work easier and more efficient for everyone. 3. Evolving the Tech Stack (i) Assessing Tech Needs If tools aren’t fully integrated (e.g., a tool not writing data back to the CRM), identify their gaps and consider evolving the tech stack. (ii) Holistic View Use insights from the discovery and alignment phases to start envisioning necessary tech improvements that align with company goals. Beginning of the 90-Day Phase: Vision and Execution This phase, described as “Vision and Execution,” involves shaping and executing a strategy based on insights gathered from the discovery and alignment phases. a. Roadmap Creation Create a roadmap covering the next two quarters, focusing on long-term, high-impact changes that align with business goals. Use learnings based on stakeholder needs, organizational goals, and the findings from the first 60 days i. Set Priorities Collaborate with end users (Sales, Marketing, Customer Success) to understand their pressing needs and align the roadmap with these needs. ii. Strategic Execution Prioritize initiatives that will have immediate revenue impact or

Top 10 Relationship Intelligence Tools for 2025

Top 10 Relationship Intelligence Tools for 2025 RevOps 10 min When it comes to sales, building strong relationships is essential.  But let’s face it, the process can be incredibly time-consuming and demands a significant amount of effort from the sales reps. But here’s the kicker: Today, 44% of millennial buyers prefer minimal contact with a sales rep during the buying process. That means your sales rep has ~5% of the prospect’s time to establish a connection. It’s tougher than ever to develop relationships from a seller’s point of view. Does this mean that your reps should stop building relationships? Should your reps just try and sell whatever they can to whoever you find? The answer to that is a resounding NO. In the digital era, data and insights are what drive sales . They have the potential to give out more information than you know about your prospects. CRMs capture all possible data, churning it and spurting out information that otherwise was not visible earlier. But wait. There’s more to sales success than your CRM. To truly understand your prospects, you need to dig deeper to uncover hidden insights to help close your deals faster. That means mining your CRM data for a wealth of valuable information that will give you a competitive edge. This is exactly what relationship intelligence does. What is a Relationship Intelligence Tool? Picture this: You have access to a wealth of data from your clients, colleagues, and partners, but it’s scattered across various touchpoints like emails, phone calls, messages, meetings, and more.  How do you make sense of all that information? That’s where relationship intelligence comes in.  By pooling in, processing, and analyzing all that data, relationship intelligence technology provides invaluable insights, builds stronger relationships, and helps you make smarter decisions.   With relationship intelligence, you can discover a treasure of data-driven and actionable insights that support the organization’s understanding of the customer, identify the optimal solutions, and determine the best communication strategies. This results in a more tailored and informed approach to prospects to maximize the best chance of a positive outcome. Your prospects are more than just a phone number or an email. Relationship intelligence broadens your potential and plays a strong role in connecting the dots from other sources. It supplements your CRM, finding other & useful opportunities to close prospects, otherwise not visible to us. Why Does a Relationship Intelligence Tool Matter? Enterprise-based selling in B2B is no walk in the park.  With a plethora of relationship intelligence tools out in the market, organizations are spoilt for choice. However, tools that leverage AI/ML, offering data-driven intelligence with invaluable and actionable insights, will be the ones that will dominate the market. On the flip side, the process of onboarding a tool no longer rests in the hands of a single decision-maker. Gartner states that the number of buyers involved in the last decade has increased from 5 to 20. A potential account will have multiple stakeholders who will be involved in the decision-making process. Hence, it becomes critical for sales reps to identify and engage with key stakeholders regularly. With the rise of digital selling, organizations can now track the process of selling in a more in-depth manner. All forms of digital outreaches and communication with prospects can now be tracked, analyzed, and acted upon with the help of relationship intelligence.  Today, with markets being down and companies being extremely meticulous in their choice of tools to invest, having a relationship intelligence tech stack will be the game-changer. Here’s how 1. Showcasing a single view of all your relationships with your prospects Having relationship intelligence data will bring together all the stakeholders in one view, so sales reps have a clear idea of the sales cycle the account is currently in.  2. Identify every stakeholder involved With the buying process evolving constantly, the final decision often lies not with one but multiple owners. In other words, for a sales rep, multithreading is the best way forward. And in this process, it’s very easy to confuse the right person to engage with, especially if there is a handover involved.  Sales reps often fail to map out the stakeholders involved. The dots are not connected and not visible, which can lead to confusion and no clarity to other higher authorities. Relationship intelligence tools fill these gaps. It will identify each & every stakeholder involved at every stage of the selling process, bring them together, and map out the relationship of each, and provide all the information about these stakeholders. Not only that, but the data also provide insights to those who are frequently engaging and also point out the next best champion to continue the sales process seamlessly if the key decision maker is unavailable at any stage of the sales process. 3. Give detailed insights about each prospect The thing about relationship intelligence tools is that not only do they provide details in one place, but they also show you the best possible way to contact and reach out to your prospects. It can be email, phone calls, or video calls; it will give you solutions that are sure to boost your process of converting. 4. Recover lost leads In the world of sales, not all leads or prospects will convert.  If the target is to convert 2 leads in a month with a value of X, sales reps need to build a pipeline of at least 10 leads with a value of 10X. This results in 8 leads that will not convert or be disqualified or lost in the process. However, these 8 leads don’t have to be lost forever. With relationship intelligence, you can identify the most engaged buyers and reignite the relationship with them. And here’s the kicker: the relationship intelligence technology considers all the data even before onboarding the tool.  This kind of intelligence will only unleash hidden superpowers for your sales reps. Who knows, your lost prospect’s business priorities might have changed over time, and getting back to them might just make all the difference. 4. Discover trends in

5 Steps to Navigate Buying Groups in 2025: A RevOps Guide

5 Steps to Navigate Buying Groups in 2025: A RevOps Guide RevOps 10 min In today’s business environment, B2B buying is never just one person. According to Forrester Research, more than half of global business buyers purchase in complex buying scenarios that include more people, more departments, and generally higher price points. And this buying group can be made up of 7 to 20 people! Unlocking the power of buying groups is a crucial aspect of the B2B landscape. This blog is a synopsis of our conversation with revenue operations leader, Nandini Karkare. She is currently the SVP of RevOps at Zywave. Nandini suggests strategic steps to navigate through the realms of Revenue Operations and helps uncover the strategies, insights, and best practices that constitute a comprehensive guide to mastering the dynamics of buying groups. Read on to get actionable tips on how you can navigate buying groups in 2025 (and beyond). And implement the learnings to create a winning GTM motion. Here are the 5 steps Nandini recommends: 1. Decode Your Buying Groups The buying groups typically consist of members from departments and they all contribute different aspects. It is critical to understand the scope of decision-making including the people who play the most significant roles in making the call. Gartner’s report on B2B Buying highlights that 77% of B2B purchases involve a buying group of four or more people. PS: The key stakeholder can turn out someone altogether different from who you had building a relationship with all along. a. Capturing Buying Group Members   Effective buying group management means considering not just decision-makers but influential stakeholders across departments. Misidentifying key players or focusing solely on the main contact risks derailing the sale. (i) How can you map the entire buying group efficiently? Leverage internal and external data to identify the key players Segment the Group by Role and Influence (ii) Not everyone in the buying group holds equal power or influence. Segment them into categories: Decision-makers (who give the final heads-up) Influencers (who sway the decision) Users (who use the product and provide feedback) Budget owners b. The Role Transition Within a Buying Group   Moving the focus from a buying group to a renewal or expansion committee includes knowing precisely who remains in the relationship, as well as who becomes more active as an account grows. (i) New roles may emerge in a Buying Group Technical or operational leaders may become more influential post sale, since they are now using the product. (ii) The focus shifts from buying to renewal The interaction should be more about the return on investment (ROI) of the product placed on the market, ongoing value delivery, and ongoing needs. (iii) Alignment between the buying groups and renewal committee Leveraging the same enthusiasm and relationships generated at the first-buying stage helps in anchoring the transitions and preventing any drop-offs in engagement. Related Resource: Navigate Enterprise Buying Committees: Strategies for Driving Alignment c. Understand the Personal and Collective Priorities of a Buying Group As per McKinsey & Company, B2B buying decisions increasingly require engagement across departments, with 60% of purchasing committees including members from outside traditional procurement, like IT and HR. (i)Alignment Between C-Suite and Technical Teams Decisions aren’t Made in a Vacuum Collaboration between C-suite and technical teams ensures a holistic approach to solving customer problems, creating stronger, more sustainable relationships Their cross departmental collaboration can help with: (ii) Alignment on Strategic Goals C suite executives need technical assistance to translate their strategic vision to reality that also aligns with company-wide objectives. (iii) Technical Validation These insights guide the C-suite in making informed decisions that fit technical infrastructure and future-proofing. (iv) Cross-functional Communication Bridging the gap between these two groups involves continuous, open communication, ensuring that technical evaluations don’t delay business goals but instead support them cohesively.   iii. Understand the Product Take product demos, listen to sales calls, and use tools that show how the product is sold. This helps in understanding the customer needs better. iv. Dive into Your CRM Understand your CRM (whether Salesforce or HubSpot) to assess how the data is organized. This is to check whether it’s easy to use, and identify immediate improvements. The CRM should be the central source of truth, with other tools supporting it. The data should be unified with easier adoption for the teams. v. Build Trust Internally Establish trust within your teams by listening carefully, asking questions about how RevOps can help, and addressing quick fixes to show you’re there to help. Having this trust shows them that you’re here to support their success. Quick wins, such as small fixes that make people’s jobs easier, helps in establishing credibility early. 2. Establish Clear KPIs   i. Understanding Team KPIs It is important to ask you stakeholders about the KPIs that matter to understand their goals and what their expectations are. ii. Aligning KPIs Across Teams Different departments oftentimes work in silos. RevOps should strive to align these departments and check if these KPIs match the overall business objectives. Gaps must be closed if their KPIs don’t align. iii. Setting RevOps KPIs As you approach the end of the first 30 days, start establishing RevOps-specific KPIs that match company goals, which may involve metrics like revenue increase, conversion rates, or improvements in overall efficiency. 3. Tech Stack Audit Deep dive into the existing tools that your company is using. Identify all redundancies, and find opportunities to streamline the entire tech stack. i. Map Out Tools Compile a list of all tools used by teams, noting their purpose and how they work with the CRM. ii. Evaluate Use and Cost Determine if tools are actively used or if there are duplicates. Look for cost-saving opportunities by consolidating tools when possible. https://www.youtube.com/watch?v=sVDJ9KI1tGw&t=869s Next 30 days – Alignment and Control The next 30 days marks a shift from discovery to alignment. The goals should be to create cohesion between departments (e.g., Sales, Marketing) and laying down effective controls. The improvements need to be implemented without overwhelming the teams. This phase combines

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top

Just one more step