top of page

Frank Baker on New Firm, October Capital: Investing in Technology’s Deployment Gap

6 days ago
11 min read

Frank Baker is launching October Capital with three initial investments, betting that technology adoption creates opportunities beyond the companies building the technology. The story behind “Frank Baker on New Firm, October Capital” centers on services supporting AI infrastructure, physical security, and financial infrastructure. Its central tension is practical: growing demand for technology does not automatically produce profitable deployment businesses.

Bloomberg’s services investment coverage confirms that Siris formed the firm with Baker at its helm. The strategy puts implementation and operations at the center of the investment case. Blackstone’s investments in data centers and energy provide a useful reference, although the firms approach that opportunity through different businesses.

For enterprise buyers, the immediate significance concerns the suppliers behind their technology plans. For investors, it concerns whether those suppliers retain value as customers expand. October Capital’s launch makes that distinction explicit: demand for an underlying technology and returns from servicing it require separate evidence.

Frank Baker on New Firm, October Capital: What Actually Changed

October Capital gives a dedicated investment identity to services businesses that help enterprises put technology into operation. Siris announced the firm’s creation on October 21, 2026. Baker serves as CEO and managing partner.

The October Capital launch identifies Takkion as a completed acquisition. EQ Retirement Solutions and Lenvi are signed acquisitions. That distinction matters because signed agreements still depend on closing conditions.

The announcement describes initial priorities spanning AI infrastructure, physical security, and financial infrastructure. These categories cover different customers and operating requirements. Their shared investment logic is the need to implement, integrate, and operate technology.

That logic deserves attention without assuming every business belongs to the same economic category. Installing equipment, maintaining energy assets, administering pensions, and supporting lending involve different sources of revenue. A shared technology theme does not erase those differences.

Private equity, investment in businesses outside public stock markets, provides the ownership model behind this launch. The relevant question is what dedicated ownership changes operationally. A new name alone cannot answer it.

An investor can direct resources toward hiring, acquisitions, systems, or expansion. Each choice creates a different route to growth. Readers should assess those decisions through portfolio developments rather than treating the launch itself as evidence of improved performance.

The initial portfolio also gives the strategy more substance than a statement of future intentions. There are identifiable businesses to examine. Their customer relationships, service obligations, and operating results offer places to test the investment thesis.

However, a portfolio announcement cannot establish how much future growth will come from AI. A business can benefit from several sources of demand. Assigning all expansion to AI would obscure its existing market and customers.

Consider the distinction between an established supplier receiving additional orders and a newly created market producing an entirely new business. Those situations call for different expectations. October Capital’s initial investments should be evaluated individually before readers draw conclusions about the broader strategy.

The launch therefore changes the organization of the investment effort more clearly than it changes the underlying technology landscape. It establishes a focused platform. Evidence about execution must follow through actual ownership decisions and customer outcomes.

This is the useful starting point for Frank Baker on New Firm, October Capital. The event establishes a services investment strategy with an initial portfolio. It does not establish that every technology deployment bottleneck will become an attractive investment.

Technology Buyers Still Have to Turn Plans Into Working Systems

The strategy targets the distance between buying technology and operating it reliably. That distance creates work for suppliers, but also creates obligations that customers will expect those suppliers to meet.

For an enterprise buyer, a technology purchase rarely resolves the whole operating problem. Equipment needs installation and maintenance. Software needs access to accurate information. Staff need clear responsibilities when systems fail or produce uncertain results.

These are illustrative requirements, rather than reported outcomes at October Capital’s portfolio companies. They explain why services deserve separate analysis. The customer ultimately needs a functioning process, regardless of how promising its components appear.

That shifts attention toward procurement teams, the people selecting and contracting with suppliers. They must judge technical capability alongside operating capacity. A provider’s expansion plans matter less than its ability to deliver the specific work promised.

Ownership changes can make those judgments more pressing. Buyers need clarity about management continuity, service commitments, and future investment priorities. They also need to understand whether an acquisition changes responsibility for existing contracts.

