Systems that take the manual work out of how a small organization runs.
I'm Jacob Filer. I build automation — increasingly AI — that gets deployed, adopted, and left running. And I'll tell you which of the things on your list you shouldn't build at all.
Approving still happens. Chasing it doesn't.
Where this usually starts
Most of this work begins with a sentence somebody says out loud in a meeting.
“The newsletter takes two days.”
What I build insteadA pipeline: the request goes in, a formatted, scheduled draft comes back in your email platform or on your site.
“We export from the CRM and re-key it into the website.”
What I build insteadAn integration between the two systems, so there's nothing to re-key and one place to fix a bad record.
“Someone builds the board report by hand every month.”
What I build insteadThe assembly done on a schedule, so the person who used to rebuild the report reviews it instead.
“We pay for ChatGPT and nobody really uses it.”
What closes the gapOne narrow tool pointed at work people already do — not another login. (92% of nonprofits report using AI; 7% have anything to show for it.)
Very little of this is an AI problem. Most of it is plumbing.
What I build
Five kinds of work, most of it already running.
Systems I built and still keep running. The organizations stay unnamed — the same discretion you'd get.
What I'll tell you not to build
Most organizations bring me a list. Usually a third of it shouldn't be built.
Some of it is a process problem wearing a software costume. Some of it is a feature you already pay for in a tool nobody finished setting up. Some would save four hours a month and cost more than that to keep alive.
How I work
Fixed price, named deliverable, hard end date.
Tell me what's costing you the most time.
Describe the workflow, and I'll tell you what I think it takes — or that it isn't worth doing. If it looks like a fit, we'll get on a call before you pay for anything.