Fifty opportunities, two salespeople, and a founder confident that something would close. Todd Blaschka wanted to know which something. In an account he published in May 2025, the founder had a list with recognizable company names and very little clarity about the next purchase order. Which deals were expected this quarter? Which prospects were the salespeople prioritizing? The answers were vague. A crowded pipeline had become a rather elaborate way of keeping everybody occupied.
It is an unglamorous opening for a technology career, which makes it useful. Software companies can spend years making difficult things work. Then someone must persuade another organization to pay for them. Between those achievements sits a collection of people with different budgets, anxieties and calendars. Blaschka has spent much of his working life in that space. The forecast is where their intentions have to become specific.
Based in Pleasanton, California, he now advises founders and leadership teams through Accelerate Revenue. He is also listed as a CEO coach and partner at Alchemist Accelerator. His work concerns the decisions that follow a functioning product: whom to approach, what to charge, how to qualify interest and when to bring an experienced revenue executive into the business. The fifty-opportunity story shows his preferred method. Ask a question simple enough that an evasive answer becomes conspicuous.
The databases came before the advice
Before coaching founders, Blaschka held commercial roles at IBM, Electric Cloud and Sendmail, alongside sales leadership positions at Dataguise and Clustrix. These were businesses selling technology to organizations that needed reasons to change their existing arrangements. At Clustrix, he was vice president of worldwide sales. The announcement of his next appointment credited him with more than doubling customer numbers and revenue in less than eighteen months while expanding international operations.
That appointment arrived on October 18, 2017. TigerGraph named him chief operating officer, responsible for growth initiatives and the operations needed to support expanding customer adoption. The company had emerged from stealth the previous month with a $31 million Series A round. Its founder, Yu Xu, was building a business around graph database technology. Blaschka’s assignment was to help turn the technology into an enterprise company with customers, teams and a commercial routine.
The distinction between those tasks matters. A database must answer a technical question. A business must answer several more: who needs it, who can authorize the purchase, who will support the deployment and how the next customer will hear about it. Blaschka’s record puts sales and operations beside each other. That combination helps explain why his later advice reaches beyond the pitch into hiring, account relationships and the machinery of revenue.
after five years
he says he joined
dollar retention
Looking back, he describes TigerGraph growing from zero to $30 million in annual recurring revenue over five years. He says he ran its revenue function for the first three before hiring a chief revenue officer who reported to him. Those figures tell us the scale of the work he claims. The more revealing detail is his account of participating in the first 130 enterprise deals. It places the executive close to the awkward, individual conversations through which a new technology earns a market.
The business inside the graph
Blaschka’s public interviews offer a parallel history: an executive explaining why connected data matters. In 2018, at the Open Data Science Conference in Boston, he discussed how graph databases differ from relational systems. In a 2020 interview, he described contextual AI, digital twins and making analytics accessible to people who do not write code. The emphasis kept returning to what an organization could understand or do differently.
His December 2021 introduction to graph analytics treated relationships as the useful unit of analysis. A company can know many isolated facts and still miss the pattern connecting them. A graph allows those connections to become part of the question. Think of a supply network: a component belongs to a supplier, a supplier serves several factories, and a delay travels through those relationships. The business wants to know where the consequences will land.
In 2022, discussing TigerGraph’s expansion in France, he identified fraud detection, customer understanding and supply-chain analysis as practical uses. He also described connectors being added in response to customer requests. That last detail is modest but telling. Enterprise technology has to live beside the systems customers already possess. A promising architecture meets an organization with its own history, and the organization rarely volunteers to forget it.
His writing about retail recommendations made a similar argument from the customer’s side. An irrelevant suggestion, or a recommendation for something already bought, can make personalization feel inattentive. Technical sophistication has to produce a recognizable improvement in the experience. Across these explanations, Blaschka’s commercial interest is visible: find the consequence that gives a buyer a reason to care.
A good user, a different buyer
The same attention to relationships appears in his advice about open-source software. Developers may download a tool, contribute code and recommend it to colleagues. Their enthusiasm matters. A purchasing decision, however, may sit with a chief technology officer, an engineering leader or a business unit that controls the money. The founder has to understand how interest moves between those people.
Blaschka addressed this in 2023 and returned to it in September 2026. He treats open-source adoption as information about a potential customer, with commercial work still to do. His recommendation is to develop the community and the commercial approach in parallel. Waiting for appreciation to turn spontaneously into contracts leaves too much of the business to other people’s schedules.
There is a courtesy in that argument. It allows the developer to be valuable without requiring them to perform a job they were never hired to do. They can test the software and recognize its merits. Someone else may have to explain the economics, manage risk and authorize a commitment. Good sales work identifies those responsibilities rather than assuming that enthusiasm includes a company credit card.
“Vanity metrics won’t pay the bills.”
Todd Blaschka, May 2025
His August 2026 writing extends the problem into existing accounts. A person who uses a product and a person who actively advocates for it internally have different roles. He recommends mapping budget owners and strategic priorities, building executive relationships and helping users explain business value. The software can be working perfectly while the people deciding next year’s spending remain unaware of it.
Ninety days on the clock
In 2022, Blaschka says, he decided to pursue advisory work rather than return to an in-house operating role. His current practice offers early-stage CEO coaching and commercial advice, fractional revenue leadership for larger businesses, and help with AI product sales. Engagements begin with ninety days. It is a concrete interval in a profession that can otherwise leave the finish line rather tastefully undefined.
His case studies show how varied the assignments can be. For Sapient AI, he describes a testing product with usage signals but little commercial conversation. The work focused on identifying the enterprise buyer and building a route from product adoption to customers. For 2ndChair.ai, he describes customer selection, pricing and founder-led sales for a legal collaboration product. The common task is finding a purchase that the customer can explain in their own terms.
These are his accounts of the engagements, and their specificity is useful. Pricing, buyer identification and customer adoption create different kinds of work. A founder looking for help needs to know which problem is being addressed. Blaschka’s service descriptions include running revenue programs, developing partner channels and supporting post-merger integration. Advice, in this version of the job, can come with an operating responsibility.
When the company outgrows the room
His September 2026 essay on scaling shifts attention from the prospect to the organization doing the selling. As companies grow, informal coordination becomes harder to maintain. People can no longer depend on being near every conversation. Blaschka argues for explicit ownership, a repeatable revenue process and deliberate investment in the leadership layer. The habits that made a small team quick need revision as the team becomes larger.
For an executive who says he joined 130 early enterprise deals, the implication is especially interesting. At some point, knowledge has to travel without the person who acquired it. A new salesperson needs a usable process. Customer expansion needs clear responsibility. The founder needs confidence in decisions made in rooms they never entered. Growth changes the practical meaning of being involved.
Graphwise provides a more recent setting for that work. A November 2024 webinar listed Blaschka as its senior vice president of sales and an executive advisor to Ontotext. Graphwise brought together Ontotext and Semantic Web Company, businesses concerned with giving enterprise data meaning and context. In August 2026, Oakley Capital announced an agreement to acquire a majority stake. Blaschka describes supporting management through the transaction and commercial programs around the merger.
A ticket to the live room
Outside work, his interests have a welcome lack of corporate polish. A Bay Area native and 49ers fan, he enjoys concerts, musicals, opera and comedy. He says he has flown to Europe for a weekend performance. At home, he cooks Italian food, mentions his spouse’s Sicilian heritage and describes life with two daughters, hiking and travel. An opera ticket is quite a different sort of commitment from a software subscription, although both benefit from checking the date.
The personal details do not explain every professional choice. They do give the profile some air. Here is someone whose working vocabulary includes forecasts and recurring revenue, and whose leisure can involve crossing an ocean to sit in an audience. A live performance offers an experience that cannot be moved to next quarter. Everybody has agreed to be there at the same time.
That brings us back to the founder with fifty opportunities. Blaschka’s question was about commitment: which customer, which decision, which quarter? A startup can have a compelling product and still need to learn how other people choose. His career follows that difficult education, from enterprise databases to AI advisory. The next useful conversation begins when somebody can say exactly what happens after it.