None of those questions implies a problem at October Capital. They are practical tests for any supplier undergoing an ownership transition. They become especially relevant when the investment thesis emphasizes growth and broader service capabilities.

The pressure also reaches supplier management teams. A technology trend can help open customer conversations. Winning and retaining those customers requires staffing, scheduling, execution, and accountability.

For example, imagine a financial institution replacing a process that depends on manual reconciliation, the comparison of records to identify discrepancies. Automation changes the workflow. Someone still must decide how exceptions are reviewed and who remains responsible for errors.

A service provider can create value by managing those obligations effectively. Yet automation can also reduce the amount of manual work customers purchase. The investment case depends on which effect dominates within a particular contract.

A similar distinction applies to physical security, the protection of people, buildings, and equipment. A customer might purchase new monitoring technology while retaining older systems. Connecting those systems creates implementation work, but also creates expectations about reliability and response.

October Capital’s sector priorities make those operational questions relevant. They do not establish that the firm has already solved them. The evidence must come from the businesses it owns and the work those businesses deliver.

Developers should care because implementation choices shape the systems they can build and maintain. A product dependent on unavailable infrastructure cannot meet its intended schedule. A well-designed application still needs dependable operating conditions.

Knowledge workers face a related issue when processes cross teams and suppliers. Decisions, requirements, and service commitments need to remain accessible. A searchable knowledge base can support that coordination, although documentation cannot replace operational capability.

The broader implication is straightforward: technology buyers need to evaluate the organization delivering the service alongside the technology itself. October Capital’s launch puts that organization at the center of the investment story.

Takkion Shows How Indirect the AI Infrastructure Connection Can Be

Takkion illustrates an investment route through energy services rather than direct ownership of AI computing equipment. That distinction makes the portfolio more interesting, while requiring care about how the AI connection is described.

Siris’s March Takkion acquisition agreement described a renewable energy services provider. Its activities include operations, maintenance, repair, construction, transportation, and logistics. Siris subsequently announced completion in May.

The March announcement identified wind services as an established business and discussed expansion into solar, batteries, and transmission. It also connected the investment rationale to electricity demand from data centers. Those descriptions establish the intended connection, not its eventual financial contribution.

The distinction is essential. An energy services business does not become a direct AI supplier simply because AI increases electricity demand. The connection runs through customers, energy projects, and the work those projects require.

That creates several steps between a technology forecast and a supplier’s results. A proposed computing facility needs an energy solution. An energy project needs approval and financing. A service provider then needs to win and execute relevant work.

Each step affects timing. An expanding project pipeline can coexist with delayed revenue. Customers can change specifications, postpone decisions, or select competing suppliers before a service contract begins.

The International Energy Agency’s electricity demand outlook supports the wider demand argument. It projects data center electricity consumption rising from 485 terawatt-hours in 2025 to 950 terawatt-hours in 2030. A terawatt-hour measures electricity consumed over time.

The agency also identifies near-term bottlenecks that constrain expansion. Its assessment supports both sides of the investment tension. Electricity demand creates reasons to expand infrastructure, while practical constraints limit how quickly expansion proceeds.

For Takkion, the analytical question is where its capabilities intersect with funded customer work. Broad demand estimates cannot identify that intersection alone. Readers need evidence about contracts, delivery, and the composition of growth.

A hypothetical wind project shows the difference. A developer might require transportation and maintenance services regardless of whether its electricity ultimately supports industrial demand or computing. The supplier’s immediate customer relationship remains the project developer.

An AI label therefore tells readers less than the details of the work. Contract duration, execution requirements, and repeat business are more informative. Those details show whether demand translates into a durable operating relationship.

The same reasoning prevents an overly narrow interpretation. An energy services business need not depend exclusively on AI to fit a technology infrastructure strategy. Multiple demand sources can support its market.

This makes October Capital AI infrastructure an operating thesis rather than a simple category label. The proposed advantage lies in serving necessary activities around expansion. Its strength depends on the economics of those activities.

