Connecting Tech Selection to Business Strategy
How to build the right team and run a strategy-aligned selection process
THE TECH STRATEGY SERIES FOR CAPITAL CONSTRUCTION
When technological change delivers its intended business value, that’s because it started with a clear vision, the right team, and aligned execution across three connected stages:
1
Building the case for change: Establish the business need, expected value, and organizational alignment.
2
Selecting the right solution: Assemble a strategy-aligned team and evaluate options against business requirements.
3
Driving adoption: Lead the people, processes, and accountability required to realize the intended benefits.
1
Building the case for change: Establish the business need, expected value, and organizational alignment.
2
Selecting the right solution: Assemble a strategy-aligned team and evaluate options against business requirements.
3
Driving adoption: Lead the people, processes, and accountability required to realize the intended benefits.
InEight has compiled three expert guides that detail proven practices that lead to positive transformation journeys—including the key questions champions should keep in mind along the way.
This is guide TWO: Connecting Tech Selection to Business Strategy
Connecting Tech Selection to Business Strategy
A Value-Driven Selection Process Begins Well Before the First Demo
Capital construction organizations understand the value of qualifying a major project before committing scarce estimating and business development resources towards chasing it. A project without a realistic path forward doesn’t deserve the same investment as one the organization is prepared to win. Technology selection benefits from that same discipline.
choosing software is a business decision, not an IT project
By the time a transformation champion begins assembling the selection team, the organization should already have reached alignment on the business imperative for change, secured meaningful executive sponsorship, and confirmed that the initiative has a realistic path to funding. See the first guide in this series, Building an Aligned Case for Change.
That scaffolding is important because choosing software is a business decision, not an IT project —if executive leadership views the initiative as "an IT problem," it’s already off track.
Start with the End in Mind
An effective process starts with the end in mind. The organization needs to define the outcomes it wants to achieve and the business processes required to achieve them. Those decisions inform requirements. Requirements guide the team selection. And the team evaluates potential solutions against that shared vision.
An Aligned Transformation Journey
Done well, the outcome of a thoughtful selection process is more than a vendor or solution choice. Organizations should walk away set up for success with documented goals, defined future-state processes, cross-functional alignment, and a core group of people prepared to carry the initiative through implementation and adoption—driving the change that will enable the organization to achieve its transformation goals.
Connecting Tech Selection to Business Strategy
1. Confirm Buy-in Before Beginning to Shop
Too often, selection processes stall because motivated champions start researching vendors, scheduling demonstrations, and developing preferences without answering a more fundamental question: Is this initiative a genuine priority to the organization? That distinction matters. When executive commitment, budget authority, or business goals remain unresolved, selection teams risk investing significant time in an initiative that eventually gets sidelined in favor of a more urgent organizational priority. Before assembling the selection team or reaching out to vendors, confirm three key things:
- Alignment on the business case. The problem or opportunity and its connection to strategic goals should already be agreed upon to avoid re-litigating "Why are we doing this?" mid-process.
- Leadership supports moving forward. Identify the executive sponsor who understands the initiative and is prepared to remain involved so the team isn’t left "just seeing what's out there."
- A realistic path to funding. Identify the budget owner and confirm that the effort is a currently funded priority and not a “nice to have” sometime in the future.
CHECKLIST FOR MOVING AHEAD
- Has leadership endorsed the initiative?
- Who owns the budget?
- Is funding available within the expected decision window?
- Are the intended business outcomes documented and understood?
- What would cause the organization to pause or deprioritize the selection?
Connecting Tech Selection to Business Strategy
2. Define the Future-State Before Defining the System
An organization searching for “a new estimating system” has already narrowed the conversation to a solution category. Too often, teams narrow their focus in this way too early in their process by failing to build a strategically aligned case for change, or by neglecting to fully explore the organization’s needs. A stronger starting point is to define what their targeted business processes need to accomplish differently, and how that change supports the organization’s broader goals.From there, the team can work backwards.
skipping this important step results in solutions that inadvertently reinforce current operational inefficiencies, instead of resolving them
Suppose the team notes that the current estimating process too often delivers inconsistent or unreliable information that undermines cost control efforts once a project is awarded. The selection process should examine more than the estimating workflow itself, such as: Where does the information originate? How will it move into project controls? What does finance ultimately need? Which data should move into scheduling or field execution? Where are teams currently reconciling information between systems? This larger, operational view can reveal requirements that a single department might never identify on its own. And skipping this important step results in solutions that inadvertently reinforce current operational inefficiencies, instead of resolving them. For every process area in scope, the team should align to establish:
- The desired business outcome
- How the process works today
- What needs to change in the future
- Who provides information to the process
- Who consumes its outputs
- Where information crosses organizational or system boundaries
- Which requirements are essential to achieving the future state
Create Guardrails Against Scope Creep
Discipline related to scope is also critical. Looking across connected processes may reveal valuable opportunities to solve adjacent problems, but it might also cause the initiative to expand every time a vendor demonstrates another capability. While a considered choice to widen the scope may make sense, the selection team needs to think back to the business case for change. The agreed business outcomes provide the guardrails to prevent scope creep. New opportunities should be evaluated against the transformation goals, implementation capacity, and value case established for the initiative.
The agreed business outcomes provide the guardrails to prevent scope creep
Connecting Tech Selection to Business Strategy
3. Build the Smallest Team that Can Make the Right Decision
Among B2B buying teams, 74% exhibit “unhealthy conflict” during the decision process, according to a Gartner survey, but the same survey noted that the buying groups that reach consensus are 2.5x more likely to report a high-quality deal. Selection teams often grow larger in the name of representation, which can leave them unwieldy. InEight’s experience points toward a tighter model: assemble enough of the right people—people who deeply understand the processes and implications of the decision—while keeping the core decision-making group as small as possible.
“The ideal size for a selection team? Enough that it’s representative, but small enough that decisions can be made.”
- Justin Ludlow, VP Sales – Americas and Europe, InEight
B2B buying teams DECISION PROCESS
74% exhibit “unhealthy conflict” during the decision process
2.5x
Buying groups that reach consensus are 2.5x more likely to report a high-quality deal
B2B buying teams DECISION PROCESS
74% exhibit “unhealthy conflict” during the decision process
2.5x
Buying groups that reach consensus are 2.5x more likely to report a high-quality deal
Pick People with Process + Technical Expertise
The first priority is people with business-process expertise. For each major area in scope, the team needs someone who understands how work actually happens, including the handoffs, exceptions, and downstream consequences that may be overlooked in a basic process diagram. Strong team members also bring enough technical literacy to understand how systems, data, and integrations work, so the team can avoid chasing magic bullet solutions, as well as distinguish genuine requirements from attractive features that do little to advance the future-state process.
“If I don’t have to fight to get them, I don’t want them on the team.”
Unfortunately, the strongest candidates are often among the hardest to release from their day-to-day responsibilities. But the effort (and trade-off) is likely worth it. An InEight customer discussing the selection team involved in a multi-year transformation effort drew a clear line: “If I don’t have to fight to get them, I don’t want them on the team.” To build the strongest selection team, champions should work closely with their executive sponsor to free up the people with the right expertise. A highly-qualified person who can contribute only intermittently may be less valuable than someone with enough protected time to participate meaningfully and carry the work forward later.
SET CLEAR EXPECTATIONS FOR COMMITTING TIME
The core selection team may spend only weeks or months part-time gathering requirements, evaluating options, and reaching a decision. But for some members, it marks the beginning of a much longer commitment. A significant technology transformation extends well beyond selection, with implementation and adoption continuing for a year or more, depending on scope, so team members should understand that longer potential timeline from the outset. Selection team participants can provide important continuity later because they deeply understand the business goals, requirements, and reasoning behind the decision, so protecting their capacity is important. When forming the selection team, consider:
- How much time will members need during requirements gathering and selection?
- Who should remain involved as the initiative moves into implementation and adoption?
- Can their operational responsibilities be adjusted to protect that capacity?
- Does each participant understand the potential time commitment at each phase?
Treat selection team participation as a real internal project assignment with clear expectations and protected capacity to do the work well.
Choose a Ringleader Who Can Connect the Pieces
The selection team also needs a “ringleader” who can hold the strategic goals in view, translate them into requirements across process areas, and understand the intersections among all impacted functions. The leader keeps decisions connected so that one team doesn’t optimize its own processes, while creating new friction somewhere else. That person may be a Business Architect, Project Leader, or Transformation Lead—their title matters less than their ability. They also need enough authority, or access to authority, to keep decisions moving forward.
Add a Healthy Dose of Skepticism
Healthy challenge is useful in a team dynamic. A participant who questions assumptions can expose potential weaknesses others may have overlooked, leading to better decision-making. However, a person pre-convinced that the initiative will fail can bring unhealthy conflict. Champions should decide deliberately whether to include an outright skeptic on the team and how the team will handle contrarian temperaments.
CHECKLIST FOR PROGRESS
- Who genuinely understands each in-scope business process?
- Who understands the downstream effects of changing those processes?
- Does the core team have enough technical fluency to evaluate system implications?
- Who can keep the entire process connected to the strategic goal?
- Can each team member devote meaningful time to the work?
- Is the group small enough to reach decisions efficiently?
- Should the team include a transformation nay-sayer?
Connecting Tech Selection to Business Strategy
4. Keep Executive Sponsors and Internal Partners in the Process
Executive sponsorship carries more weight when people can see it. Sponsors don’t need to attend every working session, but they should be visibly engaged at meaningful points throughout selection process.
Executive sponsorship should be visible enough that the organization recognizes selection as a business priority.
Their presence reinforces the importance of the initiative, helps resolve decisions that cross organizational boundaries, and maintains continuity with the business goals established earlier. When they lend their name to sponsor the initiative and then disappear, it can send the wrong message. The core team also needs to loop in key internal partners at the right time—early enough to vet, not so late that they veto:
- IT and information security should understand the initiative early enough to identify any non-negotiable technical or security requirements that could eliminate a vendor, regardless of solution fit.
- Procurement should clarify the required purchasing process, including RFI or RFP requirements, competitive quotes, approved vendor policies, and contracting steps.
- Finance becomes especially important when the solution connects with an ERP or financial system, or changes how project information ultimately reaches financial reporting. They may also provide input on how the solution should be budgeted and how the investment will be measured.
Loop in key internal partners at the right time—early enough to vet, not so late that they veto.
Avoid Late-Stage Surprises
The goal is early, thoughtful partnership that avoids unhealthy conflict and keeps the selection process on track. Internal partners should understand where the selection is headed and have opportunities to identify constraints before those constraints create expensive, late-stage surprises that can result in the initiative being parked.
Connecting Tech Selection to Business Strategy
5. Anchor Vendor Discussions to the Case Goals
Once goals, future-state processes, requirements, and team roles are clear, the team can follow a disciplined selection process that both validates vendors and hones the team’s vision. The key principle is that vendors should be evaluated against the requirements that the organization established before being influenced by vendor presentations. Depending on the organization and scale of the investment, the process may include:
Each process area should identify and rank its most important criteria, which the team can use to consistently evaluate vendors as the field narrows. Before demonstrations, inform vendors about:
- The business outcomes the organization is pursuing
- The relevant current and future-state processes
- The specific scenarios they are expected to demonstrate
- The requirements the team will evaluate
This approach allows vendors to prove their value in a structured way, so the selection team doesn’t waste time on generic demos. It can also help the team sharpen its thinking.
Refine the How, Not the Why
Seeing software in action, the team may realize that a workflow that looked sensible on paper may become unnecessarily complicated—or that a capability they hadn’t considered may create genuine value across multiple processes. The team should use demos to refine future-state vision, while maintaining the agreed-upon business outcomes as its reference point. That distinction helps manage scope creep. New capabilities deserve consideration when they strengthen the transformation case, not just because they appeared impressive in a demo.
Connecting Tech Selection to Business Strategy
A Successful Selection Leaves the Organization Ready to Change
The final vendor decision is one important output of the selection process. A strong process leaves much more behind. Once a vendor solution is chosen, the organization should enter implementation with:
- Agreed strategic and business outcomes
- Documented future-state processes
- Prioritized requirements
- A clear record of why the solution was selected
- Cross-departmental partners who understand the initiative
- Visible executive sponsorship
- Process leaders who can carry critical knowledge forward
That continuity becomes valuable as implementation introduces real-world details and trade-offs. When a feature behaves differently than expected or a process needs refinement, the team can return to the goals that shaped the original decision, rather than reopening the entire selection. The work begun while building the case for change has now moved another step forward. The next challenge is turning the selected technology and future-state processes into everyday ways of working across the organization. That is the focus of guide three: Driving Tech Adoption that Delivers on Strategy.
Research Notes
Technology Alignment Differentiates Today’s Capital Construction Leaders
InEight conducted in-depth qualitative research with capital project leaders from around the world about their approach to technology acquisition and digital transformation. Through approximately 60 hours of one-on-one interviews and online discussion, the research found that leaders at companies that are setting the pace in their markets think about technology differently—and they think big, aligning teams, tech, and strategy around unified organizational goals. This aligned approach provides the foundation for their operational success, empowering them to leapfrog competitors.
MOVE FROM SELECTION TO SUCCESSFUL TRANSFORMATION
InEight helps capital project organizations connect business processes, data, and teams across the project lifecycle—providing a foundation for more consistent, predictable project delivery.
Explore how InEight can support your organization’s transformation journey.
ABOUT INEIGHT
InEight is a leader in construction project controls software, empowering over 850 companies taking on challenging projects in industries including construction and engineering; transportation infrastructure; mining; water; power and renewables; and oil, gas and chemical. Uniquely suited to capital construction and other complex work, our integrated, modular software manages projects worth over $1 trillion globally, taking control of project information management, costs, schedules, contracts, and construction operations, and delivering insights with advanced analytics and AI. InEight's solutions adapt and scale to meet the dynamic needs of modern construction, driving operational excellence and successful project outcomes. For more information, follow InEight on LinkedIn or visit InEight.com. © 2026 InEight, Inc. All Rights Reserved