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.

Tell me what's eating your week How I work

Approving still happens. Chasing it doesn't.

How it's priced
Fixed price, paid spec first
Timeline
Weeks, not quarters
Capacity
One assessment, one build at a time
Where it runs
Your accounts, not mine

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, all of it running somewhere today.

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

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.

I'd rather say that in week one than invoice for it in week six.

Running in production

Three systems, in daily use.

Systems I built and still keep running. The organizations stay unnamed — the same discretion you'd get.

14 months, 3 sites, one pipeline

A content pipeline at a 40-person national nonprofit. Staff post a request in the tool they already use; a scheduled draft appears with a reply on the thread.

Plain English in, citations out

Document search across years of Word files, PDFs and old project archives. Every answer comes back with the source it came from.

6 integrations, 1 sign-on, PII stripped

From government data APIs to an applicant-tracking system, with personal information redacted before it ever reaches a model.

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. A bad estimate is mine to absorb.
A hard end dateWeeks, not quarters. Anything that can't finish in weeks gets cut into pieces that can.
Your accounts, not mineYour hosting, your keys, your data — handed over 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

Who you'd be working with

Filer Labs is one person: me, Jacob Filer, working out of Missouri. The person who scopes your project is the person who builds it — which is why there's only ever one assessment and one build in flight.

Every system on this page I built myself and still keep running.