# noombat: The whole market, watched.

> Go-to-market intelligence for B2B sales. noombat follows every company you could sell to and names the ones where pipeline is forming this week: a new logo, an account ready to buy more, a lost deal ready to reopen.

noombat is a go-to-market intelligence product for B2B sales teams, built by a team that has spent years building sales pipeline for B2B companies. It is configured per customer and priced per pod (one revenue team, sales and marketing together, on one market). Contact: hello@noombat.ai. Book a call: https://noombat.ai/talk.

## How it works (https://noombat.ai/product)

1. Follow the whole market. Every company you could sell to, read every day: company registers, tenders, hiring, funding, press, your website, your LinkedIn, your CRM.
2. Score against your definition. You describe a good customer once: size, sector, stack, the roles that buy. Every company is scored against it, wherever it sits.
3. Time the call. Each dated move goes into the company's file. Outside clues time the call; something of yours confirms it.
4. Post the list. Every morning, the companies worth a message today, with the reason and who to write to, in Slack or Microsoft Teams.

Three kinds of pipeline: a new logo, an account ready to buy more, a lost deal ready to reopen.

The seven sources of a company file:
- Your posts: reactions and comments, matched to a company
- LinkedIn ads: impressions and engagement, per company
- Competitor engagement: who warms to them before calling you
- The buying committee: name, role, employer, by company
- Market watch: registers, tenders, hiring, funding, press
- Website identification: the company behind every visit
- Your tools: HubSpot, Salesforce, Pipedrive, GA4, Slack, Teams

