Your team already pays for AI. I connect it to the work.

I'm Jacob Filer. I build automation and AI tools for nonprofits, policy organizations, associations, and small businesses.

Tell me about a workflow
  1. “Post the report.”
  2. Copy it into the website
  3. Fix the formatting
  4. Rebuild the endnotes
  5. Chase someone for approval
  6. A scheduled draft, waiting for a yes.

What I build

Most of this is plumbing, not AI.

Most nonprofits are trying AI. Only 7% have actually put it to work. The tools got bought, but nobody connected them to the documents, data, and routines people use every day. That connection is what I build.TechSoup and Tapp Network, The State of AI in Nonprofits 2025: 85.6% are exploring or using generative AI; 7% have successfully adopted it for operations and mission work.

  • AI that knows your organizationConnectors that let Claude or ChatGPT read your documents, your CRM, and the outside data your staff look up by hand, behind the same login as everything else.
  • Workflow automationThe copy-paste work between systems, done on its own, with a person approving anything that leaves the building.
  • Publishing pipelinesA finished document in one end, a formatted, scheduled draft on your website out the other.
  • Search across what you've writtenAsk a question in plain English and get an answer cited to the document it came from.
  • IntegrationsTwo systems that don't talk, made to talk. Usually with some cleanup of the data you inherited.

A person approves before anything goes out.

Who you'd work with

I'm an engineer, and I build for small teams.

Some of what I've built is running today: a bot that turns a finished report into a scheduled web post, search across an organization's past work in plain English, and connectors that let an AI assistant read legislative and campaign-finance data, signed in through the same login as every other tool. They're in daily use, not demos.

Running them after launch is what taught me what not to build. Filer Labs is for organizations that need this kind of work and don't have an engineer on staff to do it.

How it works

A fixed price for a named thing, finished in weeks.

A paid spec firstScope, price, and timeline in writing before any build. You keep the document either way.
A price that doesn't moveQuoted after the spec. The number you agree to is the number you pay.
Your accounts, not mineYour hosting, your keys, your data. I work inside them and hand everything back documented.
An honest noIf the thing you want isn't worth building, I'll say so before you pay for it.

Packages, method, and the technical detail

Start here

Tell me what's eating your team's week.

Describe the workflow. I'll tell you what I think it takes, or that it isn't worth doing. If it's a fit, we talk before you pay for anything.

[email protected]