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.

ai transformation

 

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.

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.


“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

Top 15 Guided Selling Tools for 2025

Top 15 Guided Selling Tools for 2025 RevOps 10 min Imagine that you are planning to build a new house but are unsure where to start. You have a basic idea of what you want but are not an expert in home construction or design. In such a situation, you would need a skilled architect who understands your needs, preferences, and budget and then guides you through designing your dream home. The architect would help you make informed decisions about your new home’s design, materials, and features. Similarly, a guided selling tool uses customer data and sales expertise to help customers navigate the purchasing process and make informed decisions. It can provide personalized recommendations based on the customer’s needs and preferences, answer questions, and offer advice to help them choose the right product or service. What is Guided Selling? Guided selling is a strategy involving a structured approach to lead potential customers through the sales process. It is the process of analyzing current sales, historical sales, and customer data to help sales reps provide tailored product recommendations to customers and increase the likelihood of conversion.  Let’s say you are shopping for a new laptop. You visit a website that offers guided selling, and you’re prompted to answer a series of questions. The questions might include things like: What will you primarily use the laptop for? Do you need a large screen or a lightweight design? How important is battery life to you? What is your budget? Based on your responses, the website would then recommend a few different laptops that meet your needs. It might provide detailed information about each laptop, such as the processor, RAM, and storage capacity, as well as customer reviews and ratings. The website might offer additional guidance, such as recommending accessories or providing information on warranties and support. Throughout the process, the focus is on helping you make an informed decision based on your unique needs and preferences. Guided selling can be particularly effective for complex or high-value products or services where customers may require more personalized guidance and support to make informed purchasing decisions. By providing a more consultative sales approach, guided selling also helps to establish long-term customer relationships. How Does Guided Selling Work in B2B SaaS In B2B SaaS, guided selling typically involves a sales representative or a customer success manager who guides the customer. The process usually begins with the customer expressing their needs and goals and the guide using that information to suggest relevant products or services. The guide may use various tools, such as a software demo, to help the customer understand the features and benefits of each option. In addition, guided selling often involves providing educational resources to the customer to help them better understand the product or service and how it can help them achieve their goals. This may include case studies, white papers, or other content that provides valuable insights into the benefits and use cases of the product. Let’s have a look at the guided selling process in detail: The Process of Guided Selling Tools The guided selling process is a customer-centric approach to sales that involves guiding potential customers through the buying process by providing personalized recommendations, advice, and support. The following are the general steps involved in a typical guided selling process: 1. Gathering customer information The first step of the process involves collecting data on the customer’s needs, preferences, budget, and any other relevant information that can help the sales process. 2. Identifying customer pain points In this stage, the sales team uses the information gathered in the previous stage to identify the customer’s pain points or areas of concern.This is typically done through a series of questions or a needs assessment. 3. Providing product recommendations Based on the customer information and pain points identified, the sales team provides recommendations on the products or services that best meet the customer’s needs. 4. Presenting solutions At this stage, the sales team presents the recommended products or services to the customer and explains how they address the customer’s pain points. The sales representative provides information about the recommended products or services, including their features, benefits, and pricing. 5. Handling objections If the customer has any objections or concerns, the sales team addresses them and provides additional information or alternative solutions as needed.  6. Closing the sale Once the customer is satisfied with the recommended product or service, the sales team closes the sale by facilitating the purchase process. 7. Follow-up and customer support After the sale is complete, the sales team provides follow-up support to ensure the customer is satisfied with their purchase and offers any additional assistance or support as needed.   Examples of Guided Selling Tools in Businesses Here are some examples of techniques of guided selling tools:  1. Automate sales playbook To ensure consistent performance, sales playbooks should be automated. Guided selling relies on a solid foundation of methodologies, blueprints, and plays that facilitate the sales process. It’s important to choose a solution that simplifies the playbook for sellers, allowing them to follow the plan and consistently advance deals easily. 2. Identify specific needs In some situations, customers may need a clearer idea of what they are looking for when they visit your website. In such cases, a brief questionnaire can be used to determine and guide their specific requirements. For instance, if you run an online clothing store, you could ask customers questions about their preferred fit and fabric to steer them toward products that best match their preferences. This approach can increase the likelihood of a purchase by helping customers make informed decisions based on their needs. 3. Real-time response For a guided selling software to be effective, it needs to be adaptable and flexible, able to react to changing circumstances in real time. At a fundamental level, ensuring that sales representatives remain attentive to communication and other sales activities can reduce the time it takes to close deals and result in higher revenue velocity. In other cases,

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

Leave a Comment

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

Scroll to Top

Just one more step