Skip to content
Avenalia
Menu

Event-based demand intelligence

From verifiable fact to explained opportunity.

Avenalia organises every signal to answer what happened, who may need something, why it fits your company and what the next reasonable action is.
Explore the productReview the sources
Coverage is enabled source by source after validating access, evidence, quality and incremental processing. This page does not present future connectors as operational.

Sources

An opportunity starts from a retrievable origin

Finding text is not enough. Every source retains authority, licence or permission, frequency, history and critical fields.

Public procurement

Publications, awards, lots, modifications and documents distinguish bidding from selling to the awardee.

Contractual coverage
PCSP and TED, with official support sources where applicable.

Grants

A call and an award follow different routes: apply for funding or investigate a beneficiary's resulting need.

Contractual coverage
BDNS/SNPS and related official decisions.

Company and regulatory change

Acts, permits, investments, sites and regulation may reveal a need, never a confirmed purchase on their own.

Contractual coverage
BOE, BORME, open portals and corporate domains.

Authorised private opportunities

A request received by the customer is processed inside its organisation with confidentiality and isolated access.

Contractual coverage
RFPs, RFQs, prequalification and submitted invitations.

Naming a source does not mean it is active. It only produces visible opportunities when its contract, history, incremental processing, quality and operations are validated.

Product journey

Eight capabilities, one traceable decision

Every step retains its input and output so a person can review, correct or discard it.
  1. Sources

    Ingests official publications, corporate information and authorised private inputs without bypassing controls.

    Output: versioned document or record.
  2. Events

    Extracts the fact, participants, location, dates, typed amounts and state.

    Output: normalised event with evidence.
  3. Needs

    Links the fact to probable purchases or work packages and shows what still needs confirmation.

    Output: explained inferred need.
  4. Matching

    Compares need and customer profile by offering, territory, capacity, exclusions and timing.

    Output: fit with reasons and negative signals.
  5. Contacts

    Recommends the relevant role before obtaining a permitted and verifiable professional channel.

    Output: role, provenance and state kept separate.
  6. CRM

    Turns a qualified opportunity into follow-up, task, note, deal or workspace without losing its origin.

    Output: assigned and auditable work.
  7. Evidence

    Links every assertion to the document, field, excerpt, version and moment supporting it.

    Output: reproducible explanation.
  8. Security

    Applies permissions, isolation, minimisation and human approval to sensitive data and actions.

    Output: permitted action or explicit block.

Opportunity anatomy

The record answers before asking you to act

A useful opportunity is not a generic alert or a company in a list.

What happened

Event, phase and participants confirmed by the source.

Who may buy

Target organisation and role without confusing buyer, awardee or beneficiary.

What they may need

Probable need kept separate from any confirmed purchase.

Why it fits

Relationship with your offering, territory, capacity and exclusions.

When to act

Deadline, phase, validity and temporal evidence supporting timing.

What to do next

Bid, apply, sell, respond, research, monitor or discard.

Contacts and CRM

The action depends on the route

Avenalia does not turn every opportunity into an email or every grant into a proposal.

Relevant contact

It identifies the role first. Channel, provenance, verification, eligibility and authorisation remain separate decisions.

CRM follow-up

Opportunity, company, evidence, contact, tasks, activity and outcome keep a shared, auditable history.

Workspace when applicable

Tenders, applications and private responses can prepare documentation. Signing, submitting or sending remains under human control.

Evidence and security

Explanation and control are not extras

A recommendation is useful only when it can be verified and the proposed action is actually permitted.

Visible evidence

  • Origin and authorityPrimary, secondary or authorised private source clearly identified.
  • Fact and inferenceObserved, extracted and inferred fields are never presented as equivalent.
  • Version and changeHash, date, replacements and reprocessing make the decision reconstructable.
  • UncertaintyMissing data, contradictions and required review remain visible.

Control by design

  • IsolationPrivate documents, contacts and work from one organisation are not reused in another.
  • Minimum accessEach route applies permissions and purpose before revealing or executing.
  • Authorised actionGenerating is not signing, submitting or sending.
  • Explicit failureA failed source or missing critical field is not hidden with invented content.

Next step

Choose the route before preparing the action

See how the work changes between bidding, applying for a grant, selling to an awardee or responding to a private request.
View opportunity routesReview privacy
Commercial requests will open with verifiable persistence, consent, anti-abuse protection and routing.