{"id":15722,"date":"2026-09-16T10:14:42","date_gmt":"2026-09-16T15:14:42","guid":{"rendered":"https:\/\/www.mrc-productivity.com\/blog\/?p=15722"},"modified":"2026-09-16T10:15:14","modified_gmt":"2026-09-16T15:15:14","slug":"how-can-my-business-use-ai","status":"publish","type":"post","link":"https:\/\/www.mrc-productivity.com\/blog\/2026\/09\/how-can-my-business-use-ai\/","title":{"rendered":"10 Things AI Can Do That Your Current Software Can&#8217;t"},"content":{"rendered":"\n<figure class=\"wp-block-image aligncenter size-full\"><img decoding=\"async\" src=\"https:\/\/d4ey5ve3eb27c.cloudfront.net\/img\/blog\/ai-10-things-featured-title.webp\" alt=\"Illustration of an email, a scanned packing slip, a spreadsheet, and old code flowing into one AI answer with an approve button\"\/><\/figure>\n\n\n\n<p>If you run IT, you&#8217;ve probably been asked &#8220;What&#8217;s our AI strategy?&#8221; at least once this year. Maybe more than once.<\/p>\n\n\n\n<p>It feels like every company is rushing to do something with AI. But most of them are approaching it from the wrong direction. They start with the technology. What can we build? A chatbot? A copilot? Or they look at what the AI vendors are selling, pick something that sounds useful, and try to find a place for it.<\/p>\n\n\n\n<p>It&#8217;s not a terrible approach. But it leads to a lot of the same, generic use cases. Why? Because the project started with the tool instead of the problem.<\/p>\n\n\n\n<p>There&#8217;s a better question: What can AI do that we can&#8217;t do today? What can it do that&#8217;s impossible, or really painful, with the software, code, and processes we already have?<\/p>\n\n\n\n<p>Answer that, and you&#8217;ll have a much easier time coming up with ideas.<\/p>\n\n\n\n<p>Now, the answers to those questions vary by business. That being said, here are 10 different answers that could apply to a variety of organizations. At the end of each one, I&#8217;ll tell you the easiest way to try it.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">1. Understand unstructured data<\/h2>\n\n\n\n<p>Most of the information that comes into your business isn&#8217;t structured. I&#8217;m talking about things like customer emails, PDF purchase orders, scanned packing slips with notes written on them, or even spreadsheets where every customer uses a different layout.<\/p>\n\n\n\n<p>Software has never been able to do much with any of that. Usually, you need a person to read each one and type it into the system.<\/p>\n\n\n\n<p>AI can read all of it&#8230;and understand it. For instance, suppose a customer writes, &#8220;Send us our usual plus 50 more of the widgets from February, the ones in the box with the red logo on it.&#8221; Today, someone has to figure out who &#8220;us&#8221; is, what &#8220;our usual&#8221; means, and which SKU comes in a box with a red logo. AI can look up the customer, find their usual order, match the SKU, and draft the order for someone to approve.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img decoding=\"async\" src=\"https:\/\/d4ey5ve3eb27c.cloudfront.net\/img\/blog\/ai-10-things-01-email-to-order.webp\" alt=\"Illustration: a customer email asking for their usual order plus 50 more widgets, beside the draft order AI built from it, awaiting approval\"\/><figcaption class=\"wp-element-caption\"><em>Illustration. The email comes in on the left. The draft order on the right is what a person approves before anything ships.<\/em><\/figcaption><\/figure>\n\n\n\n<p><strong>Try this first:<\/strong> Start with the most common piece of unstructured data you deal with. For instance, suppose you receive vendor invoices every day. But, no two vendors format them the same way, so someone in AP is stuck manually entering data. Let AI read each invoice and fill in the entry, and have that person check it before it&#8217;s saved. After a month, you&#8217;ll know how often the AI got it right and which vendors trip it up. That tells you whether or not this is an area worth automating with AI.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">2. Answer &#8220;What&#8217;s going on with order 12345?&#8221; in one place<\/h2>\n\n\n\n<p>Here&#8217;s a question that takes 15 minutes to answer in a lot of companies: &#8220;What&#8217;s going on with order 12345?&#8221;<\/p>\n\n\n\n<p>Someone checks the order system and sees the order is on hold. They open the credit system to find out why. Then the warehouse system, then the carrier&#8217;s website. If they still don&#8217;t have the whole story, they log into the CRM to see if the customer already called. Fifteen minutes and six different screens later, they have half an answer.<\/p>\n\n\n\n<p>AI can pull from all of those systems at once and write one answer: &#8220;Order 12345 is on credit hold. The customer is $12,400 over their limit, and their last payment was 52 days ago. The shipment is staged and ready to go. I&#8217;d suggest contacting AR about a limit increase, or asking the customer for a partial payment to release the hold.&#8221;<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img decoding=\"async\" src=\"https:\/\/d4ey5ve3eb27c.cloudfront.net\/img\/blog\/ai-10-things-02-one-answer.webp\" alt=\"Illustration: six system windows for orders, credit, warehouse, carrier, CRM, and email beside one assistant answer explaining why order 12345 is on hold\"\/><figcaption class=\"wp-element-caption\"><em>Illustration. Today someone opens the six screens on the left. AI reads all six and writes the answer on the right.<\/em><\/figcaption><\/figure>\n\n\n\n<p>Of course, you could pull data from different systems together without AI. The difference is that AI can read all of it together and explain what it means.<\/p>\n\n\n\n<p><strong>Try this first:<\/strong> Start in one area, for instance, orders on hold. They take the most digging, and the answer is spread across two or three systems. Give AI read-only access to those and have it write one paragraph per held order, ending with what it recommends. Keep it read-only until you trust it. If your team stops opening five screens to answer &#8220;Why is this on hold?&#8221;, it&#8217;s working.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">3. Let anyone ask the database a question, then ask a follow-up<\/h2>\n\n\n\n<p>How many times a day does someone ask IT for data? Maybe a sales rep needs an order status. Or, the CFO has a question on Sunday night when nobody&#8217;s around to run a report.<\/p>\n\n\n\n<p>With AI, they can type the question and get the answer from the database. They don&#8217;t need to know SQL, and they don&#8217;t need to open a ticket.<\/p>\n\n\n\n<p>One of the best parts of this approach is that users can have conversations with their data. &#8220;Show me my top 10 customers by revenue.&#8221; &#8220;Now just manufacturing.&#8221; &#8220;Compare that to last quarter.&#8221; &#8220;Write a summary for my boss.&#8221; Each question builds on the last one. Traditional reports can&#8217;t do that. Every question starts over with a new filter or a new report.<\/p>\n\n\n\n<p><strong>Try this first:<\/strong> Pick the person who asks you for reports the most, and give them access to the one database those reports come from. Before you hand it over, spend an hour describing your tables and fields. The answers are only as good as those descriptions. Then leave them alone with it for two weeks and read the questions they asked. Some will be questions nobody ever asked before. That list tells you what to build next.<\/p>\n\n\n\n<p>Want to see what this looks like? Here&#8217;s a video of it in action:<\/p>\n\n\n\n<div style=\"position:relative;padding-bottom:56.25%;height:0;overflow:hidden;\"><iframe style=\"position:absolute;top:0;left:0;width:100%;height:100%;\" src=\"https:\/\/www.youtube-nocookie.com\/embed\/yHGP7aiwsn4\" title=\"Build AI-Powered Analytics Over Your Database | The m-Power Platform\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen loading=\"lazy\"><\/iframe><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">4. Handle the cases nobody wrote a rule for<\/h2>\n\n\n\n<p>Business rules are great at the cases someone thought of. Everything the original developer planned for gets handled.<\/p>\n\n\n\n<p>But&#8230;what about the problems nobody planned for? Maybe a purchase order doesn&#8217;t match any approval rule. Or, there&#8217;s complaint that&#8217;s part billing problem, part quality problem, and part &#8220;we might lose this customer.&#8221; Maybe an order looks normal except for one detail that&#8217;s a little off.<\/p>\n\n\n\n<p>Without AI, those cases might go to an employee. Someone has to dig into each one and decide what to do.<\/p>\n\n\n\n<p>AI can look at those and make a recommendation with a reason. For example: &#8220;This PO is unusual because the vendor changed their pricing last month, but the total is still within budget. I&#8217;d approve it and let procurement know to renegotiate before the next order.&#8221;<\/p>\n\n\n\n<p><strong>Try this first:<\/strong> Find the process that someone works through by hand on a regular basis. Things like held orders, flagged POs, whatever it is. Have AI go through the same queue first and write one line on each: Where it should go and why. The person still makes every decision. What you&#8217;re testing is how often they agree with the AI. Once they&#8217;re agreeing most of the time, let the easy ones through on their own.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">5. Watch things overnight and flag what&#8217;s unusual<\/h2>\n\n\n\n<p>Every company runs scheduled jobs. They execute on a timer, dump output, and trust a person to read it.<\/p>\n\n\n\n<p>The problem is that scheduled jobs have no judgment. They can&#8217;t tell the difference between a routine result and an urgent problem.<\/p>\n\n\n\n<p>An AI agent can run on the same schedule, but it can decide what matters. It scans yesterday&#8217;s orders, finds the ones that are actually unusual out of hundreds, and posts a short briefing. The same idea works for a sales briefing. One agent, and every rep gets a summary of only their own accounts.<\/p>\n\n\n\n<p>I&#8217;d keep an agent like this read-only while you test it. Also, put one person in charge of reviewing its output and deciding whether or not it should keep going.<\/p>\n\n\n\n<p><strong>Try this first:<\/strong> Take a common report, and run the same data through AI overnight and have it write a half-page summary with the exceptions on top. Let the person read both for a couple of weeks. If the summary catches everything they would have caught, you&#8217;ve given them back 20 minutes a day. If it misses something, you&#8217;ve learned what the AI needs to be told.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">6. Add and update records by chat, with a person confirming<\/h2>\n\n\n\n<p>Most of what AI does with your data is read it. This one writes to it, which is where most IT leaders (rightly) get nervous.<\/p>\n\n\n\n<p>Here&#8217;s how it can work safely. A user tells the assistant, &#8220;I need to add a new customer.&#8221; The assistant asks for the fields it needs, and the user fills them in. Then, before anything touches the database, the user sees everything the assistant collected and has to click Confirm. That&#8217;s the human in the loop. The AI never writes to the database on its own.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img decoding=\"async\" src=\"https:\/\/d4ey5ve3eb27c.cloudfront.net\/img\/blog\/ai-10-things-06-human-in-the-loop.webp\" alt=\"m-Power assistant asking for customer name, city, and state after a user says they want to add a new customer, with a Submit button\"\/><figcaption class=\"wp-element-caption\"><em>Human in the Loop in m-Power. The assistant asks for the fields it needs, and nothing is saved until the user clicks Submit.<\/em><\/figcaption><\/figure>\n\n\n\n<p><strong>Try this first:<\/strong> Pick a form people fill out away from their desk, like logging a customer call or a site visit. Have the assistant ask for the details and read them back before saving. You&#8217;ll find out quickly whether people prefer it to the form. If they do, move on to the forms with more fields.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">7. Draft the follow-ups nobody has time to write<\/h2>\n\n\n\n<p>Some things don&#8217;t get done because nobody has time. Overdue invoices pile up because nobody in AR can write 40 individual emails a day. Quotes go stale because the rep who sent them got busy.<\/p>\n\n\n\n<p>AI can write those drafts from your data. An overdue-invoice assistant reads each customer&#8217;s payment history and writes a note that fits their situation. A quote follow-up mentions the actual products and prices from the quote.<\/p>\n\n\n\n<p>The rule I&#8217;d set is simple: AI writes the drafts, but people are in charge of sending. Once you&#8217;ve read a few weeks of drafts you would have sent without changing a word, then decide which ones can go out on their own. That being said, there are some that should always get sent by a person. For instance, the $40,000 invoice reminder should probably always wait for a person.<\/p>\n\n\n\n<p><strong>Try this first:<\/strong> Pick the follow-up your team is worst at. For most companies, it&#8217;s overdue invoices. Have AI draft a reminder for every invoice past terms and put the drafts in a queue. Every morning, someone in AR reads them and sends the ones they agree with. Keep a tally of how many went out unchanged. When it&#8217;s most of them, start sending the small ones automatically and keep the big ones in the queue.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">8. Answer questions from your own handbooks and procedures<\/h2>\n\n\n\n<p>Every company has answers buried in documents. For example, the employee handbook, your SOPs, years of support history, contracts, etc&#8230; New hires can&#8217;t find them, so they ask a senior person, and the same questions get answered over and over.<\/p>\n\n\n\n<p>AI can search those documents by meaning instead of by keyword and answer the question directly. For instance, a question like &#8220;How many vacation days do I get after five years?&#8221; is answered from your policy.<\/p>\n\n\n\n<p>Of course, you should always be careful with permissions when setting up something like this. A good rule of thumb: If someone couldn&#8217;t open the original document, they shouldn&#8217;t get its contents from a chatbot either.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img decoding=\"async\" src=\"https:\/\/d4ey5ve3eb27c.cloudfront.net\/img\/blog\/ai-10-things-08-handbook-answers.webp\" alt=\"Meridian HR Assistant answering a vacation carryover question from the policy document, then declining to show another employee's balance\"\/><figcaption class=\"wp-element-caption\"><em>The HR assistant we built in m-Power for a demo. It answers the carryover question from the policy document, then declines to show another employee&#8217;s balance.<\/em><\/figcaption><\/figure>\n\n\n\n<p><strong>Try this first:<\/strong> Upload the employee handbook and nothing else. Give it to one team and tell them to ask it the questions they&#8217;d normally ask HR. After two weeks, ask HR whether the questions they get have changed. If they have, add the next set of documents. If they haven&#8217;t, find out what people asked and where the answers fell short.<\/p>\n\n\n\n<p>If you&#8217;d like to see what this look like in action, check out this video:<\/p>\n\n\n\n<div style=\"position:relative;padding-bottom:56.25%;height:0;overflow:hidden;\"><iframe style=\"position:absolute;top:0;left:0;width:100%;height:100%;\" src=\"https:\/\/www.youtube-nocookie.com\/embed\/pAg6kiHMyUU\" title=\"How to Build an HR AI Agent Over Your Own Database | The m-Power Platform\" frameborder=\"0\" allow=\"accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share\" referrerpolicy=\"strict-origin-when-cross-origin\" allowfullscreen loading=\"lazy\"><\/iframe><\/div>\n\n\n\n<h2 class=\"wp-block-heading\">9. Explain the code nobody wants to touch<\/h2>\n\n\n\n<p>Every company has at least one system that was built years ago by someone who&#8217;s gone. Nobody fully understands it, and nobody wants to touch it. The business rules live in the code and nowhere else.<\/p>\n\n\n\n<p>This is where AI shines. It can read the code and explain what it does, which business rules are buried in it, and what would break if you changed something. A developer asks, &#8220;What happens if I change this field?&#8221; and gets a list of every program and integration that uses it, instead of spending days tracing it by hand.<\/p>\n\n\n\n<p><strong>Try this first:<\/strong> Pick the one program everybody&#8217;s afraid to touch. Have AI write up what it does and list the business rules buried in it. Then hand that write-up to the person who knows the program best and ask them to mark what&#8217;s wrong. You&#8217;ll end up with documentation that didn&#8217;t exist before, and you&#8217;ll know how far to trust the AI on the next one.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">10. Give customers a portal that answers &#8220;Where&#8217;s my order?&#8221;<\/h2>\n\n\n\n<p>Your customer service team answers the same questions all day. Where&#8217;s my order? Can you resend my March invoice? What&#8217;s my balance?<\/p>\n\n\n\n<p>A customer portal helps, if customers can find what they need in it. An assistant added to the portal takes it further. The customer asks the question the way they&#8217;d ask a person, and the assistant answers from the ERP, under that customer&#8217;s own login. They see their orders and their invoices, and nobody else&#8217;s.<\/p>\n\n\n\n<p><strong>Try this first:<\/strong> Ask your customer service team what customers call about most. It&#8217;s almost always &#8220;where&#8217;s my order.&#8221; Build an assistant that answers only that, from the same order data the portal already shows, and put it in front of a handful of customers you know well. If the calls from those customers drop, roll it out to everyone else.<\/p>\n\n\n\n<p><strong>What this looks like in m-Power:<\/strong> Companies have been building customer portals over their ERP data with m-Power for years. Adding an assistant means building one in the AI Studio with a tool over the same order and invoice data the portal already uses. Then you apply row-level security so each customer only sees their own records. <a href=\"https:\/\/www.mrc-productivity.com\/solutions\/ai.html\">See how teams build AI tools over their data with m-Power<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Where to start<\/h2>\n\n\n\n<p>What are the common themese across those 10 ideas? Messy input, manual data entry, judgment calls, and the ability to understand text and code.<\/p>\n\n\n\n<p>Any process in your business with one of those is a candidate. To test it out, start small. Pick the smallest example. Let AI draft or recommend, and keep a person approving the result until you know where it gets things wrong.<\/p>\n\n\n\n<p>That&#8217;s also what separates the projects that pay off from the ones that don&#8217;t. According to McKinsey&#8217;s November 2025 State of AI survey, 88% of companies use AI somewhere, but only 39% see any impact on earnings. The companies that do see it were 2.8 times more likely to have redesigned the process around the AI, instead of adding a tool to a process that didn&#8217;t change.<\/p>\n\n\n\n<figure class=\"wp-block-image aligncenter\"><img decoding=\"async\" src=\"https:\/\/d4ey5ve3eb27c.cloudfront.net\/img\/blog\/ai-10-things-mckinsey-chart.webp\" alt=\"Bar chart: 88% of companies use AI regularly in at least one business function, 39% report any impact on company-wide EBIT. Source: McKinsey, The State of AI, November 2025\"\/><\/figure>\n\n\n\n<p>Every one of these ideas gives AI access to some of your data, so every one is a security decision too. Before you start, answer these: What data can it see? Whose permissions apply? Which model does it use, and what gets sent to it? Who can turn it off? Answer those once, on a platform you control, and you can reuse the answers for every project after that, instead of working them out again for each new tool.<\/p>\n\n\n\n<p>That&#8217;s why we built the AI features into m-Power itself. m-Power is a low-code development platform from mrc, a software company in business since 1981 with more than 1,500 customers. It installs in your environment and builds applications and AI tools directly over the databases you already have. IT controls what data the AI can access, who can use each tool, and which model runs, under the same security model as every other m-Power app. And when a project outgrows your team, our support and services people can step in. They build with m-Power every day.<\/p>\n\n\n\n<p>Many of these are things you can build in m-Power today. If one of them looks like a problem you have, <a href=\"https:\/\/www.mrc-productivity.com\/aw\/mpower-demo.html\">request a demo<\/a> and tell us which one. We&#8217;ll set up a demo that&#8217;s specific to your situation.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\">Frequently asked questions<\/h2>\n\n\n\n<p><strong>How can a small business start using AI?<\/strong><\/p>\n\n\n\n<p>Pick one process with messy input or a manual investigation, and start with the smallest version. AI drafts, a person approves. One inbox, one report, or one exception queue is plenty. Measure the time it saves before you expand.<\/p>\n\n\n\n<p><strong>What data does AI need access to?<\/strong><\/p>\n\n\n\n<p>Only what the use case needs. A collections assistant needs invoices and payment history, not your whole customer database. And permissions should match what the user could already see on their own. If someone couldn&#8217;t open a record before, the AI shouldn&#8217;t show it to them now.<\/p>\n\n\n\n<p><strong>Do we need our own AI model?<\/strong><\/p>\n\n\n\n<p>No. You can connect a commercial model, or run one on your own servers. The decisions that matter are who approves the model, what data it&#8217;s allowed to receive, and whether you can swap it out later.<\/p>\n\n\n\n<p><strong>What should we not use AI for first?<\/strong><\/p>\n\n\n\n<p>Anywhere a wrong answer is expensive and nobody reviews it. Customer-facing pricing, payments, and compliance decisions can wait. Start where a person checks the work before it takes effect.<\/p>\n\n\n\n<p><em>Sal Stangarone is President of mrc and has been at mrc since 1990. mrc has helped businesses build custom applications over their own databases since 1981.<\/em><\/p>\n","protected":false},"excerpt":{"rendered":"<p>Stop asking what to build with AI. Ask what AI can do that your software can&#8217;t. Ten answers, each with the easiest way to try it first.<\/p>\n","protected":false},"author":8,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":true,"template":"","format":"standard","meta":{"site-sidebar-layout":"default","site-content-layout":"default","ast-global-header-display":"","ast-main-header-display":"","ast-hfb-above-header-display":"","ast-hfb-below-header-display":"","ast-hfb-mobile-header-display":"","site-post-title":"","ast-breadcrumbs-content":"","ast-featured-img":"","footer-sml-layout":"","theme-transparent-header-meta":"","adv-header-id-meta":"","stick-header-meta":"","header-above-stick-meta":"","header-main-stick-meta":"","header-below-stick-meta":"","slim_seo":{"title":"10 Things AI Can Do That Your Current Software Can't - mrc&#039;s Cup of Joe Blog","description":"Stop asking what to build with AI. Ask what AI can do that your software can't. Ten answers, each with the easiest way to try it first."},"footnotes":""},"categories":[140],"tags":[138,153,154,137],"class_list":["post-15722","post","type-post","status-publish","format-standard","hentry","category-ai-for-it-teams","tag-ai-agents","tag-ai-for-it","tag-ai-use-cases","tag-artificial-intelligence"],"_links":{"self":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/15722","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/users\/8"}],"replies":[{"embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/comments?post=15722"}],"version-history":[{"count":5,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/15722\/revisions"}],"predecessor-version":[{"id":15730,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/posts\/15722\/revisions\/15730"}],"wp:attachment":[{"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/media?parent=15722"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/categories?post=15722"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.mrc-productivity.com\/blog\/wp-json\/wp\/v2\/tags?post=15722"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}