⛃Biman data collector

It works through project marketplaces and career networks automatically and delivers projects, profiles and career histories as a table to take away.

The decisive difference from the opportunity search: this area deliberately writes nothing into the CRM. The result is a file.

Every tile is a job of its own, and the fields below adapt to it:

• Project search and job search — tenders and projects,
• Talent search — profiles,
• Career histories — professional background,
• Monitoring — recurring runs.

A running job can be stopped with “■ Stop”.

Enlarge

In plain text in this browser. This is not carelessness but a deliberate design decision — the data collector works in the user’s browser, not on the server — but it has consequences:

• Do not enter them on other people’s computers.
• Delete them after use.
• Do not use the main password of an account that can do other things as well.

If you keep to these three rules, you are on the safe side. If you ignore them, you leave login details behind on other people’s devices.

“↓ CSV” downloads the table — this area deliberately writes nothing into the CRM.

Anything useful you then take over with the data import for contacts or opportunities. The detour is intentional: this way you see what arrives before anything is written, and your records do not fill up with useless rows.

Treat the exported file like any other export: it contains personal data and leaves the protected area.

That depends on the portal — and not only on the law, but on its terms of use. Many platforms expressly prohibit automated access; a breach can lead to the account being blocked.

This is not a theoretical question: the account that gets blocked is the one you signed in with.

So clarify beforehand what applies to the platform in question, and treat personal data from such sources with the same care as any other — publicly visible profile data is personal data too.

• Opportunity search if you want opportunities and need the result directly in the CRM. It creates opportunities, enriches contact persons and costs money.
• Data collector if you want a table — profiles, career histories, a market overview. It deliberately writes nothing into the CRM.

In short: the opportunity search delivers work for sending, the data collector delivers material to look at.

That depends on the mode and the scope — think in minutes, not seconds, because browser automation works through one page after another.

A running job can be stopped with “■ Stop”. Whatever has been collected up to that point stays and can be downloaded.

That is the risk that comes with automated access: many platforms expressly prohibit it, and the account that gets blocked is the one you signed in with.

What helps now is not technology but the platform’s support. What helps in future: work more slowly and in smaller quantities, do not let it run round the clock — and clarify beforehand what the terms of use allow.

Like any other list from an outside source — with one additional point: publicly visible profile data is personal data too.

In practice:

1. Review before importing. Not everything collected belongs in the CRM.
2. Only import what you need. Data minimisation is not a recommendation here.
3. Record the origin — with a tag when importing, so that it is clear later where a record came from.
4. Treat the downloaded file like an export: it is outside the protected area.

It runs the same search repeatedly to detect changes — such as new tenders from particular clients, or changes in career histories.

Two notes: repeated access is more noticeable to a platform than a one-off run, and the result here is still a file. If you need permanent monitoring in the CRM, you are better served by the opportunity search and follow-ups.