The Integrate Intelligently Podcast, Ep.2: The Growth of AI in Data Entry Automation and Beyond

Relentless Reinvention: Why Continuous Improvement Is Our Favorite Value (Episode 2)
The Integrate Intelligently Podcast, Episode 2 — with Jeff Bickler and Scott Bickler (CADTALK)

Introduction and Recap
Jeff: Welcome back to the second episode of The Integrate Intelligently Podcast. I'm Jeff Bickler, your host, joined again by my brother and CEO of CADTALK, Scott Bickler. Great sharing the mic with you again.

Scott: The first one was a lot of fun — looking forward to this one too. We're recording this during Fourth of July week, so it's hot outside, but we're safely in the air conditioning.

Jeff: Last time, we talked about our tagline, Integrate Intelligently — I really enjoyed that conversation, both from a software angle and how it shows up in our partnerships. Today, I wanted to dig into our core values — values I think were really born out of your personality and life experience, and that show up directly in how the company's structured and what we're trying to achieve, both as individuals and with our customers. One of those values is Relentless Reinvention. Before I get your take, let me set up what it means: at CADTALK, Relentless Reinvention centers on continuous improvement — which, coming from your manufacturing background, makes a lot of sense as a foundational value, both personally and professionally. It reflects a culture, and a personality, that's constantly striving to improve, never fully satisfied with where you are individually or where the company stands — because the better we get individually, the better our leaders get, the better our whole team gets. That mindset of perpetual learning and continuous improvement is what drives a better customer experience and helps us overcome challenges. Given your manufacturing background — and I know Japanese manufacturing philosophy leans heavily on continuous improvement as part of industrial engineering — how did you land on Relentless Reinvention specifically? What resonated with you about it?

Scott: It's actually funny — of all the values, this is genuinely my favorite, probably because it's the one I landed on first, with continuous improvement as the real underlying concept. When we built out all the values, I wanted them to be memorable, so we made them alliterative — Integrate Intelligently, Relentless Reinvention, they all share that pattern. But the real substance goes straight back to industrial engineering roots — process engineering, continuous improvement engineering. A lot of manufacturing embraces the concept of kaizen, Japanese for continuous improvement — constantly refining how you do something, always looking for a better way. That improvement is never a one-time event, it's ongoing.

Naturally, whenever I look at a process or a product, I'm less interested in fixing the single issue directly in front of me and more interested in building a better underlying system so the issue simply never recurs. That's just how I'm wired — much more of a systems thinker. The most frustrating thing to me is a problem that keeps resurfacing, and my instinct is always: how do we fix the actual system so it stops happening entirely, rather than just addressing the symptom each time it pops up.

Jeff: So not playing whack-a-mole.

Scott: Exactly — hit it once, it comes back, hit it again, and you never actually get anywhere. I'm always looking backward and asking how we make the underlying system better so that specific problem never recurs. There's a related principle in software development, DRY — don't repeat yourself. If an issue comes up, I want to genuinely squash it at the root so I never have to solve the same problem twice. It's really just my personality applied consistently — always asking how we improve a process a little, every day. Small, 1% improvements, but they compound. Like compounding interest — 1% stacked daily adds up to something genuinely massive over the long haul, and if you think about it that way, you'll be dramatically better a year from now than you are today.

Embracing AI for Continuous Improvement
Jeff: Where do you think that instinct for continuous improvement first showed up — through school, university, your early career — or was it just always there?

Scott: As long as I can remember, honestly. I think it comes down to genuinely not wanting to just do ordinary things — think about the word "extraordinary" itself, it literally requires doing extra, doing things most people simply don't do. To do more, you have to become more — you have to keep learning, keep identifying problems and fixing them, whether that's in yourself, a system, a process, or a product. I call it the growth game — how do you grow faster? From a business standpoint, there's that idea of the "law of the lid" — a company only grows as far as its leader does. So from a company perspective, continuous improvement genuinely has to be baked in. But even younger, I always thought — if I want to do genuinely epic things, things nobody else has done, I have to figure out how to become the kind of person capable of that. That's always appealed to me. I want an extraordinary life — I want to leave everything on the field, not leave anything unexplored. That's just always been my personality.

