US K-12 Cyber & IT RFP Monitor

Find public school district and municipal cybersecurity, managed IT, network modernization, software, device, E-Rate and edtech procurement opportunities as clean sales-lead data.

This Actor is built for public-sector sales teams that do not want to manually check scattered district bid pages, PDF-heavy procurement sections and portal lists every week.

What You Get

• One dataset row per matched procurement opportunity.
• Buyer name, buyer type, state, source, title, URL, status and deadline when available.
• Matched keywords and a relevance score so sales teams can filter the list.
• Public attachment links grouped under the nearest opportunity when possible.
• Cross-run dedupe for scheduled monitoring with emitOnlyNew.
• Pay-per-event pricing tied to emitted qualified_opportunity rows.

Best For

• Cybersecurity vendors selling endpoint, SIEM, MDR, vulnerability management, incident response, IAM or network security to school districts.
• MSPs and managed IT providers looking for school and municipal RFPs.
• Edtech, SIS, assessment, progress monitoring and infrastructure vendors.
• Public-sector BDR, RevOps and founder-led sales teams that need fresh leads in CSV, API, Sheets, CRM or alerts.

What It Finds

The Actor crawls public procurement pages and looks for RFP, RFQ, bid and proposal records that match cyber, IT, network, software, device, E-Rate and edtech keywords.

It is a vertical lead monitor, not a generic tender database. Use it to find and triage likely opportunities, then review the source page and attachments before selling or bidding.

Live Demo Results

Apify Cloud demo run on 2026-06-24:

• Actor: barking_wisdom/us-k12-cyber-it-rfp-monitor
• Run: rZaaQecfVZddWnYJH
• Dataset: P5gkvtTfMhK8zyvbN
• Public sources checked: 2
• Candidate links found: 125
• Qualified rows emitted: 31
• Failed requests: 0
• Pricing model in run metadata: PAY_PER_EVENT
• Charged events recorded: qualified_opportunity = 30
• Platform usage cost measured for the run: about $0.00276

Example rows from that live dataset:

Opportunity	Buyer	State	Score	Matched keywords
Bid 3271 Information Technology Services Apple Devices	Jackson Public Schools	MS	14	information technology services, technology services, devices, apple devices
RFQ 2026-01 Rapid 7 Cybersecurity Software as a Service (SaaS) - Proposal (PDF)	Jackson Public Schools	MS	12	cybersecurity, software
Bid 3270 Information Technology Services Equipment and Devices	Jackson Public Schools	MS	11	information technology services, technology services, devices
Bid 3281 Jackson Public Schools Information Technology Services Equipment and Device	Jackson Public Schools	MS	9	information technology services, technology services
RFP 2026-10-26 Progress Monitoring Tool for English Learners (EL)	Jackson Public Schools	MS	7	progress monitoring

For tighter sales lists, start with minScore of 5 or higher and review the source page. Some public procurement pages list unrelated documents near IT keyword text, so low-score rows are best treated as discovery leads.

How To Use It

1. Run the default school-district-pages preset to inspect the output shape.
2. Tune keywords, states, minScore and maxPagesPerSource for your sales motion.
3. Export the dataset to CSV, Excel, JSON, Google Sheets, an Apify integration or your CRM workflow.
4. Schedule the Actor daily or weekly with emitOnlyNew: true so only new opportunities are emitted.
5. Use the score, matchedKeywords, deadlineAt, attachmentUrls and source links to qualify leads before outreach.

Recommended Sales Input

{
  "sourcePreset": "school-district-pages",
  "keywords": [
    "cybersecurity",
    "managed IT",
    "network security",
    "E-Rate",
    "network modernization",
    "information technology services",
    "student information system",
    "software",
    "devices"
  ],
  "lookbackDays": 365,
  "maxPagesPerSource": 25,
  "minScore": 5,
  "includeAttachments": true,
  "emitOnlyNew": true,
  "proxyConfiguration": {
    "useApifyProxy": false
  }
}

For a broader discovery run, lower minScore to 1. For a cleaner sales-ready feed, keep it at 5 or above.

API And Automation Examples

