Ops & Supply

How to vet and onboard vendors as Foundation and Nonprofit Ops Teams

Ops & SupplyFor Foundation and Nonprofit Ops Teams2 apps10 steps~20 min to set up

Your four-person ops team vets a new vendor every time a program officer decides to hire a consultant, rent a meeting space, or contract a fiscal sponsor. That means chasing W-9s by email, manually checking the IRS Tax Exempt Organization Search for grantee fiscal sponsors, running Candid or Guidestar lookups to confirm 501(c)(3) status, and then routing a vendor approval through whoever is supposed to sign off — which is a different person depending on whether the contract is above or below $10,000. Onboarding paperwork lands in a shared Google Drive folder that nobody agreed on. Two months later someone asks whether that translation vendor is approved and you're searching Gmail for 'W-9 signed' like it's 2011.

Build this on Starch → See the apps used

Ops & SupplyFor Foundation and Nonprofit Ops Teams2 apps10 steps~20 min to set up

Outcome

What you'll set up

A structured vendor intake and vetting workflow that pulls status checks from the IRS TEOS and Candid through browser automation — no API needed — and logs results directly into a vendor registry you describe in natural language and Starch builds

An onboarding checklist app that tracks W-9 receipt, insurance certificates, conflict-of-interest disclosures, and contract execution status for every vendor, visible to your whole ops team without another Google Sheet

Automated routing and reminder logic so approval requests go to the right signatory based on contract value, with Slack notifications and a QuickBooks vendor record created only after all boxes are checked

The Starch recipe

Apps, data, and prompts

The combination of Starch apps, the data sources they pull from, and the prompts you use to drive them.

Apps used

Project Management Contract Lifecycle Management

Data sources & config

Starch syncs your QuickBooks data on a schedule so vendor records, payment history, and bill status are current when your app runs. Connect Salesforce from Starch's integration catalog; the agent queries it live to pull grantee and vendor contact data into your registry. Starch automates the IRS Tax Exempt Organization Search, Candid/GuideStar, and any vendor portal your team uses through your browser — no API needed for any of them. Slack connects from Starch's integration catalog for approval notifications and expiration alerts.

Prompts to copy

Build me a vendor registry app that tracks each vendor's name, EIN, 501(c)(3) status, W-9 received date, insurance expiration, contract value, approval status, and the program officer who requested them. Add a view filtered to vendors with missing documents or expired insurance.

Create an onboarding checklist template that fires when I add a new vendor. It should include tasks for: request W-9, verify IRS exempt status via TEOS, check Candid profile, collect COI disclosure, route contract for signature, and create vendor record in QuickBooks. Assign each task to the right team member based on task type.

Set up a weekly automation that checks every active vendor for insurance certificates expiring in the next 60 days and sends me a Slack message listing them with the vendor name, expiration date, and the program officer who owns the relationship.

Run these in Starch → or paste them into your favorite agent

Walkthrough

Step-by-step

1 A program officer submits a new vendor request — name, EIN, estimated contract value, and scope — via a simple form you build in Starch and share as a link. This creates a new entry in your vendor registry app automatically.

2 Starch triggers a browser automation that searches the IRS Tax Exempt Organization Search for the vendor's EIN, extracts the exemption status and ruling date, and writes the result back to the vendor record. No manual lookup, no copy-paste.

3 A second browser automation pulls the vendor's Candid/GuideStar profile — 990 filing status, financial health indicators, leadership — and attaches a summary note to the registry entry so your ED or program director has context before approving.

4 Your onboarding checklist fires: task one asks the program officer to upload the W-9 directly into the vendor record; task two routes to your ops coordinator to collect a certificate of insurance if the contract is over $5,000.

5 If the contract value is above your foundation's threshold (say, $10,000), Starch routes an approval request to your ED via Slack with a summary of the vendor's IRS status, Candid notes, and the contract scope. Below that threshold, your ops director approves.

6 Contract Lifecycle Management — coming soon — will handle drafting from your standard vendor agreement template, routing for e-signature, and storing the executed contract with a full audit trail. Today, Starch can generate a contract summary and track signature status in the registry even while you use DocuSign separately.

7 Once all checklist items are complete and the contract is signed, Starch creates the vendor record in QuickBooks automatically — pulling the vendor name, EIN, and payment terms from your registry so your bookkeeper doesn't re-enter them.

8 Your vendor registry app shows a board view: Pending Vetting, Pending Approval, Pending Onboarding Docs, Active, Expired or Inactive. Your ops team checks this view instead of searching Gmail.

9 Every Monday morning, Starch runs an automation that checks active vendors for insurance expirations in the next 60 days and contracts approaching their end date, then sends a consolidated Slack alert so renewals don't sneak up on you.

10 At the end of each quarter, you ask Starch to pull a vendor spend summary from QuickBooks grouped by program area and vendor type, cross-referenced against your approved vendor list, and surface any payments to vendors who didn't complete onboarding — a common audit flag for foundations under expenditure responsibility rules.

See this running on Starch

Connect your tools, describe what you want, and the agent builds it. Closed beta is free.

Try it on Starch →

Worked example

