AGIVC
Back to Blog

From Bootstrap to Venture-Backed: Lessons from a Two-Time Founder Who Started at 47

By AGIVC Team

Chris Bartholomew spent 12 years at Solace, a messaging company. Good job. Reasonable hours. Steady paycheck. Then, in his late 40s, he quit to start Kesque, a Pulsar-based streaming platform. No salary. No venture backing. Just an idea and personal savings.

Five years later, he's done it twice. He bootstrapped Kesque, sold it to DataStax, worked there for three years, and left to start Vectorize.io when the AI moment hit. This time with venture capital.

The two experiences couldn't be more different. And the lessons from both are worth understanding if you're thinking about starting something.

Starting at 47

Most founder stories start with someone in their 20s pulling all-nighters. Chris took a different approach.

Before starting Vectorize with his co-founder, he laid down the ground rules: "It's a marathon, not a sprint. I'm too old to be doing all-nighters. I can work nine hours during the day, but I still need seven or eight hours of sleep. And I have to work out."

This isn't about being soft. It's about being realistic. "You can't think clearly when you're tired," he says. He structures his day around this. Morning for creative work. Evenings for maintenance tasks, DevOps, rotating keys. "By the end of the day, I don't have a lot of brain capacity left. Usually around 9 or 10 p.m., that's when I write code I have to delete the next morning."

At Kesque, he learned this the hard way. The product was a messaging bus, which sits in a critical spot in the technology stack. If it goes down, everything fails. He was on pager duty most of the time. "I would get paged at 3 a.m., wake up, shake off the cobwebs, try to fix a problem. Even if it takes half an hour, you're too wired up. Can't go back to sleep." Lots of nights with only a few hours of sleep.

He wanted to avoid that the second time around.

Learning Everything the Hard Way

When Chris started Kesque, he didn't know how to incorporate a company. He asked around at Invest Ottawa's incubator program. Someone mentioned Ownr.co. He looked it up.

That was the pattern for everything. "Kesque was a huge learning curve. Not technically. It was about everything else. How to set up a business. Banking. Finance. Legal. Insurance. Payroll. Accounting. All the stuff you have to learn."

He never consulted a lawyer. "Everything was a template I downloaded. Paid like $125 for a service." When he sent contracts to customers, he knew they had legal counsel on their team. "They can do due diligence on your documents for you, for free essentially."

For incorporation, he used Ownr.co twice now. "It takes like 20 minutes to incorporate. Compared to a lawyer, which would be a couple thousand dollars just to do the same thing." The Silicon Valley lawyers Vectorize uses now are significantly more expensive.

The YC Interview

With Kesque gaining traction in the Pulsar space, Chris applied to Y Combinator. "I'm an outsider. Never been a founder before. Don't live in the valley. Don't have any connections there. YC is ideal for that kind of founder because anyone can apply."

He had founder-market fit. A decade-plus in the messaging space. Technical. And everyone knew about Confluent making money on Kafka. He got through the initial rounds, flew to Mountain View for the in-person interview.

"Very intimidating and challenging. Eight people grilling you. I think it was eight minutes, not even ten. They asked all kinds of hard questions that at the time I wasn't prepared to answer." He didn't get in.

But going that far was a vote of confidence. "I really applied on a whim. Never thought I'd even get anywhere. The fact that I got that far was encouraging."

He kept going.

When COVID Hit

Late 2019. Kesque was the only Pulsar cloud service in town. A competitor called Streamlio had been acquired, and they shut down their beta service. Inbound started flowing.

"I was getting consulting contracts. One in Austria. They were going to fly me out. It was starting to snowball. I remember looking at these growth projections. Might be profitable by the end of the year. Pay myself a modest salary."

Then COVID hit.

"There was a bit of a lag. Nothing really changed for a period. Then everyone stopped spending money." The Austria project got canceled. "A lot of stuff started falling off. The inbound dropped off a cliff. No one wanted to take technology risks, and Pulsar was a relatively new technology."

He was running out of personal funds. "I wasn't thinking in terms of runway. I had some personal savings to pay my bills. Was donating a little bit of money to keep the company going. But it wasn't much."

His adviser told him about venture debt. "Everyone says you should never take it, but I didn't have an option." He talked to Business Development Bank of Canada, got a term sheet. He'd have to put his house on the line. "I'm basically risking my mortgage."

Then the CTO of DataStax reached out through the Pulsar Slack community.

The Acquisition

DataStax wanted to expand beyond Cassandra into streaming. They were eyeing Pulsar, and Chris was one of the only vendors in the space. Talks started. An acquisition offer came.

"I got lucky. At the time when things were looking a little bit bleak, I got an offer from a strategic acquirer."

He never took the venture debt. BDC was understanding. "I said I just got the term sheet and then I get this call. They were like, okay, fine."

