RelayWorks Replaces a Founding CTO Without a Shadow Role

Situation. RelayWorks sells workflow software to insurance companies. It has 260 employees, 95 in product and engineering, and strong revenue growth. The founding CTO, Arun, wrote the original product, hired most technical leaders, and owns significant equity. He reports to the CEO, who is also a cofounder.

Enterprise customers now demand reliability, audit evidence, data controls, and predictable delivery. Engineering managers depend on Arun for architecture decisions. He dislikes performance management and spends increasing time on a new technical concept. The board says the company needs a “scale CTO.”

Diagnosis. The company initially frames the problem as Arun’s failure to scale. The role diagnosis shows a more complicated system. Product priorities change frequently. The CEO privately asks Arun to rescue customer commitments. A promised VP Engineering hire was delayed. Arun has not built enough delegation, but the company has rewarded his interventions.

The future work requires engineering leadership, platform and reliability investment, enterprise readiness, senior technical paths, and a CEO relationship that can make capacity tradeoffs. Arun says he wants to lead architecture and incubation, not a 100-person organization.

Options. The board considers keeping Arun as CTO with a strong VPE, making him chief architect with a new CTO, and asking him to leave operations.

The first option could work if the title does not require executive management, but the CEO wants one technology executive accountable for the whole system. The third option would remove valuable product and customer knowledge and is not what Arun wants. The second can work only if chief architect is a real role and Arun gives up shadow management.

The decision rights specify that Arun owns incubation for one named product area and advises enterprise-significant architecture. The new CTO owns engineering leadership, platform strategy, technical risk, capacity recommendation, and final architecture decisions within agreed thresholds. The CEO resolves product-capacity conflict. Arun has no direct reports initially and cannot accept private escalations from engineering managers.

Search. Candidates receive the founder-transition structure before final interviews. One candidate demands that Arun leave within three months. Another says the relationship will work because they respect founders but cannot describe authority. A third, Lena, asks to review three past decisions where Arun’s informal role overrode management. She proposes a joint technical history process and a weekly transition meeting that ends after 90 days.

Lena’s evidence includes taking over a product organization from a revered technical founder. References say she preserved the founder’s product insight but waited too long to address a weak infrastructure leader. The risk plan creates an explicit day-60 leadership assessment.

First 180 Days. During the first month, employees continue to ask Arun for approval. He answers twice. The CEO addresses both cases publicly through the decision-rights model rather than blaming individuals. Lena invites Arun into architecture discussions as an adviser, records the final decision, and follows through.

At day 90, the transition is stable, but the product organization still routes urgent promises through the CEO. The mandate review adds a customer-commitment mechanism shared by product, sales, finance, and the CTO.

At day 180, Lena has appointed a VP Engineering, protected reliability capacity, and stopped an unfocused platform program. Arun’s incubation work has produced a useful prototype but not a roadmap commitment. He says the new role has more technical depth and less status. This is treated as a good result.

One Year. Delivery predictability and reliability improve, but one enterprise launch misses. The review finds product scope and late sales commitments contributed. Lena had raised the issue but did not escalate the accumulated risk early enough. The first-year result is strong with a specific candor improvement.

The company now has a CTO, a VP Engineering, and a founder technical leader whose roles are understood. The success came from CEO enforcement of boundaries, not from chemistry alone.

Lesson. The company replaced a role design and redistributed authority. It did not rewrite history to make the new appointment appear necessary.