Jeff: It's interesting — people say we're similar yet different, and I think I had a version of that same drive, but for me the origin was really wanting to be different from everyone else. I just didn't want to do the same thing as everybody around me — no particular reason, just an instinct that doing the expected thing felt boring. So for me, the roots of that same reinvention impulse came from wanting to do something unique rather than typical — it felt better, for whatever reason. But I think the outcome ends up being the same, whether you're intrinsically motivated to improve, or motivated to simply be different.

Scott: Right — and to build on that a bit, without getting too metaphysical: we don't really know much for certain, but we know we have this one life. So why not make it the absolute best version possible — become the fullest version of yourself you're capable of being? I heard a quote once — heaven is meeting the person you could have become, and hell is meeting that same person, having never actually become them. I think about that a lot. How do you become that fullest version of yourself — the person who, when you finally meet them, can honestly say "yes, you did it, you gave it everything." That's a genuinely useful frame for me.

Jeff: You don't really know what you're capable of — you're just always in motion. Nine years in at CADTALK now, and I've personally changed a lot. How has CADTALK itself reinvented over the last decade or more? I think about AI now, ChatGPT — obviously AI can transcribe and summarize this very podcast — how has that broader shift influenced your thinking around Relentless Reinvention specifically?

Focusing on Constraints and Documenting Assumptions
Scott: AI is a massive disruptor — much like the internet was, and I'm old enough now to have watched a few of these disruption cycles play out firsthand. AI is clearly the next one, with real potential to disrupt a lot of industries. Part of Relentless Reinvention is recognizing that if you don't disrupt yourself first, someone else eventually will. You constantly have to look at your own product and ask: how would someone build this without us? What would cause that, and how do we keep providing more value than expected to stay genuinely relevant — because every product trends toward commodity over time, becoming increasingly commonplace. You have to keep reinventing and re-establishing your value in the market.

How do I stay valuable, provide something nobody else can, deliver more value than customers could reasonably expect? The gap between what someone pays and the value they actually receive — you want that gap as wide as possible, and AI has real capability to widen it dramatically, in ways that honestly haven't existed before in history. You can approach that two ways: be afraid of it, worried about some Terminator scenario, or lean into it, genuinely learn it, and figure out how to leverage it to deliver more value. The constant underneath any technology shift is that the ability to provide real value never goes away — AI is simply a tool to get there, but you have to stay genuinely engaged with the tools available, keep reinventing, keep adjusting as things change in real time. That's why we've embraced AI at CADTALK for a while now — the product today functions more like what's called an expert system, a rules-based engine, which is a somewhat lower-level form of AI, but what we're building toward will make that meaningfully more powerful and capable of delivering even more value than it does today.

Jeff: Why does that reinvention matter so much for CADTALK specifically? The product's always worked, always delivered on what we say it does, and we've steadily improved it — but why is reinvention important for something that fundamentally still works the same basic way it did 20 years ago?

Scott: Part of it is exactly that AI capability — but also, some problems genuinely get solved once and stay solved, while others reveal more and more layers over time, like peeling an onion. You solve the first layer — "I just need to move data from here to there" — and then the next layer emerges: "I need to augment that data with real intelligence, understand routing, timing, things a manufacturing engineer would know." Eventually AI can start genuinely predicting those things. You're continuously taking more off an engineer's plate, freeing them up to focus on higher-level, more specific work. Take something like the engineering change process — figuring out how to communicate that effectively is its own layered problem. It really connects to Theory of Constraints — once you resolve one constraint, the bottleneck simply shifts somewhere else, and you have to go address that new constraint. That's why we keep reinventing: the constraint keeps moving, so we have to keep following it to keep delivering real value. What was a genuinely novel capability 20 years ago is table stakes today — customers now just expect it, since plenty of others do it too — so you constantly have to figure out where the next layer of real value actually sits.

The Evolution of CADTALK
Jeff: There's that old saying — nothing new under the sun, that everything's ultimately some reiteration of what came before, every movie some version of an existing hero's journey. Given that, you obviously can't reinvent literally everything every single time — so where's the line? What stays fundamentally consistent — your own ethics, your work ethic — versus what genuinely gets reinvented, in the product or in how we work with customers? How do you avoid falling into shiny-object syndrome, constantly discarding things that were genuinely working just because something new looks interesting?

