Ian White and the company that outgrew its own map

At two people, a company can keep much of its organization in conversation. At 200, conversation needs assistance. Ian White had helped Sailthru make that journey, and success brought a peculiar difficulty: he could build sophisticated software for customers while struggling to assemble a clear picture of his own team. The information existed. Getting it together was another occupation.

The familiar tools were waiting: exports, spreadsheets, tables, more exports. A company could change while someone was still describing it. Hiring and promotions kept moving. The document attempting to explain them acquired the historical value of yesterday’s weather forecast.

White eventually made that frustration into ChartHop. As its founder, CEO and CTO, he has spent years working on the proposition that people should be able to understand the organization they belong to without first becoming its unofficial archivist.

The map stopped keeping up

Sailthru’s growth gave him a close view of the problem. The business expanded from two people to 200 in roughly three years. The early ways of working began to strain when the team reached about 50. Decisions about people required information scattered across systems, and White found himself spending days assembling it.

There is an awkward comedy to this. An engineering leader can examine the behavior of a server in considerable detail, then turn to a question about staffing and begin an expedition through Google Sheets. White had used software that made technical systems visible. He wanted comparable clarity about the people building them.

His later consulting work widened the view. Other organizations, including much larger businesses, were doing the same manual reconstruction. That gave the idea a different weight. A difficulty he had experienced personally turned out to be a recurring operating problem.

A programmer with a theater education

White studied computer science and theater at Brown University, then earned an MFA in theater. He chose the technical route professionally, but he has credited theater with preparing him to communicate and lead teams. It is a useful detail in a career increasingly concerned with helping people understand one another’s work.

In 2008, he joined Business Insider as its first engineering leader and architected its publishing platform. The job put him inside a media business, building the machinery through which other people’s reporting reached readers. Before the workforce diagrams came the pages.

He was also an early MongoDB user. The database company’s historical documentation identifies him as the first person outside its original company, 10gen, to use MongoDB in production. His public code includes SimpleMongoPHP, a library wrapper for the database. This side of his biography is comfortably specific: he made things, deployed them, and left some of the tools where other developers could find them.

At Sailthru, he became co-founder and CTO, working on technology that personalized communications for publishers and commerce businesses. Later, through Stardog Ventures, he offered startups architecture, development and consulting expertise. Across those jobs, he kept encountering the practical distance between the information a business possessed and the information its leaders could readily use.

A product before a pitch

ChartHop began in 2018 and emerged publicly on February 20, 2020. In his launch announcement, White described an admiration for software that gets small details right and expands what teams can accomplish together. He named tools used during his earlier engineering career, including Stripe, Datadog, GitHub and MongoDB.

There is a recognizable builder’s instinct in that list. Good software changes the work around it. White wanted to bring that expectation to the less glamorous business of knowing who works where, what a hiring plan contains, and how the pieces connect.

He spent about two years building before the public launch. When he met Andreessen Horowitz partner David Ulevitch, he brought a demonstration of the product rather than a pitch deck. The conversation helped lead to the firm’s seed investment. Around the same time, his son was born. The calendars of entrepreneurship and family life had declined to coordinate.

He had experienced colleagues to call on, too. About half of ChartHop’s early team had worked with him at Sailthru or Business Insider. White described the pleasure of reuniting on a new problem. Familiarity offered a starting point, while hiring beyond that network brought additional perspectives.

The early commercial work involved his network, pilots, customer feedback and referrals. White’s account of those beginnings emphasizes giving the first customers something useful enough to recommend. For a technical founder, that meant learning which parts of the product people valued, then continuing to improve them.

By June 2021, ChartHop reported more than 130 corporate customers and announced a $35 million Series B led by Andreessen Horowitz. White said the team had grown from ten to more than 70 over the preceding year. His new company was acquiring experience with its own subject matter.

A $20 million Series C led by Cox Enterprises followed in January 2023. That year, ChartHop ranked No. 50 on the Inc. 5000. Those milestones mark the distance between a founder’s troublesome spreadsheet and a business that other organizations were paying to use.

The people between the boxes

White can make the case for an organizational chart sound surprisingly social. In one example he has used, finance believes three open positions are approved while recruiting believes eight are approved. Put those views together and an actual conversation can begin. Until then, each department can proceed with admirable confidence toward a different destination.

He argues that absent information invites people to supply explanations of their own. Providing context gives them something firmer to work with. His ambition for a broadly available organizational chart followed the same logic: colleagues should have an accessible way to see who is in the company and how they fit together.

“I think tech is only interesting insofar as it actually helps people.”

Ian White

That interest extends to the managers who sit between senior leadership and daily execution. In his writing, White has argued for investing in their training, communication skills and access to resources. They translate intentions into work, resolve competing demands, and help employees pursue their professional goals.

His argument has a practical consequence for software design. Useful information needs to reach the people making those everyday decisions. A manager trying to develop someone’s career or plan a team needs context while the decision is being made. A report arriving later may be beautifully formatted and thoroughly beside the point.

For someone joining a company, that context has an immediate use. A name becomes a colleague with a particular responsibility. A reporting line explains where a question can go. For a manager, the same picture can help make a proposed hire understandable to another department. These are small acts of orientation, repeated across a working week. White has chosen to spend a substantial part of his career making them easier.

White also treats communication as work that requires attention in its own right. A plan has to be understood by the people expected to carry it out. It is easy to hear why his theater education remains part of his account of becoming a leader. The audience has to follow what is happening.

A plan that can survive Tuesday

In a public demonstration of scenario planning, White described the process he had disliked: pulling data out of HR and finance systems, arranging it across spreadsheets, and asking leaders to collaborate while the company continued changing underneath them. The proposed future and the actual present could drift apart.

His demonstration moved through a different sequence. A leader could work privately on a proposed organization, change roles and reporting relationships, inspect the costs, share the proposal, and submit it for approval. Approved changes could then flow onward into connected systems. The details matter because a plan has consequences beyond the diagram.

He has described actionable data as accurate, accessible and applicable. The third requirement is especially revealing. Information has to bear on the decision someone actually faces. A colorful chart can earn a place in a presentation; relevant information can change what happens after the presentation ends.

In practice, that means comparing possible futures while keeping track of the present. A hiring decision affects cost, management responsibilities and recruiting work. Putting those relationships in view helps colleagues discuss the same proposal, with its tradeoffs still attached.

What happens after the dashboard?

By 2026, White was talking about AI helping teams move from analysis into action. The examples were ordinary office work: collecting missing information, following up on documents, cleaning records and helping with onboarding. His attention remained on the recurring tasks that consume the time available for decisions.

He also emphasized permissions. Information about an organization includes material different people are entitled to see. As software takes a more active role, those boundaries have to travel with the data. The ambition to make a company understandable comes with a responsibility to control access carefully.

There are product boundaries as well. ChartHop works with applicant tracking partners such as Greenhouse and Ashby rather than trying to build the candidate experience itself. White’s test is whether a capability strengthens the shared model at the center of the product.

He still leads the business and its underlying architecture. The combination puts him close to both the promise and the machinery needed to deliver it. Years after the first spreadsheet frustration, his question remains pleasingly concrete: can the people running a company see what is happening inside it, soon enough to do something useful?