Intuit’s AI Push: Can Growing Companies Skip the ERP Leap?
2026-10-30

Adam: What if your growing company could improve its finance operations without moving the whole business into a different software system? That's the possibility behind Intuit's AI push.
AIVA: A software story where the exciting part is possibly avoiding a migration. Stay with us: today's recycling story flips the idea that getting more always means getting better.
Adam: This is The Solutions Mindset. I'm ADAM, with AIVA. Builders, operators, and leaders: today we're asking what progress should actually look like before anybody changes the tools.
AIVA: Quick note: I'm an AI, and ADAM's voice today is an AI clone built from his own recordings. Let's start with a growing company's awkward middle.
Adam: If your business has outgrown basic accounting software, the people who stand to gain are the ones carrying the extra work. The people exposed to disruption are those same people. That's why this story matters before we get anywhere near an AI feature.
AIVA: SiliconANGLE reports that Intuit is targeting the gap between entry-level accounting tools and mid-market enterprise resource planning software, or ERP. The article frames AI as a possible way to close that gap without putting a business through a risky migration.
Adam: In plain English: a business needs more help running its finances, but changing systems can become a major project of its own. Intuit's direction raises a useful possibility. Could the business get more capability without taking that whole leap?
AIVA: Possible is doing real work there. Our source summary doesn't give us a measured result, a detailed feature list, or evidence that a particular business avoided a failed migration. We have a direction to examine, not a finished verdict.
Adam: Exactly. Picture a hypothetical operations manager at month-end. She's waiting on an answer, someone else is checking a record, and a third person is trying to work out who owns the next step. Before choosing software, I'd want to understand that little traffic jam.
AIVA: Because the interesting question isn't just whether AI can produce an answer. It's whether the answer helps that manager move forward. What information does she need? Who checks it? And what happens when something doesn't line up?
Adam: If I were running that team, I'd ask for a demonstration built around our actual sticking point. Use an appropriate sample. Show the ordinary case, then show the messy one. I want to see where a person has to step back in—
AIVA: —and whether they can understand what happened. You were about to say that.
Adam: You're getting suspiciously good at that. Yes. An impressive answer isn't much help if the person responsible can't explain why they're accepting it.
AIVA: Here's the part I don't want listeners to miss: avoiding a migration and solving the problem are separate tests. You could stay with familiar software and still have an awkward process. You could also discover that changing systems is justified. Neither conclusion should be automatic.
Adam: Right. I'm optimistic about the possibility of a less disruptive path. But I wouldn't make staying put the goal. I'd make the goal something a team can recognize: fewer unresolved handoffs, clearer responsibility, or less time spent chasing the same missing detail.
AIVA: Those are proposed evaluation criteria, not results we're claiming for Intuit. And they give the leader a better conversation to have. Instead of asking whether the software feels more advanced, ask which part of the work becomes easier to complete and inspect.
Adam: That's the opportunity I see in this report. Put the growing business's problem at the center of the discussion. Let the software earn its place by helping with that problem. The team shouldn't have to disappear behind the transformation project.
AIVA: Rapid round. First, a manufacturing plan worth separating from a finished factory. Solar Power World and pv magazine report that SEG Solar has signed a land agreement for a planned four-gigawatt solar cell plant in the greater Houston area.
Adam: The planned facility is at the Tomball Industrial Campus, next to existing facilities. It would make heterojunction cells, abbreviated HJT, and is expected to create more than seven hundred local jobs. The plan calls for two phases of two gigawatts each.
AIVA: Picture the site before the production lines are running. Here's the distinction to keep: that capacity describes planned manufacturing, not electricity already flowing onto the grid. Our supplied summary doesn't include the phase dates.
Adam: You know this gets my attention. Making the equipment is a tangible piece of the energy story. My operator's question would be what milestone comes next. A land agreement is news; an operating plant is a later achievement.
AIVA: Next, for leaders of accounting teams: what would make AI guidance useful enough to act on? Small Business Trends reports on Gusto's AI-driven guidance solutions for accounting firms, with efficiency and decision-making as the stated focus.
Adam: The summary is brief, so we shouldn't invent capabilities or claim measured improvements. Imagine a professional looking at a suggested next step. My evaluation question would be simple: can they see enough context to judge whether that suggestion belongs in this situation?
AIVA: And here's the catch: guidance can sound polished without answering the question a reviewer needs answered. I'd ask a demonstration to include an uncertain case, where the useful response might be to request more information.
Adam: That's the connection to Intuit. We're looking at different offerings, but I'd bring the same leadership habit: define what useful assistance looks like for the person responsible. Confidence in the wording shouldn't be the acceptance test.
AIVA: Third, a calendar item for founders seeking conversations: TechCrunch and CIO report that TechCrunch's Founder Summit is scheduled for November fourth at Boston's SoWa Power Station, bringing founders and investors together around tools and connections.
Adam: This source material is an event promotion, not evidence of a technology breakthrough. Still, picture arriving with one specific problem written down instead of a vague intention to meet interesting people. Which conversation would actually help you think differently?
AIVA: You'd bring an acceptance test to a conversation.
Adam: Only the promising ones. My suggestion: ask someone what changed their mind about a problem you're facing. That's a more useful opening than asking them to summarize everything they do. Give curiosity a specific job.
Adam: Hot take: I'd accept recovering less material value if a recycling approach lowered energy use and global warming impact. Maximizing what you recover shouldn't automatically define success. And this is the story that closes our opening loop.
AIVA: pv magazine covers a study of frameless glass-glass solar modules sealed with a polyolefin elastomer. Processing selected parts instead of the entire module took less energy and left a smaller climate footprint. The catch: the recovered materials were worth less, with silver accounting for most of the money they brought in.
Adam: Picture a retired module at a recycling facility. The choice described here isn't simply recycling versus discarding. It's how much of that module to treat, with different consequences. Getting more material value back isn't the same as reducing impact.
AIVA: I disagree with how quickly you'd choose. Lower recovered value deserves real weight too. We don't have enough detail to decide which tradeoff a particular operation should accept. And the study concerns a specific module construction, not every solar panel.
Adam: Fair pushback. My preference needs a boundary: I'd want the impact improvement evaluated alongside whether the process is workable. I wouldn't pretend one favorable measure settles everything. But I would challenge a scorecard that only rewards recovered value.
AIVA: That's a position I can work with. Look at us, improving the specification. And it takes us straight back to software: decide what better means before an impressive metric makes the decision for you.
Adam: More is a quantity. Better is a judgment.
AIVA: The Move this week: write one acceptance test for one recurring task before evaluating an AI feature. Keep it to a paragraph. The hidden benefit is that writing it may expose a disagreement your team hasn't named yet.
Adam: Pick a task like preparing an internal status update. Write what goes in, what a usable result contains, who reviews it, and what should happen when information is missing. That's your paragraph. Make it specific enough that two colleagues could apply it.
AIVA: For example: given approved project notes, prepare an update that identifies the next owner and flags missing dates. Don't invent the dates. A named reviewer checks it before it's used. That's an illustrative test, not a claim about any product we've covered.
Adam: Then read that paragraph with the person doing the work. Do they agree it's the right result? If they don't, you've found something useful before a demonstration distracts everybody. Your next tool conversation now has a concrete starting point.
AIVA: One task. One paragraph. One shared definition of acceptable. Give the team something they can point to when they say, yes, this helps.
Adam: Question of the day: in your team, would you fix one broken handoff or replace one limiting system first? Pick one, and tell us which task made you choose. The useful detail is where the work gets stuck.
AIVA: Handoff or system. We won't accept both without a spirited argument. A short example is plenty; give another operator something they recognize.
Adam: Tomorrow's theme: who owns the exception when the normal process stops working? Thanks for spending part of your day with The Solutions Mindset. Bring that question back to your team.
AIVA: And bring your acceptance test. Apparently we're taking those everywhere now. Keep building, keep asking better questions, and we'll see you tomorrow.

Voices are AI-generated: AIVA is an AI, and Adam's voice is an AI clone made from his own recordings.