Technology Strategy: When to Build, Buy, Partner or Watch

A great blue heron wading in shallow water with a small fish in its beak, its reflection on the surface below.

A technology strategy is a company’s standing record of which technologies it will build, buy, partner on or only watch, and what would change each of those calls. Each call has a named owner and the evidence behind it, so the record can be checked and revised instead of rewritten every year.

Most companies are better at finding technologies than at deciding on them, and the space between the two is where a technology strategy either works or quietly stalls. The capability behind those calls is thin: in Qmarkets’ Impact Gap 2026 benchmark of 60 organizations, 72% lacked a mature open-innovation capability, from scouting to partnerships.

The calls described below, made in public by Apple, Siemens, Microsoft and Volkswagen, show what deciding looks like, with dates and numbers attached.

What Is Technology Strategy, and How Is It Different From IT Strategy?

IT strategy plans how the systems a company already runs are delivered and paid for. Technology strategy decides which new technologies the company will own, acquire, reach through partners or keep under watch, and when to revisit each one. The two meet when a technology the strategy chose becomes a system IT has to run.

QuestionIT strategyTechnology strategy
What does it decide?How existing systems are run and fundedWhich technologies to build, buy, partner on or watch
Where does it start?The systems and contracts already in placeThe options scouting has found, tested against business goals
Who should own it?The CIO and the IT leadership teamA named owner for each call, with the mandate to make it
What makes it change?The budget cycle and the systems roadmapA trigger written next to each call, or its review date

The distinction needs saying because guides to the subject often start from IT. Forrester’s guide to developing a technology strategy builds on its principles for high-performance IT and takes the IT organization through four steps, from stakeholder buy-in to a “technology strategy on a page”. That serves a CIO. It does not tell a head of R&D whether to build a capability in-house or license it from a company that already makes it.

Technology strategy sits between the enterprise strategy, which sets the goals every call has to serve, and the roadmaps that schedule work once a call is made. A build call lands in a product or R&D roadmap. A buy call ends as a contract and, in time, a system IT runs.

Why Do Technology Strategies Fail When Scouting Works?

Because finding an option is not the same as deciding on it. Teams scout technologies and pilot the promising ones, and then the option waits, because nobody holds the mandate to build it, buy it, partner on it or drop it. In AI, IDC found that only four of every 33 proofs of concept reached production.

Only 4 of every 33 AI proofs of concept reached production in IDC's 2025 research with Lenovo.
For every 33 AI proofs of concept, 29 did not reach production.

The research was carried out with Lenovo and reported by CIO in March 2025. Ashish Nadkarni, a group vice president at IDC, put part of the gap down to money: “These POCs are highly underfunded or not funded at all.” An option worth piloting is either worth a budget or worth dropping, and leaving it unfunded is a call nobody made.

Gartner saw the pattern coming. In July 2024 it predicted that at least 30% of generative AI projects would be abandoned after proof of concept by the end of 2025, citing poor data quality, inadequate risk controls, escalating costs or unclear business value. Each of those causes could have been written down in advance as a reason to change a call.

A quick test for any strategy in place: pick three technologies your technology scouting team assessed last year and ask who decided what happened to each, and where that is written down. If nobody can answer within a minute, the options were collected but never decided.

What Are the Four Calls in a Technology Strategy Framework?

There are four: build, buy, partner and watch. A technology strategy framework is complete only when every call carries two things: what it commits the company to, and the condition that would change it, written down before anyone needs it. Without the condition, a call cannot be revisited on evidence, only argued about again.

CallWhat it commits the company toWhat would change it
BuildIts own people and budget, because the technology decides how the company competesCosts or delays past a set limit, or a partner able to deliver the same capability sooner
BuyA purchase or license, because others already make the technology well and it is needed nowA price or supply risk, or the technology becoming a source of advantage worth owning
PartnerShared work under agreed terms, when the company needs the technology but not all of itThe terms themselves, such as milestones or a named event written into the contract
WatchAttention only: a named owner and a review date, with no budget beyond monitoringA signal set in advance, such as a cost threshold or a supplier ready to commit at volume

