What we track · how it lands · what you Map

Signals — full overview

One workspace queue for the whole buying cycle. Early creates demand. Mid shapes the brief. Late is the crowded RFx. Tenders and jobs are a subset — not the product.

Why this exists

The edge is detecting a buying cycle 3–18 months before a tender exists. Waiting for the notice is late-cycle — everyone else is already in. Operators still Map. Nothing auto-sends from this queue.

Three levels

Every signal is classified. Filter All / Early / Mid / Late. Pending work sorts early first, then score.

  • Early — create demand

    Strategy, funding, leadership, policy, project formation, hiring, technology change. Motion: open the conversation while the programme is still forming.

  • Mid — shape the opportunity

    RFIs, pilots, consultations, stakeholder activity, partner appointments, budget approvals, incumbent dissatisfaction. Motion: get into the brief before it locks.

  • Late — crowded

    RFP, tender, RFQ, framework competition, procurement event. Still tracked. Not the edge.

Buckets we classify

Fine-grained type plus buying-cycle bucket on every row. Prefer the earliest true bucket when a story could be both a strategy and a tender.

  • Budget / funding

    Approvals, capital plans, grants, subsidies, bonds, appropriations — usually before any RFx.

  • Strategy / roadmap

    Digital, GIS/data, climate, infra, modernization, cloud, asset-management plans and policy commitments.

  • Project formation

    Feasibility, pilots, consultations, market soundings, RFIs, business cases, planning apps.

  • Procurement

    RFIs, RFPs, RFQs, tenders, frameworks, DPS, PINs, awards, supplier days. Portals cover the late slice.

  • Contract lifecycle

    Incumbent expiry, exhausted extensions, poor performance, amendments, vendor consolidation.

  • Hiring

    Transformation, implementation, data, PMO, infra, cloud, sustainability — not only “GIS Manager.”

  • Leadership

    New CIO/CTO/CDO/Head of GIS/transformation/procurement, mayor/council, BU head.

  • Technology stack

    Cloud, Esri/SAP/Salesforce/Snowflake, GIS/data/IoT/ERP, legacy retirement.

  • Pain / failure

    Outages, audits, breaches, missed targets, cyber, public criticism.

  • Regulatory

    New laws, reporting, safety, environment, data-sharing, cybersecurity mandates.

  • Expansion & M&A

    New sites, geo expansion, acquisitions, carve-outs, shared services, agency consolidation.

  • Asset / infrastructure

    Roads, rail, utilities, data centres, renewables, ports, municipal development.

  • Board / council

    Minutes, agendas, resolutions, funding discussions — strong B2G.

  • Public statements

    Earnings, annual reports, speeches, investor decks, interviews.

  • Partner / competitor

    Implementation partners, consortia, competitor wins, incumbent losses.

  • Calendar / cyclical

    Budget year, planning season, framework renewal, grant and FY-end windows.

How intel gets into the queue

Coverage is not equal. Taxonomy can classify everything below. Only some paths fill the feed by themselves.

  • Procurement portals

    TED, Find a Tender, SAM.gov, TenderNed, and other Sources — late procurement.

  • Gemini research families

    Board, budget, strategy, project, contract, leadership+hiring, stack/pain/regulatory, partner/competitor.

  • Paste

    Chats, URLs, and notes. Structured into the same types and levels. Source stays manual.

  • Jobs research

    Open roles that reveal a programme.

  • Default Gemini / Exa

    Full-cycle prompt, still biased toward news and notices unless you pick a family.

Not sourced yet

Types exist so paste and research can tag them. There is no first-party feed until that data exists.

  • Usage / intent

    Site, webinar, event, multi-person engagement — later.

  • Org activity

    Procurement/finance/legal joining, champion forwarding — later.

  • Dux-Soup LinkedIn ingest

    Touches already log in OS. Queue ingest is later.

What happens after the queue

A human Maps a signal into a qualified account, then a mapped account with buying committee. From there: account development, 1:1 outbound, or a cold email campaign. Suppression and CRM checks run before send. EmailBison executes. Locatix does not auto-send.

Related