---
name: account-technology-landscape
description: Builds a cautious, source-backed view of the technologies and vendors an account publicly appears to use, with confidence, relevance, and research gaps. Use for account research, technology landscape review, prospect preparation, vendor context, or solution positioning.
license: Apache-2.0
metadata:
  adlass.categories: "sales-crm/lead-research"
  adlass.industries: ""
  adlass.tags: "account-research, technology, vendors, prospecting, sales-intelligence, fit"
  adlass.adaptation: "reference-doc"
  adlass.source: "n8n:2318, n8n:2110"
  adlass.version: "1"
---

# Account technology landscape

## Purpose

Organise public and internal evidence about an account's technology environment so a seller can assess relevance and prepare informed questions without claiming certainty from weak signals.

## Scope

Named tools, platforms, vendors, implementation evidence, business function, source, recency, confidence, likely relevance, and unknown areas.

**Excluded:** intrusive scanning, private data collection, security testing, and presenting inferred technology as confirmed fact.

## Data basis

- Account name or domain supplied as a run input.
- Account records and prior opportunity notes.
- Public company, job, partner, case-study, and technical sources when enabled.
- Company's offer profile in scope.

## Result

A technology landscape sheet and a concise positioning brief with validation questions.

## Quality criteria

- Each technology has a direct citation and date.
- Evidence type and confidence are explicit.
- Inferred use is separated from confirmed use.
- Relevance is tied to a business function or offer capability.
- Unknown areas are not filled by default assumptions.

## Instructions

Prefer account-authored or partner evidence over directories. Do not treat a job posting, logo, or integration page as proof of current deployment without qualification. Consolidate aliases and versions while preserving original wording. State when a source may be stale. Use the landscape to form questions, not to make a security claim.

## Adapt before use
Keep a clear audit trail throughout the run. Use the source wording and field values that support each material conclusion, and retain uncertainty when the evidence does not decide the issue. Separate a missing record from a negative result and a contradictory record from an exception. Prefer a short, prioritised result over unsupported completeness. Check that counts, identifiers, dates, and labels agree across the written result and the structured output. When a rule, source, or mapping is unavailable, name the limitation and explain how it affects interpretation. Do not silently infer ownership, approval, timing, or business intent.

- Add the offer profile and relevant technology categories.
- Define accepted public sources and confidence levels.
- Set the preferred lookback period and landscape format.