Most people can name the loud tech founders. The headline makers. The hoodie-wearing disruptors.
Barbara Boothe isn’t one of them.
And that’s exactly why her story is interesting.
Long before startup culture became a brand and decades before venture capital flooded every new idea, Boothe was building a serious software company. She did it in an era when “software startup” wasn’t even a common phrase. There were no accelerators, no pitch decks floating around Twitter, and very few women running tech companies.
Yet she built one anyway.
Her company, Pylon, quietly became one of the most widely used project management systems in large corporations during the 1980s and early 1990s. It solved a real problem businesses were struggling with: managing large, complicated projects with software rather than paper charts and guesswork.
And eventually, that idea became big enough that Computer Associates acquired the company in a deal worth hundreds of millions.
But the money isn’t really the point.
Boothe’s story matters because it shows how real tech companies actually get built—slowly, stubbornly, and often far away from the spotlight.
Before Startups Were Cool
It’s hard to imagine now, but in the late 1970s and early 1980s, the software industry looked very different.
Computers existed, of course. But software wasn’t yet the glamorous engine of the economy. It was still seen as a support tool for hardware.
A lot of companies wrote their own internal programs. The idea that an independent company could build software and sell it broadly was still evolving.
Barbara Boothe stepped into that environment with a pretty straightforward insight.
Large organizations were terrible at managing complex projects.
Think about construction schedules, engineering programs, government projects, or large corporate initiatives. Before modern software, much of that work relied on paper-based planning tools like Gantt charts taped to walls.
If someone changed a deadline, everything had to be recalculated manually.
Now imagine doing that across thousands of tasks.
Boothe saw that software could do this far better.
So she founded Pylon, a company focused on project management software designed for large enterprises.
It sounds obvious now. At the time, it wasn’t.
The Problem Pylon Solved
To understand why Pylon worked, picture a big company in the 1980s.
Let’s say it’s an aerospace firm building a new aircraft system. Hundreds of engineers are involved. Thousands of tasks. Deadlines stacked on deadlines.
One delayed component can ripple through the entire project.
Before software tools, managers often relied on:
- giant printed charts
- manual scheduling updates
- endless coordination meetings
It was messy. Slow. And mistakes were common.
Pylon brought those planning systems onto computers.
Instead of recalculating schedules by hand, managers could adjust tasks digitally and see the entire project timeline update automatically.
For today’s reader, that might sound like basic project management software. Tools like Asana, Monday, or Microsoft Project do similar things.
But Boothe’s company was doing it decades earlier, on far more limited hardware.
Computers weren’t fast. Interfaces weren’t friendly. Distribution wasn’t easy.
Yet large organizations started adopting Pylon because the efficiency gains were obvious.
When a tool saves a company months of delays on a multimillion-dollar project, word spreads quickly.
Building a Real Business, Not Just a Product
Here’s something interesting about Boothe’s path.
She didn’t build Pylon like a modern startup chasing hype.
She built it like a business.
Revenue mattered early. Customers mattered more than publicity. The company grew because organizations actually paid for the software and depended on it.
That’s a different mindset than a lot of tech founders today.
Imagine a sales conversation in the early days.
A project manager at a manufacturing company might say something like:
“We’ve been planning this project on paper for years. Why should we trust software to run it?”
Boothe and her team had to prove the value in practical terms. Faster planning. Fewer scheduling errors. Clear visibility across complex projects.
Not buzzwords.
Just results.
That approach helped Pylon gain traction in industries where reliability mattered more than novelty.
A Female Founder in an Unfriendly Era
There’s another dimension to Boothe’s story that’s easy to overlook today.
She was building a tech company at a time when very few women were founders in the software industry.
The tech world of the 1980s was heavily male-dominated. Boardrooms, engineering teams, and investor networks were overwhelmingly male.
Boothe navigated that environment while running a growing enterprise software company.
What’s notable is how little drama surrounds her story.
She wasn’t trying to become a symbol or a spokesperson for anything. She was focused on building software and serving customers.
Sometimes the most effective way to break barriers is simply to succeed.
And that’s exactly what she did.
The Growth of Pylon
As Pylon expanded, it became known as one of the more powerful project management systems available for large organizations.
Companies weren’t buying it because it looked modern or trendy.
They bought it because it worked.
The software helped coordinate large-scale programs across departments and teams. In industries where delays could cost millions, that capability mattered a lot.
Pylon began appearing inside major corporations and government projects.
And once enterprise software gets embedded in a large organization, it tends to stay there.
Switching systems is painful. Training teams takes time. Data migrations are complicated.
So successful enterprise software companies often grow through long-term relationships rather than explosive viral adoption.
Boothe understood that dynamic early.
Instead of chasing every possible customer, Pylon focused on organizations that truly needed complex project planning tools.
It was a classic enterprise software strategy before the term was widely used.
The Computer Associates Acquisition
Eventually, the company reached a point many founders recognize.
It had strong products, an established customer base, and a valuable position in the enterprise software ecosystem.
That attracted attention from larger software companies.
Computer Associates (CA), one of the major enterprise software firms of the time, acquired Pylon in the early 1990s in a deal reportedly worth hundreds of millions of dollars.
For Boothe, it was the culmination of years of building.
For CA, it meant adding proven project management software to its portfolio.
Acquisitions like this are common today. Big tech companies regularly buy smaller software firms.
Back then, these deals were still shaping the structure of the modern software industry.
Pylon’s success helped demonstrate that specialized enterprise software companies could become extremely valuable.
Life After the Exit
Some founders disappear after selling their company.
Barbara Boothe took a different route.
She stayed involved in the broader tech and entrepreneurial community, particularly in Utah, which has grown into a surprisingly strong technology hub.
Utah’s “Silicon Slopes” region now hosts hundreds of startups and technology firms. But decades ago, that ecosystem was much smaller.
Experienced entrepreneurs like Boothe played a role in helping it grow.
Former founders often become mentors, advisors, or investors. They help younger entrepreneurs avoid mistakes they’ve already lived through.
It’s the quiet recycling of experience that keeps startup ecosystems alive.
Imagine a young founder walking into a meeting with an idea for a software platform. They’re worried about pricing or product-market fit.
Someone like Boothe can offer something more valuable than theory: perspective.
She’s seen what happens when software companies scale.
She’s seen what happens when they don’t.
That kind of experience isn’t easy to replicate.
Why Boothe’s Story Still Matters
In today’s tech landscape, founders are often measured by visibility.
How big their Twitter following is. How viral their launch was. How loudly they talk about disruption.
Barbara Boothe’s career suggests a different model.
Solve a real problem. Build reliable software. Grow a business customers depend on.
Then keep improving it.
It’s not flashy, but it works.
There’s also something refreshing about founders who built companies before the startup playbook existed.
They didn’t have step-by-step guides on product-market fit. No endless podcasts about growth hacking. No templated pitch decks.
They figured things out as they went.
And that often produces companies that are more grounded in real customer needs.
The Kind of Founder History Sometimes Forgets
Tech history tends to spotlight a small set of names.
Gates. Jobs. Bezos. Musk.
But the industry wasn’t built by just a handful of famous founders.
It was built by thousands of entrepreneurs solving specific problems in specific industries.
Project management. Accounting software. database tools. networking infrastructure.
Barbara Boothe belongs to that group.
Her company helped organizations manage complex work long before modern SaaS tools existed. In many ways, Pylon was part of the early foundation of the enterprise software ecosystem we rely on today.
And she did it without chasing attention.
Just solid software and a clear understanding of what customers actually needed.
The Takeaway
Boothe’s story carries a simple lesson that still applies today.
You don’t have to invent an entirely new category to build a meaningful tech company.
Sometimes the opportunity is right in front of you—a messy process, a slow system, a problem businesses deal with every day.
Make it easier.
Make it faster.
Make it reliable.
That’s exactly what Barbara Boothe did with Pylon.
And decades later, that straightforward idea still captures something important about entrepreneurship: the most valuable companies often start by quietly fixing problems everyone else has learned to live with. 🚀
