Welcome to Episode 2 of The Boston Product Podcast, hosted by Kaitlyn Kirkaldy and Adam Piel… and powered by VentureFizz!
If you missed Episode 1 – click here to listen to our interview with Emily Levada, VP Consumer Product at Babylist.
Our latest interview features Lou Orfanos, a quintessential Boston product leader who helped scale iconic local tech companies like LogMeIn (join.me), Localytics, HubSpot, and Toast. Now, Lou is taking everything he’s learned from running massive product portfolios into the CEO seat at Copley, an AI operating system for demand engineering.
Lou shares candid stories about what happens when engineering speed is no longer the bottleneck, why usability and customer outcomes remain non-negotiable “product truths,” and what it really takes to transition from product leadership to CEO.
Key Topics Covered:
- The Product Scale Playbook: Lessons from join.me’s frictionless product-led growth, HubSpot’s autonomous multi-product platform, and Toast’s relentless obsession with customer TAM.
- From Product Leader to CEO: Making the move to CEO at Copley and why commercial/go-to-market fluency is the key to breaking past the Senior PM ceiling.
- How AI Changes the MVP: When AI lets teams build entire products in days, functionality isn’t the bottleneck anymore… interaction design and usability are.
- Upmarket & Downmarket Lessons: Candid stories from building products at HubSpot, Toast, and why distribution matters just as much as product vision.
- Rapid Fire: Lou’s take on the Boston tech scene, lecturing at HBS, and his current favorite product.
Transcript
Kaitlyn Kirkaldy Thank you so much for joining us today, Lou. We are so excited to dive in. We’ve got so much that we want to cover with you, so we are going to just go for it right away.
You have had what feels like a quintessentially Boston product career. You’ve gone heavily into product-led growth, you evolved HubSpot into a multi-product portfolio, you expanded into hardware at Toast, and you had time at LogMeIn and Localytics—all these classic Boston places. We wanted to kick things off by having you tell us a little bit about that progression, what it was like to do product at those companies, and share some of your favorite memories and learnings from all of that time—narrowing it down to just a few for us.
Lou Orfanos I’m excited to do that. It’s going to be a trip down memory lane. I hadn’t really thought about this Boston-centric journey until recently when I joined Copley. I looked back at it, and not only are they all in Boston, but they were all founder-led, founder-driven companies. Some of them are super iconic, and at some of them we just did okay, but I’m really happy with where we ended up.
Kaitlyn Kirkaldy Let’s start with LogMeIn. Talk to us a little bit about that experience. If you’ve been in Boston tech, that’s a company you’ve heard of. Maybe it doesn’t have the razzle-dazzle of a Toast or HubSpot brand name anymore, but it’s still a company that many of us looked to and knew a lot about. Talk to us about product there. What was that like?
Lou Orfanos LogMeIn in its heyday was the pillar company in Boston. It was one of the first freemium pioneers, and it was an incredible experience. They did a really magical job of taking this platform they had built around screen connectivity. If you’ve been working for a while, you probably remember the first time you could screen share—it was a magical experience.
LogMeIn had this platform called the Gravity Platform that enabled screen sharing. The first use cases were built around customer support and remote support. You would have an issue, give a code, and the support person could see your screen and help you. They built up a pretty good business doing that. I joined right as it became a public company, having built its bones on that remote support use case.
Then we came up with this idea that you could probably use this for sales, marketing, or collaboration. There was a moment where somebody in the company—not me—figured out that we could do this screen sharing thing really instantly and make it a general, all-purpose use case. That led to a product called join.me. If you’re over 30, you probably used join.me at some point. Did either of you ever use join.me back in the day?
Kaitlyn Kirkaldy Yes, briefly.
Adam Piel I did, yeah. Weren’t there fun little meeting room names you could pick? We would pick these silly names and use them.
Lou Orfanos Yes, you could pick your room! It had really cool creative behind it and was a very fun brand. The website was simply join.me—I remember we had to buy the .me domain from the country of Montenegro at one point.
join.me started taking off quickly because teams realized they could just send a link and instantly share their screen. There was no sign-up and no friction. We grew it to millions of monthly active users, and we layered in audio, recording, and bigger features so a sales team, a marketing team, or internal collaborators could use it. That was the beginning of it.
Kaitlyn Kirkaldy You touched on something we wanted to ask you about: being an early pioneer in the product-led growth space. How did you scale freemium and expand from that single use case to become more generic? Talk to us about how the team approached that product-led growth path.
Lou Orfanos When I first joined, the team had done a great job of building a free trial flow. You’d come in, start a trial, the sales team would follow up with you instantly, onboarding was locked down, and you got to value very quickly—because screen sharing is a use case whose value you feel right away.
With join.me, we collapsed that friction even further. We did no sign-up—you could just go to the website, hit “start a meeting,” and run whatever meeting you wanted instantly. That opened up the top of the funnel in a crazy way. Users became advocates passing the tool along to others, and growth compounded. I remember refreshing the free usage dashboard and seeing spikes—suddenly there were 20-person meetings happening hundreds, then thousands of times a day.
The challenge became: how do we harness this to turn it into an actual business without introducing too much friction at the top of the funnel? We started experimenting with feature gating—deciding that screen recording or session recording could be something we charged for. Over time, we built this into a real business while protecting the integrity of that zero-touch, frictionless start. Once someone had a real recurring use case, it was clear they’d pay for it. The team was maniacal about watching that funnel, and it was a great early lesson on funnel optimization.
The big problem came when we tried to grow the business into its next phase, right as video conferencing was taking off—which leads to a major lesson on building products and thinking about their future.
Kaitlyn Kirkaldy What is that big lesson? We all really want to hear it.
Lou Orfanos The story of join.me is incredible: it was growing rapidly and was super popular, but an emerging wave of video conferencing technology was coming. This was maybe 12 to 15 years ago. A couple of new companies were starting out—Zoom was one of them. In fact, we called them to see if they wanted to partner or do something together, and they were a little skittish and didn’t really chat with us. So we decided to build video ourselves.
The big lesson for me is: do you have a durable technology anchor underpinning your product? At the time, we had a screen-sharing capability underpinning the entire system, and we were building use cases on top of that. When we tried to shoehorn a video conferencing use case onto it, video wasn’t core to us. Literally, when you were sharing your screen in join.me, adding a video feed was an afterthought. The first time you used Zoom, the very first thing it did was put video front and center as the main element of the screen.
From both a culture and architecture standpoint, we were not video-first—it wasn’t our underlying infrastructure or our primary design thinking. Ultimately, a video-first tool like Zoom ended up winning. It’s a lesson I’ll never forget about thinking through how durable your core anchor is and whether you can pivot to the next technology wave.
Kaitlyn Kirkaldy As Adam and I have talked about many times, you learn more from failures than successes, and people need to talk about them more openly. Thank you for sharing that lesson. It ties right into what we wanted to talk about next: HubSpot. Talk about durability! You must have carried some of those lessons from join.me and Zoom into your time at HubSpot, which has had tremendous staying power and continues to evolve. Talk to us about that.
Lou Orfanos HubSpot is an incredible place. When I think about the product culture there—at least during my time—it felt magical for a few reasons. First, everyone was deeply aligned on our product-building philosophy: you have a powerful underlying platform centered around the customer record and CRM, and everything we build on top of that should be improved and accelerated by living on that platform.
Second, the leadership team—specifically Brian Halligan—gave us a far-out vision of the future. He had an excellent ability to see around corners and understand market shifts. He would set the direction: “We want to build the best-in-class, all-in-one platform, do right by our customers, and help them grow.” Everything else was up to autonomous teams to run at.
Brian would come to the monthly “science fairs” we ran and leave saying, “Holy shiitake, this is the most value I’ve ever seen.” He was genuinely surprised by all the things being built because he had created an infrastructure where people could run free, be autonomous, and instinctively know where to find customer value. Because HubSpot had built deep trust with its customer base over time, customers were willing to try new products from us. For example, when conversation intelligence tools like Gong emerged, we realized that functionality would work nicely inside HubSpot, so we built a native version—and customers who didn’t need a standalone tool bought it and loved it. The enduring lesson from HubSpot’s culture is the power of providing high context to your team and then letting them run.
Kaitlyn Kirkaldy You’re teeing up these transitions seamlessly. Next, we want to talk about leadership ethos and your transition from product leader to CEO. I’ll kick it over to Adam.
Adam Piel In one of your LinkedIn videos, you called this a moment of “person-moment fit.” For listeners who don’t know, you recently became the CEO of a seed-stage startup, Copley. What was the journey like to that seat? Did you always feel you were heading toward becoming a CEO, and what has surprised you most so far?
Lou Orfanos When you’re ambitious in product, you often think of yourself as the “CEO of your product” and assume you can be a company CEO someday—unfortunately thinking you know everything, which quickly gets humbled. However, the best part of being a product leader is sitting near the center of the company with visibility into go-to-market, commercial strategy, and unit economics. In my head, I felt those experiences were building toward a CEO role—it was just a question of when I was ready to jump.
After HubSpot, I spent four and a half years at Toast. While HubSpot was defined by autonomy and platform-centricity, Toast’s magic was following customers in the market maniacally. When I left Toast, I wrote in my farewell note that I knew the restaurant TAM deeper than almost anyone—how many pizza places exist in the US, how they’re distributed, what tech they use, their pain points, and their payment volume tiers. Everyone at Toast understood the TAM to an extraordinary depth, which added another layer of commercial excellence to my toolkit.
Bringing that to Copley—this wasn’t me joining a random seed-stage startup. One of the co-founders, Sean Marshall, was my college roommate and had an incredible run at Klaviyo. We’d been looking for a way to work together, so when he and his co-founders, Dave and Mike, started Copley a couple of years ago, I began advising them. Recently, they unlocked massive value for B2B companies. When you’re selling to marketing teams, you have to blend great product with great storytelling—which is the exact intersection I loved most in my recent roles. It was my college roommate, a Boston-based company, early traction, and the exact blend of product and commercial execution I love. I figured if I was ever going to take the leap, now was the time.
Adam Piel You’ve mentioned the commercial and go-to-market side of the product role several times. Many PMs progress steadily until they hit a career ceiling around Senior PM for a decade or more, often because commercial fluency is a blind spot. Could you speak to how PMs can build that muscle?
Lou Orfanos For a long time, I thought I was very commercial—until I got to HubSpot and saw how rigorously they messaged, positioned, and brought products to market. Then I went to Toast and saw an entirely new level of rigor around who to sell to, TAM sizing, ACV mechanics, retention, and whether an investment was commercially viable.
My advice to PMs on building commercial fluency comes down to two things:
- Have a rich point of view on your product’s market fit—without blinders: You need to be the expert on how your product lands in the market. Where PMs sometimes break is in multi-product companies when they pitch their roadmap with tunnel vision, ignoring competing company priorities or how their product affects the broader customer ecosystem. The best PMs understand how their product fits into the whole business.
- Go figure it out yourself: At Toast, a PM felt his product was plateauing among dozens of offerings. He went and listened to every single Chorus sales call mentioning his product, realized sales reps were misrepresenting how to pitch it, built a brand-new messaging and positioning guide, and jumped on calls with every rep. He brute-forced his product attach rate to double over time.
When you combine broad business context with the grit to go fix commercial bottlenecks yourself, people stop viewing you as just a feature builder and start seeing you as a business leader.
Adam Piel Let’s segue into Copley specifically. I’ve seen the term “demand engineering,” and if I’m honest, I don’t fully understand what it means yet. Can you walk us through it?
Lou Orfanos Demand engineering is an approach where demand-gen teams become maniacal about the creative they generate and test. Most marketing teams do basic A/B testing on paid ads—testing a headline, color, or offer during a single campaign. They might find a winning ad, feel good about it, and move on to the next campaign—but they lose the underlying learnings about why that creative worked.
Teams lack the stamina and infrastructure to experiment continuously at scale. Demand engineering is about identifying the underlying traits that make ads perform—and using those insights to continuously generate and test new variations until you hit optimal performance. Copley provides an operating system for demand generation: you visualize your programs, generate concepts and themes on rails, and continuously iterate through experimentation without getting bogged down by agencies or internal bottlenecks.
Kaitlyn Kirkaldy Is there a recommendation or decision-intelligence component to the platform? Having worked in both product and product marketing, I’ve seen teams struggle to run consistent A/B testing in-house. How does the platform make recommendations?
Lou Orfanos Suppose you launch three ads for a product launch on LinkedIn. Our agent monitors performance and automatically recommends increasing spend on winners, killing losers, and spinning off new variants of the winners.
We unpack thousands of underlying traits from an ad—tone, mood, lighting, urgency, offer structure—to find the exact recipe that resonates with your buyer. When an ad wins, the system generates multiple new permutations carrying those winning traits. It recommends budget shifts, new channels, and new messaging angles—like testing time-savings versus ROI outcomes versus scaling without headcount. Teams can either generate AI assets from scratch or upload curated brand assets for Copley to iterate upon.
Kaitlyn Kirkaldy It sounds like it ungates experimentation for non-technical marketers so they don’t have to pull in engineering or hire an agency. That ties into a broader question everyone in product is wrestling with right now: as AI reshapes how fast we build, how are you thinking about structuring and running product at Copley?
Lou Orfanos I’m still figuring it out, but one thing became crystal clear in my first few weeks: we can build so fast now that functionality is no longer the bottleneck. The team is deeply AI-pilled and ships features almost instantly.
Instead, the biggest bottleneck is now interaction design, taste, and usability—figuring out how to put complex capabilities “on rails.” In a way, it’s hard to build a traditional functional MVP anymore because AI lets you build the whole thing right away. Right now, we’re choosing to build out the full use case to solve the customer’s end-to-end problem, and then working hard to strip back complexity and make it dead simple—applying that frictionless join.me philosophy. To me, the modern MVP isn’t a functionality MVP; it’s a UX MVP.
Kaitlyn Kirkaldy When AI lets you keep polishing and adding features endlessly, how do you decide what is “good enough” to put in front of customers without getting stuck in an endless loop of perfecting?
Lou Orfanos It’s a judgment call, which means you have to stay hands-on. We push builds into a pre-prod environment and use Copley ourselves to market Copley. Because I’m neither an engineer nor a career marketer, I don’t have deep domain workarounds that mask bad UX—and my co-founder Sean approaches it the same way from a sales background. We go in as naive first-time users. If we get confused or can’t immediately figure it out, that’s our BS detector telling us we let the build run too far without simplifying the experience.
Kaitlyn Kirkaldy I love that—drinking your own champagne and maintaining a beginner’s mindset. Beyond Copley itself, what is your product team’s current AI tool stack?
Lou Orfanos We use Copley to run our own ad creation and marketing programs. On the product and engineering side, we use Lovable, some Figma, and Claude Code, alongside multiple models running inside Copley’s own harness. Being a small, early-stage startup is a huge shift from Toast, where I had every enterprise tool and specialist at my disposal. Right now, our stack is scrappy and fluid—whatever the team needs that day to move fast, we test and adopt.
Adam Piel On the organizational level, how do you see AI changing the day-to-day composition of product, design, and engineering teams?
Lou Orfanos Having just moved from a 200+ person PM organization at Toast three months ago to a team of fewer than ten at Copley, I think about this a lot. At scale, you have to balance leaner teams with maintaining high-fidelity reliability when customers run their entire livelihoods on your software.
Over time, I think teams will get smaller, and we’ll see some blurring between product and design roles. Because engineers and agents can generate massive functionality quickly, someone has to fiercely guard how humans actually interact with the product. Right now, my biggest anxiety isn’t whether we can build features—it’s ensuring our product is infinitely usable rather than just infinitely capable.
Adam Piel Especially when selling to marketers, who tend to have a very high visual and UX bar.
Lou Orfanos Exactly. And they’re power users of native tools like LinkedIn Ads and Meta Ads. To pull them out of their comfort zone, the product has to deliver a 10x better experience—letting them build, test, and scale across channels in one place with complete confidence.
Kaitlyn Kirkaldy What stands out in everything you’re saying is that even as tooling transforms, you keep anchoring back to timeless product truths: customer intimacy, commercial alignment, and usability.
Lou Orfanos One major truth that has become much easier to execute today is measuring product strictly by customer outcomes. Back in the LogMeIn days, we mostly tracked product usage. At HubSpot, our mission was helping organizations grow, though connecting daily product work directly to customer revenue growth was hard. At Toast, it became much clearer: are we increasing restaurant payment volume and bringing more diners in the door?
Now at Copley, our North Star is simple: are we measurably growing our customer’s top of funnel compared to what they did before? If we don’t beat their baseline, why would they use us? Because systems and data are so much better connected today, holding product teams accountable to tangible customer outcomes—not just output—is easier than ever.
Adam Piel It’s grounding to hear that even when day-to-day workflows shift dramatically, those core product fundamentals remain constant.
Lou Orfanos When I first saw the Copley team building features in days that used to take months, I thought, “This is incredible, we can ship tomorrow.” Then I tested it in pre-prod and realized, “Wait—I can’t even tell how to use this.” That was my wake-up call that you can’t throw away 20 years of product fundamentals. Teaching an AI agent to build something that feels intuitive and human still requires deep product judgment.
Kaitlyn Kirkaldy That’s a great touchstone. Since this is our second episode, we’re keeping our rapid-fire round going—I’ll hand it over to Adam.
Rapid-Fire Round
Adam Piel You’ve had a quintessential Boston tech career. What is your honest take on the Boston tech scene—its strengths, its vibe, and where it needs to grow?
Lou Orfanos We have an amazing community and extraordinary academic and technical talent here, though historically Boston has had a more conservative risk appetite—something I hear from both investors and builders. We’re starting to break out of that, especially with the momentum around applied AI and groups like the Mass AI Coalition. You don’t have to compete directly with frontier AI labs in San Francisco to build iconic companies here. There is capital, talent, and support in Boston, and the only way to shed the conservative stigma is to go out and build the next wave of pillar companies right here—which is exactly what we’re trying to do with Copley.
Adam Piel What’s your take on in-office vs. remote work right now?
Lou Orfanos At Toast, most of my team was distributed, so I had a great remote rhythm and went into the office a couple of days a week. At Copley, because we’re early and building momentum, I love being together as much as possible. Our engineers are in the office every day because that’s where they focus best, and I aim for at least two to three days a week in person while balancing family life.
Adam Piel You spent several years as a guest lecturer at Harvard Business School. What aspects of product management can actually be taught in a classroom, and what can only be learned in the trenches?
Lou Orfanos Purely academic product management is almost impossible to teach in a classroom. What made Julia Austin and Melissa Perri’s HBS courses work was that every student group was actively launching a real startup. Guest lecturers provided practical building blocks—my sessions focused on identifying the metrics that matter and knowing when to double down, using real funnel mechanics from join.me and HubSpot. Because students applied those lessons immediately to live businesses, it felt practical rather than theoretical.
Adam Piel Can you share a story about a time something fell flat—a product bet or go-to-market move that taught you a lasting lesson?
Lou Orfanos Moving upmarket and moving downmarket both taught me hard lessons. At HubSpot and Toast, we had moments where we tried to push into larger enterprise accounts prematurely. You realize quickly that enterprise CIOs don’t buy purely on product vision or consumer-grade UX—they buy on risk mitigation and specific enterprise requirements. We got a little ahead of ourselves a couple of times and took some losses.
Conversely, at Localytics, our core business served massive enterprise brands like ESPN and The Weather Channel. Early on, we tried to launch a downmarket self-serve product for startups. Even though the core tech worked, our distribution model was completely wrong for startups—we would have had to build an entirely new community and acquisition engine from scratch, so we eventually shut it down and doubled down on enterprise. The lesson: whenever you shift your ICP up or down, distribution and buyer psychology matter just as much as the core product.
Kaitlyn Kirkaldy Last question: what is one product—physical or software—that you’ve been loving recently?
Lou Orfanos I’ve been loving Wispr Flow. On the Mac, I use it constantly to dictate messages and documents—it’s dramatically better and more seamless than standard voice recognition. (The mobile experience still has some Apple/Siri friction to work through, but on desktop it’s a game-changer.)
Kaitlyn Kirkaldy Everyone is raving about Wispr Flow right now! Thank you so much for joining us, Lou—this was a blast, and we loved the energy and insights you brought.
Adam Piel Thank you so much, Lou.
Lou Orfanos Thank you both—that was great.