The main comparison remains technology adoption versus profitable delivery. Takkion supplies a concrete example of the connection. It also shows why readers should resist treating a favorable industry forecast as a company earnings forecast.

Blackstone Provides a Reference for a Different Investment Route

October Capital’s services focus and Blackstone’s infrastructure investments address related demand through different ownership positions. The comparison helps explain the strategy without inventing a direct contest between the firms.

In July 2025, Blackstone outlined digital and energy infrastructure plans in Pennsylvania. The announcement included data center development through QTS and a power-generation partnership with PPL.

That provides a concrete reference for investing in the facilities and energy supporting computing demand. October Capital’s launch instead emphasizes services that help customers deploy and operate technology. The distinction concerns the business being owned.

Owning a facility and owning a supplier to infrastructure projects create different operating responsibilities. A facility requires development decisions and ongoing operation. A service business requires the capacity to deliver work across its customer commitments.

These positions can complement each other. An expanding infrastructure owner can create demand for external suppliers. That does not mean every supplier captures the same benefit or accepts the same risks.

A service provider also faces choices about specialization. Narrow expertise can make a company useful for difficult assignments. Broader capabilities can allow it to handle more of a customer’s project.

Both approaches have tradeoffs. Specialization can limit the available market. Expansion can introduce unfamiliar work and coordination problems. Neither route deserves a favorable judgment without evidence about execution.

October Capital’s financial infrastructure priorities introduce another variation. Financial infrastructure means the systems and services supporting activities such as payments, lending, and record administration. Its economics differ from transporting equipment or maintaining energy assets.

The July Siris portfolio transaction update described plans involving EQ Retirement Solutions, EQ Customer Resolutions, and Lenvi. It placed the transaction alongside Equiniti’s proposed sale to Bullish. Readers should distinguish that earlier transaction description from October Capital’s later portfolio announcement.

A business separation can require decisions about systems, contracts, staffing, and shared services. Those are general considerations, rather than documented problems in these transactions. They help explain why the closing announcement matters beyond the legal transfer of ownership.

For customers, continuity often deserves more attention than the investment theme. Pension administration and loan servicing involve ongoing obligations. A new owner’s growth plans need to coexist with those obligations.

For investors, the comparison highlights the importance of choosing the right performance measures. Infrastructure expansion and service productivity are related, but they are different outcomes. A portfolio should be assessed against the work its companies actually perform.

Frank Baker on New Firm, October Capital is therefore best understood through the ownership choice. The firm is organizing around services needed for adoption. Blackstone offers context for the surrounding infrastructure market, rather than evidence that either approach will outperform.

A Necessary Service Does Not Guarantee Attractive Economics

October Capital’s central uncertainty is whether essential deployment work produces durable business value for its suppliers. The need for a service and the supplier’s ability to benefit from it are separate questions.

A customer can depend on a service while negotiating aggressively over its terms. Suppliers can compete for the same work. Employees, equipment, and subcontractors can become harder to secure when demand rises.

Those are general commercial risks, not allegations about the initial portfolio. They explain why a growing market needs company-level examination. Demand alone cannot establish the quality of a business.

Contract design is one place to look. A supplier might accept responsibility for completing a defined project. Another arrangement might compensate ongoing work differently. The allocation of delays and unexpected costs affects the result.

Customer concentration also matters. A company serving a small group of major buyers can face a different negotiating environment from a diversified supplier. Public launch materials do not provide enough detail to resolve that issue across the portfolio.

The same caution applies to recurring revenue, income that returns through continuing customer relationships. Repeat work can support predictability. However, renewal terms, service requirements, and customer alternatives still matter.

Automation introduces another tension. A provider can use software to improve its own efficiency. Its customers can also expect those improvements to reduce the work they need to purchase.

The outcome depends on how services are contracted and valued. A supplier paid for results faces different incentives from one paid primarily for labor. Readers should avoid assuming automation always benefits the provider more than the customer.

The acquisition timeline presents a more immediate uncertainty. October’s launch announcement says the pending transactions are expected, without guarantee, to close in November 2026. Earlier Siris materials described January 2027 expectations for related transactions.

