Develpreneur: Become a Better Developer and Entrepreneur

Minimal viable pricing is the fastest way to stop debating what your product should cost and start learning what customers will actually pay for. In my interview with Dan Balcauski, founder and Chief Pricing Officer at Product Tranquility, we talked about how early-stage teams can set pricing that's "good enough" to sell, validate value, and iterate—without getting stuck chasing the perfect number. Pricing can feel risky because it shapes perception, positioning, and revenue. But Dan's message is practical: you don't need perfect pricing to move forward—you need minimal viable pricing that creates clear decisions and real feedback loops. Minimal viable pricing isn't "cheap pricing." It's "clear pricing" that helps you test value and drive decisions. About Dan Balcauski Dan Balcauski is the founder and Chief Pricing Officer at Product Tranquility, where he helps high-volume B2B SaaS CEOs define pricing and packaging for new products. A TopTal-certified Top 3% Product Management Professional, Dan also teaches in Kellogg Executive Education's Product Strategy coursework. Over the last 15 years, he has led products across the full lifecycle—from concept incubation to launch, platform transitions, maintenance, and end-of-life—across both consumer and B2B markets. Before Product Tranquility, he served as Head of Product at LawnStarter and as a Principal Product Strategist at SolarWinds following its $4B acquisition. What "minimal viable pricing" actually means Dan's approach starts with a mindset shift: early-stage companies rarely fail because their initial price was off by 10–20%. They fail because they haven't found a repeatable customer problem, a clear value promise, or a reliable way to acquire customers. Minimal viable pricing means: You set a price you can defend. You package it in a way customers can understand. You use real conversations and real deals to refine it. It's pricing as a learning tool—not a spreadsheet exercise. Minimal viable pricing starts with your "free option" One of the most actionable parts of the discussion was Dan's breakdown of freemium vs free trial—and why it matters so much for minimal viable pricing. A free trial creates urgency. There's a natural deadline, which forces customers to evaluate value and decide. A freemium model can work, but it often creates a huge pool of users who never engage deeply enough to convert. If your goal is to learn quickly, trials often generate clearer signals: Who gets value fast? What feature set drives adoption? What objections stop the purchase? Minimal viable pricing works best when your go-to-market motion creates real decisions—not endless "maybe later." Trial length: don't confuse "short" with "effective" There's a trend toward shorter trials (like 7 days), but Dan's point is simple: a short clock doesn't help if your customer can't realistically experience value in that window. In B2B especially, onboarding delays, competing priorities, and internal approvals can chew up days instantly. A minimal viable pricing approach asks: What's the shortest trial that still allows a motivated customer to succeed? If you're selling to teams, the answer is often longer than you think. Use minimal viable pricing to clarify positioning Dan also shared a framing that sticks: are you selling a Timex or a Rolex? In other words, are you competing on affordability and simplicity—or premium value and outcomes? Minimal viable pricing isn't just about the number. It's also about: The story your pricing tells The kind of customer you attract The expectations you set around results and support You don't need a dozen plans to communicate this. You need clarity. If customers can't tell who your product is for from the pricing page, your "pricing problem" might actually be a positioning problem. The goal: learn faster, not argue longer Minimal viable pricing gives you a way to move forward without pretending you have perfect information. Start with something simple, sell it, listen hard, and iterate. If you want a practical takeaway from Dan's perspective, it's this: pricing is one of your best feedback loops. Use it early. Use it intentionally. And don't let the hunt for "perfect" delay the real work—helping customers win. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Defining An MVP Properly for Your Goals Price With Confidence: Estimation Made Simple How to Build a Minimal Viable Product Without Blowing Your Budget Building Better Foundations Podcast Videos – With Bonus Content

