The Internal Pitch
Your organisation does not know what you can do with AI. This week you fix that. Learn how to propose a clear, small AI pilot to your manager without causing alarm or getting blocked by generic corporate objections.
The full audio guide.
In this session, we map out how to build credibility for an internal AI experiment by speaking the language your manager already cares about, focusing entirely on time, costs, and quality controls.
The video breakdown.
Watch how to sequence your proposal and handle resistance from risk, compliance, or finance partners using real Australian and New Zealand workplace examples.
Getting approval starts with speaking their language, not yours.
Managers do not buy technical complexity. They buy solutions to immediate business frictions. Frame your initiative around concrete problems, specific timelines, and non-negotiable human review points.
How to propose an internal AI initiative that managers accept.
Many experienced professionals are using generative AI in private to sort data, review documents, and draft summaries. They are saving hours every week. But because these shortcuts stay hidden, the organisation does not realise the capability exists. To scale your impact and build visible career value, you need to bring these methods into the open through a structured proposal.
The mistake most people make is focusing on the tool. Pitching how advanced a specific large language model is will quickly trigger concern from IT and risk departments. Instead, pitch a narrow experiment that solves a friction your manager is already facing.
The five-part framing framework
To keep your pitch grounded and clear, organize your conversation around these five distinct pillars. This approach removes technical jargon and keeps the focus entirely on operational utility.
1. The friction
Name a specific, recurring task that is currently consuming too much team time, delaying a client response, or causing an analysis bottleneck.
2. The practical solution
Explain how you will use an AI tool to handle the initial drafting, sorting, or extraction, building directly on the skills you already have.
3. The business outcome
Describe the result in clear operational terms, such as cutting report turnaround times from three days to four hours or reducing initial review errors.
4. The narrow timeline
Keep the proposal limited to a four-to-eight week pilot. A short window lowers the perceived risk and makes it easy for a manager to say yes.
5. The specific ask
End with a single, clear decision point. Do not ask to change company policy, just ask for permission to test the method on three specific upcoming projects.
Handling the five main corporate objections
When you present an AI initiative, corporate decision-makers usually hesitate for predictable reasons. Address security and accuracy upfront, before they even ask. Use these direct responses to keep the pilot on track.
- Objection 1: Security and data privacy Managers worry about customer data leaking into public models. Response: We are using a dedicated enterprise workspace where data is completely cordoned off and never used for training.
- Objection 2: Accuracy and hallucinations Leadership fears the tool will invent information. Response: The tool is restricted to analyzing the reference files we upload, and I am personally checking every single data point against the source.
- Objection 3: Budget and licencing costs Finance does not want a massive software bill. Response: The pilot relies entirely on our existing licences, and we will measure the exact hours saved before proposing any further spend.
- Objection 4: Team disruption and capability Leaders worry the team cannot handle a complex shift. Response: I will run a single twenty-minute desk-side guide to show team members the exact template, keeping the execution simple.
- Objection 5: Policy and compliance alignment Risk teams worry about violating local guidelines. Response: This pilot mirrors current New Zealand responsible AI guidance, keeping a qualified human fully in control of every final deliverable.
Moving from private user to internal guide
Proposing a pilot is the fastest way to build your professional reputation as an AI-capable person. By structuring the test, documenting the time saved, and proving you can manage operational risks safely, you show leaders that you understand how to deploy technology responsibly in a modern business context.
Structure your next pitch conversation.
Use this preparation prompt to stress-test your proposal before you meet with your manager. It will help you refine your metrics and ensure your boundaries are clear.
Test your framing before the meeting.
Copy this text block directly into your preferred AI tool to evaluate your proposal against common corporate concerns.
Act as an experienced New Zealand corporate business analyst. Review my outline for an internal AI pilot project. Evaluate whether the friction is described in plain business terms, whether the timeline is sufficiently narrow, and whether the human checking steps are robust enough. Challenge me with the three toughest objections a risk officer or finance manager would raise in a local enterprise context, and help me write direct, plain-language answers for each.
Bring your AI capability into the open.
Pick one friction this week, outline your four-week test parameters, and have a direct conversation with your manager over coffee.