Systems that take the manual work out of how a small organization runs.

I'm Jacob Filer. I build automation, increasingly AI, that organizations adopt and keep using.

Tell me about a workflow How I work

From a system running today. A person still approves everything that goes out.

How it's priced
Fixed price, paid spec first
Timeline
Weeks, not quarters
Where it runs
Your accounts, not mine

Where this usually starts

Most of this work begins with a sentence somebody says 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.

Most of this is plumbing, not AI.

The gap

92% of nonprofits report using AI. 7% have anything to show for it.

TechSoup's 2025 survey of 346 organizations. The tools get bought. The wiring into the work people already do is what's missing, and that's the part I build.

What I build

Five kinds of work, most of it already running.

Workflow automation The copy-paste-between-systems work, with a human approving anything outward.
Content pipelines A request in one end, a formatted, scheduled draft out the other.
Document search Ask across your own documents, get answers with the source cited.
Integration & tooling APIs, membership and AMS data, dashboards, behind your single sign-on.
AI strategy & governance What to automate, what to skip, and the usage policy you don't have yet.

How I work

Fixed price, named deliverable, hard end date.

A paid spec firstScope, price and timeline in writing before code starts. You own the document either way.
Fixed priceQuoted after the spec, not adjusted after the fact. The number you agree to is the number you pay.
A hard end dateWeeks, not quarters. Anything that can't finish in weeks, I cut into pieces that can.
Your accounts, not mineYour hosting, your keys, your data, handed back with documentation someone else could run from.
The full method, packages & stack for when you want the detail

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.

jacob@filerlabs.com