If you want real improvement—not just more dashboards—workflow efficiency metrics have to start with something most teams avoid: visibility. In Part 2 of our interview with Michael Toguchi, we move from "big ideas" into the operational reality leaders face every day: shadow tools, duplicate systems, fuzzy ROI, and the pricing pressure that shows up when AI makes work faster. This conversation is a reality check for ops leaders, engineering leaders, and consultants trying to scale without drowning in tool sprawl—or measuring productivity in ways that break trust. Workflow efficiency metrics only work when the workflow is visible. If work lives in shadows, your data will lie. About Michael Toguchi Michael Toguchi is the Chief Strategy Officer at eResources, where he leads strategy for technology that supports complex, high-stakes workflows across higher education and mission-driven organizations. With 25+ years in digital transformation, Michael helps teams reduce tool sprawl, eliminate manual bottlenecks, strengthen compliance, and measure improvements in ways that translate into real operational capacity and impact. Tool Sprawl Starts as "Helpful" (Until It Becomes Expensive) Every organization eventually meets the "skunk works" problem: someone builds a spreadsheet, a quick app, a mini database, or a side process that solves a real pain—fast. It's well-intentioned. It's also how silos form. Over time, those small fixes become a parallel organization: Data gets duplicated in multiple places Teams report numbers that don't match Leaders lose confidence in what's "true" Tech debt grows quietly because no one owns it end-to-end Michael's warning is simple: when every department solves problems in isolation, the organization pays for it later—usually in rework, compliance risk, and decision-making paralysis. Shadow tools don't just create tech debt—they create decision debt. Workflow Efficiency Metrics Start With Transparency, Not Control The fix isn't to ban spreadsheets or crush experimentation. Michael's approach is more practical: shine the light on the workflow, then standardize intentionally. That means asking better questions: Who is doing this work today—and why? Where does the data enter, and where does it leave? Which steps exist because the system is unclear… versus because the work is truly necessary? What systems must integrate so people aren't forced into duplicate entry? Transparency isn't micromanagement. It's a shared map. And once everyone sees the same map, you can make changes that stick. "Shine the transparency light on the workflow." Then decide what to standardize and integrate. Workflow Efficiency Metrics That Matter: Time Saved → Capacity Gained A big takeaway from Part 2 is how Michael thinks about measurement. Leaders often struggle here because "value" feels subjective—until you translate it into something tangible. Instead of measuring activity ("tickets closed" or "hours logged"), focus on outcomes: time reclaimed errors reduced handoffs eliminated cycle time improved compliance risk reduced Michael shares a practical framing: if you reclaim even a slice of time—say 15% of a team's capacity—that's not just a feel-good metric. It's a lever you can pull: that capacity becomes more customers served more projects shipped more support coverage fewer burnout-driven departures In other words, the metric isn't "time saved." The metric is what the organization can now do because time was saved. Time saved is only "real" when it turns into capacity, quality, or revenue. When AI Shrinks Time, Time-and-Materials Pricing Breaks Then Michael hits the business-model shift that a lot of teams are quietly wrestling with: AI compresses time. Work that took weeks can take days. The value may be the same—or higher—but the hours shrink. If you sell hours, you're forced into a bad choice: charge less (even if the impact is huge), or justify hours that no longer make sense Michael's answer is to move up the stack: value-based pricing, retainers, and partnership models—ways of charging for outcomes, access, and expertise instead of minutes on a clock. That shift requires maturity: you must be able to explain your value clearly and measure the results you're creating. Which brings us right back to the point of the episode… Workflow efficiency metrics aren't just internal tools. They're how you prove impact when "time spent" stops being the story. Value-priced work + retainers make sense when time shrinks—but outcomes still matter. Closing Thoughts on Workflow Efficiency Metrics Part 2 is a playbook for modern leaders: reduce tool sprawl with transparency, measure efficiency without eroding trust, and adapt your pricing model as AI changes the relationship between time and value. In a world where speed is easier to buy, the winners will be the teams who can see the workflow, measure what matters, and price the impact. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Boost Your Developer Efficiency: Automation Tips for Developers Upgrading Your Business: Save Time And Improve Efficiency Invest In Your Team – They Will Want To Stay Building Better Foundations Podcast Videos – With Bonus Content

If you've ever felt like your team is running on duct tape and good intentions, you're not alone. In this Building Better Developers interview, Michael Toguchi (Chief Strategy Officer at eResources) makes a simple point that changes how you approach growth: process before tools. Before you buy another platform, automate another workflow, or roll out a new system, you need clarity on how the work actually gets done—and who it's meant to serve. You can't tool your way out of chaos. The real fix starts upstream—before the migration, before the CRM, before the next sprint. It starts with people, leadership, and making the work visible enough to improve it. Process before tools isn't a slogan—it's the difference between scaling sustainably and scaling stress. If you want, I can also tighten the second sentence to include the phrase again without sounding repetitive, but this version should clear the Yoast check immediately. About Michael Toguchi Michael Toguchi is the Chief Strategy Officer at eResources, where he helps lead a platform that manages complex workflows for scholarships, grants, admissions, and accessibility services. With 25+ years supporting universities, nonprofits, and foundations through digital transformation, Michael focuses on making systems simpler, sustainable, and human-centered—so teams can scale without burnout and spend more time on mission-driven work. Process Before Tools: Why "Survival Mode" Becomes the Default Michael describes a pattern that mission-driven organizations (and plenty of startups) fall into: survival mode. Everyone is moving fast, reacting to urgent needs, and doing what it takes to keep the wheels turning. The downside is that the process gets postponed indefinitely. The team says things like: "We'll document it later." "We'll clean it up after this deadline." "We just need something that works." And it does work… until it doesn't. When the organization grows, the cracks grow with it: inconsistent outcomes, tribal knowledge, bottlenecks, and the quiet creep of burnout. Process Before Tools: Start Small, Make It Digestible One of the strongest points Michael makes is that meaningful change rarely comes from a dramatic, top-down overhaul. The most sustainable improvements begin with small, digestible steps. Instead of trying to "fix everything," identify a single pain point the team feels every week: A handoff that always breaks A recurring rework loop A reporting task that eats hours A workflow that depends on one person's memory Then improve that one piece, measure it, and repeat. Sustainable change isn't a magic wand. It's a series of small wins that teams can actually absorb. Process Before Tools: You Need Leadership Alignment (Not Just Agreement) A lot of teams confuse "buy-in" with "approval." Leadership might approve a new system or initiative, but that's not the same as aligning on why it matters, what success looks like, and what tradeoffs are acceptable. Michael emphasizes clarity: What problem are we solving? Who owns the workflow? What will we stop doing to make room for the change? How will we know it's working? Without alignment, the organization drifts into mixed expectations—some people expect speed, others expect compliance, others expect perfect reporting. The result is frustration on all sides. Process Before Tools: Win With People, Not Platforms Michael's most practical warning is also the simplest: don't make it about tools. Tools can amplify a good process, but they can't create it. If you automate a messy workflow, you don't get a better workflow—you get a faster mess. The winning strategy is human-first: build champions inside the team communicate the vision in plain language reduce fear by making the change incremental keep feedback loops tight When teams feel heard, they participate. When they participate, the workflow becomes real. And once the workflow is real, the tool decision becomes obvious. Tools don't transform organizations—people do. Process Before Tools: A Practical Takeaway You Can Use This Week Here's a simple way to apply Part 1 immediately: Pick one workflow everyone complains about. Write down the steps as they happen today (no judgment). Identify one "failure point" (handoff, duplicate entry, unclear ownership). Fix only that this week. Tell the team what changed and why. That's how you move from survival mode to sustainable growth—without waiting for a budget cycle or a platform replacement. Closing Thoughts This interview is a reminder that building better systems is really about building better teams. Before you chase the next tool, tighten the workflow. Before you automate, clarify. Before you scale, align. In Part 2, we'll go deeper into workflow transparency, tool sprawl, measurable efficiency, and what happens when AI compresses time and challenges the way we price work. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Individuals and Interactions Over Processes And Tools The Science Of Processes – Interview With Samuel Drauschak Automating Your Processes Building Better Foundations Podcast Videos – With Bonus Content

