New York Tech Leadership Brief: When an AI Business Raises $75 Million, What Does Its CTO Need to Deliver Next?

By Warren Beazley | Friday 13 November 2026

Raising investment can give a technology business the resources to grow.

It also brings a new set of leadership questions.

How will the product scale? What needs to change in the engineering organisation? How will the business stay close to customers? And what does the board need its technology leader to achieve over the next 12 months?

Those questions came to mind when I read this week’s news about New York InsurTech Kalepa.

Kalepa: a funding round and a new CTO

On 5 November, Kalepa announced a $75 million Series B, led by Updata Partners, at a reported $470 million valuation.

Kalepa provides an AI platform for insurance workflows, including underwriting and portfolio decisions. The company says it intends to use the investment to expand its products and enter new markets.

The funding follows a change in technology leadership. Kalepa announced Garrett Schlesinger as CTO on 22 October. He joined after 12 years at Affirm, where, according to Kalepa, he helped build the company’s real-time underwriting system.

That combination—a significant growth round and a recently appointed CTO—is a useful example of how a technology leadership mandate can evolve.

A business at this stage may be asking its CTO to do several things at once: strengthen a product already serving customers, build an organisation capable of scaling, support expansion and maintain the confidence of the people making important insurance decisions.

Those are general leadership challenges, rather than a claim about Kalepa’s internal priorities or the terms of Schlesinger’s appointment.

The question for a board is not simply whether its CTO has worked with AI. It is whether the leader’s experience matches what the business now needs to achieve.

Sources: Kalepa funding announcement, 5 November 2026; Updata Partners investment announcement, 5 November 2026; Kalepa newsroom and CTO appointment.

The difference between an AI strategy and a leadership mandate

An AI strategy can describe what a business wants to build.

A leadership mandate needs to go further. It should explain what the technology leader is accountable for delivering and what support they will have.

In a growing InsurTech, that might include questions such as:

• Which customer and underwriting problems matter most?
• What must the platform do reliably as the business grows?
• How will engineering, product and insurance specialists make decisions together?
• Which measures will show whether the technology is creating value?
• What team and authority will the CTO need?

The answers will differ by business. A founder-led company making its first senior appointment may have very different needs from a Series B business expanding an established product.

That is why I believe the most useful starting point for a CTO search is the outcome the business needs.

HealthTech: testing AI in clinical environments

Another New York development reinforces the importance of understanding the work around the technology.

On 10 November, investor Oak HC/FT announced that it had led a $12.5 million seed round for Alterra Labs. The investor says Alterra is building simulated healthcare environments to help train and evaluate AI models and plans to expand its team of clinicians, scientists and researchers.

The leadership implication is interesting. In a clinical setting, being able to use software is only part of the challenge. A system also needs to be evaluated against the knowledge and judgement involved in the work.

That suggests a close relationship between technical teams and clinical specialists. The technology leader’s role may include creating an environment where both can challenge assumptions and agree on what should be tested.

The investment is a signal of interest in this area; it does not, by itself, establish that Alterra’s approach has improved patient outcomes.

Source: Oak HC/FT on Alterra Labs’ seed round, 10 November 2026.

AI infrastructure: what happens when systems fail?

Earlier in November, New York-founded Traversal announced a $120 million Series B for its work on AI-assisted site reliability engineering.

The company is focused on helping engineering teams investigate production incidents and diagnose problems in complex systems. The announcement was published on 3 November.

For CTOs, reliability is a commercial issue as well as a technical one. When a critical system is unavailable, customers, employees and revenue can all be affected.

Tools that help teams understand incidents may be valuable, but technology leaders still need to decide how those tools fit into incident response: what can be automated, what needs review and who makes the call when the evidence is incomplete.

The funding round signals investor interest. Claims about how well the product performs should be assessed separately from the financing announcement.

Sources: Traversal’s announcement, 3 November 2026; AlleyWatch New York tech review, 8 November 2026.

⛏️ From the Coal Face: the CTO’s role goes beyond the technology

In a conversation this week, one technology leader described the value of working close to customers and seeing directly how a product is used.

His experience had reinforced something I hear regularly: it is possible for talented teams to build and deliver technology without regularly hearing from the people it is meant to serve.

That matters when a business enters its next stage of growth. A CTO may be asked to scale the platform and grow the team, but they also need to understand which customer problems the business is trying to solve—and make sure that understanding reaches the people doing the work.

In an earlier conversation, another engineering leader described the importance of agreeing what a role is really there to achieve. They were most interested in building teams and improving engineering outcomes; the role they had taken placed greater emphasis on managing day-to-day delivery.

Neither set of priorities is inherently wrong. The difficulty comes when the business and the incoming leader have different expectations.

A third leader described wanting a role with a closer connection to commercial decisions and the future direction of the company.

These are individual perspectives, gathered in separate conversations over recent weeks. They bring us back to an important question for founders and boards:

Have you explained what your technology leader will own, how they will work with the rest of the business, and what success will look like?

The title may say CTO or VP of Engineering. The work behind it can be very different.

The clearer that picture is before a search begins, the easier it becomes to find a leader who can deliver what the business needs—and wants to do so.

A question worth asking before the search begins

Imagine it is 12 months after you have hired your new CTO.

They have exceeded your expectations. You are about to walk into their first annual review.

What have they achieved?

What have they resolved?

What have they put in place for the next stage of growth?

And what did the business need to give them—in authority, resources and support—to make that possible?

Whether the company is building insurance technology, clinical AI or infrastructure software, those answers can help turn an ambitious job description into a clear leadership mandate.

That clarity gives the board a better basis for assessing candidates. It also gives the person appointed a better chance to succeed.