Brief
Tell us the mission, budget, region, and dealbreakers. The brief becomes the agent's working set.
CompAeros Broker
Brief us once. We research listed sellers and unlisted owners, rank candidates by fit, and draft outreach for your review. You approve every message before it sends — with suppression controls, frequency caps, and a full audit trail.
How it works
Tell us the mission, budget, region, and dealbreakers. The brief becomes the agent's working set.
The agent scans the marketplace, public listing aggregators, FAA registry, and the open web. Every source it touches is logged with the query and result count.
Drafted messages for qualifying candidates land in your inbox for review. Nothing leaves the building until you click Send. Suppression list and 90-day frequency cap are enforced before drafting.
Responsible outreach
Responsible sourcing means knowing where the line is. We built the limits in before launch, not after.
Every outreach message is queued for human review. The platform will never automatically send to a contact without explicit user approval on that specific send.
Hard weekly outreach caps per brief. A 90-day per-recipient frequency cap prevents contact saturation regardless of how many briefs are active.
Candidate research respects robots.txt and Terms of Service boundaries on every data source. FAA registry data is used responsibly — for research, not harvesting.
CompAeros surfaces broker-listed aircraft through the broker, not around them. Broker attribution is preserved and outreach routes through established relationships where they exist.
Built-in compliance
Upload or maintain a suppression list of contacts, domains, and organisations who should never receive outreach. Checked before every draft is surfaced for approval.
Every outreach draft includes a compliant unsubscribe mechanism, sender identification, and physical address field — populated before the message reaches your review queue.
Every approved send, every rejected draft, every suppression check, and every frequency-cap decision is logged with timestamp and user attribution. Exportable on request.
N-number registry data is used exclusively for aircraft ownership research — not scraped for bulk contact lists. Frequency caps and suppression apply to all registry-sourced contacts.
Outreach guardrails
Off-market sourcing is a privilege, not a right. The features below are not optional — they are baked into the data model.
Pricing
Brief volume, weekly outreach cap, and FAA-registry depth scale with the plan. See the full pricing page →
FAQ
Done well, yes. Done poorly, no. We use only public data (FAA registry, owner-of-record), we make a single low-frequency touch, we identify ourselves and the buyer, we honour suppression immediately, and we ask once. If the owner says no — or simply doesn't reply — we move on.
Three things. First, every send is user-reviewed — the human approves the message AND the recipient. Second, the 90-day frequency cap is enforced cross-tenant in the database — no broker on CompAeros can re-contact a recipient another broker has touched recently. Third, brief-level weekly caps default to 5 and max at 25.
Internal listings (real time), public listing aggregators (rate-limited fetches that respect robots.txt and TOS), the FAA Aircraft Registry (public weekly snapshot), and an LLM-driven web scan when an Anthropic API key is configured. Every source the agent touches is logged with query + result count.
No. The data model literally does not have a non-reviewed path — every outbound row is created with status=awaiting_review, and the send endpoint refuses to dispatch anything in any other state. We can't enable auto-send by accident.
One click on a token-signed link in the email footer. No login. No "are you sure?" Suppression is recorded immediately and applied before any future drafting.
CompAeros Broker provides research automation and outreach drafting tools. It is not a licensed aviation broker, dealer, or agent. Users are responsible for all communications sent from their accounts. CompAeros does not guarantee aircraft availability, seller responsiveness, or transaction outcomes. All outreach must comply with applicable anti-spam laws in the user's jurisdiction.