You validated the idea. You built the page. Maybe you're even getting traffic. And yet… the conversions don't match the effort. In Part 2 of our interview with Samir ElKamouny, we shift from "prove the concept" to conversion rate optimization—the discipline of diagnosing what's actually limiting growth and improving the parts of your funnel that matter most. This isn't about chasing shiny marketing tactics. It's about execution: the kind that turns a funnel from "pretty good" into "predictable." About Samir ElKamouny Samir ElKamouny is an entrepreneur and marketing expert who believes execution is everything—an early lesson inspired by his father's legacy of big ideas. He has helped scale businesses by pairing strategic action with a commitment to impact, guided by values such as Freedom, Happiness, Health, Family, and Spirituality. In this episode, that philosophy becomes funnel execution: identify the bottleneck, prioritize the 80/20, and optimize what's already working. Conversion Rate Optimization Starts With One Question: Where's the Constraint? Many teams skip straight to A/B testing headlines or tweaking button colors. Samir takes a more surgical approach. Before you optimize anything, you need to know what kind of problem you have: Do you have a traffic problem? Or do you have a conversion problem? Because those are different fixes. If you're not getting enough visitors, obsessing over landing page micro-changes won't move the needle. But if you are getting traffic and still not getting demos, leads, or signups—then you've got a conversion bottleneck, and conversion rate optimization is exactly the right tool. Bottleneck First Traffic problem = distribution. Demo problem = messaging, offer, trust, friction, or flow. Diagnose the constraint before you "optimize." Use the 80/20 Rule to Avoid Busywork Samir's funnel advice lines up with how great engineers debug systems: don't touch everything—find the one thing causing most of the pain. That's the 80/20 rule applied to marketing and funnels: A small number of pages create most conversions. A small number of objections block most sales. A small number of steps create most drop-off. When you apply conversion rate optimization well, you're not "improving your funnel" in general. You're improving the one point that's limiting everything downstream. A practical example: if you're generating leads but no one books calls, the issue probably isn't your top-of-funnel content. It's the handoff—your booking experience, your follow-up, or the clarity of what the call is for. The "Two-Second Clarity Test" for Positioning Samir emphasizes something that's brutally simple—and incredibly effective: When someone lands on your page, they should understand what you do in about two seconds. Not "kind of." Not "after reading three paragraphs." Two seconds. That clarity acts like a conversion multiplier. If visitors are confused, they don't scroll. They don't click. They bounce. And no amount of A/B testing can fix a page that doesn't communicate the offer. Two-Second Clarity Test: Can a first-time visitor instantly answer: What is this? Who is it for? What outcome do I get? If not, start there. Don't Test What Nobody Sees One of the most actionable parts of Part 2 is Samir's reminder to test based on attention, not opinions. Teams often test sections that aren't getting seen or clicked because they "feel important." But if users never reach that section—or don't interact with it—optimizing it is wasted effort. Instead, focus on experiments where user engagement is highest: above the fold the primary CTA area pricing/packages booking forms the first "proof" section (testimonials, logos, outcomes) That's how you make conversion rate optimization practical: test the parts of the page that actually get traffic, eyeballs, and clicks. A Simple Conversion Rate Optimization Framework You Can Use This Week Here's a clean execution loop you can run without overcomplicating it: Pick one conversion goal (demo booked, lead submitted, trial started). Locate the biggest drop-off (analytics + recordings + basic funnel tracking). Form one hypothesis ("People don't trust us yet," "Offer is unclear," "Form is too long"). Make one meaningful change (not five at once). Measure the result and keep only what improves the goal. That's it. Clear goal. One bottleneck. One change. Real measurement. Closing Thoughts: Optimize the Constraint, Not Your Ego The best part of Samir's approach is that it respects reality. It avoids "marketing theater" and focuses on execution that produces outcomes. If you want conversion rate optimization to work, don't start with cleverness. Start with constraints: Where are people dropping off? What do they not understand? What stops them from taking the next step? Fix that one thing, and the whole system improves. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Business Tune-Up Checklist: How to Refresh, Refocus, and Reignite Mid-Year How to Succeed with Digital Marketing for Small Businesses Close Deals With LinkedIn Building Better Foundations Podcast Videos – With Bonus Content