Use the Actor as a scheduled lead feed:

{
  "sourcePreset": "school-district-pages",
  "keywords": ["cybersecurity", "managed IT", "E-Rate", "network modernization"],
  "states": ["TX", "CA", "FL"],
  "minScore": 5,
  "emitOnlyNew": true
}

Run it from another workflow with the Apify API:

curl "https://api.apify.com/v2/acts/barking_wisdom~us-k12-cyber-it-rfp-monitor/runs?token=$APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{
    "sourcePreset": "school-district-pages",
    "keywords": ["cybersecurity", "managed IT", "E-Rate"],
    "minScore": 5,
    "emitOnlyNew": true
  }'

After the run finishes, export the default dataset to CSV, JSON, Excel, Google Sheets or a webhook integration from Apify Console.

Input Options

• sourcePreset: built-in public source group or custom.
• startUrls: public procurement pages for custom runs. API users can add sourceName, buyerName, buyerType, state and adapter metadata to each URL object.
• keywords: terms used for matching and scoring.
• states: optional US state filters.
• minScore: minimum relevance score for emitted rows.
• lookbackDays: optional freshness window for pages with dates.
• maxPagesPerSource: cap for bounded runs and predictable cost.
• includeAttachments: include public PDF, Word and spreadsheet links when detected.
• emitOnlyNew: enable for scheduled monitoring to avoid repeated rows across runs.
• proxyConfiguration: disabled by default because the intended sources are public pages.

Output Fields

Each dataset row can include:

• opportunityId
• title
• buyerName
• buyerType
• state
• sourceName
• sourceUrl
• opportunityUrl
• status
• publishedAt
• deadlineAt
• category
• matchedKeywords
• score
• summary
• attachmentUrls
• firstSeenAt
• lastSeenAt

Example Output

{
  "title": "RFQ 2026-01 Rapid 7 Cybersecurity Software as a Service (SaaS) - Proposal (PDF)",
  "buyerName": "Jackson Public Schools",
  "buyerType": "school_district",
  "state": "MS",
  "status": "open",
  "matchedKeywords": ["cybersecurity", "software"],
  "score": 12,
  "opportunityUrl": "https://www.jackson.k12.ms.us/fs/resource-manager/view/1fefbb8a-5ab0-43cd-b583-eebb7057eeb2"
}

Pricing

The Store model is pay-per-event for qualified_opportunity at $0.05 per qualified opportunity. The Actor calls the charge event automatically in Apify Cloud when a qualified row is emitted. Local development runs do not charge events.

Compliance And Limits

This Actor is intended for public procurement pages only. It does not log in, bypass access controls, solve CAPTCHA, collect private account data or guarantee procurement completeness. Users are responsible for checking source terms, reviewing source documents and using the results lawfully.

The dataset is organization and opportunity focused. It is not intended to collect personal data.

FAQ

Is this a complete K-12 tender database?

No. It is a focused monitoring Actor for public pages and configured sources. It is best used as a fresh lead feed that your team can tune by state, keyword and source.

Can I add my own districts or portals?

Yes. Use sourcePreset: "custom" and provide public procurement page URLs in startUrls. For best output, include buyerName, buyerType, state and sourceName metadata with each URL.

Should I use emitOnlyNew?

Use emitOnlyNew: false for sample or one-time discovery runs. Use emitOnlyNew: true for daily or weekly monitoring so repeated opportunities do not keep appearing in your feed.

Why do some low-score rows need manual review?

School district procurement pages often place unrelated bids, PDFs and category text close together. The score and matchedKeywords fields make that visible. Use higher minScore values for cleaner sales lists.

Does it use Apify Proxy?

Proxy is disabled by default. The Actor is designed for public procurement pages. Enable proxy only if your configured sources require it and you are comfortable with the extra cost.

Good Next Workflows

• Schedule daily monitoring for a target state or region.
• Connect the dataset to Google Sheets, a webhook or a CRM import.
• Add custom district, city, county or procurement portal URLs with buyer metadata.
• Raise minScore for high-confidence lead lists or lower it for early market discovery.