u/FickleConnection2532

I’m testing a simple public tender/RFP digest format for GovCon, bid teams, and public-sector sales people.

The goal is not to scrape every tender portal. It is to make a short list that helps someone decide quickly whether an opportunity is worth opening.

Current fields I’m testing:

- buyer

- region

- category / CPV codes

- estimated value

- publication date

- deadline

- status

- official source URL

- match reason

- new vs updated label

For people who work with government contracts, tenders, RFPs, bid writing, or public-sector sales:

Which fields matter most when deciding whether to review an opportunity?

Would daily alerts or a weekly digest be more useful?

I’m building a UK/EU public-tender digest for bid and public-sector sales teams.

Current fields include buyer, region, category, value, publication date, deadline, status, official source, and a short match reason.

Which fields and filters genuinely help you decide whether an opportunity is worth reviewing? Would daily alerts or a weekly digest be more useful?

I’m validating the workflow before developing it further, so practical feedback is welcome.

I’m testing a daily or weekly digest of new UK and EU public tenders.

Current fields include buyer, region, category, contract value, publication date, deadline, notice type, description, and official source URL.

For people working with bids or public-sector sales: which filters or alerts would actually save you time? Are keywords and regions enough, or do contract value, CPV codes, buyer history, and deadline reminders matter more?

I’m looking for practical feedback before building further, not selling anything.

I’ve been improving my Apify Actor portfolio and one thing became clear:

A working Actor is only half the job.

Before users run an Actor, they need to quickly understand what it does, what input it needs, what output they will get, and roughly what it may cost.

Recently I focused on:

- Ready-to-run example tasks

- Small default inputs

- Cleaner dataset columns

- Clearer pricing

- Better README and input schema text

Question for other Actor builders and users:

What matters most to you before trying a new Actor?

1. README clarity

2. Example task

3. Output preview

4. Pricing clarity

5. Input schema simplicity

Curious to learn what makes an Actor feel trustworthy before the first run.

I’m working on improving existing Apify Actors and wanted feedback from other builders/users.

For public-data Actors, do you find ready-to-run example tasks useful?

Example idea:

Instead of only publishing a generic scraper README, the Actor also has a task example like:

- Trustpilot review monitoring

- SimilarWeb traffic snapshot

- App Store / Google Play app intelligence

- Ecommerce price tracking

- Supplier discovery

The example would show fixed input, output fields, and export options, so a user can understand the workflow before configuring their own run.

I’m trying to understand what helps users more:

1. Better README and input schema

2. More ready-to-run task examples

3. More output schema/table views

4. Lower pricing / clearer pricing

5. Tutorials showing how to schedule/export/API the data

For people who use or build Apify Actors, which of these matters most when deciding whether to try an Actor?

I’m working on an Apify Actor that normalizes public procurement opportunities from official sources like SAM.gov, EU TED, and UK Contracts Finder.

Current fields:

- source

- contract / tender ID

- title

- buyer / agency

- value

- deadline

- location

- category

- official source URL

I’m trying to improve the dataset schema before adding monitoring/change tracking.

For people who work with procurement or public-sector data:

1. Which fields would be most important?
2. Would you prefer one normalized dataset, or separate source-specific fields?
3. Would alerts for new tenders / deadline changes be useful?
4. Is there anything missing from this schema?

Actor link for context:

https://apify.com/fascinating_lentil/global-government-contracts-aggregator

Not trying to spam - mainly looking for schema and use-case feedback before I improve it further.