Beyond the Terminal: How Craft Founder Ilya Levtov Built a Multi-Million-Dollar Software Empire Without Writing a Single Line of Code

Share
Beyond the Terminal: How Craft Founder Ilya Levtov Built a Multi-Million-Dollar Software Empire Without Writing a Single Line of Code

Editor’s note: The following is the fourth installment in an ongoing profile series examining startup founders from non-technical backgrounds who have successfully launched and scaled venture-backed enterprises. Read the previous interviews with MagicSchool AI founder Adeel Khan, Trunk Tools founder Sarah Buchner, and Tabs founder Ali Hussain.


Executive Overview

In the hyper-accelerated ecosystem of Silicon Valley, conventional wisdom dictates that a startup founder must emerge from the proverbial garage clutching a git repository, fluent in Python, React, or systems architecture. The archetype of the hoodie-wearing, code-slinging engineering prodigy has long dominated venture capital boardrooms. Investors frequently operate under the assumption that the shortest line to a successful software company is a technical founder who can single-handedly architect the product from scratch.

Yet, Ilya Levtov—founder and CEO of the San Francisco-based supply chain software enterprise Craft—shatters this mold. By traditional Silicon Valley standards, Levtov possessed a pedigree tailor-made for high finance or venture capital: a degree from Stanford Business School, foundational experience working as a venture capitalist on Sand Hill Road, and early operating trenches inside a hyper-growth ad-tech startup.

There was just one glaring exception to his resume: he possessed zero technical background.

"I’ve never written a line of code in my life," Levtov revealed in an interview with Crunchbase News. Today, twelve years after founding Craft—a mature enterprise platform that currently collaborates with 35 federal agencies and generates double-digit millions in annual recurring revenue (ARR) while raising $42 million in total venture funding—that statement remains remarkably unchanged. "And I still haven’t written a single line of code."

Levtov’s journey offers a masterclass in modern entrepreneurship, exposing both the stark initial disadvantages faced by non-technical founders and the systemic blind spots embedded within Silicon Valley’s engineering-first orthodoxy. As artificial intelligence fundamentally reshapes the barriers to software development, Levtov’s trajectory challenges us to reevaluate what it truly takes to build, scale, and sustain a thriving technology enterprise.


Detailed Chronology: From the Concert Hall to the Boardroom

An Unlikely Prelude

Levtov’s entry into the world of technology was anything but linear. Born in the Soviet Union, his family emigrated to England when he was a toddler. Surrounded by a household of professional musicians—both of his parents made their living in the arts—Levtov picked up the cello at the tender age of four.

His childhood and adolescence were consumed by rigorous musical training. He attended a specialist music school in London, advanced to the prestigious Royal College of Music, and later participated in a selective Columbia-Juilliard exchange program. Simultaneously, he pursued an academic degree in English Literature at Columbia University.

By the time graduation day arrived, however, Levtov made a pragmatic pivot. He decided to relegate music to the status of a lifelong passion and set his sights on the corporate world. He entered the rigorous halls of Goldman Sachs, later secured admission to the Stanford Graduate School of Business, and subsequently plunged into the operational chaos of Spot Runner, an early ad-tech startup that scaled rapidly from roughly 10 employees to nearly 200 during his tenure.

"I was just totally bitten by the bug," Levtov recalls of his time at Spot Runner. "And I said, ‘This is what I want to do with my life. I want to build a company one day. Somehow, entrepreneurship is for me.’"

The Vantage Point of Capital and Operations

Before stepping into the founder’s arena, Levtov deliberately examined the startup landscape from multiple vantage points. He transitioned to the other side of the capitalization table, working as a venture capitalist at Venrock. Following his stint in VC, he stepped back into an operating role at video streaming pioneer Crunchyroll.

Seeking global perspective, Levtov relocated back to Europe, joining Deutsche Telekom where he spearheaded initiatives helping prominent Silicon Valley startups—including Evernote, Box, Dropbox, and Pinterest—establish lucrative distribution partnerships across European markets.

These experiences granted him an encyclopedic view of how early-stage companies succeed and fail. Yet, the itch to build his own venture remained unscratchable through traditional employment.

The Accidental Pivot

Craft did not begin as a grand vision for supply chain software. Rather, the company emerged from the ashes of an entirely different venture: an unsuccessful attempt to build an enterprise social network.

During the development phase of that initial project, Levtov’s lean team needed to assemble comprehensive corporate profiles. To accomplish this, they engineered a data-collection mechanism that scraped and aggregated information from corporate websites, job boards, executive management pages, and external public registries.

While their original enterprise social network failed to gain traction, an unexpected phenomenon occurred. The corporate profiles they had painstakingly compiled began climbing to the top of Google search engine results pages. Recognizing the organic momentum, Levtov recognized an entirely new business model hidden in plain sight. The pivot that would become Craft was born.


Supporting Context & Metrics: Navigating the Non-Technical Handicap

