Enterprise software has a peculiar manners problem. It is invited into an organization to make life orderly, then stays long enough to become part of the family furniture. Years pass. Teams change. Interfaces are added. Acquisitions bring more code. One morning, somebody proposes modernization and discovers that the elegant system diagram hanging in the meeting room bears only a ceremonial relationship to reality.
Rado Nikolov has made a career around that awkward morning. Today he is executive vice president and chief marketing officer at CAST, the software-analysis company. His job is marketing and communications, but his vocabulary is filled with architecture, dependencies, middleware, open-source components and structural flaws. He talks about software less like a campaigner admiring a new façade and more like a surveyor tapping the walls.
That fluency is not borrowed for a brochure. Before the executive titles, he built mission-critical applications at MacDonald Dettwiler and Associates, the Canadian space and information-systems company usually shortened to MDA. Later, at IBM, he moved through developer relations, product strategy, middleware, sales and marketing. The route matters. It gave him a view of enterprise technology from the code outward and from the buying committee inward.
The map before the journey
At CAST, Nikolov describes the product with a metaphor that does unusually heavy lifting: an “MRI for software.” The phrase makes a dense category immediately physical. Nobody wants surgery performed from a photograph of the patient. Nobody should want a critical application transformed from a slide deck, either. The hidden structure is the work.
Software intelligence, in this telling, is not merely a prettier inventory. It is a way to expose how components call one another, where data flows, which open-source packages are embedded, how architecture has drifted and where a seemingly local alteration may travel. The output can serve engineers trying to understand unfamiliar code, executives deciding which systems to modernize, and deal teams examining what they may be about to buy.
“Deploying CAST Highlight as the open source ‘control tower’ across an organization can be done in a few weeks.”
The metaphor changes with the audience. An MRI is diagnostic. A control tower is operational. Both do the same conceptual work: they turn what is dispersed and invisible into something a group can see together. Nikolov’s durable subject is not code itself. It is legibility.
A career in translation
In 2007, Nikolov was IBM’s director of strategy and emerging business for independent software vendors and developer relations. IBM was expanding support around WebSphere Application Server Community Edition and DB2 Express-C. The company offered partners access to technical advice, marketing help and sales support. More than 300 software vendors and integrators had already built applications through the earlier WebSphere program.
It was an ecosystem play, but also a lesson in reducing the anxiety of adoption. A free product is not truly easy if partners cannot integrate it, explain it or support it. The program surrounded code with the human and commercial machinery needed to make it useful. Nikolov was explaining not only what IBM had built, but how other companies could build a business around it.
His years at IBM widened from developer ecosystems into middleware products, regional software growth, CIO marketing and collaboration software. CAST credits him with work around WebSphere and Linux, relationships with large software vendors, and product lines that had to be sold across countries and executive cultures. The résumé zigzags between technical and commercial roles, yet the underlying task stays neat: translate complexity without insulting it.
Mission-critical application work and project leadership.
Strategy for ISVs and developers around WebSphere and DB2.
CIO storytelling, then award-recognized work around Domino V10.
Marketing, communications and the software-intelligence category.
The campaign with one letter
A useful example of his IBM period is “What I Can Disrupt,” a CIO campaign on which Nikolov was credited as a program director. Its premise turned the letter I into three prompts: ingenuity, initiative and inspiration. The conceit was simple enough to remember, while the campaign architecture was not simple at all: film, an interactive experience, educational chapters, paid media and lead generation.
Published results recorded more than 140,000 views for the 90-second anthem film, a 75 percent completion rate and more than 100,000 landing-page visits. The figures reveal a habit that appears elsewhere in Nikolov’s public work: the appetite for a clean story paired with an insistence on measurement. A line must travel, but it must also do a job.
Two years later, his honors list attached an ANA B2 Award and two Hermes Creative Awards to the IBM Domino V10 launch and its #dominoforever campaign. Domino was familiar technology with decades of history. Giving it a fresh public life required something harder than novelty. It required treating installed affection, technical utility and accumulated baggage as parts of the same story.
This may be where Nikolov’s “entrepreneurial streak,” the phrase used in his corporate biography, becomes most visible. Entrepreneurship inside a large technology company often looks less like inventing from nothing and more like finding a movable edge in something enormous. A middleware portfolio, a developer program or an old collaboration brand can still be repositioned if somebody identifies the opening and gives colleagues language they can repeat.
AI meets the brownfield
Now the fashionable urgency is generative AI. Models can produce code at a speed that makes yesterday’s development rhythm look upholstered. But most large companies do not operate in a clean laboratory. They live in the brownfield: old and new systems sharing data, business logic embedded in forgotten corners, and architectural decisions whose authors have moved on.
Nikolov’s recent message is that AI needs context. In CAST sessions on technical debt and developer productivity, the proposed combination is probabilistic capability grounded by deterministic information about actual applications. The model may suggest a change; the map shows the neighborhood it could disturb. This is less glamorous than a blank-screen demo and considerably closer to Monday morning.
The concern is sharpened by technical debt, a phrase that sounds financially tidy for a reality that is usually archaeological. Some debt is a hasty choice made to meet a deadline. Some is merely yesterday’s correct design surviving into a different world. The difficult part is not announcing that debt exists. It is deciding which part threatens reliability, security or performance, then separating urgent repair from aesthetic tidying.
Nikolov’s public work around ISO/IEC 5055 brings a standard into that argument. The standard describes measures for software’s structural quality across security, reliability, performance efficiency and maintainability. Standards are not known for cocktail-party charm. Their usefulness is that opposing teams can stop debating taste and examine the same rules.
AI makes the hands faster. Architecture tells them where they are.
The executive as cartographer
Nikolov occupies an interesting position in the CAST leadership group. As CMO, he must make an emerging category comprehensible. As a former builder and product manager, he knows comprehension cannot be achieved by sanding away every technical edge. Enterprise buyers are allergic to fog, but engineers are equally allergic to fairy tales.
His solution is a sequence worth stealing. Begin with the object people cannot see. Give it a concrete image: MRI, map, control tower. Connect that image to a decision the audience already owns. Then attach evidence, whether a dependency graph, a portfolio score or a campaign conversion rate. The story stays simple because the work beneath it does not pretend to be.
That pattern also explains why his career is more coherent than its titles initially suggest. Developer relations and chief marketing officer may sit far apart on an organization chart. In practice, both ask what another person needs before they can trust unfamiliar technology. Sometimes the answer is documentation and an engineer on the phone. Sometimes it is a campaign that clarifies the stakes. Sometimes it is a picture of the application nobody has seen whole.
There is also a quiet consistency between his early ecosystem work and today’s AI argument. In both, technology alone is insufficient. WebSphere needed partner support around it. AI needs architectural context beneath it. Adoption succeeds when the surrounding system is designed, not when a clever component is dropped onto the table and expected to make friends.
New York is an apt base for such work. The city runs on layered systems and institutional memory, with yesterday’s infrastructure carrying tomorrow’s ambition. Nikolov’s professional world has the same character. Banks, insurers, public agencies and global companies cannot clear the site and begin again. Their advantage depends on changing what exists while it continues to work.
The software estate will not grow less complicated. AI will add code, mergers will add applications, and business rules will continue hiding in procedures written before the newest team arrived. Nikolov’s wager is that visibility can turn that inheritance from a source of dread into a field of choices. The map does not choose the destination. It simply makes confidence less theatrical.