How a Seven-Person Nonprofit Training Provider Took Hundreds of Hours a Month Off Its Senior Staff with Claude

ImpactTek, a seven-person nonprofit that trains IT and cybersecurity professionals, had its most senior people carrying federal responses, research, enrollment materials and marketing. Here is how a no-code Claude Projects setup took that load off them.

Category: Customer Stories · 6 min read · Published 2026-09-15

ImpactTek is a 501(c)(3) nonprofit that trains adults for careers in IT and cybersecurity. It is an approved training provider under the Workforce Innovation and Opportunity Act (WIOA) in Virginia, and it also bids on federal defense training work as a subcontractor. It does all of this with a team of seven.

This is the story of how ImpactTek used Claude to take a large share of back-office work off the people it most needs in front of students, and how its staff came to run the setup on their own.

The Challenge: The Instructors Were Also the Back Office

At a small training provider, the same few senior people do almost everything. At ImpactTek, the same few people were drafting responses to federal solicitations, researching markets and funding sources, onboarding new enrollees, and keeping web and marketing content current. Larger organizations staff whole departments for this work.

Each of these jobs matters. Together they pulled ImpactTek's most experienced staff away from teaching, which is the work only they can do.

ImpactTek set clear limits on any fix. It could not add software to maintain, infrastructure to host, or anything that would need an IT administrator. Whatever it adopted had to work for a small team with no one to spare.

The Approach: Knowledge, Prompts and a Review Rule

ProposalApp worked with ImpactTek using Claude Pro and Claude Projects on ImpactTek's own accounts. The setup rests on three parts.

A knowledge base built from ImpactTek's own material. Each Claude Project holds the documents ImpactTek already had: its past performance write-ups, program and WIOA documentation, and course catalog. Claude answers from ImpactTek's material rather than from general knowledge.

About a dozen reusable prompts in plain language. Each prompt is tied to one recurring task across five work areas: federal capture, market intelligence, funding and grants, enrollment and onboarding, and marketing and web content. Staff pick the prompt that fits the task instead of writing instructions from scratch each time.

A human-review rule written into the Projects. Every Project states that a person reviews what Claude produces before it goes to a student, a funder or a government customer. The rule is part of the setup, not a policy that lives in a separate document.

There were no integrations and no custom code. That was deliberate: with nothing to host or maintain, the setup matched the limits ImpactTek had set.

Going Live on Real Work

The setup was built from ImpactTek's real documents and tested on real work rather than samples. Training sessions worked through ImpactTek's actual backlog, so staff finished with completed work rather than a demo.

The first big test was a request for information from the U.S. Air Force. ImpactTek used the capture Project to outline and draft its answer, then reviewed and finalized it, and submitted a 26-page response.

The engagement began with three half-day working sessions on May 14 to 16, 2026. Over the following weeks the market intelligence, funding, enrollment and marketing work areas went into daily use. Since about September 1, ImpactTek's staff have run all of it without ProposalApp.

The Results

ImpactTek estimates that the setup now handles 160 to 265 hours of staff work a month, about 1.0 to 1.7 full-time roles at 160 hours a month. These are ImpactTek's own estimates, not measurements, and they are not payroll savings: most of this work would otherwise not have been done at all.

Estimated hours a month, by work area:
- Federal capture and proposal drafting: 60 to 100
- Website, landing page and marketing content: 40 to 60
- Grant and funding stream research: 25 to 40
- Competitive and market intelligence: 20 to 40
- Enrollment intake and onboarding materials: 15 to 25

Specific changes ImpactTek reports:

- Federal responses: an RFI compliance outline and first draft went from a full week of distributed effort to one or two days.
- Research: competitive research and a map of funding streams now exist where there were none before.
- Marketing: landing page and outreach copy is drafted in-house instead of being outsourced or not produced.

For a team of seven, hours are the constraint that matters. The time went back to students, and to work the team previously lacked the capacity to take on.

What Other Small Organizations Can Take From This

ImpactTek's results did not come from a large platform rollout. They came from three simple choices:

1. Start from your own documents. Claude is most useful when it works from material you already trust.
2. Write the prompts once, in plain language. Reusable prompts let everyone on the team get consistent results without becoming prompt experts.
3. Build review in, not on. Writing the human-review rule into each Project keeps quality where it belongs, with the people accountable for the work.

If your team is small and your senior people are carrying the back office, this is a pattern you can copy with tools you may already pay for.