Scott: Great question, and yes, it's genuinely possible to overextend that philosophy and spread focus too thin, treating everything as perpetually improvable. A good frame here is Theory of Constraints again — if you're going to reinvent something, go directly to wherever the actual constraint sits in the business or process first. There's a great book on this, The Goal — features a character named Herbie, the Boy Scout — built around exactly that idea: locate the actual constraint in the process, and focus your reinvention energy there specifically. Improving something that isn't the actual constraint doesn't meaningfully improve the overall system. In a manufacturing process, I could be excellent at producing individual parts quickly, but if those parts don't come together into a sellable assembly for the customer, I haven't actually solved anything — no shipped product, no revenue. The goal isn't raw part-production speed; it's making the right parts, together, so they assemble into something sellable. So where's the actual constraint — maybe I have a laser cutting parts incredibly fast, but I can't deburr them fast enough. There's the real constraint — deburring — so that's exactly where reinvention effort should go, because fixing that improves the entire process. The hard part is genuinely identifying where the real constraint sits.

Another practice I'd recommend: document your assumptions. I learned this early in my career — people love pointing out that history repeats itself, going in circles. I remember starting the company in the early 2000s, and older folks would say, "we tried that back in the '70s, it'll never work." I'd push back — sure, in one sense it's cyclical, but really it's more like a helix, a spiral. An idea might genuinely have been a bad fit in the '70s, given the technology and conditions at the time — but 25 or 30 years later, with better technology and greater capability, that same idea can become not just feasible, but the best way to solve the problem. Especially now, with AI — constraints that existed 20 years ago when a process was originally designed may simply no longer exist. But if you never documented the original assumptions behind a decision, you're bound to that decision forever, defaulting to "that's just how we've always done it" without ever revisiting why. If you document the specific assumptions behind a decision when you make it, you can always revisit them later and ask: are these assumptions still true? If yes, great, it's still the best approach. If not, maybe there's now a genuinely better process available. That documentation gives you a real framework to keep reinvention deliberate and targeted, rather than reinventing purely for reinvention's sake.

Jeff: Reinvention obviously isn't purely technical, or purely about identifying constraints — it's also about the people, the company itself, since companies are ultimately made of people who change and reinvent themselves too, which in turn reshapes the environment around them. How have you seen CADTALK itself change over nearly 20 years — what's been the biggest shift?

Scott: This is probably true of companies generally, not just ours — there's this idea that companies hit inflection points around employee count and revenue milestones, and what worked at one scale simply stops working at the next. Unfortunately, this happens with people too — someone genuinely excellent when the company was small sometimes doesn't grow fast enough alongside the company as it scales, and that's a genuinely hard dynamic. We sometimes stigmatize this internally — "oh, so-and-so's been here since the beginning" — when honestly, that person might be genuinely happier, and thrive more, at a different, earlier-stage company. For a company to keep growing and reinventing itself, you often have to change your own thinking and your attachment to "how things are done today" — falling in love with the growth itself, rather than falling in love with the current state, and being genuinely okay with that shift.

There are plenty of concrete examples too — I used to personally write all our code. I remember a conversation where I flatly said, "I don't think anyone else will be able to handle this particular part of the codebase" — that was a genuinely limiting belief I held at the time. We ran an experiment instead — properly documenting and teaching it — and it worked, and we were able to spread that knowledge across the team. If I'd kept believing that original limiting assumption, we'd have genuinely stunted our own growth. It really comes down to constantly questioning your own assumptions and figuring out where your limiting beliefs actually are — but applied inward, to yourself, rather than purely to an external process. Same underlying Theory of Constraints framework — just applied to your own personality and beliefs.

Jeff: That's happened to me too, honestly — before CADTALK, I taught Latin for 11 years, and I remember, right before making the switch, genuinely doubting whether I could do anything else at all. You build up these assumptions — "I spent 25 years, from a young age through university and graduate school, building expertise in one specific thing" — and I genuinely wondered whether I could reinvent myself into something completely different. Obviously the answer turned out to be yes, and that became a huge confidence builder. Successfully reinventing yourself, and actually pulling it off, builds real, lasting confidence — "I used to think I couldn't do something, and now I've changed careers entirely," and honestly, even within CADTALK, I've changed roles multiple times since. That personal track record has genuinely built my own confidence that I can take on nearly anything, as long as I focus and stay open to the fact that it'll be genuinely hard at first, I'll make real mistakes, and I won't fully know what I'm doing initially — but if I stick with it, I'll get there.