Watch is the call that keeps scouting honest. Without it, a technology that is interesting but not yet ready tends to meet one of two fates: a premature pilot or silence. A watch call gives it an owner and an act-when trigger, the structure the Emerging Technology Watchlist blueprint sets out, so the company knows when the technology stops being interesting and starts being relevant.

Annual trend lists are natural input for watch calls. Gartner’s top strategic technology trends for 2026, published in October 2025, name ten technologies, from multiagent systems to geopatriation. Each is a candidate for a call, and most companies will start most of them as watch.

How Do You Create a Technology Strategy That Stays Current?

Start from the options scouting has already found, not from a blank page. Give each technology one owner with the mandate to make a call, then record the call with its evidence and the trigger that would change it. A review date catches what the trigger misses. The strategy is the record those steps produce.

A cycle diagram: scouting feeds options to an owner with the mandate to decide; each call is recorded with its evidence and trigger, and a fired trigger or a review date sends it back to the owner. Without an owner, an option waits.
The record stays current because every call has a way back to its owner: a trigger that fires or a review date that arrives.

The owner carries the weight. A scouting team can find and assess options, but if it cannot commit budget, the call needs someone who can: the head of the business the technology would change, or whoever holds the platform budget for technologies that cut across the company.

Write each trigger as something a person could check. “If the unit cost falls by half” or “if a second supplier can ship at volume” can be checked; “if it matures” cannot. Set the review cadence by how fast the evidence moves: a light monthly review for watch calls, as the watchlist blueprint suggests, and the annual planning cycle for build and partner calls.

Calls then feed the plans that act on them. A build call becomes a line in the innovation roadmap, and a partner call becomes a relationship to manage. Judge each call later by what it delivered, which is the test Impact-Driven Innovation applies at every stage.

What Do Technology Strategy Examples Look Like?

The clearest technology strategy examples are single public calls with the reasons given for them. In 2025, Apple shipped a modem it built itself, Siemens closed a purchase worth about $10 billion, and Microsoft signed a partnership whose terms say what would change it. Each shows one call and what it committed the company to.

How Apple Followed Its First Modem With a Faster One in Seven Months

In February 2025, Apple shipped the iPhone 16e with C1, described as “the first modem designed by Apple”. Seven months later the iPhone Air carried C1X, which Apple says is up to twice as fast as C1 and, on the same cellular technologies, faster than the modem in the iPhone 16 Pro while using 30 percent less energy overall. A build call is a commitment to keep improving the technology, release after release.

Why Siemens Spent About $10 Billion on Altair

Siemens completed its acquisition of Altair Engineering on March 26, 2025, for an enterprise value of about $10 billion. The deal added capabilities in mechanical and electromagnetic simulation, high-performance computing, data science and AI, which Siemens said would create “the world’s most complete AI-powered portfolio of industrial software”. A buy call trades the years a build would take for a price paid up front.

How Microsoft Wrote the Triggers Into Its OpenAI Deal

Microsoft’s partner call on frontier AI comes with its conditions in writing. Under the agreement published on October 28, 2025, Microsoft holds about 27% of OpenAI Group PBC, valued at about $135 billion, and OpenAI committed to buy an incremental $250 billion of Azure services. Microsoft’s rights to OpenAI’s models and products run through 2032.

If OpenAI declares artificial general intelligence, an independent expert panel now has to verify the claim. Microsoft is also free to pursue it alone or with other partners. The verification clause and the 2032 date are conditions under which the partnership changes, agreed before anyone needs them: the trigger column of a technology strategy, written into a contract, which is where managing a strategic partnership starts.

What Did It Look Like When Volkswagen Moved From Build to Partner?

Volkswagen kept building vehicle software in-house through Cariad, a unit that lost about €2.4 billion in each of 2023 and 2024, and in November 2024 put its next electrical architecture into a joint venture with Rivian worth up to $5.8 billion. For the next generation, a build call became a partner call.

