Aviation Startup - Outreach Templates

Last Updated: 2026-03-06

LinkedIn Connection Request (Spanish - 300 char limit)

For Spanish operators/dispatchers:

Hola [Nombre] -- soy ingeniero de software en Madrid investigando como los operadores bizav gestionan los briefings meteorologicos y la documentacion de cumplimiento EASA. Vi tu trayectoria en [empresa] -- me encantaria hacerte unas preguntas. Tomamos un cafe?

LinkedIn Follow-Up Message (Spanish)

After connection is accepted. Tailored for Gestair Aeroplanning's Manuel Tirado and other Spanish contacts:

Hola [Nombre], gracias por conectar.

Soy Isma, ingeniero de software con experiencia en sistemas de datos en tiempo real. Estoy investigando como los operadores de aviacion ejecutiva en Europa gestionan los briefings meteorologicos y la documentacion de cumplimiento EASA -- especificamente la retencion de briefings (ORO.MLR.100, CAT.OP.MPA.175), la preparacion para auditorias y el tiempo que lleva compilar la meteorologia de multiples fuentes para cada vuelo.

Tu trayectoria es exactamente la perspectiva que necesito -- alguien que ha vivido el dia a dia de las operaciones y entiende el peso real del cumplimiento normativo. Me encantaria invitarte a un cafe (o una videollamada de 20 minutos) para entender:

  • Como preparais y documentais el briefing meteorologico para cada vuelo?
  • Como almacenais esa documentacion para las auditorias de AESA?
  • Cuanto tiempo dedicais al proceso por vuelo?

No estoy vendiendo nada -- estoy en fase de investigacion y quiero entender si este problema merece construir una solucion antes de escribir una linea de codigo.

Te vendria bien una semana de estas?

Un saludo, Isma

LinkedIn Follow-Up Message (English)

For non-Spanish European contacts, EBACE networking, OPSGROUP members:

Hi [Name], thanks for connecting.

I'm Isma, a software engineer based in Madrid with experience building real-time data processing systems. I'm researching how European business aviation operators handle weather briefing documentation and EASA compliance -- specifically the 12-month retention requirement (ORO.MLR.100), audit preparation, and the time spent compiling weather data from multiple sources for each flight.

Your background is exactly the perspective I need -- someone who's lived the daily reality of [dispatch / flight ops / operations management]. I'd love to buy you a coffee (or do a 20-minute video call) to understand:

  • How do you prepare and document weather briefings for each flight?
  • How do you store that documentation for EASA/CAA audits?
  • How much time does the process take per flight?

I'm not selling anything -- I'm in the research phase and want to understand if this problem deserves a solution before writing a line of code.

Would any week coming up work for you?

Best, Isma

Cold Email Template (English)

For reaching out via company email (ops@, info@) when LinkedIn isn't an option:

Subject: Quick question about your weather briefing workflow

Hi [Name / Team],

I'm a software engineer researching how small business aviation operators manage weather briefings and EASA compliance documentation. I'm talking to ops teams across Europe to understand the real workflow before building anything.

I came across [Company] and would love to learn how your team handles weather briefing preparation, documentation, and the 12-month retention requirements. I'm not selling a product -- I'm genuinely trying to understand if this problem is worth solving with better tools.

Would anyone on your ops/dispatch team have 15-20 minutes for a call or video chat? I'm happy to share what I've learned from other conversations as well.

Thanks, Isma [Phone number] Madrid, Spain

Cold Email Template (Spanish)

Subject: Pregunta rapida sobre vuestro proceso de briefing meteorologico

Hola [Nombre / Equipo],

Soy ingeniero de software y estoy investigando como los operadores de aviacion ejecutiva gestionan los briefings meteorologicos y la documentacion de cumplimiento EASA. Estoy hablando con equipos de operaciones en Europa para entender el flujo de trabajo real antes de construir nada.

Me gustaria saber como gestiona vuestro equipo la preparacion meteorologica, la documentacion y los requisitos de retencion de 12 meses. No estoy vendiendo ningun producto -- simplemente intento entender si este problema merece una solucion con mejores herramientas.

Alguien del equipo de operaciones tendria 15-20 minutos para una llamada o videollamada? Encantado de compartir tambien lo que he aprendido de otras conversaciones.

Gracias, Isma [Telefono] Madrid, Espana

EBACE Follow-Up Email (English)

To send within 48 hours of meeting someone at EBACE 2026:

Subject: Great meeting you at EBACE -- [specific topic you discussed]

Hi [Name],

Really enjoyed our conversation at EBACE about [specific thing: weather briefing workflow / compliance challenges / their fleet / whatever you discussed]. [One specific detail from the conversation to show you were listening].

