---
title: "We built our own software with AI. Why isn’t the team using it?"
author: Garrett Winder
updated: 2026-11-19
url: https://garrettwinder.com/built-with-ai-team-wont-use-it/
---

# We built our own software with AI. Why isn’t the team using it?

Usually because it was built around everything the company knows, and each person needs only a few things when the work reaches them. Building with AI lets you skip the step where someone works out who does what and when. I watch the work change hands, keep the guts of what you built, and rebuild it around that.

## Why does the team go back to the old way?

Because the old way shows each person the few things they need, and the new tool shows them everything. When an owner builds with AI, the tool fills up with what the owner knows: every field, every report, every rule learned over the years. That knowledge is correct, and it’s the most valuable thing in the tool.

The trouble is where it lands. Someone doing one job opens a screen and has to hunt for their part among everyone else’s. Their old spreadsheet or notepad only ever held their part, so it’s quicker, and they go back to it.

Big companies hit the same thing. MIT researchers studied AI tools built inside large companies and reported in 2025 that most fail due to “[brittle workflows, lack of contextual learning, and misalignment with day-to-day operations](https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf).” Those companies had whole departments on the project. The last item on that list is the one I see in small companies: a tool that doesn’t line up with what a person does on a given day.

## What did building with AI skip?

It skipped the process custom software has always followed: start with strategy, work out who does what and when, then build on tried and true design patterns. AI builds whatever you describe, in whatever order you describe it, so none of those steps is forced on you.

Strategy is deciding what the software is for, usually one or two things in the business that should get faster or stop going wrong. Who does what and when is following a piece of work from the first phone call to the last invoice and writing down who touches it, what they need in front of them at that moment, and what they hand to the next person. Design patterns are the ways of laying out a screen that people already know from every other program they use, such as a list they can search or a form that asks for things in the order they have them.

An owner knows all of this already, and it stayed out of the tool because the AI never asked for it.

## Do we have to start over?

No. The guts of what you built stay. The data, the rules, the calculations and your company’s own names for things are the hard part of any software project, and you’ve already done it. What changes is what each person sees when the work reaches them.

I read the code first. Then I come to your office, in Parker County or west Fort Worth, and watch the work change hands. After that I rebuild the screens around who does what and when, one job at a time, while the tool you built keeps running.

Bringing in someone from outside is common at big companies too. The same MIT report found that AI tools built with an outside partner [succeeded twice as often as ones built in-house](https://mlq.ai/media/quarterly_decks/v0.1_State_of_AI_in_Business_2025_Report.pdf). Whoever built the tool knows where everything is, and can’t see it the way someone opening it cold does.

If the tool also isn’t finished underneath, that’s a separate job. I cover it in [who to hire to finish a tool you built with AI](/finish-ai-built-app/).

## What does this look like in a mineral company?

A mineral buyer I work with built its own tool with AI. Everything the company knew went into it. Every screen showed everything, the team found it overwhelming, and they kept working the old way.

Nothing in the tool is wrong. What’s in it is what the company runs on, so I’m keeping it and rebuilding the tool around what each person does.

Mineral companies are prone to this because the jobs differ so much. A landman running title, a buyer making offers, an analyst valuing a tract and an owner watching the pipeline all draw on the same records, and each needs something different from them. A single screen that tries to serve all four ends up too crowded for any one of them.

So each job gets a short view with what it needs for the next decision, and everything else stays a click away.

## Next step

I have room for three more companies. $2,000 to $6,000 a month, month to month. It starts with an hour at your office, at no charge. Show me what you built, and I’ll tell you what I’d do next. [Email me](mailto:gw@garrettwinder.com) to pick a day.

---

By [Garrett Winder](https://garrettwinder.com/index.md), who builds custom software for small businesses in Parker County and west Fort Worth, Texas.
