End Business Tech Frustration

Jim Kineon
  • 5.0 (2)
  • Management
  • Updated Weekly

End Business Tech Frustration is a practical podcast for small and mid-sized business leaders and entrepreneurs who want technology that works. Each episode delivers real examples and actionable steps to help you avoid tech disasters, improve customer experience, and turn technology into a competitive advantage.

  1. Oct 2

    Episode 18: The Real Reason CRM Rollouts Fail (It's Not the Software)

    Episode Overview Is your team paying for software capability it never actually uses? In this episode, Jim tells the real story of a small nonprofit with fewer than 25 employees, running mostly on volunteers, whose CRM had grown far more complex than the organization needed, with training nobody could find, support that couldn't keep up, and event data that had to be reconciled by hand. Jim uses their story to walk through CLEAR, his five-step process for making any technology decision: Check, Link, Establish, Activate, and Review. This episode is for business leaders and nonprofit executives who suspect their current system has outgrown their actual needs, and want a real, step-by-step example of how to right-size it.   In This Episode, You’ll Learn Six lessons this case study teaches about any CRM decision:   1. Right-size the software to your actual needs, not your ambitions. 2. Follow a real implementation plan — don't skip steps because the system feels smaller. 3. Clean your data before it moves, so you're working from one reconciled set of contacts. 4. Decide, on purpose, how much history you actually want to bring with you. 5. Train people for the job they do, not just the buttons in the software. 6. Match your support agreement to how fast you actually need an answer.   THE FRAMEWORK — CLEAR 1. Check: Assess your current technology health across Initiative, Organization, Process, People, and Technology, and identify the root causes creating friction. 2. Link: Connect the root-cause fix to a measurable business outcome, not a feature list. 3. Establish: Prioritize improvements, define responsibilities, identify dependencies, and build a practical sequence of action. 4. Activate: Implement the roadmap while managing communication, testing, training, and support. 5. Review: Measure progress, compare it to the outcome you wanted, and keep refining until you get there.   Connect With Me On LinkedIn www.linkedin.com/in/jimkineon   Subscribe to My YouTube Channel https://www.youtube.com/@jameskineon4185

  2. Sep 12

    Episode 17: What 9/11 Taught Me About Financial and Supply Chain System Failures

    Episode Overview If the person who runs your financial system disappeared tomorrow, would your business still function? In this episode, Jim Kineon shares a true story from a company he worked with in the World Trade Center that had just finished replacing its financial and supply chain management systems the week of September 11th, 2001. Their technology backup worked perfectly, but no one had documented who could approve an invoice or release a vendor payment if the usual person wasn’t there, and it took months to get the business running smoothly again. Jim breaks down what this means for any business running financial or supply chain systems today, and offers a simple test for finding out how exposed your own organization really is. This episode is for any leader who has never asked what happens to their approval process the day the one person who knows it isn’t in the room.   In This Episode, You’ll Learn The real story of a financial and supply chain system that survived 9/11, and the business that struggled Why a technology backup and a business continuity plan are not the same thing What happens when an approval workflow only exists in one person’s head The One-Person Test, a quick way to check your own organization’s exposure What to document before your next system goes live Why organizations of every size, from 25 employees to 250, carry this same risk Connect With Me On LinkedIn www.linkedin.com/in/jimkineon   Subscribe to My YouTube Channel https://www.youtube.com/@jameskineon4185

  3. Aug 27

    Episode 16: What Has to Go Right When You Implement Accounting Software

    Episode Overview You picked your new accounting system. Now what?   In this episode, Jim Kineon walks through what actually has to go right — before and after go-live — for an accounting and financial reporting software implementation to succeed. Using a real case study of a mid-size manufacturer, distributor, and retailer, Jim shows how a go-live can look like nothing changed while the real business outcome takes months, or years, to show up.   Jim breaks down what to prepare before you migrate, what a real implementation can expose about your organization, how the plan changes as you grow, and what ownership looks like after the system is live.   If you've already chosen your software and you're wondering whether your organization actually knows how to implement it, this episode is for you.   In This Episode, You’ll Learn Why go-live is a milestone, not the actual goal, of an implementation The four things to prepare before you migrate: data, process, people, and support A real case study of a luxury goods manufacturer whose “successful” go-live still took years to pay off How implementation planning changes as you grow from 25, to 100, to 250 employees Why separating who creates, approves, pays, and reconciles matters more than people think What ownership looks like after go-live, and why the job isn't finished when the system turns on Connect With Me On LinkedIn www.linkedin.com/in/jimkineon   Subscribe to My YouTube Channel https://www.youtube.com/@jameskineon4185

  4. Jul 29

    Episode 15: How to Choose Accounting Software Without Creating a Financial Mess

    Episode Overview In this episode of End Business Tech Frustration, Jim Kineon explains how small and mid-size business leaders should evaluate accounting and financial reporting software. The episode covers what the software is supposed to do, why financial systems become more important as businesses grow, how needs change from 1–25 employees, 26–100 employees, and 101–250 employees, and what to consider when choosing accounting and financial reporting software for your business.   In This Episode, You’ll Learn Why accounting software is really about trusted decisions, not just bookkeeping. What core functionality every accounting system should provide. How accounting needs change as a business grows. What to look for in systems for 1–25, 26–100, and 101–250 employee organizations.     Why This Matters For small and mid-size business leaders, financial reporting problems create more than accounting frustration. They affect cash decisions, hiring, pricing, payroll confidence, board reporting, grant compliance, customer billing, vendor payments, and growth planning. If the accounting system is poorly selected or poorly implemented, the business may end up with more spreadsheets, more rework, weaker controls, and less confidence in the numbers.   Connect With Me On LinkedIn www.linkedin.com/in/jimkineon   Subscribe to My YouTube Channel https://www.youtube.com/@jameskineon4185

  5. Jun 3

    Episode 14: How to Choose SCM Software Without Breaking Operations

    Episode Overview   In this episode of End Business Tech Frustration, Jim Kineon explains how small and mid-size business leaders should evaluate Supply Chain Management software. He breaks down what SCM software does, why it matters, which features to look for, how needs change by company size, and how to avoid overbuying, under-planning, or choosing a system that creates more operational friction.   In This Episode, You’ll Learn   What SCM software actually does beyond basic inventory tracking Why supply chain problems are often people, process, data, and support problems How to evaluate SCM software for 1–25, 26–100, and 101–250 employee organizations Which features matter most at each stage of growth What questions to ask vendors to uncover limitations before signing Why data migration, training, support, criticality, and downtime must be part of the decision     Why This Matters   SCM software can improve purchasing, inventory accuracy, supplier coordination, order fulfillment, warehouse operations, shipping reliability, and reporting. But when the wrong system is chosen or when implementation is rushed, it can create more confusion, more workarounds, and more frustration. For small and mid-size businesses, the goal is not to buy the biggest system. The goal is to choose the right system for the actual business, the actual team, and the next stage of growth.   Connect With Me On LinkedIn www.linkedin.com/in/jimkineon   Subscribe to My YouTube Channel https://www.youtube.com/@jameskineon4185

  6. May 21

    Episode 13: Buying the Wrong CRM Is Expensive. Here's How to Avoid It.

    Episode Overview   Someone told you your business needs a CRM. And now you're drowning in options, features, and pricing pages that all say essentially the same thing. Which one is right for your team?   In this episode, Jim Kineon breaks down what a CRM actually is and what it's designed to do, and then walks through a practical framework for evaluating CRM software based on the size and maturity of your organization. Whether you have 12 employees or 200, the right CRM is not the one with the most features. It's the one that fits your team, your process, and where your business actually is right now.   In This Episode, You’ll Learn   • Why CRM selection is not a feature comparison, and what question you should actually be asking • What a CRM is genuinely designed to do, and the difference between core and advanced functionality • A real case study of a business that upgraded their CRM to get a complete picture of their customer including: purchases, contract agreements, marketing campaigns, billing and payment history. • How to evaluate CRM software for a 1–25 person organization, including what to look for and what to avoid • How CRM requirements and risks change as you grow to 26–100 and 101–250 employees • The hidden costs of data migration, post-launch support, criticality, and what happens during downtime • How to know if your organization is actually ready for a new CRM   Why This Matters   The best CRM is not the one with the most features. The best CRM is the one your team will actually use, can afford, and can manage without creating unnecessary complexity.   Connect With Me On LinkedIn www.linkedin.com/in/jimkineon   Subscribe to My YouTube Channel https://www.youtube.com/@jameskineon4185

  7. Apr 30

    Episode 12: How to Choose Software That Actually Fits Your Business

    Episode Overview   Choosing software should not begin with demos, feature lists, or vendor promises. It should begin with clarity. In this episode, Jim Kineon explains why business and nonprofit leaders need to define what they are trying to achieve before evaluating a software application. Using CRM software as an example, Jim walks through the importance of requirements, user needs, support, training, organization size, and practical business outcomes.   In This Episode, You’ll Learn   Why software selection should begin with business outcomes How to create a first list of software requirements Why features are only one part of the evaluation process How user skill level affects software adoption Why support and training should be considered before buying How requirements change for organizations with 1–25, 26–100, and 101–250 employees   Why This Matters   Many small and mid-size organizations choose software while they are still unclear about the real problem they are trying to solve. That creates risk. The system may look good in a demo but fail in real use because it does not match the organization’s process, people, support needs, or size. Clear requirements help leaders make better decisions, reduce implementation risk, and choose systems that support the business instead of slowing it down.

  8. Apr 22

    Episode 11: How to Build an AI Strategy That Actually Helps Your Business

    Episode Overview   Most small and mid-sized business leaders do not need a complicated AI plan.   They need a practical way to start.   In this episode, I explain how to build an AI strategy by focusing on one simple idea: use AI to do real work inside the business. Instead of getting lost in jargon, tool names, or endless experimentation, I show how leaders can take one repeatable task, turn it into a useful AI agent, and begin creating real business value.   This episode builds on last week’s conversation about AI agents by showing how they fit into a broader business strategy. I also compare the similarities between ChatGPT Custom GPTs, Claude Skills, Microsoft Copilot Agents, and Gemini Gems, helping business leaders understand what these tools have in common and how to think about them in a practical, business-focused way.     Six Steps for Building a Copilot Agent or Gemini Gem "Meeting Intelligence Assistant"    Step 1: (Open CoPilot and navigate to New Agent and Configure) OR (Open Google Gemini and navigate to Gems and New Gem). Step 2: Name your Agent (or Gem): Meeting Intelligence Assistant.  Step 3: Enter your instructions. (Copy the instructions below into Instructions field) CONTEXT AND GOALS You are a business operations assistant that turns meeting notes into clear, structured outputs that drive execution. Your audience: Small and mid-size business leaders and teams Time-constrained professionals who need clarity and action Your goals: Eliminate ambiguity Highlight decisions Clearly define next steps   INPUT EXPECTATION The user will provide: Raw meeting notes, transcript, or bullet points Notes may be unstructured or incomplete   OUTPUT FORMAT Always structure your response as follows:   1. Meeting Summary 3–5 concise bullet points Focus on what actually matters   2. Key Decisions List decisions made If none are explicitly stated, infer likely decisions   3. Action Items Create a table with: Task Owner (if known, otherwise suggest role) Suggested Due Date Priority (High / Medium / Low)   4. Risks / Gaps What is unclear, missing, or could cause problems?   5. Recommendations (Optional but preferred) Suggest improvements to avoid confusion or delays   STYLE GUIDELINES Be clear, concise, and practical Avoid fluff or generic statements Use simple business language Focus on execution, not theory   WHAT TO AVOID Do not repeat notes verbatim Do not include unnecessary detail Do not leave action items vague   Step 4: Define Data Sources, Capabilities and Suggested Prompts.   Step 5: Save, test and update as needed.   Step 6: Share with your team.   Five Steps for Building a Claude Skill "Meeting Intelligence Assistant"    Step 1: Open Claude and navigate to Customize > Create Skills > “+” > Write skill Instructions. Step 2: Name your Skill and enter a Description: Meeting Intelligence Assistant.  Step 3: Enter your instructions. (Copy the instructions below into Instructions field) You are an expert business operations advisor specializing in turning meetings into clear, actionable outcomes.   Your job is to transform raw meeting notes or transcripts into a concise, structured summary that helps business leaders take action.   ---   ## STEP 1: Interpret the input   - Identify the purpose of the meeting - Identify key topics discussed - Extract decisions, actions, and unresolved issues - Ignore filler, repetition, and off-topic discussion   ---   ## STEP 2: Identify business impact   For each major topic: - What problem is being addressed? - What decision was made (if any)? - What is the impact on the business?   ---   ## STEP 3: Extract action items   For each action: - Clearly define the task - Assign an owner (if mentioned, otherwise mark as “Unassigned”) - Include due date if available - Make actions specific and measurable   ---   ## STEP 4: Identify risks and gaps   Highlight: - Missing ownership - Unclear decisions - Dependencies - Potential delays or blockers   ---   ## STEP 5: Create structured output   ---   ## OUTPUT FORMAT   ### 1. Executive Summary - 3–5 bullet points - Focus on outcomes and key decisions   ---   ### 2. Key Discussion Points - Summarize major topics - Keep concise and business-focused   ---   ### 3. Decisions Made - Clearly list confirmed decisions - If none, state “No confirmed decisions”   ---   ### 4. Action Items   Format as a table:   | Action | Owner | Due Date | Notes | |-------|------|----------|------|   - If owner not specified → “Unassigned” - If no due date → “TBD”   ---   ### 5. Risks / Issues   - Identify anything that could delay or impact outcomes - Focus on organizational and process gaps   ---   ### 6. Next Steps   - What should happen next - Keep it practical and actionable   ---   ## STYLE GUIDELINES   - Write for business leaders and executives - Be concise and direct - Focus on clarity and action - Avoid unnecessary detail - Emphasize outcomes over discussion   ---   ## CORE PRINCIPLE   A meeting is only valuable if it results in clear decisions and actions. If those are missing, highlight the gap."   Step 4: Save (click Create), test and update as needed.   Step 5: Share with your team.   Note: Once you have created your Skill. You apply it by typing “/” at a prompt and selecting your skill from the list.   Connect With Me On LinkedIn www.linkedin.com/in/jimkineon   Subscribe to My YouTube Channel https://www.youtube.com/@jameskineon4185

See All (18)

Ratings & Reviews

5
out of 5
2 Ratings

About

End Business Tech Frustration is a practical podcast for small and mid-sized business leaders and entrepreneurs who want technology that works. Each episode delivers real examples and actionable steps to help you avoid tech disasters, improve customer experience, and turn technology into a competitive advantage.

Information

  • Creator
    Jim Kineon
  • Years Active
    2026
  • Episodes
    18
  • Rating
    Clean
  • Copyright
    © Copyright 2026 All rights reserved.
  • Show Website
    End Business Tech Frustration