The eighteen kinds of line, in product words (never a tool's name): Website visit, Session recorded, Email opened, LinkedIn ad view, LinkedIn ad click, Engaged your post, Commented on your post, Engaged a competitor, Followed a competitor, Exec hire, Role change, Expansion, Hiring, Press, Tender, Funding, Deal history, Team mention.

For enterprise: connections are read through each system's API, and the only write-back is the score, the tier and the chance of a meeting, into CRM fields of their own (or none, read-only, if the customer prefers); nothing is ever sent in the customer's name; data is kept in a schema per customer, encrypted in transit and at rest, and deleted when the customer leaves; data-processing terms are written for teams in the EU and in the US; the definition of a good customer is the customer's own; the list arrives in Slack or Teams; an analyst answers questions from the customer's own data; terms, a privacy policy and a data processing agreement are available for a security review.

## Software and SaaS, for sellers in the industry (https://noombat.ai/solutions/software)

Job adverts, job changes and funding news are read each morning beside your CRM, billing and usage, and show which companies need your product now: a prospect hiring for the job it does, a customer whose champion left. Every SDR, AE and CSM gets a ranked list with the reason.

Systems read through their APIs: Salesforce, HubSpot, Stripe, Chargebee, Gainsight, ChurnZero, PostHog, Pendo, Gong, Zendesk.
Public record and signals watched: Tools in job adverts, Champion job changes, Funding and acquisitions, Company filings, Public software tenders, Pricing page visits, Engagement with your posts, Engagement with rivals' posts, Competitor ads.

The operating day:
- 08:30 · every day, SDR prospecting block (SDRs, SDR manager). Signal: On 9 Sep Halvorn Logistics advertises a role naming a rival's tool. It reads your pricing page twice. What changes: The block starts on ten accounts with a dated reason, not research.
- Monday · weekly, Pipeline review (AEs, sales manager, RevOps). Signal: Brightmere Health's buyer likes a rival's launch post on 12 Sep. Its deal has stalled for 24 days. What changes: Deals are judged on what changed outside the CRM as well as on stage.
- Thursday · weekly, Forecast call and risk review (Sales and CS leaders, RevOps, finance). Signal: Corvane Analytics' weekly seats fall from 212 to 138. Its admin changes job on 3 Sep. What changes: Risk comes with a named cause, early enough to plan a save.
- 120 days before renewal, Renewal review (CSM, account manager, deal desk). Signal: Tessaly Retail's notice window opens 30 Nov. A new digital chief joined 1 Sep from a rival's customer. What changes: The plan starts from who signs now. Last year's order form names someone who left.
- Last two weeks of quarter, Quarter-end push and deal desk (AEs, sales leaders, deal desk, finance). Signal: Kestrel Grid asks for 20% off to sign by 30 Sep. It raised funding on 8 Sep. What changes: Deal desk sees which late deals have a real trigger before discounting.

Use cases:
- Hiring for the job your product does. Signal: On 8 Sep Quillon Freight advertises for two billing analysts, naming a legacy invoicing tool. noombat: Matches the advert to your category. Names the finance director, the controller and a warm path. Action: The SDR opens on the advert's problem, through the warm path. Result: A first meeting on the prospect's own stated problem.
- A rival's audience, now on your site. Signal: Three people at Marrow & Vale comment on a rival's price-change post. It reads your migration guide twice. noombat: Links the comments to the visit and ranks the account above lookalikes. Action: The AE sends a migration note to the most senior commenter. Result: A switch talk opens while the price change is news.
- Champion gone, usage sliding. Signal: Corvane Analytics' product owner leaves on 3 Sep. Core-report usage is down 35% on its baseline. noombat: Joins the job change to the usage drop. Names the power users and the renewal date. Action: The CSM books a reset call and asks for an executive sponsor. Result: A new champion before the renewal review.
- Seats outgrowing the plan. Signal: Fennick Studios adds 41 seats since 1 Aug and posts six engineering roles on 5 Sep. noombat: Reads seat growth and hiring together, and flags the account for expansion. Action: The account manager proposes the next tier before procurement shops around. Result: Expansion agreed on the customer's growth.
- A stalled deal, a new decision maker. Signal: Brightmere Health appoints a head of IT on 2 Sep. No deal activity in 24 days. noombat: Names the new leader, what they engaged with, and a mutual connection. Action: The AE reopens the deal with the new leader. Result: The deal is active again, with the real buyer.
- A notice window about to open. Signal: Tessaly Retail's notice window opens 30 Nov. Its integration tickets doubled in August. noombat: Puts the notice date, ticket trend and new executive on one line. Action: The CSM brings the integration fix to the 90-day renewal meeting. Result: Renewal negotiated on outcomes, before notice is served.

Moments that make a company a buyer:
- A champion changes job: The person who bought your product leaves. The account loses its voice. Read via Job changes on professional profiles.
- Usage falls below its baseline: Active seats or core features drop several weeks in a row. Read via Your product analytics.
- A job advert names a tool: A company hires for your product, a rival's, or what you replace. Read via Tools named in job adverts.
- A notice window opens: The last date to cancel before auto-renewal is close. Read via Contract dates in your CRM and billing.
- New money or a new owner: A funding round or acquisition resets priorities and budgets. Read via Funding news and company filings.
- A rival's audience in play: People at a target engage with a rival's posts, then visit you. Read via LinkedIn engagement and site visits by company.

The operating calendar:
- 30 to 90 days before auto-renewal: Notice windows close. After it, the customer is locked in or gone. Save or upsell first.
- 120 days before renewal: Renewal reviews begin. A save needs a quarter of runway to change the outcome.
- Last two weeks of every quarter: Quarter-end push and discount approvals. Deals bunch up. Deal desk needs to know which are real.
- 31 Dec 2027: SAP ECC mainstream maintenance ends. Every company still on ECC funds a migration, and software around it.

Who: Head of the buying function, CIO, CTO or CISO, CFO, above a threshold, Procurement, Your product's admin or champion.
Fact: 15.5% forecast growth in worldwide software spending in 2026. Source: Gartner, worldwide IT spending forecast, July 2026.
Fact: 60% of a sales rep's time goes on work other than selling. Source: Salesforce, State of Sales, 2026.

Questions:
- Which systems does noombat read for software companies? Your CRM, billing, product analytics, support and call tools, such as Salesforce, Stripe, PostHog or Gong, through their APIs. It writes nothing back.
- Can noombat flag churn before a renewal? It flags the risk early. It watches usage against each account's baseline, support trends, champion job changes and notice windows. When they line up, the account tops the CSM's list.
- Does noombat work wherever we sell? Yes. Public sources are set up at onboarding for every market you sell into, from local company registers, filings and tender feeds.
- Does noombat send the outreach for us? No. It tells each owner who to talk to, why now and a suggested angle. Your team sends from its own tools.

## Financial services, for sellers in the industry (https://noombat.ai/solutions/financial-services)

A business picks its lessor, factor or payment provider in the weeks after a lien ends, a contract lands or a checkout changes. Those weeks are on your account owners' list, with who to call and why.

Systems read through their APIs: Salesforce Financial Services Cloud, Dynamics 365, Odessa LeaseWave, Solifi, Snowflake, BigQuery.
Public record and signals watched: Lien and charge registers, Insolvency notices, Director and accounts filings, Public contract awards, Announced acquisitions, Credit and fleet hiring, Checkout technology changes, Rival funder post engagement, End-of-term page visits.

The operating day:
- 9:00 · every day, Deal desk and credit queue (Sales manager, credit analyst, account managers). Signal: Halvern Logistics, conditionally approved but missing accounts, reads your pricing pages three times on 11 Sep. What changes: The owner chases the missing accounts before the approval lapses.
- Monday · weekly, Vendor channel review (Channel and vendor account managers). Signal: Trevik Machinery's weekly applications fall from 14 to 3. Its sales director commented on a rival's dealer post. What changes: The call to the dealer is about the rival programme.
- Month end, Portfolio and headroom review (Relationship and portfolio managers). Signal: Maridell Packaging, at 88% of its invoice finance limit, wins a three-year supply contract on 2 Sep. What changes: A limit increase goes to credit before the new invoices land.
- 180 days before term end, End-of-term book review (Portfolio, account and remarketing managers). Signal: Brellin Foods has 42 forklifts reaching term end in March. It advertises for a second-site warehouse manager. What changes: The end-of-term notice becomes an upgrade proposal, inside the notice window.
- Quarter end, Merchant attrition review (Merchant sales head and pricing lead). Signal: Olvena Home adds a second payment provider on 12 Aug. Its card volume with you falls 22%. What changes: The merchant joins the save list weeks before volume reaches zero.

Use cases:
- The rival funder's lien is gone. Signal: On 3 Sep a register marks satisfied another lessor's lien over 30 trucks at Corvane Haulage. noombat: Tops the asset finance rep's list with fleet size, operations director and a warm path. Action: The rep opens with fleet replacement, not a cold rate pitch. Result: A first facility with an operator you could not see.
- A contract won, now to fund. Signal: Tarnwell Freight wins a public transport contract on 27 Aug, then advertises for two credit controllers. noombat: Flags longer payment terms and a growing debtor book. Names the finance director. Action: The invoice finance manager offers a facility sized to the contract. Result: Signed while the cash gap is real.
- A maturity, plus a second site. Signal: Brellin Foods has 42 leased forklifts maturing in March and advertises for a second-site warehouse manager. noombat: Pairs the maturities report with the advert on the account in your CRM. Action: The account manager sends an upgrade proposal 150 days before term end. Result: Renewal and new assets in one agreement.
- A second provider on the checkout. Signal: Olvena Home adds another payment provider on 12 Aug. Card volume drops 22% in six weeks. noombat: Links the checkout change to the dip and names the e-commerce lead. Action: The relationship manager brings a pricing review before the peak-season code freeze. Result: Volume kept through peak season.
- A stalled memo, a new CFO. Signal: Ashgrove Clinics' credit memo has waited on accounts since July. It appoints a new CFO on 1 Sep. noombat: Moves the deal up with the appointment, the CFO's background and a shared connection. Action: The rep introduces the deal and asks the new CFO for accounts. Result: A quiet deal returns to credit with a sponsor.
- A platform building payouts. Signal: Fieldnote, a scheduling platform in your pipeline, advertises for a payments product manager on 4 Sep. noombat: Marks the build-or-partner decision as live and names the product leads. Action: The partnerships manager sends integration scope before engineering commits to building. Result: Signed while the platform is still choosing.

Moments that make a company a buyer:
- A lien is satisfied or filed: A rival funder's charge ends, or a new one lands. Read via Lien and charge registers.
- A supplier wins a multi-year contract: New invoices and longer payment terms arrive before the cash. Read via Public procurement awards.
- A debtor or dealer goes insolvent: Concentration and recourse exposure change the same day. Read via Insolvency and restructuring notices.
- A new finance chief: Funding lines and stalled approvals get a second look. Read via Director filings and announced appointments.
- The checkout changes: A merchant adds or swaps a payment provider. The choice is open. Read via Payment technology on the merchant's website.
- A group buys the business: The buyer's funders and payment providers usually replace the target's. Read via Merger notifications and announced acquisitions.

The operating calendar:
- Last quarter of the fiscal year: Equipment purchases brought forward. Buyers claim depreciation. Dealer volume peaks, and speed wins the deal.
- 90–180 days before lease end: End-of-term notice windows. Upgrades and buyouts are won or lost inside the window.
- Weeks before peak retail season: Merchant code freezes. Merchants will not switch providers during the freeze. Close before it.
- After year-end accounts are filed: Annual facility and limit reviews. New accounts restart stalled credit memos and justify higher limits.

Who: CFO or finance director, Controller or credit controller, Operations or fleet director, Head of e-commerce or payments, Owner or managing director, Product head, for embedded finance.
Fact: $1.54 trillion of new leasing business written worldwide in 2024. Source: Solifi, Global Leasing Report, World Leasing Yearbook 2026.
Fact: €4.04 trillion of factoring turnover worldwide in 2025, up 3.7% on the year. Source: FCI, World Factoring Statistics.

Questions:
- Which leasing, factoring and payments systems does noombat integrate with? CRMs such as Salesforce or Dynamics 365 through their APIs; servicing platforms such as LeaseWave or Solifi through their APIs or a scheduled export; facilities and card volume from your data warehouse. It reads contracts, maturities, facilities, volume and owners.
- How does noombat know a rival's lien has ended? It reads lien registers every morning. When another funder's lien is satisfied, or a new one is filed, the date becomes the reason on that account.
- Can noombat see a merchant switching payment provider? Yes. It watches the technology on the merchant's own website. A checkout script that disappears or appears becomes a dated signal, linked to any volume dip.
- Does noombat work in any country? Yes. Sources are set up per country at onboarding, from that country's registers, insolvency notices, filings and tender feeds.
- Does noombat quote rates or send outreach? No. It tells each account owner who to call and why, with the people, warm paths and a drafted angle. Your team calls and prices.

## Banking, for sellers in the industry (https://noombat.ai/solutions/banking)

Charge registers, filings and contract awards are read against your loan book every morning. Each relationship manager sees who moved, why, and an angle.

Systems read through their APIs: nCino, Finastra, Temenos, Fiserv, Oracle FLEXCUBE, Salesforce Financial Services Cloud, Dynamics 365.
Public record and signals watched: Lien and charge registers, Accounts and subsidiary filings, Officer changes, Contract awards needing bonds, Property and permit registers, Ownership changes, Treasury and finance hiring, Rival lender post engagement, Lending page visits.

The operating day:
- 08:00 · every day, Relationship manager book check (Relationship and portfolio managers). Signal: Another lender files a charge over Kestrel Mouldings' equipment on 11 Mar. What changes: The relationship manager calls that day.
- Monday · weekly, Sales pipeline meeting (Team leader and relationship managers). Signal: Palomir Logistics wins a public contract on 6 May that needs a performance bond. What changes: A prospect with a dated funding need joins the pipeline.
- Tuesday · weekly, Credit committee (Credit officers and the presenting manager). Signal: Two days before committee, Vantor Hotels' filing shows a new parent company. What changes: The credit memo reflects the new owner before it is presented.
- Month end, Maturity and annual review report (Relationship managers and credit administration). Signal: Arvell Brick's loan matures in 150 days. Its finance director engaged with a rival's refinancing post. What changes: Maturities are ranked by who is already shopping.
- Quarter end, Covenant checks and compliance certificates (Credit administration and portfolio managers). Signal: Solvara Dairy advertises for a group treasurer and files a new export subsidiary on 30 Sep. What changes: The review surfaces growth that needs currency and cash management.

Use cases:
- A contract won, a bond needed. Signal: Palomir Logistics wins a public contract on 6 May. It needs a performance bond within 30 days. noombat: Puts Palomir on the relationship manager's list with the award, start date and finance director. Action: The relationship manager offers a bond and a working-capital line. Result: A relationship that starts from a funding need.
- A prospect repays its lender. Signal: A register marks Dunhollow Engineering's charge satisfied on 14 Apr. No new charge is filed. noombat: Flags the release, recent equipment purchases and a warm path through a colleague. Action: The relationship manager asks about working capital and equipment finance. Result: A meeting while the company has no secured lender.
- Another lender files on your borrower. Signal: Another lender files a charge over Kestrel Mouldings' equipment on 11 Mar. noombat: Matches the filing to your facility, with the equipment and lender named. Action: The relationship manager calls the finance director about equipment finance terms. Result: The next asset purchase stays with your bank.
- A new treasurer, a new subsidiary. Signal: Solvara Dairy advertises for a group treasurer and files a new export subsidiary on 30 Sep. noombat: Links both to the client and notes no currency or cash management products. Action: The relationship manager brings in treasury for a cash management review. Result: Treasury work starts months before the annual review.
- A maturity, and a borrower shopping. Signal: Arvell Brick's loan matures in 150 days. Its finance director engaged with a rival's refinancing post. noombat: Ranks Arvell Brick above other maturities and names the post. Action: The relationship manager requests financials and takes refinancing terms to credit. Result: The refinancing reaches committee before a rival's term sheet.
- A new owner before committee. Signal: On 3 Aug, Vantor Hotels' filing shows a new parent company, two days before committee. noombat: Alerts the presenting manager and analyst with the filing and new directors. Action: The analyst updates the credit memo and guarantor structure. Result: One committee, decided on current facts.

Moments that make a company a buyer:
- A rival lender files a charge: Another lender takes security over a company's assets, and is named. Read via Lien and charge registers.
- A charge is satisfied: A company repays its lender. The old relationship loosens. Read via Lien and charge registers.
- A contract is won: Bonds, guarantees and working capital are due before the first invoice. Read via Public procurement awards.
- A new CFO or treasurer: Banking relationships get reviewed in the first hundred days. Read via Officer filings and job adverts.
- A subsidiary or site opens: It needs currency and trade finance the current bank may not offer. Read via Company registers and building permits.
- Shopping for lenders: A finance team engages with rival lenders or reads your lending pages. Read via LinkedIn engagement and company-level site visits.

The operating calendar:
- Every quarter end: Financial covenants tested. Breaches, waivers and amendments open conversations.
- Months after a client's year end: Annual statements and reviews due. Facilities are resized, repriced or moved elsewhere.
- 6 to 12 months before maturity: Refinancing decisions begin. Borrowers collect term sheets. A late incumbent loses.
- Client budget season: Spending plans approved. Equipment finance, term loans and guarantees are needed for the year.

Who: CFO or finance director, Treasurer, Controller, Owner or managing director, Head of procurement, for guarantees.
Fact: $1.3 trillion of net income earned by banks worldwide in 2025, again the most of any industry. Source: McKinsey, Global Banking Annual Review 2026.
Fact: Up to 60% of a relationship manager's time can go to internal admin. Source: Boston Consulting Group.

Questions:
- Which banking systems does noombat integrate with? Loan origination systems such as nCino or Finastra, cores such as Temenos or Fiserv, and CRMs such as Salesforce, through their APIs or a scheduled export from your data warehouse. It reads facilities, maturities, review dates and owners.
- How does noombat see another lender's security? It reads lien and charge registers every morning. New, amended and satisfied filings are matched to your companies, with the date, lender and assets.
- Does noombat work in any country? Yes. Sources are set up per country at onboarding, from that country's company and lien registers, filings and tender feeds.
- Does noombat write into our CRM? No. It reads. Scores and reasons live in noombat and in the morning list in Slack or Teams. It never decides credit, quotes rates or contacts clients.

## Insurance, for sellers in the industry (https://noombat.ai/solutions/insurance)

You see which accounts changed risk this quarter, read from your policy system, vehicle registers, permits and benefit-plan filings. Each producer opens the account with the filing date, the people and an angle.

Systems read through their APIs: Applied Epic, Vertafore AMS360, Guidewire, Duck Creek, Salesforce Financial Services Cloud, Dynamics 365.
Public record and signals watched: Commercial vehicle registers, Operating-authority filings, Benefit-plan filings, Building and planning permits, Lien and charge registers, Officer changes, Contract awards needing cover, Fleet and risk hiring, Rival broker post engagement, Cover page visits.

The operating day:
- 9:00 · every day, Producer prospecting block (Producers and new-business executives). Signal: Tarvik Freight files a new operating authority and registers 11 trucks on 3 Mar. What changes: The first call goes to a fleet that must bind before it runs.
- Monday · weekly, New-business pipeline meeting (Sales leader and producers). Signal: Corvane Plastics' new finance director engages with two rival broker posts. What changes: The meeting reviews prospects already talking to another broker.
- 120 days before expiry, Pre-renewal strategy meeting (Account executive, account manager, risk manager). Signal: Tellmark Foods lodges a permit for a 9,000 m² cold store on 14 Jun. What changes: Values and the submission are updated before the underwriter asks.
- Month end, Cross-sell and retention review (Account managers and branch leader). Signal: Brevan Engineering, a property-only client, advertises for a fleet manager on 22 May. What changes: The review starts from single-policy clients whose operations changed.
- Quarter end, Book review and stewardship planning (Branch leader and account executives). Signal: Oduna Healthcare's benefit-plan filing shows participants down 18% for a second year. What changes: Stewardship reports are ordered by risk. Today they run by renewal month.

Use cases:
- A new fleet, no broker yet. Signal: Tarvik Freight files a new operating authority on 3 Mar and registers 11 trucks. noombat: Tops the fleet producer's list with the filing date, vehicle count and owner. Action: The producer calls about fleet and cargo cover before the first load. Result: A meeting before the operator binds elsewhere.
- Benefit-plan participation is falling. Signal: Oduna Healthcare's filing shows covered participants down 18% for the second year running. noombat: Names the current carrier, the broker, the HR director and a warm path. Action: The benefits producer offers a plan benchmark before renewal. Result: A benchmark talk the current broker has not offered.
- A property-only client buys a fleet. Signal: Brevan Engineering, insured for property only, registers 14 vans and advertises for a fleet manager. noombat: Matches both to the client in your agency system. No motor line is held. Action: The account manager raises fleet cover at the next service call. Result: A second policy on a single-policy account.
- New finance director at a key client. Signal: A filing on 9 Apr names a new finance director at Corvane Plastics, a top-20 client. noombat: Shows the rival broker posts they engaged with, and who knows them. Action: The account executive books an introduction and brings stewardship forward. Result: The relationship is rebuilt before a broker-of-record letter arrives.
- A new site before pre-renewal. Signal: Tellmark Foods lodges a permit for a 9,000 m² cold store on 14 Jun. Renewal is 1 Oct. noombat: Puts the permit on the account manager's list with 108 days to expiry. Action: The account manager asks for updated values before approaching markets. Result: A complete submission, with the new site, on time.
- A contract that needs higher limits. Signal: Salvero Maintenance wins a public contract on 2 Jul that needs higher liability limits. noombat: Links the award to the open renewal and flags the limit gap. Action: The account executive places an excess layer with the renewal. Result: Higher limits in place before the contract starts.

Moments that make a company a buyer:
- A fleet starts or grows: An operator registers vehicles. It must bind cover before it runs. Read via Vehicle registers and operating-authority filings.
- A new or bigger site: A warehouse or plant permit changes property and stock exposure. Read via Building and planning permits.
- A new CFO or risk head: The next renewal goes to someone with no tie to the current broker. Read via Officer changes in company filings.
- A benefit plan drifts: Participants fall or the carrier changes. The filing names carrier and broker. Read via Benefit-plan filings.
- A contract is won: Bonds and higher limits are conditions of the award. Read via Public procurement awards.
- Shopping the market: The team engages with rival brokers or reads your pages twice. Read via LinkedIn engagement and company-level site visits.

The operating calendar:
- 1 January, every year: The biggest reinsurance renewal. Reinsurance cost sets carrier appetite and pricing for the year.
- 1 April, 1 June, 1 July: Mid-year reinsurance renewals. Underwriters confirm or reverse January's direction.
- 120 days before expiry: Pre-renewal meeting and submission build. Values, loss history and changes must be ready before markets.
- Each client's year end: Revenue, payroll and asset values restated. The rating base changes, and so does the submission.

Who: CFO or finance director, Risk and insurance manager, HR or benefits director, Fleet or transport manager, General counsel, for directors' cover, Owner or managing director.
Fact: −6% average commercial insurance rate change worldwide, second quarter of 2026. The eighth fall in a row. Source: Marsh, Global Insurance Market Index.
Fact: 0.6% expected real growth in non-life premiums worldwide in 2026, a low point in the cycle. Source: Swiss Re Institute, sigma, World insurance in 2026.

Questions:
- Which insurance systems does noombat integrate with? Your agency management, policy and CRM systems, such as Applied Epic, Guidewire or Salesforce, through their APIs or a scheduled export. It reads expiry dates, lines held and broker of record. It writes nothing back.
- How does noombat know a client bought vehicles? It reads vehicle registers, operating-authority filings, permits and lien registers every morning. It matches each record to a company, with the date and source.
- Does noombat work in any country? Yes. Sources are set up per country at onboarding, from that country's own registers, filings and tender feeds. The model learns from your own booked meetings.
- Does noombat quote, bind or contact clients? No. It tells producers which accounts changed and why, and drafts the angle. Your team quotes, binds and calls.

## Logistics and supply chain, for sellers in the industry (https://noombat.ai/solutions/logistics)

A shipper's next bid shows months early in trade records, permits and tenders. Read each morning against your TMS and CRM, they give every owner a ranked list of shippers with the reason to call.

Systems read through their APIs: CargoWise, Magaya, Manhattan Active TM, Oracle Transportation Management, Salesforce, HubSpot.
Public record and signals watched: Import and export manifests, Warehouse building permits, New entities and sites, Transport tenders with lots, Site-closure notices, Transport and customs adverts, New logistics buyers, Freight page visits, Engagement with rivals' posts.

The operating day:
- 9:00 · every day, Morning ops and capacity call (Ops manager, carrier sales, account managers). Signal: Kestrel Home Goods sends 41 loads on its top lane, against an award of 60. Third week running. What changes: The account manager knows which award is leaking, not just which loads are open.
- 10:00 · every day, Spot quote desk (Pricing analysts, brokers, inside sales). Signal: Norrfield Beverages asks for seven spot quotes on one lane in 20 days. It hires a transport planner. What changes: Repeat spot requests from a hiring shipper flag a contract lane forming.
- Tuesday · weekly, Pipeline and shipper scorecard review (Sales director, key accounts, ops lead). Signal: Palisade Cold Chain files a permit on 2 Sep for a 24,000-pallet chilled warehouse. What changes: The review gets shippers adding sites, each with a named owner.
- Bid season, Bid-or-no-bid on lane RFQs (Bid manager, pricing, network planners, owner). Signal: Lumen Retail Group tenders 14 lots on 9 Oct. Six match lanes you run at 94% on time. What changes: The decision starts from network fit and who engaged, not reading every RFQ.
- Quarter end, Quarterly review with lane KPIs (Account director, shipper's logistics manager, ops). Signal: Orbis Components' manifests show 38% more containers on another provider's lane. Its logistics lead likes a rival's post. What changes: The review moves from on-time scores to share of lanes.

Use cases:
- A new warehouse in the permit file. Signal: On 2 Sep Palisade Cold Chain files a permit for a 24,000-pallet chilled warehouse. noombat: Matches the permit to the company. Names the head of supply chain and two warm paths. Action: Ask for a site visit before an operator is chosen. Result: A seat at the table months before the RFQ.
- Manifests show a new lane. Signal: Vantor Outdoor moves 11 containers on a new lane in six weeks. It reads your ocean freight page. noombat: Sees you sail that lane weekly. Names the logistics manager to call. Action: Offer a lane review with your record on that exact lane. Result: A one-lane trial that becomes a routing-guide slot.
- Loads leaking from an award. Signal: Kestrel Home Goods sends 41 loads a week against an award of 60, three weeks running. noombat: Compares loads in your TMS with the award in your CRM. Notes a new transport manager. Action: Call before the quarterly review and ask where the loads go. Result: Volume back in the routing guide before renewal.
- A rate sheet expiring, a new buyer. Signal: Hollin Paper's rate sheet expires 31 Jan. A new head of procurement started 1 Sep. noombat: Puts the expiry and the hire side by side, and finds who knows her. Action: Book an introduction with a lane performance summary before the RFQ. Result: A renewal talk instead of a blind rebid.
- Spot quotes that want a contract. Signal: Norrfield Beverages asks for seven spot quotes on one lane in 20 days, and hires a transport planner. noombat: Groups quotes by lane, reads the advert, and lifts the account above one-off spot traffic. Action: Propose dedicated contract capacity on that lane. Result: Contract freight instead of chasing the spot board.
- Bid-or-no-bid, with evidence. Signal: Lumen Retail Group tenders 14 lots on 9 Oct. Its logistics team commented on your peak-season post. noombat: Matches lots to lanes you run, shows who engaged, and logs the deadline. Action: Bid the six lots that fit your network. Pass on the rest. Result: Fewer, stronger bids in the busiest weeks.

Moments that make a company a buyer:
- A new site: A shipper builds or extends a warehouse, plant or distribution centre. Read via Building and planning permits.
- A new lane: Containers start moving on a route the shipper never used. Read via Import and export manifests.
- A tender is published: A shipper or public body tenders transport or warehousing in lots. Read via Public procurement notices.
- A new buyer: A new head of logistics, transport or procurement starts. Read via Profile changes and company announcements.
- A site closes: A plant or warehouse closes, and its freight moves. Read via Site-closure and mass-layoff notices.
- Interest in a rival: A shipper's logistics team engages with a rival provider's posts. Read via LinkedIn engagement with rivals' posts.

The operating calendar:
- October to March: Annual lane RFQ season. Most shippers rebid once a year. Invitations are settled before the RFQ.
- June to October: Peak season and surcharges. Capacity tightens. Shippers let down last peak find a backup first.
- Six weeks around Lunar New Year: Pre-holiday rush and factory closures. Orders pull forward and sailings fill. Missed bookings show who needs backup.
- Every contract anniversary: Rate sheet expiry. An expiry becomes a rebid unless the account owner gets there first.

Who: Head of supply chain, Transport manager, Procurement or category manager, Import and customs manager, Warehouse or operations director, CFO, for multi-year contracts.
Fact: 12.3 billion tons of goods moved by sea in 2023, up 2.4% on the year. Source: UNCTAD, Review of Maritime Transport 2024.
Fact: 44 days on average from a container entering the export port to leaving the destination port. Source: World Bank, Logistics Performance Index 2023.

Questions:
- Which logistics systems does noombat read? Your TMS or forwarding platform, such as CargoWise or Magaya, through its API or a scheduled export, and your CRM through its API. It writes nothing back.
- How does noombat see a shipper's volume shift? For accounts, it compares loads by lane in your TMS with the award in your CRM. For prospects, it reads site permits, job adverts and, where they are public, import manifests.
- Does noombat work wherever we ship? Yes. Sources are set up at onboarding for each market, from local registers, permits, trade records and tenders. Records that are not public are left out.
- Does noombat quote freight or send outreach? No. It tells each owner who to call and why, with the buyers and a drafted angle. Your team quotes, calls and writes.

## Manufacturing and industrial, for sellers in the industry (https://noombat.ai/solutions/manufacturing)

Building permits, contract awards, import records and closure notices are read each morning against your ERP and CRM, and show which companies need what you make: a buyer opening a plant, an OEM with a new contract, a rival's customers looking for a source. Each account owner gets them ranked, with the purchasing lead named.

Systems read through their APIs: SAP S/4HANA, Epicor, IFS, Infor, Oracle, Salesforce Manufacturing Cloud, Dynamics 365 Sales, Tacton CPQ, SPS Commerce.
Public record and signals watched: Building and plant permits, Public contract awards, Supply tenders with lots, Import and export records, Plant-closure and insolvency notices, Product launches and approvals, New purchasing and plant leaders, Production and purchasing adverts, Spec-sheet and product page visits, Engagement with rivals' posts.

The operating day:
- 9:00 · every day, Order desk and open-order review (Inside sales, customer service, key account managers). Signal: Ashcombe Furniture asks for samples of three hinge sizes on 4 Sep, the day after its supplier Corrick Mouldings filed a closure notice. What changes: The sample request is handled as a supplier switch, with lead times and a visit, before the buyer tries a third source.
- Monday · weekly, Sales pipeline and quote review (Sales manager, sales engineers, inside sales). Signal: Norvane Trailers wins a five-year public fleet contract on 6 Sep. Your axle quote to it is 40 days old. What changes: The old quote goes back to the buyer with the contract's volumes in it.
- Wednesday · weekly, Distributor and channel call (Channel manager, distributor sales leads). Signal: Orrin Distribution sells 30% more of your fittings in one region. Selwood Build, a contractor there, advertises for 12 site managers. What changes: The channel manager knows which end customer is behind the rise, and helps the distributor land it.
- Month end, S&OP: sales and operations planning (Key accounts, demand planner, operations, finance). Signal: Kelso Bakeries calls off 38 pallets of trays a week against an agreement of 60, four weeks running. What changes: The planner learns why volume is short. The account manager knows which lines left, and asks where they went.
- Quarter end, Key account business review (Account director, the customer's purchasing lead, quality). Signal: Tarrow Electrics names a new head of purchasing on 1 Sep. She came from a company your rival supplies. What changes: The review starts with the new buyer, before she opens the category to bids.

Use cases:
- A second plant in the permit file. Signal: On 14 Aug Pellworth Foods files a permit for a second plant, 40 km from the first. noombat: Matches the permit to the company. Names the plant director, the purchasing lead and a colleague who knows them. Action: Ask for a place on the new plant's supplier list before its first order. Result: Supplier of record at a plant that has not ordered yet.
- A rival's plant closes. Signal: Corrick Mouldings, a rival, files a closure notice for its plant on 3 Sep. Eleven of its customers are in your market. noombat: Lists the companies that import from it or name it as a supplier, and who buys at each. Action: Call each purchasing lead with lead times and samples inside the notice period. Result: A supplier switch with a date on it.
- Call-offs falling under the agreement. Signal: Kelso Bakeries calls off 38 pallets a week against an agreement of 60, four weeks running. Its plant imported two containers of trays on 28 Aug. noombat: Compares ERP call-offs with the agreement and matches the import to the customer. Action: Ask the buyer which lines moved, and quote the imported specification. Result: Share back on the agreement before the annual review.
- A new head of purchasing at a key account. Signal: Tarrow Electrics names a new head of purchasing on 1 Sep, from a company your rival supplies. noombat: Flags the appointment, her last employer's supplier and who in your team knows her. Action: Book an introduction with your quality and delivery record before she reviews the category. Result: The relationship reset before the category goes to bid.
- An old quote, a new contract. Signal: Norvane Trailers wins a five-year public fleet contract on 6 Sep. Your axle quote to it is 40 days old. noombat: Links the award to the open quote and names the programme buyer. Action: Resend the quote priced on the contract's volumes, with a delivery schedule. Result: A stalled quote back in motion, on the buyer's own numbers.
- A tender with lots that fit. Signal: On 16 Sep Brackley Rail tenders six lots of brake components. Bids close in 30 days. noombat: Matches lots to your range and to the parts you already supply Brackley. Action: Bid the two lots where your parts already run on its fleet. Result: Bids where your references already run.

Moments that make a company a buyer:
- A buyer opens or extends a plant: A customer or prospect adds a plant, warehouse or line. It needs suppliers before the first shift. Read via Building, planning and environmental permits.
- A buyer wins a contract: An OEM or contractor wins a multi-year award and needs volume it does not have. Read via Public procurement awards.
- A buyer imports your category: A company brings in from abroad what you make. The record names the goods. Read via Import and export records.
- A rival's plant closes: A competitor closes a site or enters insolvency. Its customers need a source. Read via Plant-closure and insolvency notices.
- A new head of purchasing: A new purchasing lead, plant manager or programme buyer reviews suppliers in the first year. Read via Profile changes and company announcements.
- A buyer hires to build: A company advertises production, quality or purchasing roles naming your material or process. Read via Job adverts naming materials and processes.

The operating calendar:
- September to December: Buyers' budgets and annual agreements for next year. A supplier missing from the plan by year end waits a year.
- Months before a plant opens: The new site's approved supplier list. The list is set before the first shift, from suppliers the buyer already knows.
- Every model year and launch: New programmes and component RFQs. Suppliers missing when the RFQ goes out are rarely added later.
- Every contract anniversary: Price lists and supply agreements renewed. An anniversary reopens the category unless the account owner gets there first.

Who: Head of purchasing or category buyer, Plant or operations director, Programme or product manager, Quality lead, for approvals, Supply chain director, CFO, for annual agreements.
Fact: $24.4 trillion of goods traded across borders in 2024, up 2% on the year. Source: WTO, Global Trade Outlook and Statistics, April 2025.
Fact: 16.7% of world GDP came from manufacturing in 2023, up from 14.7% in 2000. Source: UNIDO, International Yearbook of Industrial Statistics 2024.

Questions:
- Which systems does noombat read at a manufacturer? Your ERP, CRM, CPQ and EDI, such as SAP S/4HANA, Epicor, Salesforce or SPS Commerce, through their APIs or a scheduled export. It reads orders, agreements, quotes and call-offs by customer, and writes nothing back.
- How does noombat know a company will need what we make? It reads building permits, contract awards, import records, closure notices and job adverts every morning. It matches each record to the company and to the people who buy.
- Can noombat see a customer buying from a rival? For accounts, it compares call-offs in your ERP with the agreement. Where trade records are public, it matches imports of your category to the buyer. Both become a dated reason on the account.
- Does noombat work wherever we sell? Yes. Sources are set up at onboarding for each market, from local registers, permits, trade records and tenders. Records that are not public are left out.
- Does noombat quote or send outreach? No. It tells each account owner which buyer to call and why, with the people and a drafted angle. Your team quotes, samples and calls.

## Professional services, for sellers in the industry (https://noombat.ai/solutions/professional-services)

noombat reads your CRM against filings, court claims, deal notices and tenders, and finds the companies that need advice this month. Each partner gets who moved, why, and who in the firm knows them.

Systems read through their APIs: Intapp DealCloud, LexisNexis InterAction, Salesforce, Thomson Reuters Elite 3E, Aderant, Clockwork, Invenias by Bullhorn.
Public record and signals watched: Auditor changes and tenders, Court claims, Merger notifications, Insolvency notices, Advisory tenders and frameworks, Board appointments and resignations, Leadership departures, Legal operations hiring, Rival firm post engagement, Practice page visits.

The operating day:
- 08:00 · every day, Intake and conflicts queue (Intake, conflicts and the supervising partner). Signal: Pellamar Group is sued on 10 Sep and reads your disputes page twice that afternoon. What changes: The partner has conflicts cleared early, in case Pellamar calls.
- Monday · weekly, Practice group pipeline meeting (Practice leader, partners, business development). Signal: Varosk Energy files a merger notification on 5 Sep for a grid services business. What changes: The deal enters the CRM with the partner who knows Varosk.
- Wednesday · weekly, Staffing and bench meeting (Resource manager and engagement partners). Signal: Quillon Health posts 11 finance systems roles in two weeks, after appointing a new CFO. What changes: People are lined up for Quillon before a team rolls off.
- Month end, Key client review (Relationship partner and client team). Signal: Draymore Insurance's general counsel leaves on 1 Sep. Her deputy engages with a rival firm's posts. What changes: The team maps the new decision maker before the panel refresh.
- Quarter end, Tender and panel pipeline review (Managing partner, sector heads, bid manager). Signal: Halbrook Industrial's annual report, filed 29 Aug, says its audit goes to tender next year. What changes: The partner meets the audit committee chair months before the invitation.

Use cases:
- The audit goes out to tender. Signal: Halbrook Industrial's annual report of 29 Aug says it will tender its audit next year. noombat: Names the audit committee chair and a partner who shares a board with a director. Action: The partner asks for an introduction to the chair through that board. Result: An invitation from a committee that already knows you.
- The chief executive is leaving. Signal: Sorrel Brands says on 12 Sep its CEO leaves at year end. An activist investor holds a stake. noombat: Flags the succession, with the chair and the two consultants who know them. Action: The consultant closest to the chair offers a succession conversation. Result: A retained search signed without a pitch contest.
- A panel review is coming. Signal: Draymore Insurance advertises a head of legal operations role on 3 Sep, days after its general counsel left. noombat: Reads it as the start of a panel review and names who knows the acting counsel. Action: The client team offers a service review before any tender is drafted. Result: The firm keeps its panel place by asking first.
- A key client buys a business. Signal: Varosk Energy, an advisory client, files a merger notification on 5 Sep for a grid services business. noombat: Adds the filing to the account with the teams that worked with Varosk. Action: The relationship partner proposes one integration team under the current engagement letter. Result: Integration work stays with your firm.
- A statement of work stalled. Signal: Ashbury Logistics' transformation statement of work has waited since July. It appoints a new COO on 2 Sep. noombat: Moves it up with the new COO's last employer and an alumnus who knows him. Action: The partner arranges an introduction and resubmits in the new sponsor's terms. Result: A stalled proposal goes back to a decision.
- The buyer is reading your case studies. Signal: Three weeks after your tender response, Kelvane Water reads your case studies seven times, 8–11 Sep. noombat: Flags the evaluation as live and names the procurement lead and sponsor. Action: The bid team prepares for clarification questions and asks to present. Result: Ready for the clarification round a week early.

Moments that make a company a buyer:
- An auditor change or tender: An audit committee opens the appointment to other firms. Read via Securities filings and annual reports.
- A company sues or is sued: Disputes counsel is chosen in days, often from firms already known. Read via Court dockets and new claims.
- A deal is notified: Deal, integration, tax and employment advice follow. Read via Merger notifications and announced acquisitions.
- The general counsel or CFO changes: Panels, auditors and advisers are reviewed within the first year. Read via Director filings and announced appointments.
- A CEO departure is announced: Boards start a succession search and often a team assessment. Read via Announced departures and director resignations.
- Advisory work goes to tender: Public buyers tender legal, audit and consulting work on a set timetable. Read via Public procurement notices and awards.

The operating calendar:
- After the most common year end: Audit busy season. Audit teams stop business development. Firms that keep in touch meet the tenders.
- Annual general meeting season: Auditor and board changes approved. Changes go public and set up next year's tenders and searches.
- Client budget season: Adviser budgets set for next year. Firms named in the plan get the work.
- Every two to three years: Panel reviews and framework re-tenders. Incumbents who see the review coming defend their place early.

Who: Audit committee chair, CFO or finance director, General counsel, Board chair or nominations committee, Procurement or legal operations head, People or HR director.
Fact: $275 billion forecast for the worldwide consulting market in 2025, up 6% on the year. Source: Source Global Research.
Fact: 234 chief executive departures in 2025, the most in the index's eight years. Source: Russell Reynolds Associates, Global CEO Turnover Index.

Questions:
- Which professional services systems does noombat integrate with? CRMs such as DealCloud, InterAction or Salesforce through their APIs; practice management such as Elite 3E or Aderant through their APIs or a scheduled export; search platforms such as Clockwork or Invenias for the searches and their clients.
- How does noombat know an audit is going to tender? It reads securities filings and annual reports every morning. A disclosed auditor change or tender becomes the reason on that account, with date and wording.
- Does noombat find warm introductions through our partners? Yes. It reads your team's LinkedIn connections and shared board seats, and shows who already knows someone at the account.
- Does noombat work in any country? Yes. Sources are set up per country at onboarding, from that country's registers, securities filings, court dockets and tender feeds.
- Does noombat replace conflict checks or contact prospects? No. It is not a conflicts system and never reaches out. It tells a partner which company to approach and why. Intake still clears the matter.

## Telecoms and IT services, for sellers in the industry (https://noombat.ai/solutions/telecoms)

DNS changes, tenders, new sites and vendor end-of-support dates are read each morning beside your PSA, RMM and CRM, and show which organisations need managed IT now. Each account manager and rep gets the list with the reason and the person to call.

Systems read through their APIs: ConnectWise PSA, Autotask, HaloPSA, NinjaOne, Kaseya VSA, N-able, ServiceNow, HubSpot, Salesforce.
Public record and signals watched: Vendor end-of-support dates, DNS and MX changes, Connectivity and IT tenders, New registered sites, Tools in job adverts, Disclosed cyber incidents, New IT leaders, Service page visits, Engagement with rivals' posts.

The operating day:
- 08:00 · every day, Service desk stand-up (Service manager, dispatch, NOC, account manager). Signal: VPN tickets at Veltra Dental rise from 4 to 19 in a week, all from its newest site. What changes: A pattern pointing to a network refresh reaches the account manager that morning.
- Tuesday · weekly, Sales meeting (New-business reps, account managers, presales). Signal: Ondrel Manufacturing moves its email to a new platform on 11 Sep. It hires an IT generalist. What changes: Reps spend time on prospects mid-change, each with a named contact.
- Friday · weekly, Bid or no-bid review (Bid manager, presales, sales director, delivery). Signal: Calloway Water tenders managed network and voice on 10 Sep. Three staff engaged with your case study. What changes: The bid decision weighs relationships and engagement, not only the specification.
- 90 days before contract end, Renewal and co-term planning (Account manager, vCIO, finance). Signal: Pellam Legal's connectivity contract ends 12 Dec, its firewall 30 Jan. It registers a second office. What changes: Circuit, firewall and new site become one agreement, before the client shops around.
- Every quarter, Technology business review (TBR) (vCIO, account manager, client's leadership). Signal: 38 of Brackwater Logistics' 120 devices need paid Windows 10 updates. Two servers lose support 12 Jan 2027. What changes: Lifecycle risk arrives ranked by date, so the review is about budget.

Use cases:
- An email platform move in DNS. Signal: On 11 Sep Ondrel Manufacturing points its mail records to a new email platform. noombat: Spots the DNS change, names the director who owns IT and a partner who knows him. Action: Offer migration clean-up, security and backup through the warm path. Result: A first meeting while the migration is under way.
- A tender for managed services. Signal: Calloway Water tenders managed network and voice on 10 Sep, closing 15 Oct. noombat: Matches the notice to your services and maps which evaluators engage with you. Action: The bid manager brings a qualified call to Friday's review. Result: Presales time goes only on winnable bids.
- Devices past end of support. Signal: Brackwater Logistics has 38 Windows 10 devices on paid updates. Two servers lose support 12 Jan 2027. noombat: Checks your RMM inventory against vendor dates and puts the budget on the vCIO's list. Action: The vCIO brings a dated refresh plan to the review. Result: A refresh approved a quarter ahead.
- A ticket spike at a new site. Signal: Veltra Dental's VPN tickets rise from 4 to 19 in a week, all from its August site. noombat: Links the tickets to the new site in the company register. Action: Propose a site survey and a managed SD-WAN link. Result: Recurring revenue from a site eating unbilled hours.
- Co-term before the market test. Signal: Pellam Legal's connectivity contract ends 12 Dec. A new finance director joined on 1 Sep. noombat: Lines up every end date and names the new finance director and her connections. Action: Meet her with one renewal for circuit, firewall and backup. Result: Renewal secured before a rival is asked to quote.
- A contact-centre deal gone quiet. Signal: Sorrel Home Care's contact-centre deal is quiet for 30 days. A 9 Sep advert names a rival platform. noombat: Reads the advert as proof the rival is in, and names the operations lead. Action: The AE re-engages the operations lead with a reference call. Result: The evaluation reopens before the shortlist closes.

Moments that make a company a buyer:
- Devices reach end of support: Systems, servers or network gear lose vendor security updates. Read via Vendor dates matched to your RMM inventory.
- An email platform moves: A company changes where its email or website is hosted. Read via DNS and MX record changes.
- A tender is published: An organisation invites bids for connectivity, voice or managed IT. Read via Public procurement notices.
- A new site opens: A new office, clinic or depot needs lines, network and devices. Read via New sites in company registers.
- A cyber incident is disclosed: An organisation reports a breach, and security budgets reopen. Read via Filings and announcements disclosing an incident.
- A tool named in an advert: A prospect hires for a platform you support or replace. Read via Tools named in job adverts.

The operating calendar:
- 14 Oct 2025: Windows 10 and Office 2016/2019 left support. Paid Windows 10 updates double in price yearly. Each device is a refresh talk.
- 12 Jan 2027: Windows Server 2016 support ends. Servers need replacing, moving to cloud or paid updates. That puts them in budget.
- 90 days before contract end: Circuit, voice and managed service renewals. The window to co-term before the client shops around.
- Client's first fiscal quarter: IT budgets and licence renewals. A roadmap item not agreed at the review waits a year.

Who: Managing director or owner, Head of IT, CFO or finance lead, Operations director, CISO, for security, Procurement, for tenders.
Fact: 5.8 billion unique mobile subscribers worldwide, around 70% of the world's population. Source: GSMA Intelligence, The Mobile Economy 2026.
Fact: 1 in 3 managed service providers say winning new customers is their biggest challenge. Source: Kaseya, 2025 Global MSP Benchmark Report.

Questions:
- Which systems does noombat read for an MSP? Your PSA and RMM, such as ConnectWise, HaloPSA, NinjaOne or N-able, and your CRM, through their APIs. It writes nothing back.
- Can noombat warn us before a client leaves? Yes. It matches devices to end-of-support dates and watches contract dates, tickets, DNS changes and in-house IT adverts. When they line up, the client moves up.
- Does noombat work wherever we sell? Yes. Public sources are set up at onboarding for each market, from local company registers, filings and tender feeds.
- Does noombat send outreach or quotes? No. It tells your team who moved, why, who decides and a suggested angle. Quotes, calls and emails stay with your people.

## Account-based marketing, for the team (https://noombat.ai/solutions/account-based-marketing)

Every Monday the tier-one list is rebuilt from your booked meetings. Each account arrives with its buying group, who already knows them, and score and tier written to your CRM.

Systems read through their APIs: Salesforce, HubSpot, LinkedIn Campaign Manager, LinkedIn Ads API, PostHog, Slack or Teams.
Public record and signals watched: LinkedIn engagement, rivals' too, Competitor ads, Job adverts naming tools, Funding and filings, Company registers, Tenders, Event speakers and attendees, Website visits.

Use cases:
- Rebuild tier one every Monday. Signal: This week: a job advert names a rival's tool, the CFO reacts to a rival, three pricing visits. noombat: Moves the account to tier one. Names seven decision-makers and two people who know them. Action: The owner gets it in Slack. Marketing starts a one-to-one play. Result: Tier-one meeting rate and accounts that become deals.
- Win accounts after a rival's launch. Signal: People at target accounts react to a rival's launch. The rival starts new ads. noombat: Groups engagers by company, names who decides, and logs the rival's ads with dates. Action: A small-group play with comparison ads. Result: Competitive pipeline and win rate.
- Expand through your champion. Signal: A customer registers a subsidiary. Four people from a unit you don't serve read your docs. noombat: Scores the expansion. Names the new unit's decision-makers and the path through your champion. Action: The account manager runs a one-to-one expansion play. Result: Expansion pipeline and revenue kept from customers.
- Ad audiences from rising accounts. Signal: Customers, open deals and recent losses sit in the same audience as prospects. noombat: Keeps a daily Hot list in your CRM of accounts on the rise. Action: Paid syncs it to LinkedIn and excludes customers and open deals. Result: More spend on accounts ready to buy.
- Fill the gap in a stalled deal. Signal: Stalled for 41 days. Procurement follows a rival, but nobody from procurement is on the deal. noombat: Flags the gap. Names the procurement lead and who on your team knows them. Action: Marketing targets that account. The account executive adds contacts. Result: Faster stages and fewer slipped deals.
- Book meetings before an event. Signal: The speaker and attendee list for a sector summit on 7 Oct. noombat: Returns the top 25 people most likely to meet, each with an angle. Action: Meetings booked before the event. Result: Meetings per event.

Signals that matter:
- Engagement with a rival: Someone at a target account engages with a rival's launch. Read via Rivals' LinkedIn posts and ads.
- A buying group engaging: Named people at one account react to your posts and ads. Read via Your posts and LinkedIn ads, by company.
- A hire into the buying team: A new leader reviews the tools in their first ninety days. Read via LinkedIn and job adverts.
- A public trigger: A new subsidiary, tender or funding round says it is time to act. Read via Registers, tenders, filings.
- Ad attention: Accounts that keep watching your ads for weeks. Read via LinkedIn Ads data, by company.
- A website visit: The account reads your pricing page after seeing your ads. Read via Your website, the company behind the visit.

What it moves: Tier-one meeting rate (Tiers follow this week's buying signals.); Buying group coverage (Every decision-maker named, with who already knows them.); Accounts that become deals (Ranked by chance of a meeting.); Spend on in-market accounts (Audiences refresh daily as each account's chance moves.)

Who: Account-based marketing lead, Demand and paid, Account executives, Sales development reps, Revenue operations, Marketing leadership.
Fact: 13 + 9 people shape a typical business purchase: 13 inside the buyer, 9 outside. Source: Forrester, The State of Business Buying, 2026.
Fact: 47% of account-based marketing teams name proving return on investment as their top challenge. Source: Demand Gen Report, ABM Benchmark Survey 2025.

Questions:
- How is noombat different from an ABM platform? noombat picks the accounts. An ABM platform runs campaigns at them. Each week noombat decides which accounts belong on the list, and why.
- Does noombat run our ads? No. It keeps audience lists fresh in your CRM and reads LinkedIn ad engagement by company. Your team runs the campaigns.
- Does noombat find the buying group? Yes. It spots them in engagement with your posts, ads and rivals' posts, in hiring and in public records. It adds verified contacts.
- Does noombat work for target accounts anywhere? Yes. Sources are set up at onboarding, from local company registers and tender feeds. It names the company behind a visit, and the person where the law and data allow.

## Demand generation, for the team (https://noombat.ai/solutions/demand-generation)

The companies behind visits, post reactions and ad attention are named and scored on your booked meetings. The best reach their owner the same day, so spend follows the channels that produce meetings.

Systems read through their APIs: HubSpot, Salesforce, Pipedrive, LinkedIn Ads, LinkedIn Lead Gen Forms, PostHog, Cal.com, Slack or Teams.
Public record and signals watched: Website visits and sessions, LinkedIn engagement, LinkedIn ad attention, Competitor engagement, Job adverts naming tools, Funding and filings, Tenders, Events.

Use cases:
- Follow up visitors who skip the form. Signal: A company reads pricing and integrations twice this week, without a form. noombat: Names the company, scores it, drafts the angle and alerts the owner in Slack. Action: The owner follows up the same day. Result: Pipeline from traffic that used to read as direct.
- Triage inbound requests the same day. Signal: A demo request on Friday at 18:40, from an account already active. noombat: Sends it to the owner with context. Weak requests go to nurture. Action: The owner calls on Friday, not Monday. Result: Speed to lead and meetings held.
- Build a trigger cohort. Signal: 38 manufacturers posted job adverts naming an ERP migration in 30 days. noombat: Builds the group, ranks it and keeps it fresh in the CRM. Action: Marketing runs a programme. The top ten go straight to owners. Result: Pipeline per trigger.
- Split spend by chance of a meeting. Signal: The same offer runs to every account in the audience. noombat: Splits accounts into three bands: high gets the demo offer, middle gets proof, low nothing. Action: Paid moves budget by band. Result: Cost per qualified opportunity.
- Find the signals that predict meetings. Signal: Webinars, posts, ads and visits all look busy in the report. noombat: Shows which evidence leads to meetings in your market, and which does not. Action: Budget moves to what books meetings. Result: Cost per meeting.
- Reopen a lost deal. Signal: Lost seven months ago on timing. Now a new VP, a tender and a pricing visit. noombat: Flags the account and shows what changed next to the loss reason. Action: The owner reopens the opportunity. Result: Recycled pipeline.

Signals that matter:
- A visit with intent: Pricing, integrations and comparison pages, read twice in a week. Read via Your website, company and person where allowed.
- A recorded session: A minute on pricing means a comparison is under way. Read via Session replays on your site.
- Ad attention: Companies that keep watching your ads for weeks. Read via LinkedIn Ads data, by company.
- Reactions to your posts: Named people at target accounts. Read via Your posts and promoted posts.
- A rival's audience: People engaging with a competitor's content. Read via Rivals' LinkedIn posts and ads.
- A hiring trigger: Job adverts naming the problem you solve. Read via Job adverts and careers pages.

What it moves: Marketing-sourced pipeline (Visits and engagement turned into named, routed accounts.); Speed to lead (Hot accounts reach their owner the same day.); Cost per qualified opportunity (Budget follows the chance of a meeting.); Meetings held (The signal mixes that book meetings, from your own data.)

Who: Demand generation, Paid media, Marketing ops, Sales development reps, Account executives.
Fact: 59% of marketing chiefs say budget falls short of strategy, with marketing flat at 7.7% of revenue. Source: Gartner, CMO Spend Survey 2025.
Fact: 95% of business buyers are not in market at any given time. Source: Ehrenberg-Bass Institute and the LinkedIn B2B Institute.

Questions:
- How is this different from our lead scoring? It predicts meetings. A points score adds up clicks. The model learns from the meetings your pipeline booked, and old evidence fades.
- Does noombat identify anonymous website visitors? Yes. It names the company behind a visit, and the person where the law and data allow.
- Does noombat read LinkedIn Ads data? Yes, through the LinkedIn Marketing API. It shows companies reached, engaged and booked in the same dates, plus ad attention by company.
- Does noombat send nurture emails? No. It ranks and routes accounts. Your marketing automation sends the emails.

## Marketing attribution, for the team (https://noombat.ai/solutions/marketing-attribution)

One dated timeline per company holds post reactions, ad views, visits, email opens and booked meetings. Marketing ops can tie LinkedIn ad reach to a meeting and name the people behind influence no cookie saw.

Systems read through their APIs: HubSpot, Salesforce, LinkedIn Ads API, PostHog, Cal.com, Salesforge or Reply, Pipedrive or Attio.
Public record and signals watched: Posts, organic and promoted, LinkedIn ad reach, attention, Website journeys, Session replays, Email opens and clicks, Meetings booked, Competitor engagement, Company registers.

Use cases:
- Explain a meeting marked direct. Signal: 19 Aug: a VP reacts to your founder's post. Then ads, a pricing visit, a 'direct' meeting. noombat: Writes all three touches onto the company timeline, with names and dates. Action: The meeting is reclassified in reporting. Result: Share of pipeline with known touches.
- Prove founder posts work, by name. Signal: Leadership asks if founder posts are worth the time. noombat: Lists the quarter's named engagers and which companies booked meetings. Action: The team defends the social budget with evidence. Result: Pipeline influenced by organic posts.
- Tie LinkedIn ad reach to meetings. Signal: LinkedIn reports impressions. The board asks for meetings. noombat: Shows target companies reached, engaged and booked in the same dates, with dwell time. Action: Budget moves to campaigns that reach accounts that book. Result: Pipeline per unit of spend.
- Settle a credit dispute. Signal: Sales development claims a deal as outbound-sourced. noombat: Shows eleven touches from four decision-makers before the first reply. Action: Both teams use one shared record of credit. Result: Trust in reporting.
- Add missing contacts to deals. Signal: Campaign influence looks low because each deal has one contact. noombat: Lists decision-makers who engaged but are not on the deal. Action: Marketing ops adds them as contact roles. Result: Influence coverage.
- Check what a 20% chance means. Signal: Sales asks whether a 20% chance of a meeting means anything. noombat: Shows the model's checks on your outcomes: ranking, top-tenth capture, calibration. Action: Routing thresholds are set from evidence. Result: Sales trust in marketing-sourced accounts.

Signals that matter:
- A post reaction: A named person at a known company, with a date. Read via Your posts and promoted posts.
- An ad seen, with attention: Reach and dwell time by company, over weeks. Read via LinkedIn Ads data.
- An ad click: The campaign behind the visit. Read via LinkedIn Ads, tracking links, landing pages.
- A journey on your site: Pages read in order, with the session recorded. Read via Your website and session replays.
- An email opened: The email that came before the reply. Read via Email open dates in your CRM.
- A meeting booked: The outcome every other touch is measured against. Read via Cal.com and your CRM.

What it moves: Meetings with known touches (One dated timeline per company, by name.); Influenced pipeline (Posts and ads tied to accounts that booked.); Ads to meetings (Reached, engaged and booked in the same dates.); Reporting trust (Marketing and sales read one timeline.)

Who: Marketing ops, Marketing analytics, Demand generation, Social and content, Revenue operations, Marketing leadership.
Fact: 100% of Slack, WhatsApp and Discord link visits showed as direct in testing. Public LinkedIn posts: 14%. Source: SparkToro, dark social research.
Fact: 53% of marketing decisions are shaped by marketing analytics. Source: Gartner, Marketing Analytics Survey.

Questions:
- Is noombat a multi-touch attribution tool? No. It does not split revenue credit. It keeps the dated touches per company that attribution needs, and ties LinkedIn ad reach to meetings.
- What happens when visitors decline cookies? Most of the timeline needs no cookie. LinkedIn engagement, ad reach by company, company registers and your CRM still tell the account's story.
- Does noombat use LinkedIn Ads data for attribution? Yes, through the LinkedIn Marketing API. It adds reach and ad attention to each company's timeline, next to the meetings that followed.
- Does the timeline sync to our CRM? Partly. Score, tier and chance of a meeting go into new CRM fields. The full timeline stays in noombat, where Snout, the AI analyst, answers questions.

## Social media, for the team (https://noombat.ai/solutions/social-media)

Every reaction and comment on company, founder, employee and rival posts gets a name, matched to target accounts and open deals. The social team sees which posts reach buyers, and the account owner gets the alert.

Systems read through their APIs: LinkedIn company page, Founder and employee profiles, LinkedIn Ads API, HubSpot or Salesforce, Slack or Teams.
Public record and signals watched: Reactions and comments, Promoted posts, Competitors' posts and engagers, Competitor ads, Job changes, Visits after a post, Company registers.

Use cases:
- Send post engagers to the deal owner. Signal: The CEO's post on 9 Sep gets 212 reactions and comments. noombat: Finds 31 people at target accounts, 4 on open deals, 2 CFOs missing from the CRM. Action: Each deal owner gets a Slack card with the angle. Result: Meetings influenced by social.
- Find topics that attract decision-makers. Signal: Ninety days of posts, from pricing teardowns to team milestones. noombat: Compares, per topic, the share of target-account engagers and the meetings that followed. Action: The editorial calendar shifts toward what buyers read. Result: Engagement from target accounts, counted by name.
- Reach a rival's launch audience. Signal: A rival posts a launch on 3 Sep. 22 engagers work at target accounts with no deal. noombat: Names them and who knows them. Flags companies hiring for the rival's tool. Action: The founder posts a view. Owners reach out. Result: Meetings won from a rival's audience.
- Measure advocates by who engages. Signal: An engineer's posts draw nine decision-makers at rising accounts. The company page draws none. noombat: Shows named engagers by account for every author. Action: That post runs as a thought-leader ad to those accounts. Result: Decision-makers engaged per post.
- Report follower quality. Signal: Follower growth is reported as a number. noombat: Reports the share of new followers at target accounts. Action: The team reports who engaged, by account. Result: A metric leadership believes.
- Re-engage a lost account. Signal: Three people at a lost account react to your posts. It also posts a relevant job. noombat: Flags the account and alerts the owner. Action: The owner re-engages on the topic they reacted to. Result: Recycled pipeline.

Signals that matter:
- A reaction or comment: A named person at a known company, on a known topic. Read via Your company, founder and employee posts.
- A comment thread: A public question in the comments is a question for sales. Read via Comments on your posts.
- Engagement with a rival: Someone engaging with a competitor's post. Read via Rivals' posts.
- A follow: A new follower at a target account. Read via Your company page.
- A visit after the post: The engager's company lands on your site. Read via Your website.
- A job change: A past engager starts at a new account. Read via LinkedIn.

What it moves: Target-account engagement (The share of engagers at your target accounts.); Deals touched (Engagers on open deals, sent to their owners.); Topic yield (Which topics draw decision-makers.); Rival's audience (Named people engaging with a competitor.)

Who: Social media lead, Content marketing, Founders and executives, Employee advocates, Account executives.
Fact: 63% of hidden buyers, who shape deals unseen by sales, read thought leadership over an hour weekly. Source: Edelman and LinkedIn, B2B Thought Leadership Impact Report 2025.
Fact: 40%+ of business deals stall because the buying group does not agree. Source: Edelman and LinkedIn, B2B Thought Leadership Impact Report 2025.

Questions:
- Can noombat see who engages with rivals' posts? Yes. It reads reactions and comments on the competitor posts you pick, and names the people and their companies.
- Does noombat track founder and employee posts? Yes, plus the company page and promoted posts.
- Does noombat post or schedule content? No. Keep your publishing tool. noombat tells you who engaged and what it is worth.
- What data does noombat use to name people? Public LinkedIn engagement, public records and your CRM. Website visits name a company, and a person where the law and data allow.

## Paid ads & performance, for the team (https://noombat.ai/solutions/paid-ads)

You spend on the accounts likely to book. LinkedIn Ads is read by company, reach, attention and meetings in the same dates, and daily Hot, Warm and Cold lists in your CRM feed the ad audiences.

Systems read through their APIs: LinkedIn Campaign Manager, LinkedIn Ads API, LinkedIn Lead Gen Forms, PostHog, HubSpot or Salesforce, Cal.com.
Public record and signals watched: LinkedIn ad reach, attention, Promoted-post engagers, Competitor ads, Competitor post engagers, Website visits after ads, Job adverts, Funding and filings.

Use cases:
- Retarget the accounts that are rising. Signal: The audience holds hundreds of accounts. A few dozen showed new buying signals. noombat: Keeps a daily Hot list in your CRM of accounts on the rise. Action: The list syncs to an always-on ad set. Result: Pipeline per unit of spend.
- Target a rival's launch audience. Signal: A rival's launch post draws engagers. Its new ads appear the same week. noombat: Groups engagers by company and logs each rival ad with the date first seen. Action: A comparison campaign to that company list. Result: Deals won from that competitor.
- Cut spend on the wrong accounts. Signal: Campaign reporting shows 1,200 engaged companies. noombat: Shows the share outside your target market, and the campaigns reaching rising accounts. Action: Budget is cut or moved. Result: Wasted spend and cost per opportunity.
- Reach, attention and meetings side by side. Signal: Impressions are up. The board asks what they bought. noombat: Shows target companies reached, engaged and booked in the same dates, with attention per account. Action: Creative and budget move to accounts that watch and book. Result: Cost per meeting.
- Show pricing visitors a next-step offer. Signal: Hot accounts that visited pricing still see early-stage ads. noombat: Keeps a daily Hot Website Visitors list in your CRM. Action: The list syncs to a late-stage ad set. Result: Blended acquisition cost.
- Watch competitors' ads. Signal: A competitor starts running 'alternative to' ads. noombat: Shows the new ads with dates, next to the accounts engaging. Action: Creative and comparison keywords change the same week. Result: Share of voice held.

Signals that matter:
- An ad seen, with attention: Dwell time by company, averaged across weeks. Read via LinkedIn Ads data.
- An ad clicked: The campaign that brought the account in. Read via LinkedIn Ads and your landing pages.
- Engagement on a promoted post: Named engagers on paid posts, with the campaign. Read via Promoted posts in active campaigns.
- A competitor's new ad: What a rival started saying, and when. Read via LinkedIn ad library search.
- A visit after the ad: The account lands on your pricing page. Read via Your website.
- A rival's engagers: People engaging with a competitor's content. Read via Rivals' LinkedIn posts.

What it moves: Pipeline per ad spend (Reach and meetings in the same dates.); In-market share of spend (Audiences of accounts whose chance rose this week.); Cost per opportunity (Off-target engagement shown by campaign, so you can cut it.); Competitive share (A dated record of what rivals advertise.)

Who: Paid media manager, Performance marketing, Demand generation, Marketing ops, Account-based marketing lead.
Fact: 95% of business buyers are out of market at any time. Follow the ones who aren't. Source: LinkedIn B2B Institute and Ehrenberg-Bass Institute.
Fact: 300 matched members is LinkedIn's minimum audience to serve an ad set. Source: LinkedIn Marketing Solutions help.

Questions:
- Does noombat connect to LinkedIn Ads? Yes, through the LinkedIn Marketing API. It reads campaign reports, companies reached and engaged, ad attention by company, and the posts behind campaigns.
- Does noombat push audiences to ad platforms? Through your CRM. It keeps daily Hot, Warm and Cold lists there, and your CRM's ad integrations sync them to LinkedIn, Google and Meta.
- Can noombat track competitors' LinkedIn ads? Yes. It keeps a dated record of rivals' LinkedIn ads, next to the accounts engaging with them.
- Does noombat manage bids or budgets? No. It shows where budget should go. Your team and ad platforms run it.

## Growth, for the team (https://noombat.ai/solutions/growth)

Growth experiments are measured in meetings. Your own data shows which signals come before one, hot signups go to sales the same hour, and session replays are filtered to the top accounts.

Systems read through their APIs: PostHog, LinkedIn Ads API, HubSpot or Salesforce, Your warehouse, Cal.com, Slack.
Public record and signals watched: Signups and form fills, Site journeys and replays, LinkedIn engagement, LinkedIn ad attention, Job adverts naming tools, Funding and filings, Competitor engagement.

Use cases:
- Run a play on signals that book. Signal: A job advert naming a rival's tool, plus two pricing visits in a week, books far above average. noombat: Builds the segment and keeps it current. Action: Growth runs the play against a control group of accounts. Result: Experiment win rate and meetings per play.
- Hand a hot signup to sales. Signal: 8 Sep: a free signup from an account whose decision-makers engaged this week. noombat: Names the decision-makers and who knows them. Alerts the owner in Slack. Action: Sales follows up the same day. Result: Signup to meeting.
- Watch replays from your top 10% only. Signal: Replays from top accounts show visitors quitting the sales form at a required phone field. noombat: Filters session replays to the accounts that matter. Action: Growth tests the form without the phone field. Result: Visit to meeting for target visitors.
- Test speed to lead. Signal: High-intent inbound leads wait in a queue. noombat: Routes high-intent leads to the owner, with the reason. Action: Growth measures it against the normal queue. Result: Meeting rate and time to first touch.
- Ranked list versus static list. Signal: A static account list against one ranked by chance of a meeting. noombat: Provides the ranked list, refreshed daily, split into test groups. Action: Paid runs the test. Growth owns the design. Result: Meetings per unit of spend.
- Pause programmes that don't book. Signal: Every channel reports its own success. noombat: Shows which evidence predicts your meetings, refit weekly. Action: Low-yield programmes are paused. Result: Cost per meeting.

Signals that matter:
- A signup: A free account from a company already showing buying signals. Read via Website forms and your CRM.
- A visit to pricing: Where visitors hesitate and drop off. Read via Session replays.
- Signals that book: The signals that weigh most toward a meeting in your data. Read via The model, refit weekly.
- Post engagement: Decision-makers react to your posts. Read via Your LinkedIn posts.
- Ad attention: Accounts that spend time on your LinkedIn campaigns. Read via LinkedIn Ads data.
- A hiring trigger: A job advert naming the problem you solve. Read via Job adverts.

What it moves: Experiment win rate (Plays built on the evidence behind your meetings.); Signup to meeting (Signups with buying signals go to sales assist.); Speed to lead (Hot leads go straight to an owner.); Cost per meeting (Programmes judged on the meetings they produce.)

Who: Growth marketing, Product-led growth, Paid media, Marketing ops, Sales assist.
Fact: 8% of Google searches with an AI summary led to a click, against 15% without. Source: Pew Research Center, 2025.
Fact: 67% of business buyers prefer to buy without a sales rep. Source: Gartner, 2026 sales survey.

Questions:
- Can we trust the model to design experiments? Yes, because every refit is checked. It is refit weekly on your outcomes and tested for ranking and calibration. A worse refit is rejected.
- Does noombat run A/B tests? No. It gives growth the segments, routing and evidence. Your testing tool runs the tests.
- Does noombat read product usage data? Partly. It reads site journeys and session replays from PostHog. Signups count when they reach your CRM as form fills.
- Is noombat only for product-led companies? No. Account-level plays work for sales-led teams too. The control group is a list of accounts.

## RevOps, for the team (https://noombat.ai/solutions/revops)

Revenue operations gets a score it can defend: a model refit weekly on your meetings and checked for quality. Accounts are routed with the reason, and each data source shows whether it earns its keep.

Systems read through their APIs: Salesforce, HubSpot, Attio, Pipedrive, Your sequencer, Your enrichment vendors, Slack or Teams, Your warehouse.
Public record and signals watched: Job changes and departures, Mergers and dissolutions, Website visits, LinkedIn engagement, Job adverts naming tools, Funding and filings, Tenders.

Use cases:
- Retire the points score. Signal: The lead score dates from 2021. A webinar is worth 15 points. noombat: Fits a model on your meetings, compares it with the old score, writes its own fields. Action: Both scores run for 30 days. Then the points score retires. Result: Share of meetings in the top tenth.
- Route to the owner, with the reason. Signal: 2 Sep: a named account reads pricing. 3 Sep: it posts a job in your category. noombat: Finds the owner in the CRM. Sends the reason and a brief to Slack or Teams. Action: The owner works the account within your team's target. Result: Speed to lead.
- Prune the stack. Signal: Renewals for intent data, visitor ID, job-change alerts and enrichment fall due next quarter. noombat: Shows which signal families predict your meetings, in the weekly fit. Action: Sources with no lift are downgraded or cancelled. Result: Tool spend per meeting.
- Rebalance territories. Signal: One rep has 38 hot accounts untouched for 14 days. Another has 4. noombat: Snout, the AI analyst, counts hot accounts per owner and lists the untouched ones. Action: Idle hot accounts are reassigned. Result: Hot accounts touched within a week.
- Clean CRM records with public data. Signal: A contact left in July. A company register shows a merger. noombat: Flags job changes, mergers and closures from LinkedIn and company registers. Action: RevOps cleans records and re-parents accounts. Result: Stale-contact rate.
- Check risk on a committed deal. Signal: A committed deal: no two-way contact in 34 days, champion gone, two decision-makers eyeing a rival. noombat: Raises a risk, with the evidence. Action: The deal moves out of commit in the pipeline review. Result: Committed deals that close.

Signals that matter:
- A booked meeting: The outcome the model learns from. Read via Your CRM and calendar.
- A champion leaves: An open deal at risk, and a way into a new company. Read via LinkedIn.
- A company changes: Mergers, closures and new entities that need CRM cleanup. Read via Company registers.
- A high-intent visit: Routed to the owner with the reason, while it is hot. Read via Your website.
- A hiring trigger: A job advert naming your category. Read via Job adverts.
- A team connection: Someone on your team already knows them. Read via Your team's relationships.

What it moves: Model quality (Ranking and calibration checks, shown for every fit.); Speed to lead (Owner routing, with the reason.); Tool spend per meeting (Sources judged on the lift they add in your data.); Deal risk (Risks on committed deals flagged early, with evidence.)

Who: Revenue operations, Sales ops, Marketing ops, Sales leadership, Finance.
Fact: 50% of sellers feel overwhelmed by their tech, and are 45% less likely to hit quota. Source: Gartner, 2024 sales survey.

Questions:
- How is noombat's scoring model built? It learns from your own booked meetings. Each signal counts by how often it came before a meeting, and old evidence fades. A weekly refit that ranks worse is rejected.
- Does noombat write to our CRM? Yes. Score, tier and chance of a meeting go into its own fields, so nothing is overwritten. It can stay read-only.
- Which CRMs does noombat work with? HubSpot, Salesforce, Pipedrive and Attio. Routing alerts go to Slack or Teams.
- Who maintains noombat? We configure and run it for you. RevOps owns the rules and thresholds. We own the plumbing.

## Account executives, for the team (https://noombat.ai/solutions/account-executives)

The day your champion leaves, a new executive lands or the account warms to a rival, you know. Each open deal and target account carries every decision-maker, who in your company knows them, and the angle.

Systems read through their APIs: Salesforce, HubSpot, Your sequencer, Your calendar, Slack or Teams.
Public record and signals watched: Job changes, new executives, LinkedIn engagement, rivals' too, Competitor ads, Website visits, Funding and filings, Tenders, Job adverts naming tools, Company registers.

Use cases:
- Revive a stalled deal. Signal: 61 days in evaluation. 28 Aug: a new VP Ops joins, and pricing is read three times. noombat: Names the new VP, finds your CEO knows them, writes the angle. Action: A warm introduction, then a new discovery call. Result: Faster stages and shorter cycles.
- Act when the champion leaves. Signal: 5 Sep: the champion's LinkedIn shows a new employer. noombat: Flags the deal, names who is left, and adds the new company to your list. Action: Add contacts to the deal. Open a conversation at the new company. Result: Win rate when champions move.
- Counter a rival mid-deal. Signal: 9 Sep: two decision-makers react to a rival's post. The rival advertises to them. noombat: Shows who engaged and when, with an angle for the comparison. Action: Raise the comparison first, with proof and an executive sponsor. Result: Competitive win rate.
- Add contacts to a one-contact deal. Signal: The deal has one contact. noombat: Names decision-makers in finance, IT and operations, and who on your team knows each. Action: Executive-to-executive outreach. Result: Contacts per deal.
- Spot expansion or churn risk. Signal: One customer registers a subsidiary and hires twenty. At another, the power user leaves. noombat: Raises expansion at one and risk at the other, with who now decides. Action: The account executive and customer success act before renewal. Result: Revenue kept and grown from customers.
- Reopen a lost deal. Signal: Lost nine months ago on budget. Now a funding round, a new CFO and a tender. noombat: Writes what changed next to the loss reason, with an opening line. Action: The account executive reopens the opportunity. Result: Pipeline from lost deals.

Signals that matter:
- A champion changes jobs: Risk on the deal, and a way into the new company. Read via LinkedIn.
- A new executive: Someone new reopens the budget. Read via LinkedIn, filings.
- Engagement with a rival: The decision-makers are looking at alternatives. Read via Rivals' posts and ads.
- Pricing read again: The deal is being weighed right now. Read via Your website.
- A buying trigger: A funding round, tender or subsidiary gives you a reason to call. Read via Filings, tenders, registers.
- Someone on your team knows them: A warm path to a decision-maker. Read via Your team's relationships.

What it moves: Win rate (Every decision-maker named, rivals caught mid-deal.); Cycle length (Stalled deals revived when something at the account changes.); Contacts per opportunity (Every decision-maker named, with who on your team knows them.); Revenue retention (Expansion and churn risk flagged before renewal.)

Who: Account executives, Sales managers, Solutions engineers, Customer success, Executive sponsors.
Fact: 5–16 people form a buying group, across up to four functions. 74% of groups show unhealthy conflict. Source: Gartner, 2025 sales survey.
Fact: 3.9 years is the median job tenure in one of the largest labour markets, the lowest since 2002. Source: US Bureau of Labor Statistics.

Questions:
- Does noombat record or analyse sales calls? No. It reads call outcomes logged in your CRM. Recording and coaching stay with your call tool.
- How does noombat find warm introductions? It matches your team's LinkedIn connections to the decision-makers. The warm path shows next to the account.
- Where do account executives see noombat? In Slack or Teams, and in its own CRM fields, with a brief per account.
- Does noombat write the email? Partly. It drafts the angle and opening line. You decide what to send, and you send it.

## Sales development, for the team (https://noombat.ai/solutions/sales-development)

Sales development reps open a ranked list at 9:00. Each account has a dated reason to call, the person, a verified contact and an opening line. Accounts in a live deal stay off.

Systems read through their APIs: Your sequencer, Salesforce or HubSpot, Pipedrive or Attio, Cal.com, Slack or Teams.
Public record and signals watched: Website visits, LinkedIn engagement, rivals' too, Job adverts naming tools, Funding and filings, Tenders, Event speakers and attendees, Company registers, Job changes.

Use cases:
- Work a morning list of twelve. Signal: From the last 72 hours: a job advert in your category, a funding round, a speaker slot. noombat: Ranks twelve accounts. Each has the reason, the person, a verified contact and a first line. Action: Tailored outreach to all twelve. Result: Reply rate and activities per meeting.
- Call a target account on pricing. Signal: 10 Sep: three page views, including pricing, and no form. noombat: Names the company, and the person where allowed, with fit, owner and decision-makers. Action: A same-day call with a relevant angle. Result: Visitor to meeting.
- Reach people who engaged a rival. Signal: This week, five people from one account react to a rival's post. noombat: Groups them by account, with roles and an angle from the post's topic. Action: Outreach built on that topic. Result: Connect and reply rates.
- Book meetings before an event. Signal: A conference in three weeks. noombat: Matches speakers and attendees to target accounts, ranks them and drafts opening lines. Action: Reps book meetings for the event. Result: Meetings held around the event.
- Ramp a new rep without double-touching. Signal: A new rep in week two. noombat: Gives a scored territory. The timeline shows a colleague's 'not now' and an open deal. Action: The rep skips those and works the fresh accounts. Result: Ramp time and complaint rate.
- Work public buying triggers. Signal: A tender is published, a subsidiary registered, a hiring wave starts. noombat: Names the decision-makers, a warm path and the angle. Action: Only those contacts go into a sequence. Result: Meetings per hundred contacts.

Signals that matter:
- A visit to pricing: A reason to call today. Read via Your website, company or person where allowed.
- A hiring trigger: A job advert naming the tool you replace. Read via Job adverts.
- A funding round or tender: A dated reason to start the conversation. Read via Filings, press, tenders.
- A reaction to a rival: A topic the prospect already cares about. Read via Rivals' posts.
- A speaker slot: A meeting to book before the event. Read via Event calendars.
- A job change: A past contact at a new account. Read via LinkedIn.

What it moves: Meetings held (A short list ranked by chance of a meeting.); Reply rate (A dated reason and a first line for every account.); Ramp time (A scored territory with a timeline per company.); Deliverability (Fewer, better sends. noombat never sends in your name.)

Who: Sales development reps, Sales development managers, Account executives, Revenue operations.
Fact: 60% of reps hit quota in 2025, a record low. Ramp 3.0 months, median attrition 40%. Source: The Bridge Group, SDR Metrics Report 2025.
Fact: 73% of business buyers avoid suppliers who send irrelevant outreach. Source: Gartner, 2025 sales survey.

Questions:
- Does noombat replace our sequencer? No. It decides who to contact and why, finds the verified contact and drafts the first line. Your sequencer sends.
- Does noombat find phone numbers and emails? Yes. It finds verified emails and mobile numbers by checking several data providers in turn.
- How do reps stay off accounts executives are working? noombat reads ownership and open deals from your CRM. Those accounts stay off the rep's list.
- Is noombat an AI SDR? No. noombat decides who to contact and why. Your team sends every message. noombat never sends anything in your name.

## Compare (https://noombat.ai/compare)

How noombat compares with the tools revenue teams usually weigh it against. Claims about each product come from that vendor's own material, read in September 2026; noombat's price is not compared.

### noombat vs 6sense (https://noombat.ai/compare/6sense)
6sense is a strong ABM platform when RevOps runs it and media budget flows through it. For most revenue teams, noombat is more complete. It scores every company with a chance of a meeting, a reason and an opening line, and is run for you.
Choose noombat if: You want the work done for you. 6sense is a platform your RevOps team runs. You sell in several countries, each read from its own registers. You want a chance of a meeting today. 6sense gives a buying stage. You want the angle and opening line written for you. You want results in your CRM, with no new tool to learn.
Choose 6sense if: You want display ads and audiences driven by the same account scores. You already run 6sense, and RevOps is behind it.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. 6sense: An ABM and revenue AI platform: predictive account scoring, intent, web de-anonymisation, contact data and a display DSP.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. 6sense: Its intent network, partner feeds (Bombora, TechTarget, TrustRadius, G2), web tag, contact data, your CRM and marketing automation.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. 6sense: A London office and intent in 40+ languages. Reviewers consistently report weaker accuracy outside the US.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. 6sense: Predictive scoring and a 6QA buying stage, fitted on its own network. Strong at ranking large lists.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. 6sense: No. A buying stage shows where an account sits.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. 6sense: Sales Intelligence shows the account and its signals. Your team writes the message, with AI help.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. 6sense: Holds EU business contact data under legitimate interest and supplies it to subscribers. Web identification is account-level only.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. 6sense: Reads and writes, optional per object. Pushes fit, stage and intent scores to Account, Lead and Contact daily.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. 6sense: A platform, usually run by RevOps or marketing ops, after a multi-week implementation.
- What arrives. noombat: One list every morning, and one file per company. 6sense: Scores and stages in the platform and your CRM, plus audiences and alerts.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. 6sense: A demo, a negotiation and an implementation.

### noombat vs ZoomInfo (https://noombat.ai/compare/zoominfo)
ZoomInfo is the biggest database here, and hard to beat for reaching people in the US. It tells you who exists. noombat tells you who moved, your chance of a meeting and what to open with.
Choose noombat if: You sell in several countries, each read from its own registers. You want scoring and a chance of a meeting. ZoomInfo sells the list. You want each row to come with the reason and opening line. You want results in your CRM, with no new tool to learn.
Choose ZoomInfo if: You need to reach people in the United States at volume. You need direct dials, mobiles and verified emails at volume. You want conversation intelligence and chat from the same vendor.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. ZoomInfo: A contact and company database sold as a platform: search, intent, visitor ID, conversation intelligence and CRM enrichment.
- Where the data comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. ZoomInfo: A contributory network, public sources and partners, plus its own web and research operation.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. ZoomInfo: Good on large European companies, thinner on smaller ones. Its filings put non-US revenue at about 12%.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. ZoomInfo: Fit and intent scoring across its own database. Copilot suggests accounts to work.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. ZoomInfo: No. It ranks accounts by fit and intent, but does not estimate your odds of a meeting.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. ZoomInfo: Copilot suggests talking points from the record it holds.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. ZoomInfo: Holds and licenses personal data on EU, UK and Swiss individuals without consent, citing legitimate interest among others.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. ZoomInfo: Reads and writes, with per-field rules. Its Salesforce app needs read, write and edit on Account, Contact, Lead.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. ZoomInfo: A platform, with licences to administer and credits to manage.
- What arrives. noombat: One list every morning, and one file per company. ZoomInfo: Search results, enriched records and alerts, in the platform and your CRM.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. ZoomInfo: A demo, a negotiation and an annual or multi-year commitment.

### noombat vs Clay (https://noombat.ai/compare/clay)
Clay is the best workbench here and suits teams with a GTM engineer. noombat is the finished system, run for you, with a chance of a meeting, the committee and the angle. Build it yourself in Clay, or get the result without the hire.
Choose noombat if: You want the result with nothing to maintain. Clay is a workbench. You sell in several countries, each read from its own registers. You want scoring and a chance of a meeting from day one. You need your data held in the EU.
Choose Clay if: You have, or will hire, a GTM engineer or RevOps builder. You want enrichment from many vendors under one contract. Your use cases keep changing and you want to change it yourself.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Clay: A spreadsheet-shaped workbench that routes each row through 150+ data vendors and AI research agents.
- Where the data comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Clay: Vendors you pick from its marketplace, AI web research, and any provider you bring your own key for.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Clay: Investing in Europe in 2026: London office, do-not-contact screening. About two-thirds of its data providers are still US-based.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Clay: Whatever you build: a formula or AI column you write and maintain.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Clay: Only if you build and calibrate it yourself, from your own outcome history.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Clay: AI columns can draft copy from the row you assembled.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Clay: Depends on your chosen providers. Clay states it is not in a position to monitor each provider's sourcing.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Clay: Reads and writes. Writing is optional: lookups sit alongside create and update.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Clay: Tables, waterfalls and credit budgets, run by a GTM engineer, RevOps builder or partner.
- What arrives. noombat: One list every morning, and one file per company. Clay: Whatever you build, wherever you send it.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Clay: An afternoon to a quarter, depending on who is building.

### noombat vs Apollo.io (https://noombat.ai/compare/apollo)
Apollo is the best value in this category: database, sequencing and dialing for one seat price. Apollo works a list, and noombat decides what belongs on it, with a chance of a meeting for each. Run both, with noombat choosing accounts and Apollo working them.
Choose noombat if: Your problem is choosing the accounts and the moment. Apollo solves sending. You sell in several countries, each read from its own registers. You want a chance of a meeting and an angle. Apollo gives filters. You want results in your CRM, with no new tool to learn.
Choose Apollo.io if: You want database, sequencer and dialer in one seat. You are an SMB or mid-market outbound team and price matters most.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Apollo.io: A contact database bundled with sequences, a dialer and AI research, sold per seat with credits.
- Where the data comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Apollo.io: A contributor network, public sources, live engagement signal and its own research.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Apollo.io: Its weakest area. Its docs limit do-not-call screening to US, UK, Germany, France, Canada, Australia and New Zealand.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Apollo.io: Rules-based scoring over its database fields and your engagement history.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Apollo.io: No. It ranks and filters, but does not estimate your odds of a meeting.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Apollo.io: AI writing help inside sequences, drafted from the contact record.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Apollo.io: Holds EU personal data as a controller, without consent, on a legitimate-interests basis.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Apollo.io: Configurable two-way sync with Salesforce and HubSpot.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Apollo.io: Seats, sequences and a credit budget.
- What arrives. noombat: One list every morning, and one file per company. Apollo.io: Search results, sequences and dialer activity.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Apollo.io: Minutes, self-serve.

### noombat vs Common Room (https://noombat.ai/compare/common-room)
Common Room is right if your buyers are active in a visible community like GitHub, Discord or product-led software. noombat reads the public record, which exists without a community. For logistics groups or regional banks, registers, tenders and hiring are the signals that exist.
Choose noombat if: Your buyers are companies with no online community. You sell in several countries, each read from its own registers. You want every company scored with a chance of a meeting. You want results in your CRM, with no new tool to learn.
Choose Common Room if: You sell developer tools or product-led software. Your buyers are active in Slack, Discord, GitHub or a forum. Product usage is one of your strongest buying signals.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Common Room: Resolves community, product and web signals to people and companies, and pushes them to your CRM and sequencer.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Common Room: Slack, Discord, GitHub, forums, your LinkedIn page, product usage, site visits, job changes and Bombora intent.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Common Room: Person-level website de-anonymisation is US-only, by its own documentation.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Common Room: Signal scoring and routing across the channels it watches.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Common Room: No. It ranks people and accounts by signal strength.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Common Room: AI research and drafting from the signals it captured.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Common Room: Names people from community and first-party channels. Contact enrichment costs extra credits.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Common Room: Reads and writes. Create and update switch on separately, and Salesforce overwrite is off by default.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Common Room: A platform, with signals, topics and contact counts to manage.
- What arrives. noombat: One list every morning, and one file per company. Common Room: Signals and alerts in the platform, your CRM and your sequencer.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Common Room: Connect your sources, then tune what counts as a signal.

### noombat vs HubSpot Breeze (https://noombat.ai/compare/hubspot-breeze)
Breeze is the easiest start if your team works in HubSpot and buyers mostly find you online. noombat watches the market outside HubSpot's network and writes each company's chance of a meeting into HubSpot. It is fitted to your meetings and run for you.
Choose noombat if: You want companies that never visited and are not in HubSpot. You want a chance of a meeting today. Breeze gives a 90-day close likelihood. You want registers, tenders, job adverts and competitor activity read for you. You want results in HubSpot without configuring markets, topics and plays.
Choose HubSpot Breeze if: Your pipeline is mostly web inbound, on HubSpot Professional or Enterprise. You want an agent to draft and send, paid per recommended lead. You want nothing beyond the platform you already own.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. HubSpot Breeze: HubSpot's AI layer: Assistant, agents, enrichment and buyer intent, sold with HubSpot seats and Credits.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. HubSpot Breeze: Tracking code via reverse IP, research-intent network of sites running HubSpot's code, news and job-change data, CRM activity.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. HubSpot Breeze: EU hosting in Germany is available. European visitor coverage needs analytics-cookie consent. HubSpot skips visitors who decline.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. HubSpot Breeze: Rule-based fit and engagement scores with AI-suggested rules. AI contact scores on Marketing Hub Enterprise.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. HubSpot Breeze: Higher tiers predict a contact's likelihood to close within 90 days. Nothing estimates today's chance of a meeting.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. HubSpot Breeze: The Prospecting Agent drafts sequences from CRM data and signals. Breeze Assistant drafts on request.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. HubSpot Breeze: HubSpot processes your CRM data for you, and is an independent controller for enrichment and shared intent data.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. HubSpot Breeze: It is the CRM. Breeze works only on HubSpot.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. HubSpot Breeze: You or a partner set up tracking, consent, markets, intent criteria, topics, scores, agent plays and credit limits.
- What arrives. noombat: One list every morning, and one file per company. HubSpot Breeze: Signal events and properties on records, intent views, workflow enrolments, and emails the agent drafted or sent.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. HubSpot Breeze: A paid HubSpot seat plan, tracking code with consent, then markets, topics and plays your team configures.

### noombat vs Agentforce Sales (https://noombat.ai/compare/salesforce-agentforce)
Agentforce is the broadest set of sales agents on any CRM, with enterprise governance. With admins, clean data and Data 360, it does a lot inside Salesforce. noombat reads the market outside it, scores every company on your meetings, and arrives built.
Choose noombat if: You want outside signals without licensing three data vendors. You want a chance of a meeting today. Agentforce gives a conversion score. You want it live in days, without an Agentforce build. You want each account sent to its Salesforce owner, with the reason.
Choose Agentforce Sales if: You run Salesforce with admins, clean data and Data 360 in place. You license ZoomInfo, Demandbase or 6sense and want those signals in Salesforce. You want service, marketing and sales agents under one governance model.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Agentforce Sales: Salesforce's agent platform on Sales Cloud: prebuilt sales agents with Einstein scoring and Data 360 underneath.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Agentforce Sales: Salesforce records, emails, calls, Data 360, web research, and licensed vendors like ZoomInfo, Demandbase, 6sense and Sales Navigator.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Agentforce Sales: Hyperforce hosts in the EU. Its EU Operating Zone covers only some products, so check yours.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Agentforce Sales: Einstein Lead and Opportunity Scoring learn from your history. Both need Unlimited edition or above, or an add-on.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Agentforce Sales: No. It gives lead conversion and deal win scores, for records already in Salesforce.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Agentforce Sales: Prospecting and nurturing agents draft outreach citing their signals. Research and prep agents produce briefs.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Agentforce Sales: CRM data falls under Salesforce's DPA and Trust Layer. Licensed vendor data falls under those vendors' terms.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Agentforce Sales: It is the CRM. Agentforce Sales runs on Salesforce.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Agentforce Sales: Admins or an integrator build and maintain agents, topics, instructions, data streams and credit controls.
- What arrives. noombat: One list every morning, and one file per company. Agentforce Sales: Prioritised lists and briefs in Salesforce and Slack, field updates, scores, and emails agents drafted or sent.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Agentforce Sales: Enterprise edition or above with Agentforce add-ons, vendor licences for outside data, and Agentforce Builder setup.

### noombat vs Gong (https://noombat.ai/compare/gong)
Gong sets the bar for coaching, deal inspection and forecasting. If your pipeline is full and the problem is winning it, buy Gong. noombat finds who to talk to next, with a chance of a meeting, the committee and the opening line.
Choose noombat if: Your problem is the companies that have not talked to you yet. You want a chance of a meeting before there is a deal. You want registers, tenders, hiring, LinkedIn and competitor ads read for you. You want it run for you, with no new tool to adopt.
Choose Gong if: Your pipeline is full and winning it is the problem. Your large team meets buyers on recorded calls and needs the record. You want conversation intelligence, sequencing, forecasting and enablement from one vendor.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Gong: A revenue AI platform built on recorded calls, meetings and emails, with sequencing, forecasting, enablement and agents.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Gong: Your team's calls, meetings, email and calendar, joined to CRM data. Outside signals come via separately licensed partners.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Gong: Used globally, with multi-language transcription and an EU data centre option.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Gong: Scores open deals. Accounts can sort by imported third-party fit scores.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Gong: No. There is no meeting probability outside the pipeline, and Gong's own docs say the deal score is no win probability.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Gong: Strong: follow-ups drafted from real conversations, account briefs, and trackers for objections and competitor mentions.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Gong: Records and transcribes calls, so consent is central. Gong provides consent tools and a DPA.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Gong: Deep two-way Salesforce, HubSpot and Dynamics integration, filling CRM fields from calls and emails.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Gong: An admin sets up workspaces, recording, consent, trackers and boards. Managers run coaching and forecasts.
- What arrives. noombat: One list every morning, and one file per company. Gong: Recordings, transcripts, deal boards, risk alerts, forecasts, coaching scorecards and drafted follow-ups.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Gong: A sales-led quote, then email, calendar, conferencing and CRM connected. Predictive deal scores need closed-deal history first.

### noombat vs UserGems (https://noombat.ai/compare/usergems)
UserGems is the benchmark for following past buyers to their next company. If your biggest untapped pipeline is people who know you, it is an excellent buy. noombat reads the wider market too and gives every company a chance of a meeting, run for you.
Choose noombat if: You want the whole market ranked. UserGems starts from people you know. You want a meeting chance. UserGems gives an A to D grade. You sell in several countries and want registers and tenders read. You want it run for you, with one owner on your side.
Choose UserGems if: Your biggest untapped pipeline is past customers and users who change jobs. You run Salesforce or HubSpot with Outreach, Salesloft or Gong Engage. You want a RevOps-tuned platform and sell mainly into the US.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. UserGems: AI command centre for outbound and ABM, grown from job-change tracking. Agents write outreach and sync ad audiences.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. UserGems: Dozens of public-source signals rechecked daily, licensed contact intent, US website visitors, and your CRM, calls and email.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. UserGems: Website de-anonymisation covers US visitors only, excluding the EU and EEA. Contact-level intent is processed in the US.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. UserGems: Visible, editable points for customer similarity plus signals, rolled into A to D grades.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. UserGems: No stated probability. It gives a grade and ranked audience, with after-the-fact reporting.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. UserGems: Gem-E writes multi-step sequences from signals and CRM history, and pushes them to your sequencer for review.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. UserGems: Acts as your processor. Visitor ID is US-only, and customer data does not train models.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. UserGems: Deep Salesforce and HubSpot write-back: creates and de-duplicates records, maps fields and assigns owners.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. UserGems: Tracked-contact lists, ICP and scoring settings, signals, campaigns and workflows, with customer success helping.
- What arrives. noombat: One list every morning, and one file per company. UserGems: New or updated CRM records, alerts, sequence enrolments with AI copy, and synced ad audiences.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. UserGems: Sales-led setup: CRM integration user, custom fields, tracked-contact reports and a sequencer. Live within weeks.

### noombat vs Trigify (https://noombat.ai/compare/trigify)
Trigify is one of the broadest social listening tools, self-serve and quick to try. It suits buyers who talk in public and GTM engineers who build workflows. noombat weighs LinkedIn engagement with hiring, filings, tenders, site visits and your CRM, fitted on your booked meetings.
Choose noombat if: You want an answer: which company, why, who calls. Trigify gives a feed. You want engagement weighed with hiring, registers, tenders, visits and CRM. You want a model fitted on your meetings. Trigify gives rules you tune. Nobody on your team should build and maintain workflows.
Choose Trigify if: You are a GTM engineer or agency wanting a raw social feed. Your buyers talk in public on Reddit, X, Hacker News or YouTube. You want a cheap, self-serve test of social engagement.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Trigify: A self-serve social listening and signal platform. Its workflow builder passes activity to steps you set up.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Trigify: Public posts on LinkedIn, X, Reddit, YouTube, podcasts and more. Job changes, hiring and news for listed accounts.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Trigify: Filters public posts by country or language. A UK company with a DPA for EU and UK transfers.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Trigify: Scores from rules and AI steps you configure.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Trigify: None. It says a signal fired, and your rules judge if a meeting is likely.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Trigify: A copywriter step drafts a message from the signal, inside a workflow you build.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Trigify: Uses named people's public posts and engagement plus third-party enrichment. Lawful use is the customer's responsibility.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Trigify: Workflow actions create and update HubSpot, Salesforce and Attio records. You design the field mapping.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Trigify: All of it: queries, watch lists, filters, enrichment order, workflows and credit budget.
- What arrives. noombat: One list every morning, and one file per company. Trigify: A feed of posts and signals, an optional digest, and whatever your workflows send on.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Trigify: Self-serve sign-up and a first workflow the same day. Reviewers report about a week of noise tuning.

### noombat vs RB2B (https://noombat.ai/compare/rb2b)
RB2B names the US visitors on your website, fast. If a feed of today's visitors is what you need, it is hard to beat. noombat weighs each visit with registers, tenders, hiring, LinkedIn and more, and gives a chance of a meeting.
Choose noombat if: Most of your market never visits your site. You want each visit weighed with all your other evidence. You sell in several countries, each read from its own registers. You want the ranking, committee and opening line, run for you.
Choose RB2B if: Your buyers are mostly US, with business traffic nobody follows up. You want a free or cheap Slack alert for named pricing-page visitors. You already know who to work, and only need visitors.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. RB2B: Visitor ID: matches visitors to US people and companies worldwide, and pushes them to your tools.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. RB2B: Only your website traffic, matched against identity data for people and reverse IP for companies.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. RB2B: Names people in the US only, by design. Non-US visitors can resolve to company level, with consent.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. RB2B: Rules. Hot Leads tags matches to your criteria, and Hot Pages flags high-intent pages.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. RB2B: None. It shows who visited and what they read.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. RB2B: The page history is the context. The rep or sequencer writes the message.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. RB2B: Names US visitors from a consumer identity database with public opt-out. Supplies disclosure wording and a DPA.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. RB2B: HubSpot and Salesforce sync creates or updates records and flags existing CRM visitors.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. RB2B: Very little: script, rules, exclusions and integrations. What follows the alert is your process.
- What arrives. noombat: One list every morning, and one file per company. RB2B: A real-time card per visitor, a dashboard with page history, exports and pushes to your tools.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. RB2B: Minutes: a free plan or trial, one script tag and a Slack connection.

### noombat vs Warmly (https://noombat.ai/compare/warmly)
For a US-heavy, inbound-led team, few tools act faster on a visit than Warmly. Its guidance says European visitors mostly resolve to the company. noombat reads the market before the visit, gives every company a chance of a meeting, and sends nothing in your name.
Choose noombat if: You want to reach the market before it visits. You sell into Europe, where Warmly mostly names companies and noombat names the person where data allows. You want a calibrated chance of a meeting. Warmly gives tiers and thresholds. You want nothing sent in your team's name without them.
Choose Warmly if: Most pipeline starts on your website, mostly from US traffic. You want an AI chatbot and live alerts that book meetings. You accept AI agents sending outreach, and your team owns workflows.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Warmly: An AI revenue orchestration platform built on visitor identification. Inbound and market agents share one context.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Warmly: Your website pixel, chat, forms and team LinkedIn activity, plus third-party intent, news, hiring and job changes.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Warmly: Strongest on US traffic. Its guidance says mainly European audiences should expect company-level identification.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Warmly: AI ICP tiering trained on closed-won deals, plus a weighted intent score.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Warmly: No stated probability. It uses tiers, and intent thresholds that trigger actions.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Warmly: AI chat talks to live visitors. AI-written emails and LinkedIn messages go via reps or AI senders.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Warmly: The pixel collects visitor data. Person matches come from a partner network. You handle EU consent as controller.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Warmly: Salesforce and HubSpot matching, sync, field mapping and routing, plus webhooks and an API.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Warmly: The pixel, chatbot, audiences, routing rules and agent workflows, with a CSM at setup.
- What arrives. noombat: One list every morning, and one file per company. Warmly: Real-time alerts, identified visitors and accounts, chat conversations, booked meetings and synced audiences.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Warmly: A pixel shows identified traffic within minutes. CRM, routing and chatbot follow over days to weeks.

### noombat vs Unify (https://noombat.ai/compare/unify)
Unify is among the most complete tools for fast intent action, with 40+ sources, mailboxes and a sequencer on one bill. Its plays fire on rules, with no chance of a meeting. noombat weighs every signal, including registers and tenders, against your booked meetings.
Choose noombat if: You want accounts ranked by chance of a meeting. Unify fires plays from rules. You want registers, tenders and events read, as well as intent. You sell in several countries, each read from its own registers. You want nothing sent in your team's name without them.
Choose Unify if: You want reps to run signal-triggered outbound in one product. You are US-focused, with heavy web or product traffic to act on. You would rather build plays self-serve than have them run for you.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Unify: An AI outbound platform. A chat agent and plays turn signals into researched, enriched, multi-channel sequences it sends.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Unify: Web and product events, CRM, and 40+ bundled vendors: intent, tech stack, hiring, funding, news, warm intros.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Unify: US-hosted with an SCC-based DPA. Its own guide notes EU visitor reveal fails without consent.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Unify: Audience filters, stacked signals, lookalikes and AI yes-or-no qualification, or an imported score.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Unify: None in its public docs. Plays fire when a record matches your rules.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Unify: A real strength: AI research and snippets write email, LinkedIn and call copy from the triggering signal.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Unify: Supplies B2B contact data from a large database, processed in the US. SOC 2 Type II.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Unify: Salesforce and HubSpot sync: read-only on Pro, read-write on Business.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Unify: Audiences, personas, exclusions, plays, sequences, mailboxes and a credit balance.
- What arrives. noombat: One list every morning, and one file per company. Unify: Sequences from managed mailboxes, a rep task list, research reports and Slack alerts.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Unify: Free or per-seat plans in minutes. Full-volume sending needs a CRM, website tag and mailbox warm-up first.

### noombat vs 11x (https://noombat.ai/compare/11x)
11x helped create the AI SDR category, and suits teams with more prospects than SDRs. The risk with any AI SDR is a mistargeted message under your name. noombat does not send, and gives every company a chance of a meeting today.
Choose noombat if: You want fewer, better conversations. 11x makes more sends. You want nothing sent in your team's name without them. You want a calibrated chance of a meeting on every company. Your brand and domain reputation matter more than volume.
Choose 11x if: You have more prospects than SDRs and want software to reach out. Inbound leads wait too long, and you want replies within a minute. You can name one owner for knowledge base, ICP and deliverability.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. 11x: AI sales platform with two digital workers: an AI SDR that prospects and sends, and an inbound agent.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. 11x: A built-in contact database, web search, news, job postings, funding, executive hires, website visitors and your CRM.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. 11x: Many languages, no published EU hosting. Its docs note a different legal profile for EU and UK visitors.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. 11x: Filters prospects against your ICP, and qualifies fit before outreach.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. 11x: No per-company meeting probability documented. Results are published as cross-deployment averages.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. 11x: Its core strength: cited research, a recommended angle, and copy from your knowledge base.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. 11x: Processes prospect data, outreach, replies and call recordings. Consent and lawful basis are the customer's responsibility.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. 11x: Two-way Salesforce, HubSpot, Pipedrive and Zoho connectors.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. 11x: A named owner for knowledge base, ICP and thresholds, plus sending-domain setup.
- What arrives. noombat: One list every morning, and one file per company. 11x: Emails, messages and calls to prospects, sorted replies, and meetings booked on reps' calendars.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. 11x: An annual contract, then a few weeks connecting CRM, mailboxes and calendars, and tuning.

### noombat vs Rox (https://noombat.ai/compare/rox)
Rox is ambitious, ships weekly, and suits large enterprise teams wanting governed agents over CRM, warehouse, email and calls. Its signals centre on companies you already track. noombat ranks the market beyond them by chance of a meeting, and is live in about a week.
Choose noombat if: You want the companies you do not have yet. You want a calibrated chance of a meeting on every company. You want it live in days, without a rollout. You sell in several countries and want registers and tenders read.
Choose Rox if: Your large enterprise team wants agents for prep, deal risk and CRM. Your richest context is in email, calls and a data warehouse. You want one platform RevOps will own and extend.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Rox: An AI-native revenue platform: a knowledge graph over CRM, warehouse, email, calendar and calls, with agents.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Rox: Your own systems plus public news, job postings, company blogs, filings and enrichment vendors.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Rox: Enterprise customers in the US and Europe, SOC 2 Type II, and in-region deployment for data residency.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Rox: Criteria you set plus agent reasoning. Research columns can produce reasoned ICP scores.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Rox: No calibrated probability. Forecasting and deal risk apply to opportunities already open.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Rox: A core strength: briefs, call scripts, meeting prep, live coaching and sequences grounded in your documents.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Rox: A large contact database, plus your team's email, calendar and call transcripts under admin-granted access.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Rox: Deep Salesforce and HubSpot integration with field mapping and write-back.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Rox: Admins set assignment rules, research columns, agents, sequences, permissions and an actions balance.
- What arrives. noombat: One list every morning, and one file per company. Rox: A daily feed and digest of account changes, Slack or Teams messages, drafted sequences, briefs and deal risks.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Rox: Self-serve plans connect in minutes. Enterprise rollouts add the warehouse, single sign-on and org-wide access.

### noombat vs Cognism (https://noombat.ai/compare/cognism)
If your problem is reaching people in Europe by phone, buy Cognism. noombat works a layer above: it scores the whole market with a chance of a meeting, the committee and an angle. If you sell into Europe, running both makes sense.
Choose noombat if: You can reach people but need which companies to contact, and when. You want a meeting chance and an angle. Cognism gives an export. You want the whole market watched. Cognism is a database you query. You want results in your CRM, with no new tool to learn.
Choose Cognism if: You need verified European mobile numbers for cold calling. You run high-volume outbound into EMEA, and reach is the constraint. You want European do-not-call screening done before data arrives.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Cognism: A B2B contact and sales-intelligence platform, strongest on phone-verified European mobile numbers.
- Where the data comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Cognism: Its own data operation plus partners. People verify premium numbers by phone. Third-party intent comes from Bombora.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Cognism: Europe is its strongest ground, and ZoomInfo's own comparison page says so.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Cognism: None. Filters and third-party intent topics.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Cognism: No. It is a data provider.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Cognism: No drafted angle. You write the message.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Cognism: Holds and licenses EU personal data without consent, under legitimate interest, and documents this openly.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Cognism: Reads and writes, with field-level overwrite control.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Cognism: Seats and a credit budget.
- What arrives. noombat: One list every morning, and one file per company. Cognism: Search results and enriched records.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Cognism: A demo and a sales conversation. No self-serve trial.

### noombat vs Dealfront (https://noombat.ai/compare/dealfront)
Dealfront is the most European product here and the closest to noombat in approach. If your website is your main demand channel, it is an excellent buy. noombat watches the market that has not visited, and gives every company a chance of a meeting.
Choose noombat if: You want companies that have not visited your site yet. You want a chance of a meeting. Dealfront gives a feed to sort. You want registers, tenders, hiring and funding used as signals. You want results in your CRM, with no new tool to learn.
Choose Dealfront if: Your website is your main demand channel. You want published self-serve pricing and a free tier. You want to start this week without a sales process.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Dealfront: Visitor identification plus a European company and contact database, built from national trade registers and web data.
- Where the data comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Dealfront: Official national trade registers and chambers of commerce, public web sources, and your website traffic.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Dealfront: Its home ground: built on European registers for a decade.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Dealfront: Lead scoring on identified visitors and firmographic fit.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Dealfront: No. It scores and filters identified companies, but does not estimate your odds.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Dealfront: No drafted angle. It shows the company and the pages it read.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Dealfront: Holds EU personal data under legitimate interest, and documents the basis openly.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Dealfront: Writes: creates and updates companies, contacts, deals and tasks in bulk.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Dealfront: A tool and a feed to sort, with filters and lists to maintain.
- What arrives. noombat: One list every morning, and one file per company. Dealfront: Identified companies from your traffic, and alerts.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Dealfront: A tag on your site, self-serve.

### noombat vs Demandbase (https://noombat.ai/compare/demandbase)
Demandbase is a strong enterprise ABM platform, and earns its place in a funded account-based programme. noombat answers what comes first: which companies belong on the list. Each gets a chance of a meeting, the reason and the opening line, run for you.
Choose noombat if: You want the account list built for you from public records. You sell in several countries, each read from its own registers. You want a seller's list with a chance of a meeting. You want results in your CRM, with no new tool to learn.
Choose Demandbase if: You run a real account-based programme with ad budget behind it. You want identification, intent, orchestration and display from one vendor. You need hierarchies resolved across large group structures.
- What it is. noombat: One ranked list every morning. Behind each row: score, chance of a meeting, dated reasons, people and angle. Demandbase: Enterprise ABM: account identification, intent, scoring, web personalisation, orchestration and its own B2B ad network.
- Where the signal comes from. noombat: Registers, tenders, job adverts, funding, press, filings, LinkedIn engagement on your posts and competitors', competitor ads, events, site visits and your CRM. Demandbase: An identity graph over cookies, IPs and device identifiers, plus intent, firmographics and your CRM.
- Countries covered. noombat: Each country is read from its own registers and tender feeds. A visit names the company, and the person where data allows. Demandbase: Europe is not a named limited-coverage region, and it claims broad coverage. Person-level data is its most-cited weakness.
- Lead scoring. noombat: Every company in your market is scored. Weights come from your booked meetings, refit as more land. Old evidence counts less. Demandbase: Account scoring and journey stages, with account-level pipeline prediction.
- Chance of a meeting. noombat: Yes. Scent is your chance of a meeting if you reach out today. Fresh activity lifts it. Age lowers it. Demandbase: A journey stage and an account score.
- What to say next. noombat: Who to write to, why now, and an opening line drafted from the company's file. Plus a pre-call brief. Demandbase: Sales intelligence surfaces the account and its intent. You write the message.
- Personal data. noombat: No database is sold to you. It names the committee from engagement and public records, then finds verified emails and mobiles. Demandbase: Holds and commercially uses EU personal data. Its contract makes the customer liable for tag consent.
- Your CRM. noombat: Reads it. Writes score, tier and chance of a meeting to fields of their own, so nothing is overwritten. Or read-only. Demandbase: Two-way sync with Salesforce, HubSpot and Dynamics, with restricted, configurable write-back.
- What you operate. noombat: Almost nothing. It is set up and run for you, with one owner on your side. Lists land in Slack or Teams. Demandbase: An enterprise platform. Its own reviewers describe a long time to value.
- What arrives. noombat: One list every morning, and one file per company. Demandbase: Scores, journey stages, audiences and ads.
- What it takes to start. noombat: A pilot on your own market and your own companies, live in five to seven days. Demandbase: A demo, a negotiation and an enterprise implementation.

## Integrations (https://noombat.ai/integrations)

noombat reads the customer's own tools through their APIs and posts the morning list where the team reads. Every CRM connection is read-only and one-way, with the history included; the channel connections post and read nothing back.

### Salesforce (https://noombat.ai/integrations/salesforce)
A one-way, read-only connection. noombat reads your CRM on a schedule and writes nothing back. A Salesforce admin completes the setup in about 20 minutes.
Access: A read-only integration user with a permission set of its own. Time: About 20 minutes. Who: A System Administrator. Cost on the customer's side: Usually nothing: five Salesforce Integration licences come with Enterprise, Unlimited and Performance.
What noombat reads: Account (the companies you sell to); Contact (the people at those companies); Lead (prospects you have yet to qualify); Opportunity (pipeline and revenue outcomes); OpportunityContactRole (who was involved in each deal); RecordType (how you classify records); Campaign and CampaignMember (optional, if you track campaigns); Task and Event (calls and meetings; visibility follows the related record); User (record owners, for attribution); EmailMessage (logged emails; access follows the parent record).
Steps: 1. Create the integration user 2. Assign the permission set licence 3. Create the read-only permission set 4. Create the External Client App 5. If you use Einstein Activity Capture 6. Send us the connection details
Questions:
- Is this read-only? Yes, and Salesforce itself enforces it. The permission set grants Read only, with no Create, Edit or Delete on any object, so the platform rejects any write attempt. We also ask you to leave Modify All Data and View All Data off.
- The Salesforce API Integration licence lists Modify All Data. Does noombat get that? No. That list is a catalogue. Salesforce's documentation says it directly: "For users to access additional license functionality, they must both be assigned the permission set license and a permission set containing the feature permissions." The user has what your permission set enables, which is Read plus View All. You can verify on the user record: Modify All Data appears nowhere.
- What does noombat read, and why? Accounts, contacts and leads (who you sell to), opportunities (pipeline and revenue), and the calls, meetings and emails logged on those records. noombat keeps a read-only mirror, scores your market against it, and connects the companies it names to the meetings and revenue that follow. History matters: the scoring learns from what already happened, which is why a forward-only feed such as a webhook is too little.
- Can we keep specific fields private? Yes. Field-level security stays entirely in your hands: exclude any field from the permission set's field permissions and we never receive it. The connection works without non-essential fields.
- What does this cost on the Salesforce side? Usually nothing. Enterprise, Unlimited and Performance editions include five free Salesforce Integration user licences, API-only users made for exactly this; beyond five they cost about $10 per user per month. Professional edition sells API access as an add-on, so talk to us before setting up.
- Could we send a webhook instead? A webhook pushes one object's changes in real time and stops there: it sends changes from today on, while noombat learns from the existing history; each object needs an automation built and kept on your side; and a receiver ends up calling the API for the full record anyway. We add webhooks on top of API access for time-sensitive events when a customer asks.
- How do we revoke access? At once, from your side, in either of two ways: freeze or deactivate the integration user, or revoke the External Client App. Access ends immediately and nothing on our side can restore it. If the Consumer Secret is ever compromised, rotate it in the app settings.
- Can we audit what noombat reads? Yes. Every API call runs as the single dedicated integration user, so your login history and event logs show what was read and when, attributable to noombat alone. The account has no UI access: the Salesforce Integration licence is API-only, so there is no password to phish and no screen to look at.
- Is our data safe with noombat? Your data is kept apart from every other customer's, in a schema of its own, encrypted in transit and at rest, read through connections that write nothing back, and deleted when we part ways. Data-processing terms written for a security review, for teams in the EU and in the US. We walk through them with your security team on request.

### HubSpot (https://noombat.ai/integrations/hubspot)
A one-way, read-only connection. noombat reads your CRM on a schedule and writes nothing back. One private app, one token: a HubSpot super admin completes the setup in about 10 minutes.
Access: A private app holding read scopes only. Time: About 10 minutes. Who: A super admin. Cost on the customer's side: Nothing: private apps come with every HubSpot tier, the free CRM included, and use no seat.
What noombat reads: crm.objects.companies.read (the companies you sell to); crm.objects.contacts.read (the people at those companies, and with them the calls, meetings and notes logged on your records (HubSpot has no separate scope for those)); crm.objects.owners.read (record owners, so activity and companies attribute to your reps); crm.lists.read (which of your lists each company and contact belongs to); sales-email-read (the content of one-to-one emails logged on your records); crm.objects.deals.read (optional: deals and pipelines, so revenue outcomes connect back to the market); forms (optional: form submissions, if you capture demand through HubSpot forms); content (optional: marketing email opens and clicks; Marketing Hub or CMS Hub Professional or Enterprise only).
Steps: 1. Create the private app 2. Copy the access token 3. Send us the connection details
Questions:
- Is this read-only? Yes, and HubSpot itself enforces it. The private app holds read scopes only. Every write endpoint checks for the paired .write scope, which the app lacks, so the platform rejects any write attempt. There is nothing to configure to get this guarantee; it is how HubSpot scopes work.
- What does noombat read, and why? Companies and contacts (who you sell to), deals (pipeline and revenue), the engagements logged on your records (calls, meetings, emails, notes), list memberships, form submissions and marketing email opens and clicks (how your market responds), and owners (who works what). noombat keeps a read-only mirror, scores your market against it, and connects the companies it names to the meetings and revenue that follow. History matters: the scoring learns from what already happened, which is why a forward-only feed such as a webhook is too little.
- Can we keep specific properties private? HubSpot's scopes are object-level, so a token cannot be limited to specific properties the way Salesforce field-level security works; HubSpot's own docs note that its user-facing property restrictions leave API access untouched. Two things do help. First, noombat requests the specific properties it uses, and we share the exact list. Second, on Enterprise, HubSpot's Sensitive Data feature gates any property you classify as sensitive behind dedicated *.sensitive.* scopes, which we never request, so those values are blocked to our token by the platform.
- What does this cost on the HubSpot side? Nothing. Private apps are included in every HubSpot tier, the free CRM included, with up to 20 per account, and a private app is an account-level credential rather than a user, so no seat is consumed. The one tier-dependent piece is the optional content scope (marketing email opens and clicks), which HubSpot offers on Marketing Hub or CMS Hub Professional and Enterprise; everything else works on any tier.
- Could we send a webhook instead? A webhook pushes one object's changes in real time and stops there: it sends changes from today on, while noombat learns from the existing history; each object needs an automation built and kept on your side; and a receiver ends up calling the API for the full record anyway. We add webhooks on top of API access for time-sensitive events when a customer asks.
- How do we revoke access? At once, from your side, in either of two ways: on the app's Auth tab choose Rotate and expire now (the old token dies immediately), or delete the private app (its token is permanently revoked). Nothing on our side can restore access. For a graceful handover, Rotate and expire later keeps the old token alive for 7 days while the new one is delivered.
- Can we audit what noombat reads? Yes. The private app's page in HubSpot has an API call log covering the past 30 days: every request with its method, endpoint and response code, filterable and exportable as CSV. Because noombat is the only thing using this app's token, everything in that log is attributable to us alone. HubSpot keeps the calls themselves in the log, without request or response payloads.
- Is our data safe with noombat? Your data is kept apart from every other customer's, in a schema of its own, encrypted in transit and at rest, read through connections that write nothing back, and deleted when we part ways. Data-processing terms written for a security review, for teams in the EU and in the US. We walk through them with your security team on request.

### Pipedrive (https://noombat.ai/integrations/pipedrive)
A one-way connection. noombat reads your CRM on a schedule and writes nothing back. One dedicated user, one API token: an admin completes the setup in about 15 minutes.
Access: A dedicated integration user with the fewest write permissions Pipedrive allows, and its API token. Time: About 15 minutes. Who: A Pipedrive admin. Cost on the customer's side: One seat at your plan's per-seat price; Pipedrive sells no free integration seats.
What noombat reads: Organizations (the companies you sell to); Persons (the people at those companies); Leads (optional, if you use the Leads inbox); Deals, pipelines and stages (pipeline and revenue outcomes); Activities (calls, meetings and tasks on your records); Notes (context logged on deals and contacts); Deal- and contact-linked emails (emails shared into the CRM; private inboxes stay private); Users (record owners, for attribution).
Steps: 1. Create the integration user 2. Permissions and visibility 3. Copy the API token 4. Send us the details
Questions:
- Is this read-only? Our sync is strictly one-way: noombat reads, and writes nothing back. On the platform side, the honest difference from HubSpot and Salesforce: Pipedrive API tokens cannot be scoped, so the token can do whatever the integration user can do, and Pipedrive has no fully read-only user, since creation rights stay on. That is why step 2 strips every write permission Pipedrive lets you strip (deleting, exporting, bulk editing, editing others' items), why we use a dedicated user so every API action is attributable to noombat alone, and why the record change history would show any modification. If platform-enforced read-only is a hard requirement for you, talk to us and we walk through it together.
- What does noombat read, and why? Organizations, persons and leads (who you sell to), deals (pipeline and revenue), and activity: calls, meetings, notes, shared emails. noombat keeps a scored mirror and connects the companies it names to the meetings and revenue that follow. History matters: the scoring learns from what already happened, which is why a forward-only feed is too little.
- What does this cost on the Pipedrive side? One seat, at your plan's per-seat price. Pipedrive sells no free integration users, so the dedicated account takes a normal paid seat. If that is a blocker, the fallback is an existing admin's token, with the trade-offs that access then rides on that person's account (it leaves when they leave and dies if their token is regenerated) and API actions show under their name. We recommend the dedicated seat.
- Will this eat our API limits? Pipedrive gives each company a daily API budget (30,000 tokens × plan multiplier × number of seats). Our sync is scheduled and incremental: after the initial history pull it reads what changed, and it backs off on 429s, so it lives well within the budget alongside your other integrations.
- How do we revoke access? At once, in two ways: regenerate the integration user's API token (each user has exactly one valid token, so a new one kills ours immediately), or deactivate the user. Both are your-side actions we cannot undo.
- Is our data safe with noombat? Your data is kept apart from every other customer's, in a schema of its own, encrypted in transit and at rest, read through connections that write nothing back, and deleted when we part ways. Data-processing terms written for a security review, for teams in the EU and in the US. We walk through them with your security team on request.

### Attio (https://noombat.ai/integrations/attio)
A one-way, read-only connection. noombat reads your workspace once a night and, with the optional webhook, again within the hour of a change. A workspace admin completes the setup in about 10 minutes.
Access: An access token with read scopes only, and an optional webhook for same-hour refresh. Time: About 10 minutes. Who: A workspace admin. Cost on the customer's side: Nothing: access tokens and webhooks come with every Attio plan and use no seat.
What noombat reads: Companies (the companies you sell to: name, domain, description, category, location, LinkedIn page); People (the people at those companies and their roles); Deals (the stage each deal is at, its value and its owner); Lists and their entries (which of your lists a company or person sits in, and the attributes you keep on the entry); Notes (optional: the context your team logs on a record); Workspace members (record owners, for attribution).
Steps: 1. Create the access token 2. Add the webhook (optional) 3. Send us the details
Questions:
- Is this read-only? Yes, and Attio itself enforces it. The token carries read scopes only, so the platform rejects any write attempt. noombat mirrors your book and never writes a field, a note or a task into it.
- What does noombat read, and why? Companies, people and deals (who you sell to and where each deal stands), your lists and their entries (how you segment the book), notes if you allow them, and workspace members (who owns what). noombat keeps a read-only mirror, scores your market against it, and connects the companies it names to the meetings and revenue that follow.
- How fresh is the mirror? Once a night in full. With the webhook from step 2, a change in Attio reaches the board within the hour. The nightly read remains the source of truth, so a missed webhook costs at most a day.
- What does this cost on the Attio side? Nothing. Access tokens and webhooks come with every Attio plan and use no seat.
- How do we revoke access? At once: revoke the token under Settings > Developers, or delete the webhook. Nothing on our side can restore either.
- Is our data safe with noombat? Your data is kept apart from every other customer's, in a schema of its own, encrypted in transit and at rest, read through connections that write nothing back, and deleted when we part ways. Data-processing terms written for a security review, for teams in the EU and in the US. We walk through them with your security team on request.

### Slack (https://noombat.ai/integrations/slack)
noombat posts the morning list and its alerts into the channels you choose, and answers questions where your team talks. One install from your noombat settings, about 5 minutes, no admin rights on the Slack side on most workspaces.
Access: The noombat Slack app, installed from your noombat settings through Slack's own consent screen. Time: About 5 minutes. Who: A noombat org admin; on workspaces that restrict app installs, a Slack admin approves it. Cost on the customer's side: Nothing: the app uses no Slack seat.
What noombat posts: The morning list (the companies worth contacting today, each with its reason, posted to the channel you choose, one message per account owner where you want that); Alerts (an account turning hot, a meeting booked, a lead routed to someone, a scheduled routine finishing, a sync failing); Snout in a DM (ask the analyst about your own data; it answers with the numbers, a table or a chart); @noombat in a channel (mention it in a thread and it answers there); /noombat (the slash command, for a quick question without leaving the channel); Files and canvases (a CSV or a report delivered into the channel, and a canvas that stays current).
Steps: 1. Start the install from your noombat settings 2. Approve the app in Slack 3. Choose the channels
Questions:
- What can the app read? A DM someone sends it, and a channel thread where someone mentions it. It has no scope to read the rest of a channel and no user token. The full scope list is in step 2, each with its reason.
- Can several channels, or several workspaces, receive the list? Yes. Each channel is a choice in your noombat settings, and each Slack workspace is its own install tied to one noombat organisation, so one customer's list can never land in another's channel.
- What does this cost on the Slack side? Nothing. The app uses no Slack seat and no paid Slack feature.
- Does it work on Enterprise Grid? Yes. The app is built for org-wide deployment from day one, so an install covers the workspaces your Slack admin allows.
- How do we revoke it? Remove the app from the workspace under Slack's Manage apps. Slack tells us the moment it happens, and every post and every answer stops. Reinstalling from noombat's settings brings it back.
- Is our data safe with noombat? Your data is kept apart from every other customer's, in a schema of its own, encrypted in transit and at rest, read through connections that write nothing back, and deleted when we part ways. Data-processing terms written for a security review, for teams in the EU and in the US. We walk through them with your security team on request.

### Microsoft Teams (https://noombat.ai/integrations/teams)
noombat posts its alerts and the morning list straight into a Teams channel of your choice. No app install, no admin rights, no cost: one workflow link, about 5 minutes.
Access: A Teams workflow link that posts cards into one channel. Time: About 5 minutes. Who: Any member of the team. Cost on the customer's side: Nothing: the Workflows app ships with Teams on every business plan.
What noombat posts: The morning list (the companies worth contacting today, each with its reason, as one card with a button back into your workspace); An account turning hot (the company, the signal and who owns it); A meeting booked (who booked, with whom, and the account it belongs to); A lead routed (who it went to, and why); A routine finishing, a sync failing (so the team knows the same minute).
Steps: 1. Pick or create the channel 2. Add the webhook workflow 3. One quick check, then send us the link 4. If posts fail with "sender is not a member": the fix, step by step
Questions:
- What can this link do? Post cards into that one channel. It cannot read messages, files or members; it grants noombat no access to your tenant, and nothing is ever read back. It is the only credential in this setup, and it is post-only: the worst anyone holding it could do is post a message into that channel. We treat it like a password all the same.
- Why do the posts come from "Workflows" and not from noombat? Microsoft fixes the sender identity of webhook workflows: every one posts as the Workflows app, and that name cannot be changed. The noombat mark and name lead every card instead, so there is never a doubt who it is from. A full Teams app would change the sender name, and it needs an app install and admin consent in your tenant; we keep this connection lighter than that.
- What does noombat post? Whatever you subscribe the channel to: the morning list (the companies worth a call today, with the reasons), an account turning hot, a meeting booked, a lead routed to someone, a scheduled routine finishing, or a data sync failing. Each is a card with a link back into your noombat workspace, the same alerts Slack customers get.
- How do we revoke it? Delete the workflow, in the channel's Workflows list or at make.powerautomate.com. The link dies with it, at once and for good, and nothing on our side can restore it. Re-adding the workflow creates a fresh link, which is also the rotation procedure: delete, re-add, send us the new one.
- Can we use a private channel? Microsoft's Workflows bot posts to standard channels only; that is a platform limit. The pattern that works: a standard channel inside your team, the team itself being private, which already limits the audience to team members. If a private channel is a hard requirement, ask us about the service-account setup.
- What does this cost on the Microsoft side? Nothing. The Workflows app ships with Teams on every Microsoft 365 business plan, the webhook template uses standard connectors only (no premium Power Automate licence), and no user seat is consumed.
- Can alerts go to several channels, or several teams? Yes. Each channel gets its own workflow and its own link, and each link is bound to exactly one noombat workspace on our side, so one customer's alerts can never land in another's channel. Repeat this guide per channel and send us each link, telling us what should go where.

## Pricing (https://noombat.ai/pricing)

Priced per pod, configured per market. A pod is one revenue team, sales and marketing together, working one market (a country or region and one definition of a good customer); the price follows the size of that market and the sources that feed it. There is no per-seat price: everyone in the pod sees the list. Every pod includes: every company in its market followed daily; its definition of a good customer, written together in the first week; the seven sources; the morning list to its Slack or Teams channel; the company file for every company; an analyst you can ask; read-only connections and EU hosting; a three-month pilot to start (one pod, one market, one list, one review at day 90). Most customers start with one pod and add pods by team or by market. Quotes from https://noombat.ai/pricing.

## Careers (https://noombat.ai/careers)

A team of senior people that has spent years building sales pipeline for B2B companies. Open roles:
- Enterprise Solution Architect (Remote, Full-time, posted 2026-09-11): You set up noombat for enterprise customers. You own the first 90 days of every account. Apply: hello@noombat.ai
- Senior Go-to-market Engineer (Remote, Full-time, posted 2026-09-11): You build the signal pipelines, the scoring and the morning list. TypeScript and Postgres, shipped weekly. Apply: hello@noombat.ai
- Enterprise Business Development Representative (Remote, Full-time, posted 2026-09-11): You open conversations with B2B sales leaders. You work our own noombat list every morning. Apply: hello@noombat.ai

## Legal

- Terms: https://noombat.ai/terms
- Privacy: https://noombat.ai/privacy
- Data processing addendum: https://noombat.ai/dpa