CI/CD Campaign
Everything you need to know about the CI/CD campaign.
Campaign Overview
Business Objectives
- Connect with the manager of App/Dev, show them the value of GitLab CI
- Drive conversion optimization throughout the funnel to increase asset downloads
- Free trials driven by the campaign page
Campaign Visual
Campaign Pages & Activities
See the FY22 Marketing Calendar for upcoming virtual events »
Always On Lead Generation:
- 📚 Content [eBook] The benefits of single application CI/CD
- 📚 Content [eBook] Modernize your CI/CD
- 📹 On-Demand Webinar [Demo + Q&A] Continuous Integration with GitLab
Research & Prep
Persona & Positioning
Target Persona 1: Manager of App & Dev
- Level: Manager
- Function: Dev, App
- Challenges we’re trying to solve with this campaign:
- Too many DevOps integrations/toolchain overload
- Lack of scalability (usually intensified the larger the org)
- Easy entry for teams to get started with CI/CD
- Additional info:
- DevOps Manager: Needs to effectively support the DevOps tools and infrastructure integral to their org’s application delivery. Concerned with providing development teams with the best possible tools, environments, and integrations for them to be successful. Challenged with prioritizing development work as an individual contributor (features/bug fixes) and supporting dev teams.
- Dev Leads (Development Manager): Needs to have a finger on the pulse of their development team’s capacity and priorities. Concerned with improving productivity and unblocking any issues that get in the way of progress. Challenged when development deadlines and assigned tasks change rapidly or too frequently. Also challenged when work on feature delivery is interrupted by show-stopping bugs or blockers.
- Ideal state:
- Dev and Ops are empowered to work better together, no more “throwing things over the proverbial wall”
- Improved visibility and communication, gain faster feedback and integrate smaller code changes frequently (with less risk of build-breaking changes)
- Increase release velocity and ship more reliable code, faster time to market and more reliable builds = value into the hands of customer sooner with higher degree of confidence
- Improve overall quality of the application due to increased test coverage and frequency of automated test execution, which enables preventing bugs from shipping
- How GitLab helps:
- Delivering better products/software faster - Validated, secure code gets to production faster and lovable features get into the hands of customers sooner. Happy customers, higher confidence, and more revenue!
- Increasing operational efficiencies - Automation reduces manual work and overall cost of tools. Less overhead. Improved performance.
- Reducing security and compliance risk: Regular releases on a monthly cadence (thanks to rapid innovation) minimizes security risk along with automated tests and scan
- Why is GitLab a better solution than competitors:
- GitLab as a single application provides end-to-end visibility into the SDLC and promotes better, more frequent, collaboration among teams. Errors are caught earlier in the process before they turn into bigger problems.
- GitLab enables faster release cycles in batches of small iterations without requiring a complete overhaul of existing development workflows and/or DevOps tools
- GitLab’s built-in CI means less context switching between tools and more time that developers spend writing code. Overall productivity increases
Target Persona 2: Practitioners
- Level: Practitioner
- Function: Developers, DevOps engineers, Development leads
- Challenges we’re trying to solve with this campaign:
- Too many DevOps integrations/toolchain overload = too much context switching
- Wasted development time
- Poor user experience/CI that “just works” the first time
- Lack of education and/or official support
- Additional info:
- Developers: Needs automation to replace otherwise tedious, manual, work. Concerned with delivering high quality code as fast as possible. Challenged when planned work is disrupted and productivity is negatively impacted.
- DevOps Engineer: Needs to effectively support the DevOps tools and infrastructure integral to their org’s application delivery. Concerned with providing development teams with the best possible tools, environments, and integrations for them to be successful. Challenged with prioritizing development work as an individual contributor (features/bug fixes) and supporting dev teams.
- Ideal state:
- Dev and Ops are empowered to work better together, no more “throwing things over the proverbial wall”
- Improved visibility and communication, gain faster feedback and integrate smaller code changes frequently (with less risk of build-breaking changes)
- Increase release velocity and ship more reliable code, faster time to market and more reliable builds = value into the hands of customer sooner with higher degree of confidence
- Improve overall quality of the application due to increased test coverage and frequency of automated test execution, which enables preventing bugs from shipping
- How GitLab helps:
- Delivering better products/software faster - Validated, secure code gets to production faster and lovable features get into the hands of customers sooner. Happy customers, higher confidence, and more revenue!
- Increasing operational efficiencies - Automation reduces manual work and overall cost of tools. Less overhead. Improved performance.
- Reducing security and compliance risk: Regular releases on a monthly cadence (thanks to rapid innovation) minimizes security risk along with automated tests and scan
- Why is GitLab a better solution than competitors:
- GitLab’s built-in CI means less context switching between tools and more time that developers spend writing code. Overall productivity increases
- GitLab as a single application provides end-to-end visibility into the SDLC and promotes better, more frequent, collaboration among teams. Errors are caught earlier in the process before they turn into bigger problems.
- GitLab enables faster release cycles in batches of small iterations without requiring a complete overhaul of existing development workflows and/or DevOps tools
Keyword Research
See the CI/CD keyword research doc »
Polished Messaging
Overall
| Polished Messaging | |
|---|---|
| Overall Message | Work better together |
| Headline | Automate and collaborate with GitLab CI/CD |
| Statement | GitLab’s complete DevOps platform with built-in CI/CD helps DevOps teams build, test, and deploy from a single application. |
| Key Messages | 1. Eliminate siloes: A complicated toolchain isolates teams and tools, creating bottlenecks in the development lifecycle. GitLab brings dev, sec, and ops together in one interface. |
| 2. Greater visibility: With full visibility across the entire SDLC, teams can solve problems faster with fewer roadblocks. | |
| 3. Increased efficiency: Instead of managing a brittle plugin environment or maintaining multiple tools, teams can focus on more productive tasks. | |
| 4. Industry-leading CI/CD: Teams don’t have to sacrifice functionality for convenience. GitLab’s CI/CD offers everything teams need for cloud native application development and was voted #1 CI by the Forrester Wave. | |
| Topics | 1. Continuous integration |
| 2. Continuous delivery | |
| 3. Cloud native | |
| Top-level Keywords | continuous integration, ci, ci cd pipeline, ci process, ci tools, yaml, DevOps |
Enterprise Segment
| Polished Messaging | |
|---|---|
| Overall Message | Secure CI/CD from start to finish |
| Headline | Build it, test it, deploy it seamlessly under one roof |
| Statement | GitLab’s leading CI/CD delivered as a single application means you spend less time switching between tools and tabs and more time working on value that ends up in the hands of your customers . |
| Key Messages | 1. Secure CI that just works: Automate everything from start to finish with confidence that GitLab will keep your pipeline secure from end-to-end. |
| 2. A better developer experience: GitLab knows that happier developers creates higher throughput and better retention. Improve the developer experience with a single application and avoid context switching, deployment delays, and too much downtime. | |
| 3. No forced tradeoffs between speed, quality, and ease of use: Don’t sacrifice quality for speed. GitLab understands that mimimal viabile changes create faster, superior deliverables in a single, convenient platform. | |
| Topics | 1. Continuous integration |
| 2. Continuous delivery | |
| 3. DevSecOps | |
| 4. CI/CD | |
| 5. DevOps | |
| Top-level Keywords | CI, continuous integration, CI pipelines, CI/CD pipelines, CD, continuous delivery, DevSecOps, DevOps |
Buyer Journeys, Content & Emails
Prescriptive Buyer Journeys
Individual Contributor
Manager
Marketo Nurture Emails
See Marketo Nurture Email Copies »
Outreach Emails
MASTER|Inbound sequence for each region
MASTER|Outbound sequence for each region
Behind the Scenes
Campaign Execution Documentation & Resources
Last modified July 29, 2024: Fixing broken `{:` formatting, link anchors, and colorization from the handbook migration (
68731e6c)
