The graph Rob Woollen likes to show begins as a joke with excellent timing. For years, the line lies flat at zero. It keeps lying there, indifferent to the usual founder mythology about quick validation and hockey sticks. Then it rises so abruptly that the chart finally resembles the story Silicon Valley prefers to tell. The line is Sigma's revenue. The long horizontal part is the more useful half.
Woollen co-founded Sigma in 2014 with Jason Frantz to make cloud data usable by people who did not write SQL. The conviction arrived before the product. Teams built prototypes. Ideas were tried and set aside. Investors waited, sometimes less than joyfully. Early employees stayed. The office, by Woollen's later description, was terrible, which at least kept the burn rate tidy. For roughly seven years, the company searched for the implementation that could carry its original idea.
By May 2026, Sigma said it had crossed $200 million in annual recurring revenue, served more than 2,000 customers, and closed an $80 million Series E at a $3 billion valuation. Those figures make the flat line look ordained. It was not. At every earlier point, there were reasonable reasons to stop.
A programmer before the title existed
The urge to make computers behave arrived early. Woollen grew up in Palatine, Illinois, with a father who began as a programmer and moved into IT management, a mother who taught English, and an older sister whose good grades preceded him into classrooms. His family's first computer was an Apple IIe. He played games, then started opening up programs and altering them, occasionally breaking what his parents had paid for.
The first substantial program he remembers writing had a customer close at hand: his mother. It calculated student averages and grades. The detail feels almost suspiciously neat in retrospect. His later company would also begin with an expert who understood the work but needed software to perform the calculation. At 11 or 12, Woollen already knew he wanted to program. Executive titles, venture rounds, and corporate strategy had not entered the picture. The pleasure was immediate feedback: change a line, watch the machine react.
That instinct survived Princeton, where he earned a computer science engineering degree in the 1990s, before the internet settled into ordinary life. He still describes education less as vocational prophecy than training in how to learn. Languages age. Systems vanish into what he calls the history vaults. The habit of picking up the next thing endures.
The 1998 decision that kept paying dividends
After Princeton, Woollen joined Hewlett-Packard and worked on the HP-UX kernel. It was pure systems work, down among the bits, while the dot-com economy was making the web seem like a party occurring elsewhere. In 1998 he moved to the WebLogic team at BEA Systems. Java was new enough to feel glamorous. An automated testing suite mentioned during his interview struck him as exotic. More important, he thought the people around it could teach him.
Every job he has held since, Woollen says, connects somehow to that group. A colleague from BEA helped pull him toward Salesforce. People from that orbit later appeared among Sigma's investors and board members. Chris Fry, Mike Speiser, Sam Pullara, Scott Dietzen: the names recur not as cocktail-party contacts but as people who had watched one another work.
The distinction matters. Company selection can resemble stock picking; intelligence and generosity are easier to observe at close range. Woollen chose the team, and the team compounded. It is a pleasingly unflashy theory of a career: colleagues become the durable architecture.
The spreadsheet refuses to die
At Salesforce, Woollen moved from principal architect to platform CTO, then made a riskier transfer into platform product management. He had never been a product manager or managed people. He made mistakes. He also learned how sales teams speak, how customers behave during a crisis, and why a technically correct answer can fail to become a useful product.
One planning exercise stayed with him. A knowledgeable employee was deciding how many salespeople Salesforce should hire and when. She understood the domain far better than Woollen did, but she could not calculate directly from the warehouse. Important assumptions had become fixed numbers in a spreadsheet because that was the tool she could control.
There sat the contradiction. Cloud applications were filling databases with valuable information, yet business experts still exported small slices to personal machines. The people who could query the warehouse did not necessarily know which questions mattered. The people who knew the business could not reach the data without asking for help. Sigma's premise was to close that gap by translating familiar spreadsheet gestures into queries that ran against the cloud warehouse.
A spreadsheet, in Woollen's telling, is not a sad remnant of office life. It is a compact application-development environment used by people who would never describe themselves as developers. A financial model has inputs, logic, and outputs. The interface is popular because people can think with it. Sigma kept the grid and moved the computation.
The courage to rebuild after the first sale
The company protected one boundary from the beginning: cloud only. Prospective customers sometimes asked to host the software themselves. Agreeing might have produced short-term revenue, but it would have violated the architecture the founders believed the market was moving toward. Elsewhere, the team improvised. Woollen is candid that surviving software with technical debt is preferable to immaculate software without users.
Eventually Sigma found a product that generated roughly $1 million in annual recurring revenue. After years near zero, the amount was proof of life. Then, during the pandemic, the company decided to rebuild. Engineers had to move resources. Salespeople had to sell the unfamiliar version instead of the one they finally trusted. People left. Historical success makes the choice sound obvious; Woollen remembers the reasonable objections.
The replacement was the workbook, a broader canvas for analysis and data applications. By the end of 2021, Sigma said it had doubled its customers and tripled revenue over the preceding year. Later came the steeper portion of the line: $100 million in ARR, then $200 million. The years of delay were not a refusal to change. They were the cost of changing almost everything except the problem.
Begins work on the HP-UX Unix kernel after Princeton.
Joins the WebLogic team, forming relationships that echo through his career.
Moves to Salesforce and later becomes a platform CTO and product leader.
Co-founds Sigma with Jason Frantz after an EIR year at Sutter Hill Ventures.
Moves from CEO to CTO as Mike Palmer joins to lead the company.
Sigma announces $200 million ARR and an $80 million Series E.
An introvert learns the microphone
Woollen calls himself an introvert. In his early twenties, he dreaded a public presentation for months and shook visibly when it arrived. Now he speaks to customers, audiences, and podcast hosts several times a week. He does not present the change as a conquest of personality. He wanted to learn, practiced, and made the unnatural task ordinary.
That mixture of candor and persistence also shapes his advice about founding a company. His standard opening is discouragement. The odds are poor. Brilliant people build excellent products that go nowhere. If a ten-minute warning can persuade someone to quit, he considers the warning useful. No version of the speech would have changed his own mind. Starting Sigma, he says, was not logical; it was something he felt obliged to attempt.
Away from the warehouse, the same curiosity becomes bread. Woollen likes making food from scratch, sometimes exactly once, to understand its derivation before deciding the trouble was excessive. He likes wine, hikes in Marin, pizza, burritos, and time with his family. He says he is peaceful and cannot leave a software bug alone. The two claims are less contradictory than they appear. Calm is useful when the machine refuses to explain itself.
After the dashboard
In 2026, Sigma's language widened from analytics toward AI applications and agents that operate on governed warehouse data. Woollen argues that the next step is not merely asking a chatbot for a chart. It is allowing software to analyze, decide, and act without copying sensitive data into another system or dissolving the controls around it. The familiar spreadsheet remains, but it now shares the workspace with SQL, Python, workflows, and models.
His corporate aspiration is equally plain. Woollen has said an initial public offering was the goal when Sigma had no revenue and remains his preference. Small opportunities were discarded along the way if they did not appear capable of supporting a large independent company. That choice lengthened the flat line. It also explains why an acquisition, however flattering, has never been his favored ending.
There is no tidy rule here. Persistence can become denial. A rebuild can waste the traction already earned. Patient capital may simply postpone an honest reckoning. Woollen's record is interesting because he does not erase these alternatives. He recalls the uncertainty, the people who declined to continue, and the investors who would have preferred speed. The outcome did not make the risks imaginary.
The boy with the Apple IIe wanted to alter something and watch the result. The CTO still does. Between those two points lie a Unix kernel, a Java application server, a cloud platform, a spreadsheet, and a line that took its time before moving. Woollen's career offers no shortcut through that sequence. Its charm is that he kept debugging it anyway.