Q1 2026 Education Program — New Curriculum Consultant Onboarding

Sample numbers from a real run

Consultant: Dr. Renata Osei (curriculum design)	18,500
Contract term	0
IRS TEOS check result: Individual — no exemption required	0
COI certificate collected	0
ED approval required (above $10k threshold)	0
QuickBooks vendor record created	0

In early February, your education program officer sends a vendor request for Dr. Renata Osei, an independent curriculum consultant, at $18,500 for a 6-month engagement. Starch creates the registry entry and immediately fires the IRS TEOS browser automation — Dr. Osei is an individual, not an exempt org, so the result comes back 'Individual — standard W-9 required' within two minutes. No Candid lookup needed. The checklist fires: your ops coordinator collects the W-9 and a $1M general liability COI within three days. Because the contract is above $10,000, Starch sends your ED a Slack message with a summary: consultant name, scope, contract value, W-9 received, COI received, no conflict of interest flag. Your ED types 'approved' in Slack. Starch marks the approval in the registry, triggers a QuickBooks vendor record creation with EIN and net-30 payment terms pulled directly from the registry, and moves the entry to Active status. Total ops team time: about 25 minutes across three people over four days, down from a week of email threads and a vendor record that used to get created only after the first invoice arrived.

Measurement

How you'll know it's working

Average days from vendor request to approved and onboarded (target: under 7 business days for contracts under $25k)

Percentage of active vendors with current W-9, COI, and signed contract on file — tracked as a compliance ratio for auditors and board review

Number of payments to vendors who bypassed the onboarding checklist — a 990 and expenditure-responsibility risk metric

Insurance certificate expiration alerts resolved before expiration vs. caught after

Ops team hours per vendor onboarding cycle — baseline vs. post-Starch

Comparison

What this replaces

The other ways teams handle this today, and how the Starch version compares.

Fluxx or Foundant GLM

Purpose-built for grants management but cost six figures, assume a dedicated grants-management team, and don't have a usable vendor vetting workflow out of the box — you'd still build the vendor process on top.

Google Drive + Gmail + DocuSign (current state)

Zero software cost but zero structure — vendor status lives in someone's head, W-9s are in three different folder locations, and there's no audit trail a board or IRS examiner could follow.

Airtable + Zapier

Flexible enough to build the registry, but requires someone to design the schema, wire the automations, and maintain them — in a four-person ops team that time doesn't exist, and browser automation for TEOS or Candid lookups isn't available without custom code.

Blackbaud FIMS or Raiser's Edge NXT

Strong donor and grant data management, but not designed for vendor vetting workflows, requires significant configuration services, and the per-seat cost is hard to justify for a foundation your size.

On Starch RECOMMENDED

One platform — project management, contract lifecycle management all running on connected data. Setup in plain English; numbers stay current via scheduled syncs and live agent queries.

Try it on Starch →

FAQ

Frequently asked questions

Can Starch actually look up IRS exempt status automatically, or do I still have to do that manually?

Starch automates that lookup through your browser — no API needed. It navigates the IRS Tax Exempt Organization Search the same way you would, pulls the result, and writes it back to your vendor record. Same for Candid or GuideStar: if the page is publicly accessible, Starch can read it.

We use Salesforce for our grants database. Can Starch pull grantee and contact data from there into a vendor registry?

Yes. Connect Salesforce from Starch's integration catalog; the agent queries it live when your registry app needs contact or grantee data. You're not moving data out of Salesforce — Starch pulls what it needs when it runs.

Is Starch SOC 2 Type II certified? We have a board data-security policy.

Not yet — Starch is not currently SOC 2 Type II certified. If your board policy requires SOC 2 Type II for any system that touches vendor or financial data, that's worth flagging to your ED before you connect QuickBooks or Salesforce.

The Contract Lifecycle Management app sounds like exactly what we need. When is it available?

Contract Lifecycle Management is coming soon — it's in development and not available today. You can request beta access to get notified when it launches. In the meantime, Starch can track contract status, store metadata, and automate reminder logic in your vendor registry; you'd continue using DocuSign for e-signatures and link the executed document from the registry record.

We reconcile vendor payments in QuickBooks against program budgets in a Google Sheet. Can Starch help with that?

Yes. Starch syncs your QuickBooks data on a schedule, so vendor payment and bill data is current in Starch. Connect Google Sheets from Starch's integration catalog; the agent queries it live. You can describe a reconciliation view in natural language — 'show me Q1 payments by vendor against the program budget line in my budget sheet, flagged where actuals exceed budget by more than 10%' — and Starch builds it.

What happens if a vendor's data is in a portal we use — like a state nonprofit database — that has no API?

If you can log in and navigate it in a browser, Starch can automate it. It opens an independent browser session, navigates the site, and extracts the data you need — no API required. This works for state charity registration lookups, carrier insurance portals, government procurement databases, and similar sites.

We have a $10,000 approval threshold that's different from what other foundations use. Can we configure that?

Yes. You describe your approval routing logic in natural language when you build the automation — 'if contract value is above $10,000, route to the ED; otherwise route to the ops director' — and Starch wires that logic into the workflow. Changing the threshold later is as simple as describing the change.