If you're a developer or founder, you already know how to build. The hard part is building the right thing, for the right people, at the right time. In Part 1 of our interview with Samir ElKamouny, we dig into a practical market validation strategy that helps you avoid the most expensive mistake in software: investing months of effort into something the market didn't ask for. Samir's message is refreshingly grounded: big ideas are great, but execution is everything. And execution doesn't start with code—it starts with clarity, research, and small tests that tell you whether you're on the right path. About Samir ElKamouny Samir ElKamouny is an entrepreneur and marketing expert who believes execution is everything—an early lesson inspired by his father's legacy of big ideas. He's helped scale businesses by pairing strategic action with a commitment to impact, guided by values like Freedom, Happiness, Health, Family, and Spirituality. In this episode, that philosophy shows up as practical market validation: test demand and messaging before you overbuild. Market Validation Strategy: Start With "Is This Real?" Before "Can I Build It?" One of the biggest mindset shifts Samir reinforces is that your first job isn't product development—it's discovery. Before you worry about features, tech stacks, or perfect UI, you need answers to questions like: What problem are we solving—and for whom? What alternatives do people already use? Why would someone switch (or pay)? What would make this stand out in the market? This is where market research becomes your leverage. It reduces risk, sharpens your messaging, and keeps your roadmap tied to real-world demand instead of assumptions. Ideas Don't Win—Execution Wins: You can have a great idea, but if you can't clearly explain why it matters and who it's for, you'll struggle to sell it—even if you build it perfectly. Market Validation Strategy: Use Market Research to Find Differentiation Samir talks about loving market research because it forces you to look for what actually matters: differentiation. A useful way to think about this (especially for builders) is to treat your market research like a product spec—but for the buyer's brain: What are the top 3 pains people complain about? What outcomes do they want most? What language do they use to describe the problem? What do they distrust about existing options? That last point is gold: distrust is often where your positioning lives. If buyers think "all solutions in this space are overpriced and confusing," your market edge might be "simple, transparent, and fast to implement." Market Validation Strategy: Run the $5/Day Test (Before You Write Code) Here's where Samir gets extremely actionable: you don't need a perfect product to validate interest. You need a simple way to test messaging and capture intent. Think lightweight experiments: a basic landing page with one clear promise a short form ("Interested? Tell me your biggest challenge.") a tiny ad budget to test demand and messaging (Samir mentions even $5/day) a few direct conversations with the people you're building for This isn't about "launching." It's about getting signals—fast. The Goal Isn't Perfection—It's Proof: If people won't click, reply, or sign up when the idea is explained clearly, a bigger build won't fix that. Validation comes before optimization. Market Validation Strategy: Build a Funnel That Matches the Buyer's Learning Curve Samir also breaks down why funnels aren't one-size-fits-all. The funnel you need depends on how much your buyer must be educated before they can decide. If you're in a well-known category—say "CRM"—buyers already understand the problem and the solution type. Your job becomes differentiation and trust. But if your product is new, complex, or requires behavior change, you may need a longer funnel: more education, more examples, more proof, and more clarity before a buyer is ready to act. Either way, the key is to define the conversion goal (lead, consultation, free trial, signup) and build only what supports that path. Market Validation Strategy: A 48-Hour Checklist for Builders Try this quick validation sprint before you commit to a full build: Write a one-sentence offer (who it's for + outcome). Build a simple landing page (problem, promise, proof, CTA). Run a tiny ad test or post where your audience hangs out. Track clicks + form submissions (signals > opinions). Talk to 3–5 responders and ask what they expected. If the message lands, you've earned the right to build the next layer. If it doesn't, you just saved yourself months of building the wrong thing. Closing Thoughts: Execute Small, Learn Fast, Build Smart A strong market validation strategy is less about "finding the perfect idea" and more about building the habit of learning quickly. Samir's approach helps you move from assumptions to evidence—without betting your time, energy, or budget on hope. So before you spin up a repo, define your offer, test your messaging, and look for real-world signals. Once you have proof, then you can build with confidence—because you're not just building software. You're building something people actually want. In Part 2, we'll take the next step: how to diagnose funnel bottlenecks, improve clarity, and use smarter testing to increase conversions once you've got traction. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Branding and Marketing Fundamentals with Kevin Adelsberger Leverage YouTube For Marketing And Brand Growth How to Succeed with Digital Marketing for Small Businesses Building Better Foundations Podcast Videos – With Bonus Content

New Year's Day hits different when you're recording with a live studio audience, passing the mic around, and starting the year with a mix of laughs, honest reflection, and big goals. In this Building Better Developers special episode, Rob Broadhead and Michael Meloche kick off 2026 by sharing a "good thing / bad thing" recap from a recent Christmas party—then opening the floor to the team to talk about the New Year developer goals. It's casual, it's real, and it's a reminder that growth (personal and professional) usually starts with clarity. Michael's 2026 New Year developer goals: Payoff and Growth When the conversation turns forward, Michael shares something that hits hard for anyone building a business—or rebuilding momentum. He describes the last year (or two) as a heavy investment: retooling, branding, marketing, refining direction, and putting in the work that doesn't immediately show results. Now, in 2026, he's looking for payoff—not in a "get rich quick" way, but in the sense of seeing the fruits of consistent effort. He also mentions narrowing focus for Develpreneur and wanting to see that a clearer direction translates into growth. There's something powerful about that moment: when you stop trying to do everything, and start building depth in the things that matter. If you spent 2025 laying groundwork, 2026 is your chance to ship with confidence. Foundations aren't the finish line—but they make speed possible. Rob's 2026 New Year developer goals: Scale, Network, and Teach Again Rob's focus is straightforward: he wants to keep growing the business, but also move from "a couple projects went well" to scaling—bringing in more work and creating consistent momentum. One of the practical strategies he calls out is getting out more: business conventions, tech conventions, and networking. Not just online—real-world conversations that create opportunities. He also hints at something long-time listeners will appreciate: he wants to relaunch teaching episodes. That includes new "kitchen sink" style applications, plus content around AI and emerging technologies. It's a return to hands-on learning—less theory, more building. Team Voices on New Year developer goals: Milestones, Features, and New Seasons Wes, a programmer at RRB Consulting, brings a personal win that feels like pure New Year energy: his car is getting paid off early in the year. That's freedom. Breathing room. And honestly, a reminder that progress isn't only measured in commits and deployments. Professionally, Wes is excited about projects with features coming together in the first quarter—things moving from "in progress" to "in the client's hands." Natalie shares that 2026 is a "new season of change" for her—wrapping up big chapters and getting ready to reinvest significant time back into RRB. Rob adds another layer: he's planning to be a digital nomad in 2026 and launching a site to document the adventures and the tech behind them. One Day at a Time (Yes, Even for Developers) As the episode closes, there's a simple challenge: don't give up on your New Year's resolutions on day one. Make it to day two. Day three. Day ten. Keep it small. Keep it moving. And then: back to interviews, back to Building Better Foundations, and the ongoing push toward major milestones—like eventually hitting episode 1000. Pick one small habit you can keep for 10 days. If you can do 10, you can do 30. If you can do 30, you can change your year. Ready for 2026? This episode isn't about perfect plans—it's about momentum, focus, and showing up. Whether you're chasing payoff after a long build season, scaling your business, shipping features, or stepping into a new chapter… the message is the same: Start. Today. Then do it again tomorrow. Happy New Year—and we'll see you in the next episode. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Strategies for Your New Year Planning Become A Better Developer In The New Year Goal Setting and Habits: The Keys to a Productive New Year Building Better Foundations Podcast Videos – With Bonus Content

It's New Year's Eve-Eve, and instead of recording from our usual virtual setups, we did something we've talked about for years: we hit record in the same room. If you're watching on YouTube, you can actually see us together. If you're listening on audio, you'll just have to trust us—this one was in-person. In this special episode of Building Better Developers (our Building Better Foundations season), we keep it simple: a Year-End Reflection for Developers. What are we ready to leave behind from this year? What do we want to carry into the next one? And what's the reality behind the loudest tech conversations? A Year-End Reflection for Developers isn't about perfection. It's about clarity—keeping what worked, dropping what didn't, and starting the next year lighter. Year-End Reflection for Developers: What We're Ready to Leave Behind We opened the discussion with a question you can ask your team, your friends, or yourself: What are you ready to see go away? For Rob, it was the endless, extreme framing around AI. Not AI itself—he uses it and enjoys it—but the constant "AI will save everything" or "AI will destroy everything" energy that dominated so many conversations this year. The truth is, we're still going to talk about AI next year. The goal is to move the conversation toward reality: what it can do well, what it can't, and how to use it responsibly without acting like it's magic—or doom. Year-End Reflection for Developers on AI Hype vs Reality A big part of this Year-End Reflection for Developers was dialing down the panic and dialing up practical thinking. AI tools can absolutely help developers move faster. They can help summarize, brainstorm, refactor, and even unblock you when you're stuck. But the hype has pushed people into extremes, and extremes aren't useful when you're shipping software. If you used AI this year, you already know the real story: sometimes it's brilliant, and sometimes it confidently hands you nonsense. Use AI like a tool, not a truth machine. A Year-End Reflection for Developers should include one rule: verify before you trust. Year-End Reflection for Developers on "AI Caused the Layoffs" Michael took the AI conversation in a different direction: big businesses blaming AI for layoffs. Yes, AI will impact jobs over time. But what we're seeing right now often looks more like companies correcting after the COVID-era "no hire / no fire" period. In other words, the bottom line is driving decisions, and AI is becoming a convenient headline. If you're cutting roles for financial reasons, just say that. Don't hide behind buzzwords. That honesty matters—not just for employees, but for the industry. Developers don't benefit from fear-based narratives. We benefit from transparency and real strategy. Year-End Reflection for Developers: Studio Audience Takeaways Because we had an in-room setup, we passed the mic to a few of our "studio audience" members. Ian shared the positive side of his year: getting hands-on experience in Agile and learning what it's like to build alongside a team of developers on a large project. It had hangups, and it ran longer than expected—but that's real work, and real growth. Wesley echoed the burnout around AI buzzwords and made a strong point: when we say "AI," we need to be specific. A lot of what people mean right now is "large language models," and lumping everything under "AI" only adds confusion. He also called out how hype can warp markets—like hardware prices skyrocketing when everyone jumps on the trend. Year-End Reflection for Developers: Less Fear, More People Natalie brought the most human answer of the night: she wants less fear. Less fear, less uncertainty, less constant tension—and more remembering that we're all in this together. That hit home, because a Year-End Reflection for Developers isn't just about tech. It's about how we work, how we treat each other, and how we show up next year. Year-End Reflection for Developers: What's Next We closed with a simple message: go enjoy the next few days. Get out. Socialize. Be kind. Let go of the fear and anger where you can. We'll see you in 2026. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Strategies for Your New Year Planning Make a Final Push to Setup a Great New Year Become A Better Developer In The New Year Building Better Foundations Podcast Videos – With Bonus Content

The week before Christmas has a way of exposing how the year really went. Deadlines either slow down or pile up, calendars get messy, and the pressure to "wrap everything up" shows up at the same time you're trying to enjoy the season. In this Pre-Christmas episode of Building Better Developers, Rob Broadhead and Michael Meloche keep it practical: looking back on the year, calling out what worked (and what didn't), and sharing why a year-end reset for developers is the best way to prepare for a better new year. Why a Year-End Reset for Developers Matters A year-end reset for developers isn't just taking a few days off. It's stepping back long enough to see the patterns you've been living in: where you made progress, where you got stuck, and where you've been running on fumes. This episode is about doing that reflection without guilt—and using it to set yourself up for momentum, rather than burnout. A year-end reset for developers is how you stop repeating the same year with a new calendar. The Good, the Bad, and the Real: Looking Back on the Year Rob kicks things off with a simple reflection: one good thing and one bad thing from the year. The good news is that the business made it through another year. That matters more than people like to admit. Survival means you kept moving, you adapted, and you didn't shut the doors. He also highlights a significant win: spending more time working on the business, rather than just being inside it. That includes improving systems, making changes, and investing in the foundation that supports growth. The bad is honest too: the company didn't grow as much as he wanted. Some goals didn't land. Still, even that can be useful—because it creates space to strengthen the core instead of rushing to scale. A year-end reset for developers starts with one question—what did you build that will help you next year? Micro Goals: How a Year-End Reset for Developers Turns Into Progress One of the biggest themes in this episode is that progress doesn't require dramatic change. Rob leans into incremental improvement—the small steps that keep forward motion alive when life gets busy. He talks about regularly touching key areas of the business: rebuilding and redesigning parts of the brand, creating internal tools, and moving toward more custom systems to reduce dependency on licenses and patchwork solutions. It's a steady approach: a little time each week, consistently, until the results show up. He also points out that networking and marketing may not be fun for everyone, but doing them consistently builds relationships—and those relationships often become valuable in ways you can't predict. Micro goals are the engine of a year-end reset for developers—small steps, repeated, create big change. When You're Split Across Stacks, the Reset Becomes Essential Michael talks about something many devs feel: context switching is expensive. This year, he has had two major projects running in two different technology worlds—Django/Python/Apache on one side and Java/Spring/AWS/Redis on the other. Even when you enjoy the work, the mental shift between stacks adds friction. That's why a year-end reset for developers needs to include something most of us skip: rest. Not "watch a screen while thinking about work" rest—real rest. Rest Is Not a Suggestion: The Core of a Year-End Reset for Developers Michael shares what he's been trying to implement more seriously: turning off distractions, stepping away from screens, and scheduling real breaks. Michael took a couple of days off over Thanksgiving and felt a clear difference. Because the truth is, there's a point where "powering through" stops working. You can still finish tasks, but it takes ten times the effort. Your mind gets foggy. Your focus disappears. Then you start mistaking exhaustion for a productivity problem. So the recommendation is simple: schedule rest like it's a requirement. Take a walk. Read a book. Get away from devices. Let your eyes rest. Get out into your community. Look at holiday events, concerts, or just go see Christmas lights. The goal is to reconnect with life outside your backlog. The fastest way to improve your output is often a year-end reset for developers—rest first, then refocus. Boundaries Make You Better: Deadlines, Routines, and Quitting Time Rob adds an important point: structure helps. Having a "quit time" creates a boundary that forces smarter choices. He's found that shrinking the to-do list and accepting "it'll be there tomorrow" can actually increase productivity. We've preached this for years, and it still holds: once you push past a certain number of hours each week, you're not producing more—you're just working longer. A year-end reset for developers includes rebuilding boundaries that protect your focus. He also shares something worth repeating: everyone needs a way to disconnect. Exercise, cooking, a hobby, a walk—whatever it is, find it. If you don't have it, go discover it. Closing Thoughts: Enjoy the Season and Start Fresh This episode wraps with a simple holiday message: enjoy the time you have. Spend it with family and friends. Take a break. Indulge a little. Get out of the house. Recharge. Then when the new year hits, you'll be ready to set goals that actually stick—because you'll be thinking clearly and moving on purpose. A year-end reset for developers isn't a luxury. It's how you finish the year with gratitude—and start the next one with momentum. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources The Magic of Christmas Movies: A Heartwarming Tradition Gratitude and Growth: A Thanksgiving Special on Building Better Developers Thanksgiving Reflections for Developers: A Moment to Reset and Appreciate Building Better Foundations Podcast Videos – With Bonus Content