What this looked like in practice. Cariad pools the group’s software expertise to build standardized platforms for its vehicles. Volkswagen’s 2024 annual report puts the unit’s operating result at minus €2,392 million in 2023 and minus €2,431 million in 2024, against sales revenue of €1.3 billion.

The joint venture launched on November 12, 2024, with a 50% stake for Volkswagen, to develop the next electrical architecture and software for both companies’ electric vehicles. Volkswagen’s chief executive presented it as a step within the existing strategy:

“The partnership with Rivian is the next logical step in our software strategy.”

Oliver Blume, Volkswagen Group, November 2024

Volkswagen has since reported where the partner call stands:

  • November 2025: the venture, RV Tech, employed more than 1,500 people.
  • Early 2026: reference vehicles from the Volkswagen, Scout and Audi brands were due to begin winter testing.
  • 2027: the ID.EVERY1 is due as the first group vehicle on a version of the architecture.

What a reader can take from it is structural. Volkswagen split the technology by generation: it kept building for the platforms already on the road and partnered for the next one. A record that allows two calls on one technology, each with its own owner and trigger, makes that split visible while the next generation is still a choice.

Q-scout is built for the step this article is about, between finding an option and recording a call. Each technology or startup moves from discovery through a review committee and proof of concept to a decision, with expert scorecards along the way and a required close reason, so a pass is written down as clearly as a yes. See how Q-scout moves scouted technologies to a decision.

Technology Strategy: Common Questions Answered

What is a technology strategy?

A technology strategy is a company’s record of which technologies it will build, buy, partner on or only watch, and what would change each call. It differs from an IT strategy, which plans how existing systems are run and paid for. Each call needs a named owner and a date when it will be looked at again.

Can you provide an example of a technology strategy?

Microsoft’s partner call on frontier AI is a public one. Its October 2025 agreement with OpenAI sets the stake at about 27%, extends its rights to models and products through 2032, and names an event that changes the terms: an expert panel verifying any claim of artificial general intelligence. A full strategy holds such a call for every important technology.

What does a tech strategist do?

A tech strategist keeps the company’s technology calls current. They bring options from scouting to the person with the mandate to decide, and they keep the record of each build, buy, partner or watch call, its evidence and its trigger, reopening a call when the trigger fires. They advise on calls; the business owner makes them.

What are the top 10 strategic technology trends for 2026?

Gartner’s list, published in October 2025, names AI supercomputing platforms, multiagent systems, domain-specific language models, AI security platforms, AI-native development platforms, confidential computing, physical AI, preemptive cybersecurity, digital provenance and geopatriation. For a technology strategy, each is a candidate for a call, and most companies will start most of them as watch.

Who should own the decision on a scouted technology?

The person whose budget or roadmap the technology would change, with a date by which the call is due. A scouting team can find and assess options, but if it cannot commit money or people, it needs an owner who can. Without one, the option waits, and the next team to find it starts from the beginning.

How often should build, buy, partner and watch calls be reviewed?

On a fixed date, and whenever a trigger fires. Watch calls suit a light monthly review, because the evidence behind them moves fastest. Build and partner calls can follow the annual planning cycle, with their triggers as the exception that forces an earlier look. A call past its review date without a decision is open again.

You Might Also Like...

An orange hermit crab peering out of a borrowed spiral seashell on rocky ground.
Article Innovation Management Technology Scouting
Not invented here syndrome is usually a routing problem: outside ideas arrive with no owner and face different tests. How to get them...
by Ilona Gochman
11.03.26
7 min
Scaffolding around a building under construction against a bright sky
Article Foresight & Trends Technology Scouting
What corporate venture building is, how it differs from corporate venture capital, and the four structural reasons most programmes never...
by Elliott Wilkins
09.25.26
8 min
An engineer watching a bank of monitoring screens in a control room.
Article Foresight & Trends Technology Scouting
Horizon scanning software collects signals from outside your organization — research, patents, funding rounds, regulation, competitor...
by Elliott Wilkins
09.25.26
8 min