Product
Everything you can hand overSee every feature →
Use cases
What Felesh looks like for youAll use cases →
PricingTrust
Resources
Log in

Can AI run my business for me?

No. It can keep the business known and do the work you approve, while the judgement calls wait for you. Here is where the line sits.

6 min read · · The Felesh team

The short answer

Can AI run your business for you? The question has a quiet appeal. You run the work, the people, the promises and the odd problems that fall to you. Someone asks for a price you have not thought about. A customer repeats a question you answered last week. By Friday you wonder whether a machine could simply get on with the whole thing.

The honest answer is no. Felesh does not run the business. It keeps the business known. It does the work you approve.

That is the dividing line, and it is a useful one. Execution is one thing and judgement is another. A change in price, a promise to a difficult customer, a decision about what to take on: those stay yours. What Felesh can do is keep the facts around them in order, so that you decide from what is in front of you rather than from memory.

Fig. 1 Felesh keeps the business known and does the work you approve; the judgement calls wait for you.

What AI can take off your plate

Admin is the part of a business that never ends. A call finishes and you scribble the details on whatever is nearest. You promise a customer you will sort something out, and the date lives in your head. The next step depends on you remembering it. Meanwhile the messages from the website sit beside the messages from social media, and most of them ask the same things.

None of that needs judgement. It needs care and a decent memory. It is also the work that eats your afternoon when you would rather be doing the job.

After a conversation, you type one sentence about what happened. Felesh drafts the note, the promise with its date if you gave one, and the next step. Each draft shows its reason and waits for your yes. A task is added directly, with no approval step.

The other side of admin is the customer who writes in. You teach Felesh by uploading documents and writing instructions, and it answers from those. Customer messages from your website chat and Instagram arrive in one inbox. A customer asks whether you cover their area. Another asks how long a job takes. The words are almost the same each time, and the answers come from your own wording.

What still needs you

The worry behind the question is that the machine will decide something on your behalf. A customer asks for a discount, or wants a job done in a way you have never done it. A complaint arrives that needs a careful reply. You would not hand those over, and you should not have to.

The customer conversation is where the line shows most clearly. When Felesh cannot answer a message, it does not guess. The message goes to a waiting list for you, with the reason it could not answer. Nobody is pinged and nothing is sent to the customer. When a person joins the conversation, Felesh stays quiet.

So the routine questions get routine answers, and the awkward ones reach you with a note on why. You decide the discount, the special arrangement and the careful reply. You are not pulled away mid-job by a message that could have waited, and you are not surprised by something said in your name that you never approved.

What it knows about your business

Your business lives in your head, in notes on your desk and in messages spread across your accounts. A customer calls about an old job and you have to dig. You may also wonder what the software can see.

The answer is narrower than you might fear. Felesh knows what is done on Felesh. It knows the contacts and companies you bring in from a single Excel or CSV file, and you see the column mapping and the rows before anything is saved. It knows what you upload or teach it.

Once it holds that, you can use it. You can ask Felesh questions in your own words about your work: what you promised a customer, or which jobs are still open. It answers from your own records.

You stay in charge of what it holds, and the answers are only as good as what you put in.

A day with the work approved, not run

Take an ordinary day. You start it by asking Felesh what is open and what you promised this week, and it answers from your own records.

The next call ends with a promise you are not sure you can keep. The draft waits anyway. You leave it until you have checked something. The decision is yours, and it takes the time you need.

Later you look back over the day. The notes are written and the promises are recorded with their dates. The next steps are where you can find them. Any draft you did not accept is still waiting for you. The writing and the remembering were done for you. The deciding was not.

That is what it looks like to approve work instead of handing the business over. You still carry the responsibility. What changes is the amount of paperwork standing between you and the decision.

Why the line sits there

There is a reason the line sits at your yes. A business is a set of promises made by a person, to people who expect that person to answer for them. If a tool made those promises without you, the customer would still look to you when something went wrong. Handing over the writing, the sorting and the remembering is a fair trade. Handing over the answering-for-it is not.

This is also why the answer to the question is no, and why it is a modest no. Felesh will not manage your business. It keeps your records in one place and does the drafting once you have said what happened.

Where to start

Start small. After your next conversation, type a sentence about what happened and see what Felesh drafts. You can talk to Felesh in plain words about your work, and read how drafts and approvals fit together. The yes is yours to give.

Next question Do I need a CRM when it’s just me? Often not yet. Here are the signs a notebook has stopped working, and a way to keep a record without the upkeep.