In Part 2 of our Building Better Foundations interview with Hunter Jensen, founder and CEO of Barefoot Solutions and Barefoot Labs, we explore how companies can begin adapting their business to AI over the next one to three years. Rather than imagining futuristic scenarios, Hunter keeps the focus on what's already happening—and what leaders must do now to stay ahead. About Hunter Jensen Hunter Jensen is the Founder and CEO of Barefoot Solutions, a digital agency specializing in artificial intelligence, data science, and digital transformation. With over 20 years of experience, Hunter has worked with startups and Fortune 500 companies, including Microsoft and Salesforce, to implement innovative technology strategies that drive measurable ROI. A seasoned leader and expert in the AI space, Hunter helps businesses harness cutting-edge technologies to achieve growth and efficiency. Facebook / Twitter (X) / LinkedIn / Website Where Companies Will See the First Wins When Adapting Their Business to AI Hunter starts by shortening the timeline. Five years is too far; the real transformation is happening in the next 12–36 months. Today's early value comes from AI supporting back-office functions: HR Accounting Research Administrative work These areas already show measurable ROI. But adapting your business to AI isn't just about automating repetitive tasks. "What comes next is using AI to support the thing your business actually does." – Hunter Jensen If you're in cybersecurity, AI will amplify cybersecurity tasks. If you work in finance, AI will speed up analysis and deal preparation. If you're in legal, AI will reshape workflows and client expectations. These shifts mark the second major phase of adapting your business to AI. The Coming Surplus: How AI Redefines Knowledge Work When Adapting Your Business to AI As companies begin adapting their business to AI, productivity skyrockets. Hunter predicts that many teams will get 5x more output from the same number of people. We see this creating a new challenge: a surplus of available work hours. This has already happened in software development. With AI-enhanced coding, the same team can deliver far more in far less time. Hunter warns that other knowledge-work fields—including law, consulting, and analytics—are next in line. "Layoffs are not a growth strategy. You need to innovate." – Hunter Jensen Instead of cutting staff, leaders should redirect excess capacity into new products, services, and innovation. Adapting Your Business to AI Requires Rethinking Your Model The biggest disruption comes not from tools—but from business models. Hunter shares how Barefoot Solutions, after 20 years of hourly-based software development, had to rethink its entire model when adapting its business to AI. With AI writing code faster than ever, traditional hourly billing simply couldn't reflect true value. The result? A shift toward product development, leading to the creation of Compass, an internal AI platform that helps organizations securely use their data. Many industries—especially those built on billable hours—will need to make similar changes. That means exploring: Value-based pricing Productized services Internal tools that create leverage Hybrid service + product offerings Adapting your business to AI means adapting how you make money, not just how you work. What Developers and Students Should Do Now For younger developers or recent graduates, adapting your career to AI is just as important as adapting your business to AI. Hunter recommends: Building strong AI literacy Understanding how to investigate, validate, and critique AI output Learning to integrate AI APIs into real applications Creating proof-of-concept projects that solve real business problems "The best way to learn is by building. Anything. Solve one real pain point." – Hunter Jensen Those projects become powerful résumé builders—and valuable stepping stones into the industry. Why Data Is Now the Ultimate Competitive Advantage The era of "first mover advantage" is over. AI allows competitors to replicate an idea in a weekend. But one thing cannot be cloned: your proprietary data. Hunter argues that adapting your business to AI means treating your data like a strategic asset. Companies with decades of untouched data—financial, healthcare, legal, operational—hold the new competitive moat. If you can use AI to unlock insights from that data, you create advantages no competitor can copy. Turning Disruption Into Opportunity As Hunter explains, adapting your business to AI is not optional: Productivity will surge Pricing models will shift Historic data will become a treasure chest Innovation will define survival But for entrepreneurs, leaders, and developers, this is also the most exciting moment in decades. The companies that adapt will not only survive—they'll lead. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Leveraging AI for Business: How Automation and AI Boost Efficiency and Growth Business Automation and Templates: How to Streamline Your Workflow Why Bother With Automated Testing? Building Better Foundations Podcast Videos – With Bonus Content