The Value of Learning Meta Skills
Scott: I think what makes that transition feel scarier than it needs to be is that people conflate the specific skill they spent years building with the broader meta-skills they picked up alongside it — how to learn effectively, how to study, how much sustained effort something genuinely requires. Those meta-skills fully carry over into something new, even when the specific subject matter doesn't. So people assume switching means starting completely from zero, spending another ten years to reach the same level — but actually, because you're not relearning those underlying meta-skills, you get to a comparable level two or three times faster than the first time around. What you really got good at wasn't just the original subject — it was learning how to learn, and that specific meta-skill is what genuinely accelerates everything afterward, and makes taking on something new feel far less intimidating: "I already know how to learn, I just need to put in the time on this new specific thing."

Jeff: That's exactly right — I draw analogies constantly to my teaching background in meetings, demos, all sorts of things here at CADTALK, and I know it sometimes seems disconnected to people who weren't teachers themselves. But the underlying skills you build doing genuinely hard work — the effort, the concentration, the tenacity, that dog-with-a-bone refusal to let go of a problem, working at it repeatedly — those are really the transferable skills that matter, both in life and in any career or company. That constant desire to get better and learn new things.

Slightly off-topic, but why do you think so many companies and cultures genuinely undervalue that transferable capability? I went to university, earned scholarships, studied Latin — a story I've told plenty of times — and society, work culture generally, tends to push you toward "learn this one specific skill" rather than genuinely valuing the transferable ability to learn quickly. Everyone wants to hire someone with existing experience, someone who already knows everything relevant, rather than someone who's simply excellent at figuring things out.

Undervaluing Transferable Skills
Scott: I used to be genuinely down on my own college experience for a long time, honestly — I went through engineering school and felt like almost nothing I directly learned applied to the business world afterward. The older I get, the more I've come to believe that view was wrong — there's real value in that meta-skill of learning how to genuinely figure something out, how to study and truly work hard at something difficult. Did I use calculus daily afterward? No. But I actually took two years off partway through college, working as an electrician — different story for another time — and when I came back and had to relearn calculus, it was genuinely hard the first time through in a way high school math never had been, because I'd honestly never fully learned how to study before that. Coming back, I studied three or four hours a day for an entire semester just to earn a B — and that was one of the first times in my life I truly understood what real studying, real effort, actually felt like, including how genuinely crushing it can be. That skill — understanding that you simply have to put in the volume, the sustained effort — that's genuinely what I was learning, far more than the calculus itself.

College, in a sense, is poorly marketed if you think about it that way — it's framed as "you'll become an engineer" or "you'll learn Latin," when really the deeper value is "I'm going to teach you how to do something genuinely hard," teaching the underlying meta-skill. From a pure business standpoint, though, hiring someone who already has the specific skill means you're not paying for them to build it from scratch — but that expertise comes at a real cost, since experienced people are naturally more expensive. If you can afford that, it's genuinely the fastest path. Earlier in a company's life, with less capital available, you instead invest in someone with the capacity to learn the skill — someone who's fundamentally good at learning itself. That's actually good general career advice too: early in your career, or early in any new career, optimize for learning, not for immediate earning.

Optimizing for Learning
Scott: That trade-off — earning versus learning — gives you the chance to work somewhere you'll genuinely learn a lot, alongside genuinely excellent people, really mastering something, which sets you up to earn more down the road. It really depends on the company's stage and the individual's own stage — well-capitalized companies tend to simply buy existing expertise outright, while earlier-stage companies tend to invest in raw learning capacity instead, and sometimes a company genuinely values both simultaneously, because both bring real value. I think that's really why the market prices it the way it does — people generally want to pay as though someone's still learning, while quietly hoping they already have the skill fully baked in, and that's just not realistically how it works economically.

