Which answers that should be easy to get always take too long?

Most of the businesses I meet have been told the same two things: that they need a system, and that it costs more than the problem does.

Are you dealing with any of the following?

The business runs on a few Excel files that don’t agree with each other, and somebody spends their week keeping them in line.

Something gets checked by hand, in person, because there is no other way to know.

You bought software before, and it does a hundred things you don’t need and not the few that would help.

Someone told you that AI would sort it out, but nobody looked at your numbers first.

None of that is a technology problem yet. It is a question of what you actually do all day, and which part of it is costing you the most.

So what has changed?

Until recently you had two options: a product built for somebody else’s business, or something built for yours at a price that only a big company could carry. That is no longer true. Building something that fits one business no longer has to cost what it used to.

What has not changed is the part everyone skips. A tool built on the wrong problem is expensive at any price, and most of the tools you were quoted for were built on somebody else’s problems.

How would we start?

If you want to find the real problem, I would start by learning how you actually work. I come to you. I talk to the people who do the work, not only to whoever is in charge of it. I look at the files you really use, the ones with the notes in the margins, rather than the ones somebody made for a meeting. I watch the chore that everyone has stopped noticing.

Then we pick the one thing worth fixing first, and I build you a working tool to fix it. You try it out on your own business and tell me where it is wrong, and we keep adjusting until the tool fits the chosen thing.

It takes a few days, it is paid work, and the price is fixed before we start.

What do I get at the end?

Two things.

A short written read of what I found, in plain language, including what I would do next and what I would leave alone. It is yours to keep and to hand to anyone you like. Everything else we find goes on the list for later, with what it would take.

And, for most jobs, something that works: the one thing that hurts most, built so you can try it on your own business and see whether it does what you hoped. Not a presentation of what it could look like one day.

Then you decide, knowing what the rest would cost. There are three ways it can go, and I will give you my recommendation.

Your own people can take it from here. The read tells them what to do, and they do it.

It needs someone else, and now you can ask for exactly what you need instead of listening to what a supplier wants to sell you.

You have something that works, you know what the next step costs, and we carry on.

And after it works?

I write the first training documents, because explaining a thing clearly is part of building it.

And I’ll be available for the changes: when the business grows, when you add a line of work, when a new rule changes how something has to be recorded. That is the part I like, and it is when a small system either keeps up with you or starts holding you back.

The day-to-day running stays with you, and you are free to call anyone you want for it. Nothing I build locks you to me, and your data stays yours.

What about AI?

I use it, and I will always tell you where. I question everything it produces and check everything that goes out, the same as I have done for my own work for years.

There is almost always a way to build the same thing without it. If that is the version you prefer, that is the version I will build. No black boxes.

So where would we begin?

With the answers that take too long. Write to me at dorithkleinstein@gmail.com and tell me what the situation is, as you see it. A few lines are plenty. If I think I can help, I will tell you what the first step would look like and what it costs, before you commit to anything. If not, I will tell you that too.