In this episode of Building Better Foundations, we interview Hunter Jensen, founder and CEO of Barefoot Solutions and Barefoot Labs, to explore what it really takes when getting started with AI in your business. As companies rush toward AI adoption, Hunter offers grounded, practical advice on avoiding early mistakes, protecting your data, and choosing the right starting point. About Hunter Jensen Hunter Jensen is the Founder and CEO of Barefoot Solutions, a digital agency specializing in artificial intelligence, data science, and digital transformation. With over 20 years of experience, Hunter has worked with startups and Fortune 500 companies, including Microsoft and Salesforce, to implement innovative technology strategies that drive measurable ROI. A seasoned leader and expert in the AI space, Hunter helps businesses harness cutting-edge technologies to achieve growth and efficiency. Facebook / Twitter (X) / LinkedIn / Website Why "Just Add AI" Is Not a Strategy When Getting Started with AI in Your Business Hunter begins by addressing the biggest misconception leaders face when getting started with AI in their business: the belief that a single, all-knowing model can absorb everything your business does and instantly deliver insights across every department. "Leaders imagine an all-knowing model. We are nowhere near that being safe or realistic." – Hunter Jensen The core issue is access control. Even the best models cannot safely enforce who should or should not see certain data. If an LLM is trained on HR data, how do you stop it from sharing salary information with an employee who shouldn't see it? This is why getting started with AI in your business must begin with clear boundaries and realistic expectations. Safe First Steps When Getting Started with AI in Your Business As Hunter explains, companies don't need to dive straight into custom models. A safer, simpler path exists for getting started with AI in your business, especially for teams on Microsoft 365 or Google Workspace. Start With Tools Already Built Into Your Environment Hunter recommends two solid, low-risk entry points: Microsoft 365 Copilot Google Gemini for Workspace These platforms provide: Built-in enterprise protections Familiar workflows Safe, contained AI access A gentle learning curve for employees Hunter emphasizes that employees are already using public AI tools, even if policy forbids it. When getting started with AI in your business, providing approved tools is essential to keeping data safe. "If you're not providing safe tools, your team will use unsafe ones." – Hunter Jensen These tools won't solve every AI need, but they are an ideal first step. Choosing the Right Model for Your Needs Another common question when getting started with AI in your business is: Which model is best? ChatGPT? Gemini? Claude? Hunter explains that the landscape changes weekly—sometimes daily. Today's leading model could be irelevent tomorrow. For this reason, businesses should avoid hard commitments to a single model. Experiment Before Committing Hunter suggests opening multiple LLMs side-by-side—such as ChatGPT, Claude, and Perplexity—and testing each for quality and speed. This gives teams a feel for what works before deciding how AI fits into their workflow. This experimentation mindset is essential when getting started with AI in your business because: Different models excel at different tasks Some models are faster or cheaper Some handle long context or code better New releases constantly change the landscape Your AI system should remain flexible enough to shift models as needed. Protecting Your Data from Day One One of Hunter's strongest warnings is about data safety. If you're serious about getting started with AI in your business, you must pay attention to licensing. If you are not paying for AI, you have no control over your data. Some industries—like legal, finance, and healthcare—may need even stricter controls or private deployments. This leads naturally to the next stage of AI adoption. The Next Step After Getting Started with AI in Your Business Once companies understand their needs, the next phase is building an internal system that: Connects securely to business software Honors existing user permissions Keeps all data inside the company network Uses models selected for specific tasks Hunter's product Compass is perfect for this phase. Instead of trusting the model to protect data, you rely on your own systems and access controls. This is how AI becomes truly safe and powerful. "The model should only see what the user is allowed to see—nothing more." – Hunter Jensen Final Thoughts on Getting Started with AI in Your Business Part 1 of our interview with Hunter Jensen makes one thing clear: getting started with AI in your business isn't about chasing the latest model. It's about protecting your data, giving your team safe tools, and preparing for a multi-model future. Stay tuned for Part 2 as we dive deeper into internal AI deployment, advanced architectures, and building long-term AI strategy. Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Leveraging AI for Business: How Automation and AI Boost Efficiency and Growth Business Automation and Templates: How to Streamline Your Workflow Why Bother With Automated Testing? Building Better Foundations Podcast Videos – With Bonus Content