Jeff: It really depends on what you actually need at a given moment — there's real value in hiring for that Relentless Reinvention mindset specifically, someone who'll dive in, figure it out, work hard, and genuinely enjoy that process, versus someone less personally invested in that mindset but who already knows exactly how to execute the specific job. Both have real upside, though ideally you're looking for someone who brings both.

It's interesting, thinking back to joining CADTALK — realistically, if I'd applied cold, most companies wouldn't have hired a former Latin teacher for a software role, reasonably assuming I didn't know anything relevant. And I understood that reaction. But the ability to learn quickly, combined with genuine dedication, matters enormously — probably far more than most companies or hiring cultures tend to value, at least in my experience, though maybe that's simply a reflection of a given company's specific culture.

Scott: I remember a business partner years ago telling me — we were running a business together at the time that honestly didn't fully interest me anymore — "you're probably the best in the world at this specific thing, why would you walk away from that?" And my honest reaction was: sure, but I could probably become excellent at the next thing too — figuring out something new never felt genuinely scary to me. Might sound a little arrogant, but to me, the next challenge was never intimidating — I'd just do the work and learn it again. His underlying belief was "why give up being the best at something to start over as a beginner?" — but I was genuinely fine taking that ego hit of dropping from expert back down to beginner, because honestly, that early climb from beginner toward mastery is actually the most exciting part of the whole process — there are real diminishing returns as you go further.

The Excitement of the Journey From Beginner to Mastery
Scott: It's similar to learning a new language — you go from knowing absolutely nothing to suddenly knowing a meaningful amount, and that early jump feels huge and genuinely exciting. But the curve gets steep fast, and progress noticeably slows the further along you get — the growth continues, but it's much less exciting, because that's when the real grind sets in, once the initial rush of fast, visible progress fades.

Jeff: There's real beauty in mastery too, though — genuinely refining a craft, going from the 90th to the 92nd to the 95th percentile. Those later gains are almost exponentially harder to earn.

Scott: Right — you can typically reach the 90th percentile of almost any skill fairly quickly with real, sustained effort. It's the percentiles beyond that which genuinely demand enormous additional time and effort — sometimes worth it, sometimes not, but you have to invest disproportionately more time, and time is the one resource none of us have an unlimited supply of. My daughter's a competitive swimmer, and she's asked me variations of "how do I get to the very top" — realistically, you can probably reach the 90th, even 95th percentile of most skills in a reasonable amount of dedicated time. Beyond that threshold, genetic and other largely uncontrollable factors start playing a much bigger role, and a fair amount comes down to genuine luck. But I do genuinely believe almost anyone can reach roughly the 90th percentile of nearly any skill they choose to pursue, in a reasonable timeframe — it's just that final 5 to 10 percent that takes exponentially longer to earn.

Closing Thoughts
Jeff: This has been a genuinely great conversation — I could keep going for a long time, honestly. Really enjoyed digging into Relentless Reinvention today, touching on reinventing ourselves individually as well as the company itself, and where we're headed. Any parting thoughts before we close out?

Scott: Just that, as I mentioned, this genuinely is one of my favorite values — maybe my absolute favorite, though I think they're all genuinely representative of who we are. My honest advice to anyone listening: you're capable of far more than you currently believe. People consistently sell themselves short, and if you consistently ask yourself "how could I make this better, how could I refine this, how could I become more" — that's a genuinely useful frame that makes life more exciting, and keeps you asking how much more value you can create and contribute in the world. I think that's just a great overall way to approach things.

Jeff: Thanks, Scott, really appreciate this conversation. That wraps up episode two of CADTALK's Integrate Intelligently Podcast. For anyone unfamiliar — CADTALK, founded by Scott, is an integration platform connecting engineering software — the alphabet soup of PDM, PLM, and popular ERP systems. We started this podcast to share our values, share who we are, and share some genuine thought leadership. Please subscribe and find us on YouTube and wherever you get your podcasts, and visit us at cadtalk.com. Anything else, Scott, before we sign off?

Scott: If you enjoyed this, please leave us a review — it genuinely helps spread the word to others who might find it valuable. Looking forward to the next one.

Jeff: Looking forward to it too — have a great Fourth of July, enjoy the weekend.

Scott: You too — thanks.