The difference does not establish a transaction problem. Expected dates can change. It does mean readers should use current closing disclosures rather than presenting an earlier timetable as settled.

The launch materials also leave important analytical questions unanswered. They do not establish a consistent portfolio-wide measure of AI-related revenue. Nor do they provide enough comparable operating detail to isolate the contribution of the new strategy.

That limits what can reasonably be concluded about October Capital investment strategy today. The firm has defined its focus and identified initial businesses. It has not yet provided a public record of results under the new identity.

There is also a distinction between diversification and strategic coherence. Operating across energy, security, and financial services can spread exposure. It can also demand different management knowledge and performance measures.

A common investment philosophy helps explain why the businesses sit together. It cannot substitute for expertise within each market. Management decisions will show whether the shared platform adds practical value.

The skeptical position is therefore specific, rather than dismissive. Technology adoption creates work, but suppliers must convert that work into satisfactory operating results. October Capital’s investment case becomes more persuasive as that conversion becomes visible.

Watch Closings, Customer Evidence, and the Next Portfolio Addition

The next useful evidence will concern completed transactions, measurable customer work, and the direction of portfolio expansion. Those signals offer a better assessment than another general statement about technology demand.

First, watch for closing disclosures on the signed acquisitions. Completion would clarify the initial portfolio and reduce uncertainty about transaction timing. Any revised timetable would require readers to update their understanding.

A closing announcement should also establish which businesses sit within the resulting structure. That matters when earlier transaction materials describe a broader set of assets. Clear boundaries help customers and observers identify the relevant operating companies.

A completed deal would strengthen confidence in the launch’s immediate execution. It would not establish the long-term success of the investment. Ownership begins the operating chapter rather than completing it.

Second, look for customer evidence connecting the strategy to delivered work. Relevant disclosures might include contract wins, expanded assignments, or improvements in service execution. The useful detail would explain what changed and which customers or activities contributed.

For the AI infrastructure thesis, that means looking beyond general electricity forecasts. Evidence should connect customer spending with a portfolio company’s actual services. The connection becomes stronger when it concerns funded work rather than an anticipated market.

Company disclosures will require careful reading. A new contract does not establish its profitability. A larger project pipeline does not establish when work begins. A technology partnership does not automatically establish customer adoption.

This is also where independent evidence becomes valuable. Customer confirmation or transaction documentation can add context to a supplier’s description. Readers should assess what a disclosure demonstrates before extending it into a broader conclusion.

Third, watch the next portfolio addition or capability expansion. It should reveal how October Capital applies its stated priorities when selecting another business. That decision will provide more detail than the launch’s broad sector categories.

An investment closely connected to an existing capability would suggest one approach to expansion. Entry into a different service category would suggest another. Neither outcome should be judged solely by how prominently AI appears in its description.

Over the coming months, the most informative question is whether the firm makes its operating logic easier to evaluate. Clear disclosures would strengthen the case. Repeated thematic announcements without customer or execution detail would leave the central uncertainty unresolved.

For enterprise buyers, translate those signals into questions about your own suppliers. Identify the services your deployment depends on and the commitments protecting continuity. Keep ownership changes, delivery obligations, and operating results in the same review.

Return to Frank Baker on New Firm, October Capital as those disclosures arrive. Compare the initial promise with completed ownership changes and actual customer work. Track whether expansion adds useful capabilities, and distinguish forecast demand from services already being delivered. The launch identifies where Baker wants to invest; subsequent evidence will show how that focus works in practice. For now, follow the companies, contracts, and closing announcements closely enough to judge the strategy on its operating record. Which new disclosure would most clearly show that technology demand is becoming dependable business for the suppliers supporting it?

Give every agent the context to do better work

Connect your agents to the knowledge, decisions, and history already organized in remio.

remio currently supports Windows 10+ (x64) and Macs with Apple silicon.

Your AI Partner at Work
Get more done with remio

Plan. Create. Deliver.
All in one place.

bottom of page