In hindsight, the venture debt might have worked out. 2021 brought the tech boom. "Share prices went through the roof. Shopify went nuts. You could get 100x revenue for almost any company. I certainly would have been trying to raise in 2021."

But he took the acquisition.

The Painful Transition

Going from founder to employee at DataStax was tough.

"Challenge one: they're a database company. They understood databases. They didn't understand anything about streaming. I spent a lot of time just trying to explain what it was."

And then: "Everything moves so slowly here."

Not that DataStax was particularly slow. It's just that compared to founder speed, everything moves slowly. "I solo built the first version of Kesque. You realize how much time you spend when you have a team. Explaining what you mean. Debating the way to do something. When you're coding by yourself, all of this happens in your own head. Very quickly. You don't have to explain anything to yourself."

The team came from a database background. "They don't understand what I'm talking about because I'm speaking in different technology terms. I need to do a marketing post and I have to explain to the marketing team what streaming is. They're used to selling databases."

He was working as many hours, if not more, than before. But not building the product. Building alignment.

The team went from two people to fifteen. "Great to have that much of a team, but now you have management overhead. Growing pains."

Starting Again

Chris always wanted to try again. "I learned so much the first time. I can't make any more mistakes than I made the first time."

Then ChatGPT happened.

"It's one of those things where everyone could see a technology shift. If you don't take advantage of that and you don't try something, you're going to regret it." He references Bezos's regret minimization framework. "At 80 years old, why didn't I try?"

He also wanted to try venture-backed. "It's different than bootstrapped. In a lot of ways it's easier. In some ways it's harder."

The timing was right. Investors in Silicon Valley were keen on AI startups. Chris and his co-founder had both worked on streaming and vector databases at DataStax. Founder-market fit. RAG was hot.

They raised on a priced round.

Bootstrap vs Venture-Backed

Having done both, Chris sees the trade-offs clearly.

Bootstrapped advantages:

  • You control everything
  • Decisions happen instantly (in your own head)
  • No implied valuation to live up to
  • Survival pressure keeps you focused

Bootstrapped disadvantages:

  • No salary (Chris went without)
  • Limited resources to hire
  • Personal finances at risk
  • Slower growth potential

Venture-backed advantages:

  • Salary from day one
  • Resources to build a team
  • Runway gives you time
  • Credibility with customers

Venture-backed disadvantages:

  • Implied valuation creates pressure
  • You need to hit that number or you'll never raise again
  • Expenses add up quickly (cloud bills, team costs)
  • Market conditions affect your ability to raise

"When you're bootstrapped, it's more like the business is going to die immediately. You feel that pressure. When you're venture-backed, you have runway, you have flexibility. But as soon as you take venture money, you get an implied valuation. You're under pressure to get to that valuation in real life, or you're never going to raise money again."

The pressure is different, not less.

The Value of a Co-Founder

At Kesque, Chris was alone for the first eight or nine months. At Vectorize, he has Chris as a co-founder from day one.

"Having a co-founder to bounce ideas off, to work through things. At Kesque, we were both engineers. Now my co-founder has sales experience, sales engineering, product management. Different perspectives."

They've worked together for five years, starting at DataStax. They know each other's quirks. "Not a lot of drama. Kind of figured each other out."

They meet in person every couple months. Chicago, Tampa, San Francisco. "We disagree, sometimes we strongly disagree. But we can both step back and talk it out."

This matters to investors. "One of the key reasons companies fail is founder breakup. That's an important dynamic to suss out."

Bring Your Own Cloud

Vectorize's differentiator is what Chris calls "bring your own cloud." They deploy the data processing software in the customer's VPC and manage it remotely.

The model is simple. "I say to the customer: create a Kubernetes cluster in your cloud. Install this Teleport Helm chart. Here's a key. Now I can SSH into your Kubernetes cluster. That's all you need to do."

If they ever want to cut access, they just uninstall Teleport. No keys needed. No cloud access required.

"From a DevOps perspective, I cannot tell whether I'm in my own cloud or the customer's cluster. They all look exactly the same. I can take the exact same scripts, exact same processes, and just move them everywhere."

For highly regulated industries, this matters. And Chris has done it dozens of times across Kesque and DataStax.

The Real Risk

At the end of the conversation, Chris shared something that stuck with me.

"When I first quit my job to become an entrepreneur, I was definitely afraid of not having a salary. That security of having a job. I was so used to getting a regular paycheck for 20 years."

Then, six months into being an entrepreneur: "What stressed me out was going back to having a real job. That's the thing I didn't want to do."

That's the real risk of entrepreneurship. Not failure. The risk is that you'll never want to go back to being an employee again.

Chris did go back, for three years at DataStax. "But not for long."

Now he's building Vectorize, aiming for a Series A. If you have the opportunity to try entrepreneurship, no matter where you are in your career, he says try it. "Even if you don't succeed, and the odds are low, you'll become a better person. You'll have more knowledge. You'll be able to take your career farther."

Just be prepared: you might not want to go back.