Kebra GTM brain

category

market profile

• text: Field service information is fragmented across technicians, photos, texts and incomplete reports, creating downstream coordination work.
• text: Kebra positions itself as an AI layer for field operations rather than describing a general-purpose assistant.

personas

• title: Field service operations leader
  pains:

  • Incomplete job records slow follow-up and make it difficult to see what happened on site.
  • Dispatch and back-office teams must coordinate work across disconnected systems.
• title: Service manager or technician
  pains:

  • Job documentation competes with time spent completing repairs.
  • Field teams need accessible job context when decisions must be made on site.

icp

• text: Field service and residential service businesses with technicians working at customer sites.
• text: Teams with recurring reporting, warranty, coordination or compliance work spread across existing systems; exact company size is unverified.

message pillars

• text: Make otherwise inaccessible field knowledge usable by software.
• text: Equip the skilled workforce for AI-enabled operations.
• text: AI's effectiveness depends on field context.

objections

• objection: Our field records are too inconsistent for AI.
  response: Start with one recurring job type and compare captured information with the existing report before expanding.
• objection: We already have field service software.
  response: Evaluate whether Kebra can use existing systems and automate the follow-up around them; confirm integrations during a demo.

competitors

• name: ServiceTitan
  why: Trade service platform with AI for dispatch and other field workflows.
• name: Zuper
  why: Field service management provider offering AI-enabled scheduling and technician tools.

influencers

• name: Luca Hadife
  why: Kebra co-founder and CEO, a potential source of product and market views.

keywords

• field service AI
• technician job documentation
• field service automation
• warranty claims automation
• AI dispatch software
• field technician knowledge

voice

• Concise and technical
• Field-worker focused
• Operational and forward-looking

signals

• text: Hiring dispatchers or administrators to keep up with field work suggests a coordination burden worth exploring.
• text: A growing technician workforce and recurring warranty claims can make consistent documentation valuable.

pricing

motion

channels

• LinkedIn

confidence

Founders

• name: Luca Hadife
  title: Founder/CEO
  role: CEO
  bio: Co-Founder and CEO of Kebra. Built multimodal AI systems at Microsoft. Early team member at Amata (Series A). UC Berkeley Data/ML and ASUC Senator
• name: Mohamed Hosny
  title: Founder/CTO
  role: CTO
  bio: Co-Founder of Kebra. Taught Computer Architecture and Signal Processing at UC Berkeley EECS. Software Engineer on data center switches at Arista Networks.