Find the Right Role for Your Future

Co-Founder & Chief Technology Officer

Role Summary

Flite AI is hiring a technical co-founder to serve as CTO, starting with a paid trial on November 1, 2026 and moving to full-time co-founder in January/February 2027.

Flite AI builds AI agents that do the repeatable work of enterprise software implementation — discovery, configuration, data migration, testing — and licenses them to systems integrators and software vendors’ professional services teams.

The CTO architects the Flite AI platform from V1, owns how it gets built, and builds the engineering team, while the CEO owns what gets built.

Why Join Flite AI

The seat is a true co-founder role on a company with a paid agent already in production and a platform still to be designed.

The Vision

• A 20-person firm delivers like a 2,000-person one. A mid-market company gets the implementation quality only the Fortune 500 could afford. Switching enterprise systems becomes as easy as buying them.
• Flite AI gives the teams that deliver implementations one platform of agents that carries every project’s knowledge into the next.

Why Now

• Agents can now do the repeatable work of implementation. The firms that deliver implementations know that if they don’t change how they work, AI will change it for them.

The Founder

• Alex Sutty has 18 years on every side of enterprise implementations: ABAP developer and manager on SAP transformations at Accenture, 50+ implementations led at Zuora, and one of two PMs who took Workday subscription billing from zero to launch.
• She holds a patent-pending no-code rating model builder. She has done this work by hand and is building the way out.

Traction

• A paid agent is live in production with Salesforce as partner. A second agent is in progress with a legal-tech software vendor. Active prospects include software vendors in legal, hospitality, and finance.
• Seed round targeted for Q1 2027.

The Seat

• 30% starting equity. You architect the platform from V1, own how it gets built, and build the engineering team.

What You’ll Own

The CEO defines what Flite AI builds and sets the budget; the CTO defines how it gets built and delivers it within that budget.

• Platform Architecture: Design and build the Flite AI platform — the orchestration layer that carries one structured requirement through Design, Build, Test, Deploy, and Post Go-Live; agents that hand work forward between phases, keep vendor solutions in sync within a phase, and call third-party agents agent-to-agent.
• Agent Delivery: Ship new agents to production on a quarterly cadence, built on shared components so each new agent reuses the last.
• AI Reliability: Context persistence across long-running work, a shared knowledge base plus per-customer project data, evaluation, and deterministic validation of LLM output.
• Security and Compliance: Tenant isolation, zero data retention, private or self-hosted model options, and the SOC 1, SOC 2, and GDPR programs.
• Infrastructure: Cloud portability across AWS and Azure; Flite AI hosts all agents.
• Live Agent Support: Support SLAs, uptime, and the feature requests the CEO prioritizes from live customers.
• Engineering Team: Decide the team model (employees, offshore, or partners) and hire within the CEO’s budget.

Requirements

• The top requirement is founder experience through a fundraise or technical due diligence; the rest are listed in
• priority order.
• Must-have
• Has been through a fundraise or technical due diligence as a founder.
• Has been a CTO, founding engineer, or technical co-founder at an early-stage company, building from
• zero to production.
• Hands-on with production LLM and agent systems: orchestration, RAG and vector databases, evaluation,
• and deterministic validation of model output.
• Data engineering and migration experience: SQL, schema mapping, ETL, and messy enterprise data.
• Has architected multi-tenant SaaS with security built in: tenant isolation, zero data retention, and access
• controls.
• Has led SOC 1 and SOC 2 audits, or meaningfully participated in them.
• Brings a network of engineers to build with and has managed distributed teams within a budget.
• Comfortable with the split: the CEO defines what gets built, the CTO defines how.
• US-based, West or Central time preferred. No visa sponsorship.

Nice-to-have

• Azure and multi-cloud experience; legal-industry customers run mostly on Azure.
• Familiarity with the current stack: Python, FastAPI, Strands Agents, Qdrant, MongoDB, Redis, Amazon
• S3, Anthropic API on AWS.
• Agent governance or neurosymbolic approaches, such as rule extraction to deterministic code or proofbased
• gating.
• GDPR program experience.