Local AI Setup for Small Businesses

Local AI agents draft. A person reviews. A reply waits in front of the person who would have typed it. A change to a FileMaker record waits the same way. The model is the helper. The review is the product.

iRusty is Russell Haney’s practice at 113 Sailfish Way, Brunswick, Georgia, in the Golden Isles. He has 35+ years with business software. He runs his own business on a local OpenClaw agent setup on a Mac, and he sets these up for clients from that daily use. That is the firsthand part. It is not a time saved or a count of shops. Brunswick is the only office. Georgia, Florida, South Carolina, North Carolina, Jacksonville, and the rest of the country are served from there.

Hardware, cloud, and hybrid

A local model has to fit on the machine. A current Mac or PC is the usual start. A very old computer, or one with very little memory, can make the agent slow enough that nobody will use it. If the machine already struggles to open the tools the shop uses all day, do not pile a local model on top of it. Use a stronger computer, or keep that job in a reviewed cloud step.

A cloud model is the better choice when the question is hard and rare, when the local machine cannot hold a model good enough for the draft, or when you already have a reviewed path and the text in that path is safe to send. Private AI does not mean “never use a cloud model.” It means you do not paste the customer list into a public chat because the box was easy.

A hybrid setup is the ordinary version. Customer records and the FileMaker file stay on the machine you control. A private connection to OpenAI or Claude is used only for the draft that needs a larger model, and only for the fields you chose to send. The reply still waits for a person. Hybrid is a choice you can point at. It is not a leak you find later.

FileMaker shops are the other clear fit. The file already holds the work. The owner wants an agent that can read a record, draft a summary, or propose a next step, and then stop. If the file is fragile, the first job is FileMaker rescue, not an agent on a mess. If the agent must call out and write back under review, that is FileMaker AI integration.

Email and document intake

A hypothetical shop retypes bills, forms, and customer email into the system of record. A local agent can read a document on the machine, or a message saved where it is allowed to look, and draft who it is from, what it asks, and which record it might match. A person checks that draft before a record is created. Unmarked mail does not become a task because a model thought it looked urgent.

Drafting replies for review

A hypothetical office wants a first draft that already knows the job notes on the machine. The agent writes the draft. The person edits it and sends it, or throws it away. The agent does not send mail.

Summaries, research, and scheduled reports

A long customer history or a FileMaker record full of comments can be drafted into a short brief for the person who is about to call. Research means the agent looks through material the business already stored and comes back with a draft. A scheduled report is that habit on a clock: what changed in the records the agent was allowed to see. This page does not claim the report found revenue or saved hours.

Working alongside FileMaker

A hypothetical FileMaker user wants a local agent to look at one job, draft the missing note, and stop. FileMaker remains the system of record. The agent does not get a full-access account. A person accepts the note before it is written back. If that write needs a script or Insert from URL, it is scoped as FileMaker AI integration, with the same review.

Models are described in generic terms on purpose. They are open-source models that run on your own hardware, or a private connection to OpenAI or Claude when the local model is the wrong tool for that step. This page does not name other products. The exact tool list is not confirmed beyond OpenClaw, and it should not be guessed in public copy.

1. Discovery call. You say what the agent should draft, what it must not see, and whether FileMaker is the system of record. A free 20-minute call is the published way to start. If the real problem is a broken FileMaker file, the $500 Rescue Diagnostic is the published first look at that file. It is not a local-AI package price.
2. Setup. OpenClaw goes on the Mac or PC you choose. The agent is pointed at the folders, mail, or exports you named. It is not pointed at the whole disk because that was faster to click.
3. Security hardening. Accounts, keys, and what leaves the machine get a pass before anyone calls the setup finished. A cloud step, if you want one, is a private connection you can see, not an accident.
4. Training. The person who will review drafts learns what the agent may do, how to throw a bad draft away, and when not to use it.
5. Ongoing support or a retainer uses the same published terms. Hourly work is $220/hr. Fixed-price support is 50% upfront and 50% on delivery. This page does not invent a monthly number.

Call (912) 736-3477, email russellhaney@irusty.com, or use the contact page. Send the problem. Do not send passwords or the production file.

A hybrid step changes the claim, so it has to be visible. If a draft needs a private connection to OpenAI or Claude, the text you chose to send does leave the machine for that call. Do not call that step fully local. Keys for that call do not belong on a sticky note, in a shared inbox, or on a FileMaker layout a user can read.

The agent should not see more than the job. A folder of active jobs is a boundary. The whole disk is not. Customer, medical, legal, and financial detail stays out of the prompt unless that workflow needs it and a person agreed. A hypothetical clinic or law office gets that same boundary. It does not get a certification claim.

A draft can smooth over a fact. The person who knows the customer will see that. An unattended send will not. A FileMaker write waits the same way.

A local agent on a machine with no backup is a reliability problem too. If FileMaker is involved, get a backup-aware plan before the agent is pointed at the file. Passwords and production files still do not belong in ordinary email.