Acquire (Lifecycle Activity) Explained (ITIL® 5)
Preparing for the ITIL® 5 Foundation exam? Acquire is the third activity in the ITIL® Product and Service Lifecycle, and it covers more than just "buying software." This guide explains what it actually involves.
Quick Answer
Acquire is the lifecycle activity focused on obtaining whatever is needed to bring a design to life — people, technology, and suppliers — whether that means building something in-house, buying it, or hiring outside expertise. It sits between Design, which specifies what's needed, and Build, which assembles it.
What Is the Acquire Activity?
Acquire is about sourcing the components a solution actually requires once Design has specified what's needed. That can mean hiring or assigning people with the right skills, purchasing or licensing technology, or engaging external suppliers and partners — often some combination of all three.
Acquire isn't limited to procurement in the narrow sense of "buying things." Deciding to build a component in-house rather than buy an off-the-shelf alternative is still an Acquire decision — it's about obtaining the right resource through whatever route makes sense, not simply making a purchase.
How Acquire Connects to Design and Build
Design specifies what's needed. Acquire obtains it. Build assembles and tests it into a working solution. If Acquire brings in the wrong resource — the wrong skill set, a supplier that can't actually deliver, a tool that doesn't fit the architecture — that gap usually doesn't show up until Build, when it's more expensive to fix.
Real-World Example
Once Design specifies that a new notification feature needs a third-party SMS gateway and a developer familiar with that gateway's API, Acquire is the activity where the team evaluates SMS providers, negotiates a contract with one, and either assigns an existing developer or brings in a contractor with the right experience.
Only once those pieces are actually in place does the team move into Build to start assembling the feature.
Why This Matters
Understanding Acquire matters because:
- It clarifies that "acquiring" covers people and expertise, not just technology purchases
- It connects design decisions to real-world sourcing constraints like supplier lead times, budget, and skill availability
- Getting Acquire wrong — the wrong supplier, the wrong skill set — tends to surface as expensive problems later in Build
Common Exam Mistakes
The most common mistake is assuming Acquire only refers to purchasing software or hardware. In practice, Acquire also covers hiring, assigning staff, and engaging suppliers for expertise or services — any route to obtaining a needed resource.
A second mistake is treating Acquire and Build as the same activity. Acquire obtains the components; Build is where those components are actually coded, configured, assembled, and tested into a working solution.
Memory Trick
Think:
Design says what's needed.
Acquire gets it — buy it, hire it, or build it in-house.
Build puts it together.
If you're sourcing people, tools, or suppliers, you're in Acquire.
Key Takeaways
- Acquire is the lifecycle activity focused on obtaining the people, technology, and suppliers needed to bring a design to life.
- It covers buying, hiring, and building in-house — not just procurement in the narrow sense.
- Acquire sits between Design (specifying what's needed) and Build (assembling it).
- Sourcing the wrong resource during Acquire tends to surface as costly problems later during Build.
- This activity is part of the eight-activity ITIL® Product and Service Lifecycle, a frequently tested area of the ITIL® 5 Foundation syllabus.
One Practice Question
Which statement best describes the Acquire lifecycle activity?
- It is limited strictly to purchasing software licenses.
- It is the activity focused on obtaining the people, technology, and suppliers needed to bring a design to life, whether by buying, hiring, or building in-house.
- It is the same activity as Build.
- It only happens after a solution has already been coded and tested.
Show Answer
Correct Answer: B
Acquire covers obtaining any resource needed to realize a design — people, technology, or suppliers — through buying, hiring, or building in-house, and it happens before Build assembles those components into a working solution.
Frequently Asked Questions
Does Acquire only mean buying software or hardware?
No. Acquire also covers hiring staff, assigning existing team members, and engaging suppliers for expertise or services — any route to obtaining a needed resource.
How is Acquire different from Build?
Acquire obtains the people, technology, and suppliers a design calls for. Build is where those components are actually coded, configured, assembled, and tested into a working solution.
What happens if the wrong resource is acquired?
Problems from an unsuitable acquisition — the wrong skill set, an unreliable supplier, a poorly-fitting tool — often don't fully surface until Build, when they're more expensive and disruptive to fix.
Is this topic tested on the ITIL® 5 Foundation exam?
Yes. The eight lifecycle activities, including Acquire, are part of the Product and Service Lifecycle, a significant and frequently tested area of the ITIL® 5 Foundation syllabus.
Ready to Test Yourself?
Now that you understand what Acquire covers, the next step is seeing how it connects to Build and the rest of the lifecycle. Take our free diagnostic quiz at PassTheFoundation.com to test yourself, or continue exploring the other ITIL® 5 lifecycle activity guides.