← Technology Operating Partner · the methodology underneath
What technology costs, what it risks, and where it is going. Reported in one relationship.
This is the methodology under the Technology Operating Partner relationship. It puts technology on the same footing as finance and risk: a cost baseline leadership can read, risk in annual dollars (annualized loss expectancy, or ALE), and a direction the board can follow. We target a risk baseline in dollars within 30 days, work through the renewal calendar and vendor spend, and report in the format your CFO and board already use. The technical depth sits underneath.
Why this matters
Why a change keeps getting postponed
A proposed change often gets the same answer: "We still have 18 months left on that agreement." The answer sounds reasonable each time. Added up, it can tie a company to a product long after it stops fitting.
| Example: agreements around one platform | Time left | What it is tied to |
|---|---|---|
| Core platform license | 18 months | Everything below |
| Add-on module | 7 months | The platform and one department |
| Integration or connector | 26 months | The platform and two other systems |
| Vendor support plan | 11 months | The platform |
| Hosting or infrastructure | 14 months | The platform and its data |
| The question | Why it is hard | Who has to be in the room |
|---|---|---|
| What depends on what? | One platform change reaches integrations, add-ons, and data connections, each with its own agreement and end date. | IT, finance, the system owners |
| What does leaving early, or not renewing, cost? | Notice windows, termination terms, and price changes at renewal differ by agreement. They have to be read, not assumed. | Procurement, finance, legal |
| Is the product still getting the support it needs? | Where a provider's support in some areas weakens, the cost of staying rises while the service falls. It does not show up as one line on one invoice. | IT, the system owners, finance |
| Which date lets several agreements line up? | Choosing a window, and sometimes aligning end dates at renewal, is a sequencing decision, not a purchasing one. | Finance, procurement, IT |
| Who is attached to the current product? | Teams know it and have built work around it. A change they did not ask for meets resistance. | Department heads, executives |
| How does it change day-to-day operations? | Processes, handoffs, and reports built around the old product have to change. The learning curve runs on several fronts at once: the technical team, the system owners, and the people who use it. | Operations, IT, department heads |
| What does the end user have to adapt to? | New habits and retraining take time away from the work. Adapting can be an intensive project of its own, with its own plan, sponsor, and timeline. | Department heads, line managers, HR |
| What does the CFO see? | Few companies hold every agreement, what it is tied to, and what leaving costs in one place. | CFO, procurement, board |
Six pillars
Six pillars, run as one operating cadence
The six pillars run as one engagement on a quarterly cycle. Each one produces a report you can trace to evidence.
Pillar 01
Technology Direction
A 12 to 24 month direction tied to business objectives and to how capital is allocated. Reviewed with leadership each quarter.
Pillar 02
Technology Risk in Dollars
Annualized loss expectancy (ALE) baseline targeted within 30 days, then the quarterly change in dollars. The number is built so a board, auditor, or buyer can review how it was derived.
Pillar 03
Spend and Contracts
Vendor consolidation, license rightsizing, and a renewal calendar for every agreement. Savings are sized against your own contracts and utilization.
Pillar 04
Board and Sponsor Reporting
One page on technology for the board and sponsor, in the same format every quarter: risk in dollars, change in spend, progress. Included at the Advance and Command levels.
Pillar 05
Adoption
Change management on every transition. A change creates value only when people use it.
Pillar 06
Execution Without a Restart
Direct handling within scope. Beyond it, we source, scope, and manage specialists so context is not lost. Aims to shorten the Proposal Treadmill™.
Pillar 06, Deep Dive
The Proposal Treadmill™
When an IT problem exceeds what the team can do, the usual route is the same cycle each time. The months lost to each cycle are the visible cost. The five costs below are harder to see.
Step 07 is the one that often goes unnamed. The vendor who shows up is sometimes not the one who scoped the work. Even when it is, it starts without a record of your environment, your past decisions, your organizational culture, or what has already failed. Each engagement starts with little context. The client team becomes the institutional memory in a room of newcomers. Then the cycle begins again.
Why It Matters
Five compounding costs the treadmill creates
Each cycle can take months, which is the visible cost. These five costs build up across engagements.
01
Amnesia tax
A new vendor arrives without your context. Your team spends time briefing each one on your environment, your history, your decisions, and your constraints. That time is billed or lost, and the knowledge leaves when the engagement ends. The next engagement starts the same way.
02
Revolving door
The people who scope a project are sometimes not the people who deliver it, and continuity is not guaranteed. The person who understands your environment can be replaced by someone who does not. Your team carries the relationship across each handoff.
03
Change management blindness
Vendors deploy technically and can leave adoption to chance. They may not know your organizational culture, your resistance patterns, your past failures, or which stakeholders need careful handling. The system goes live, users work around it, and the expected return does not appear.
04
Pattern blindness
Episodic vendors solve the symptom in front of them and may not see the pattern across problems. Experience across 100+ organizations over the founders' careers (how we count) helps Preside recognize that pattern. The same underlying pattern can come back as a different problem and start another cycle.
05
Capacity drain
Each treadmill cycle uses IT leadership time that was already allocated. Scoping, evaluating, negotiating, and onboarding all fall on internal people who have no spare time. Each cycle can leave the team more depleted and less able to do the strategic work that would avoid the next cycle.
How a relationship starts
The Program is the ongoing form. An Initiative is the starting point we recommend.
A long commitment on day one is a poor fit for both sides. We recommend starting with a fixed-price Initiative that tests the method on a defined scope in two to six weeks. If the work confirms the fit, the Program continues the cadence at one of the four Program levels, matched to how much the company wants to advance and how complex its challenges are. If it does not, either side can stop with the Initiative's report and no further obligation.
The three modes, in practice
How each operating mode runs.
The Technology Operating Partner relationship runs through three modes. Below is each mode and the costs it reduces.
Prevent
Preside watches for the conditions that start a new vendor cycle: contracts heading toward lock-in, renewals landing at the wrong time, dependencies nobody planned for, and platforms people will not adopt. Most can be handled before they turn into a project.
Problems caught earlier.
Resolve Directly
When a problem falls inside Preside's scope, Preside works on it directly, with no new proposal cycle or vendor search. Preside already knows the environment, the history, the organizational culture, and the stakeholders, so work starts without a ramp-up period.
Context carries over.
Manage specialists
When the work needs a specialist, Preside writes the scope, chooses the specialist, briefs them on your environment, and oversees the work so nothing resets. You approve the direction. Preside is not paid by the providers it recommends.
One point of coordination.
What the Program supplies
The expertise behind the six pillars
Well-run technology needs senior expertise that is hard to hire and often hard to justify as full-time headcount. The Program supplies each area below, and the judgment to connect them.
Technology strategy
Direction the business can fund and follow
Technology plans often arrive at the executive table as a budget request. The Program works the other way: a multi-year direction tied to business objectives, a budget framework finance can test, and a narrative the board can read.
Risk in dollars
A number for the risk conversation
A list of vulnerabilities does not tell a board what to fund first. The Program puts an annual dollar figure on each material exposure where the data supports one, so risk is weighed against spend in the units the business already uses.
Judgment across domains
Seeing what a change touches
A decision in one area, such as a platform, a contract, or a security control, reaches finance, operations, compliance, and the people who use the system. The Program carries that context across them, so a decision is judged on its whole effect and not only on technical merit.
Architecture decisions
Choices tested before they are hard to reverse
Platform and architecture choices shape cost and flexibility for years. The Program tests them against alternatives, contract timing, and the cost of changing course before the company commits.
Vendors and contracts
Renewals planned ahead
Each agreement renews on its own date. The Program maps every agreement, its end date, what depends on it, and what leaving would cost, so renewal decisions follow a plan.
Adoption
Change that people use
The Program plans for what users are used to, what they will resist, and what it takes to change habits, alongside the technical work.
Compliance and governance
Obligations built into how the work is done
Compliance requirements are mapped to the control and its owner as the work happens, not assembled at audit time. Project governance follows the same discipline.
Portfolio view
One format across several companies
Where a sponsor owns several companies, the same scoring and reporting format is applied to each, so results can be compared and acted on at the fund level.
How we work together
Four levels. One method.
The Program is the ongoing form of the relationship. The level sets how often we meet and how much Preside carries. It follows how much the company wants to improve beyond keeping things running, and how complex its challenges are. The more change a company wants to drive, and the more it faces, the more involvement we recommend. Regulation alone does not set the level. We recommend starting with a fixed-scope Initiative. Terms for your situation are set out in your brief.
| Foundation | Accelerate | Advance | Command | |
|---|---|---|---|---|
| Ambition | Keep things steady, with a clear baseline | Improve selected areas | Drive change across several areas | Lead change across the organization |
| Challenges faced | A focused environment with few moving parts | Growth or a technology transition under way | Several challenges at once, across systems and teams | Many entities, sites, or demands competing at the same time |
| Engagement cadence | Quarterly | Monthly | Bi-weekly | Weekly and on demand |
What each level includes
| Foundation | Accelerate | Advance | Command | |
|---|---|---|---|---|
| Reporting to the CFO on technology cost, risk, and direction | ✓ | ✓ | ✓ | ✓ |
| Translation between finance and the technical team | ✓ | ✓ | ✓ | ✓ |
| Technology risk in dollars (ALE baseline and tracking) | ✓ | ✓ | ✓ | ✓ |
| Technology cost baseline (technology P&L) | ✓ | ✓ | ✓ | ✓ |
| Cost and contract optimization | · | ✓ | ✓ | ✓ |
| Sourcing and managing specialists | · | ✓ | ✓ | ✓ |
| Board and sponsor reporting | · | · | ✓ | ✓ |
| Compliance work | · | · | ✓ | ✓ |
| Project governance | · | · | ✓ | ✓ |
| Adoption planning | · | · | ✓ | ✓ |
| Vendor and escalation support | Advisory | Works directly with vendors | Leads vendor management | Leads vendor and escalation management |
| Access between sessions | Scheduled sessions | Scheduled sessions | Scheduled sessions and ad hoc | On demand |
Every level includes the reporting to the CFO, the risk figure, and the cost baseline. The levels differ in how often we meet and how much Preside carries.
SCOPE
The leadership layer
The Program supplies the judgment across these decisions, translates between finance and the technical team, and manages the specialists who carry the work out. It does not replace the hands-on technical staff or run IT operations. Preside is not paid by the providers it recommends.
TIME
Starting in weeks
An Initiative starts in weeks. Building the same senior expertise in-house starts with recruiting and a ramp-up period for each role.
Where each option fits
These are different models for different needs. They are not mutually exclusive, and Preside works alongside any of them.
| Option | What it is for | How it relates to your IT lead, CIO, or MSP | Runs day-to-day IT operations |
|---|---|---|---|
| Full-time CIO or IT director | Runs the function and owns the team day to day. | Keeps authority and the team. Preside works alongside. | Yes, through the team |
| Fractional CIO | Fills the leadership seat part time. | The seat itself. Preside does not take it. | Depends on the engagement |
| Managed service provider | Operations and support. | Complementary. Preside coordinates cost, risk, and direction around it. | Yes |
| Project consultants | A defined project with a start and an end. | One project at a time. Context can reset between engagements. | Not usually |
| Preside | Turns what the technical team is dealing with into decisions finance and the board can make, and turns what finance needs into priorities the technical team can act on. Owns the reporting on technology cost, risk, and direction to the CFO and board. | Works with your CIO, IT director, or MSP. Where there is no technology leader, covers the leadership layer for cost, risk, and direction and manages specialists. New work starts from context already in hand, without a new proposal cycle. Does not hold the CIO role. Not paid by the providers it recommends. | No |
Built for the Boardroom
A board needs technology risk and spend in dollars.
Technology reporting often relies on status colors, a vendor inventory, and an assertion that things are running well. A board or buyer reviewing technology risk usually asks for it in dollars too.
At the Advance and Command levels, the Program produces two reports for the board: annual risk in dollars (ALE) and spend in dollars. Each shows the change since last quarter. Same format every quarter, in the units the rest of the business uses.
See how ALE works →EACH QUARTER
What the board receives
Quantify, reduce, and report each quarter.
Start with an Initiative, then continue as the Program at the level that fits.
Not sure where to start? Take the four-question Find Your Path tool for a personalized recommendation.