Building a software-as-a-service (SaaS) platform without technical capabilities introduces a unique set of operational friction points. While a technical founder can spend their nights and weekends hammering out the MVP (Minimum Viable Product) independently, Levtov faced an immediate structural disadvantage.

The Upwork Dilemma

"My first coder was literally a $20-an-hour Odesk or Upwork person," Levtov admits candidly.

Without the ability to evaluate code quality, review architecture, or gauge technical complexity, Levtov was forced into a painstaking cycle: hunting down freelance developers, attempting to translate abstract business visions into functional specifications, and hoping the final product matched his expectations. Only after securing a working prototype could he aggressively pursue the capital required to fund professional engineering talent.

Craft’s Ilya Levtov Never Learned To Code. He Built A Software Company Anyway.

Despite these hurdles, the initial data engine demonstrated remarkable organic pull. According to Levtov, Craft’s early company profiles eventually surfaced in over 100 million search results per month, pulling in roughly 2.25 million organic visitors without a massive paid marketing budget.

The Venture Capital Roadblock

When Levtov hit the fundraising trail in London between 2015 and 2016, he confronted a cultural hurdle common among non-technical founders: institutional venture capitalists overwhelmingly favored teams that could write their own code.

"I decidedly remember this clarity with which I found venture funds whose websites I go to and research. And what did they say? ‘We support technical founders in doing this and that.’ And it really was just this moment [of realizing], ‘Oh, I guess that means not me, right?’" Levtov reflects.

Despite these programmatic biases, Levtov’s blue-chip pedigree—featuring Stanford and Venrock on his resume—provided a vital bridge. He successfully secured early bridge financing from Downing Ventures in the U.K., and later closed institutional rounds with Uncork Capital after returning to Silicon Valley. In total, Craft has raised $42 million in venture backing.

The Cost of the Technical Gap

Levtov is careful not to dismiss the logic behind venture capital’s preference for technical founders.

"They’ve got a direct line between the business concept and the code in which it’s executed," he notes.

By contrast, Levtov’s lack of technical depth introduced vulnerable blind spots. He candidly shares that there were instances where he hired the wrong technical personnel and lacked the diagnostic expertise to identify the misstep quickly. This inevitable disconnect between business leadership and the intrinsic innards of the software codebase ultimately slowed the company’s early velocity.


Official Statements & Breakthrough Realizations

The turning point for Craft arrived not from an internal engineering breakthrough, but from an external market pull that validated the company’s underlying data asset.

Entering the Enterprise Space

A representative from aerospace and defense giant Lockheed Martin reached out to Craft, highlighting an unexpected utility: Craft’s data platform could be leveraged to track granular changes across a vast, complex supply chain. By monitoring shifts in corporate hiring patterns, executive departures, and newly launched product lines, enterprises could proactively manage third-party risk.

Lockheed Martin signed on as Craft’s inaugural enterprise customer. The validation proved catalytic. In 2020, the U.S. Air Force approached Craft with a mission-critical mandate: monitor 300,000 companies within the defense industrial base. Leveraging their robust data infrastructure, Craft closed a monumental five-year, $6.5 million contract just 94 days later.

"We figured out that our company is actually a supply chain company, and we haven’t looked back since then," Levtov states. Today, Craft counts 35 federal agencies among its clientele and generates double-digit millions in annual recurring revenue.

The Business-First Advantage

Crucially, Craft’s most lucrative customers were not software developers searching for niche developer tools; they were enterprise business leaders grappling with complex operational crises.

This is where Levtov believes his non-technical background transformed from a handicap into an asset. While non-technical founders may struggle to audit codebases or assess low-level engineering talent, they frequently excel in domains that dictate long-term enterprise survival: deep customer empathy, organizational leadership, strategic fundraising, and relationship building.


Future Outlook: The Evolving Role of the Founder in the Age of AI

As artificial intelligence democratizes software development—allowing complex applications to be generated through natural language prompts—the traditional divide between technical and non-technical founders is rapidly blurring. Yet, Levtov cautions against declaring the technical founder obsolete.

"It really just takes both. It takes both sides," Levtov emphasizes. "I think if you can have a technical founder and a non-technical founder, you’re probably in the ideal spot."

According to Levtov, the lifecycle of a company demands cyclical skill sets. In the earliest, pre-product-market fit days, technical founders hold an undeniable edge because velocity and raw building speed are paramount. However, as organizations scale, the operational center of gravity shifts toward go-to-market execution, strategic positioning, institutional recruiting, and high-stakes dealmaking.

"At different points in a company’s life, it’s really about the tech right now," Levtov concludes, "while at others, it’s all about the dealmaking, or all about the positioning, or the marketing."

By proving that a CEO can build a multi-million-dollar software powerhouse, secure millions in venture capital, and contract with dozens of federal agencies without ever touching a command line, Ilya Levtov has expanded the boundaries of who gets to be a tech founder—proving that in the end, solving the customer’s problem matters far more than knowing how to compile the code.

Did you find this story helpful?

Share it with your friends and colleagues on social media.

Share

Leave a Comment

Your email address will not be published. Required fields are marked *