As I mentioned, I'm building an automated weather briefing compliance platform for European business aviation operators. Based on what you told me about [their specific pain point], I think there could be real value for [their company].

I'd love to continue the conversation -- would you be open to a 30-minute call in the next couple of weeks? I could show you the prototype and get your feedback.

Best, Isma [Phone number] [LinkedIn URL]

OPSGROUP Community Introduction

For introducing yourself on the OPSGROUP forum/community after joining:

Hi all -- I'm Isma, a software engineer based in Madrid. I've been following OPSGROUP and the NOTAM reform discussions with great interest.

I'm building a weather briefing compliance platform for European Part-CAT operators -- specifically automating the EASA documentation requirements (ORO.MLR.100, CAT.OP.MPA.175) so small operators don't have to manually compile and archive weather briefings for audits.

I'm in the research phase and talking to dispatchers and ops managers across European business aviation to understand the real workflow. Would love to connect with anyone willing to share their perspective on how weather briefings and compliance documentation are handled in practice.

Happy to share what I learn along the way.

NOTAM Data Provider — Eurocontrol EAD

To: ead.service@eurocontrol.int Subject: EAD Data User Access Inquiry — Aviation Software Startup

Dear EAD Service Team,

I am the founder of an early-stage aviation technology company based in Spain, developing an AI-powered flight operations platform for European business aviation operators. One of our core modules is a NOTAM Intelligence service that parses, filters, and presents human-readable NOTAM briefings for route planning.

We are interested in becoming an EAD Data User to access NOTAM data programmatically via the B2B interface. I have a few questions:

  1. Pricing for startups: As a pre-revenue startup with minimal turnover, could you provide guidance on the applicable service charges and royalty fees under a Type 3 (commercial) agreement? We understand charges are turnover-based — what would this look like for a company in its first year of operations?

  2. Application timeline: How long does the typical process take from initial service request to having operational B2B access?

  3. Technical integration: We plan to integrate via the B2B SOAP/XML interface into a Go-based backend. Is there developer documentation or a sandbox/test environment available during the onboarding process?

  4. Scope: Initially we need NOTAM data for European airports and FIRs. We would eventually redistribute filtered, processed briefings (not raw NOTAMs) to our end-user customers — business aviation dispatchers and pilots.

We are based in Madrid, Spain and are happy to provide any additional information needed for the application process.

Thank you for your time. I look forward to hearing from you.

Best regards, Isma

NOTAM Data Provider — Laminar Data / Cirium

To: (via signup form at https://developer.laminardata.aero/signup, or contact via Cirium) Subject: NOTAM API Pricing Inquiry — Aviation Startup

Dear Laminar Data / Cirium Team,

I am building a flight operations platform for European business aviation and am evaluating NOTAM data providers for our NOTAM Intelligence module. Your spatially-enriched GeoJSON NOTAM API caught my attention — the geometry and altitude data would be particularly valuable for our route-based NOTAM filtering engine.

I'd appreciate information on the following:

  1. Pricing: What are your current pricing tiers for the NOTAM Data API (v2)? We are an early-stage startup and our initial budget for NOTAM data is approximately $200/month. Do you have startup-friendly or usage-based pricing?

  2. Coverage: We need comprehensive European NOTAM coverage (all ECAC states). Can you confirm this is included?

  3. Data freshness: What is the typical latency from NOTAM publication to availability via your API?

  4. Commercial use: We plan to build a product that processes and presents NOTAM briefings to end-user customers (business aviation dispatchers/pilots). Are there any redistribution restrictions we should be aware of?

  5. Trial access: Is a sandbox or trial period available so we can evaluate data quality and API ergonomics before committing?

We are building in Go and would integrate via your REST API. Happy to discuss our use case in more detail.

Best regards, Isma

NOTAM Data Provider Outreach — Next Steps

  • [x] Send Eurocontrol EAD email
  • [x] Submit Laminar Data / Cirium inquiry via signup form
  • [ ] Sign up for Notamify 7-day free trial (https://notamify.com/notam-api) to evaluate their API in parallel
  • [ ] Compare responses on: pricing, data quality, latency, commercial terms, developer experience

Key Principles for All Outreach

  1. Never sell in the first message. Always ask for their expertise, not their wallet.
  2. Reference specific pain points. Shows you've done homework (AC759, FAA outage, OPSGROUP).
  3. Offer value. Share what you've learned from other conversations.
  4. Be specific about what you want. "20 minutes" is better than "pick your brain."
  5. Follow up once. If no response after 1 week, send one polite follow-up. Then move on.
  6. Take notes immediately. After every conversation, write up key insights within 24 hours.
  7. Ask for introductions. "Is there anyone else I should talk to?" at the end of every interview.

results matching ""

    No results matching ""