Fahmid Uddin

Forward-deployed product engineer

Toronto, Canada

Fahmid Uddin in front of a dark architectural facade

Diagnose / Embed / Build / Deploy

Forward-Deployed Product Engineer — Building and Shipping AI Systems with Teams.

Verified proof

Named work. Scoped evidence.

Hands-on coding
15 years

Career / frontend to AI systems

Tracked engineering hours
650+

AI Account Executive

Itinerary loads
13,362

Optifly / verified 30-day signal

Lower RAG cost / faster
~15× / ~20×

LegixAI

Deployment index

Three systems, three operating contexts.

The work is grouped by the problem surface, Fahmid’s role inside it, and the evidence that can be attributed to that deployment.

01AI Account ExecutiveFractional Product EngineerEmbedded across discovery, implementation, deployment, and iteration to rebuild a broad AI sales product surface and the platform foundations underneath it.Primary production / client case02OptiflyFounder, Product & GrowthBuilt an AI-native travel planning and booking-intent product that turns a prompt into a live, shareable itinerary, then instrumented the product and acquisition loop.Live product + acquisition loop03Nexore / xOSFounder & AI Systems BuilderBuilding a self-hosted AI control plane used inside Fahmid’s own real work to keep memory, tools, and execution context attached across multiple product and client lanes.Internal control plane / current direction

Primary case file / 2025–Present

AI Account Executive

Fractional Product Engineer

Embedded across discovery, implementation, deployment, and iteration to rebuild a broad AI sales product surface and the platform foundations underneath it.

Visit AI Account Executive
Tracked product-engineering hours
650+

Discovery through deployment and iteration

AI Account Executive public workflow showing account intelligence and persona-specific messaging
Public workflow / Account intelligence + messagingLive product page / 12 Aug 2026

Diagnose

Map the operating surface

Worked across the connected research, persona, targeting, meeting-prep, content, presentation, and email workflows rather than treating each feature as an isolated screen.

Embed

Stay through the delivery loop

Contributed more than 650 tracked hours spanning discovery, implementation, staging validation, production release, and repeated iteration with the team.

Build

Ship the product and its foundations

Rebuilt core AI workflows while adding billing, credits, administration, organizations, seats, enterprise identity, integrations, exports, and internal controls.

Deploy / Iterate

Release, observe, refine

Validated fixes in staging, pushed production releases, and added Axiom and Sentry instrumentation so the team could see failures and keep improving the system.

Product workflows

  • Research and personas
  • Targeting and meeting prep
  • Content and presentations
  • Email workflows

Platform foundations

  • Billing and action credits
  • Admin and plan controls
  • Organizations and seats
  • Okta / SAML support

Integrations and evidence

  • Gmail and Outlook
  • PDF and report exports
  • Axiom instrumentation
  • Sentry error visibility

Case file / 2025–Present

Optifly

Founder, Product & Growth

Built an AI-native travel planning and booking-intent product that turns a prompt into a live, shareable itinerary, then instrumented the product and acquisition loop.

Visit Optifly
Share-landing views
11,270

Verified 30-day signal

Itinerary loads
13,362

Verified 30-day signal

Booking-click events
201

Verified 30-day signal

Request-to-plan progression
90%

Verified 30-day signal

Optifly public workspace showing chat, live travel results, and a day-by-day planner
Public workspace / Chat + results + plannerLive product page / 12 Aug 2026

Diagnose

Connect planning to action

The useful product was not another static itinerary. It needed to connect a traveler’s intent to a structured plan, live inventory, sharing, and partner booking rails.

Embed

Work the product and growth loop

Built the customer experience while instrumenting behavior with PostHog and Axiom and reviewing acquisition data at campaign and ad-group level.

Build

Prompt to shareable itinerary

Shipped AI-guided plans with flights, stays, routing, experiences, live inventory, and Expedia / Viator partner click-through paths.

Deploy / Learn

Measure the full path

Used product and campaign signals together to understand request completion, itinerary use, sharing, booking intent, and which acquisition variants earned attention.

Product

  • AI itinerary generation
  • Live travel inventory
  • Shareable plan surfaces
  • Partner booking intent

Measurement

  • PostHog product analytics
  • Axiom event visibility
  • Plan progression tracking
  • Booking-click events

Acquisition evidence

  • 167K+ TikTok impressions
  • 29.4K clicks
  • 17.6% CTR
  • ~$0.024 CPC

The TikTok acquisition snapshot covers the same verified 30-day reporting window.

Case file / 2025–Present

Nexore / xOS

Founder & AI Systems Builder

Building a self-hosted AI control plane used inside Fahmid’s own real work to keep memory, tools, and execution context attached across multiple product and client lanes.

Visit Nexore
Internal operating modelHuman-directed control plane
01 / DirectionHuman operator

Sets intent, constraints, and final judgment.

02 / Control planexOS

Routes memory, tools, workflows, and execution context.

03AKnowledge

Semantic memory, Notion, Google Workspace.

03BInfrastructure

AWS Bedrock / Secrets and GCP / Vertex AI.

Current directionAgentCore / Strands

Exploration, not a mature deployment claim.

Diagnose

Stop rebuilding context

Parallel work loses momentum when decisions, notes, and system state are scattered. xOS starts from the operating problem of keeping context durable across real work lanes.

Embed

Use it in the work it coordinates

The control plane is exercised inside Fahmid’s own product, client, campaign, analytics, and launch work rather than positioned as an abstract agent demo.

Build

Connect memory, tools, and execution

The self-hosted system connects semantic memory, agent workflows, Notion, Google Workspace, AWS and GCP services, and communication surfaces around a human-directed loop.

Adopt / Extend

Keep the claim boundary explicit

xOS is an internal operating system today. Bedrock AgentCore and Strands are active directions under exploration, not claims of mature customer production deployment.

Direction

  • Human sets intent
  • Agents extend throughput
  • Context remains durable
  • Work stays observable

Connected context

  • Semantic memory
  • Notion knowledge
  • Google Workspace
  • Communication surfaces

Infrastructure

  • AWS Bedrock and Secrets
  • GCP / Vertex AI
  • Bedrock AgentCore direction
  • Strands direction

Claim boundary: xOS is used in Fahmid’s own operating environment; this portfolio does not present it as a customer SaaS or mature AgentCore deployment.

Field notes

What changes when the engineer stays close.

Working principles drawn from product delivery, client collaboration, instrumentation, and operating the systems after launch.

Fahmid Uddin outdoors beside a railing
Portrait / TorontoPersonal archive / 2026

FN / 01

Stay close to the operating surface

Useful requirements emerge from the real workflow: the handoff that breaks, the decision that lacks context, or the repeated step nobody has named yet.

FN / 02

Ship the connective tissue

An AI feature is rarely the whole product. Billing, identity, administration, exports, integrations, and support tooling determine whether a system can actually be used.

FN / 03

Instrumentation is part of delivery

PostHog, Axiom, Sentry, traces, and evaluations turn a release into an observable operating loop instead of a one-time handoff.

Profile / 2010–Present

Fifteen years across the full product surface.

The chronology moves from games and interface work into client delivery, AI workflows, cloud systems, and forward-deployed product engineering.

TypeScript, React, Next.js, and Node.js form the strongest historical through-line. Recent AI-agent work adds substantial Python, AWS, GCP, Terraform, MCP, RAG, evaluations, traces, and production observability.

Technical leadership
Led 3–5 engineers across GPT Protocol / Airas work.
Client delivery
Direct client-site collaboration through Decise.
Current base
Toronto, Canada.

  1. 2010–2012

    Game prototypes and public builds

    Started coding and shipping small game experiments, tutorials, and working demos.
    Early game prototype video artifact
    Archive / 2010–2012

  2. 2013–2015

    3D motion and visual systems

    Built 3D animation and interface experiments that established a durable product-design instinct.
    Early PacMan 3D animation artifact
    Archive / 2013–2015

  3. 2015–2020

    UI, product, and game experiments

    Expanded from visual studies into interface systems, prototypes, and end-to-end product work.
    Collage of early interface and game experiments
    Archive / 2015–2020

  4. 2020–2021

    Metagood / OnChainMonkey

    Joined Metagood as its first engineering hire and helped turn early product direction into shipped foundations.
    Metagood and OnChainMonkey project marks
    Archive / 2020–2021

  5. 2021–2022

    Decise enterprise delivery

    Built software for City BBQ, Pieology, and Chipotle with direct client-site collaboration and production delivery.
    Decise, City BBQ, Pieology, and Chipotle project marks
    Archive / 2021–2022

  6. 2022–2023

    LegixAI workflows and RAG

    Built AI accounting workflows; verified RAG work reduced cost by roughly 15× and ran roughly 20× faster.
    LegixAI public product artifact
    Archive / 2022–2023

  7. 2023–2025

    AI systems and technical leadership

    Built AI-native products and led teams of 3–5 engineers across GPT Protocol / Airas work.
    AI Account Executive public workflow showing account intelligence and messaging
    Verified product / AI workflow

  8. 2025–Present

    Forward-deployed product systems

    Working across AI Account Executive, Optifly, and Nexore / xOS from operating problem through deployment and iteration.
    Optifly public workspace showing chat, live results, and itinerary planning
    Verified product / live workspace

Direct answers

The useful facts, without the pitch deck.

These visible answers are also the source for the site’s FAQ structured data and answer-engine context.

01What does Fahmid Uddin do?

Fahmid is a Toronto-based forward-deployed product engineer who diagnoses operating problems, embeds with teams, and builds and ships AI systems through deployment and iteration.

02What does forward-deployed mean in Fahmid’s work?

It means staying close to the real workflow and stakeholders: moving from discovery and system design into implementation, deployment, instrumentation, adoption, and ongoing iteration.

03What was Fahmid’s role with AI Account Executive?

As a fractional product engineer, Fahmid delivered more than 650 tracked hours across AI sales workflows, platform foundations, integrations, observability, staging validation, and production releases.

04Is xOS a customer SaaS product?

No. xOS is Fahmid’s self-hosted AI control plane used in his own real product and client work. Bedrock AgentCore and Strands are current directions, not claims of mature customer production deployment.

05What evidence is available for Optifly?

Verified 30-day signals include 11,270 share-landing views, 13,362 itinerary loads, 201 booking-click events, and 90% progression from request start to plan completion. The acquisition rollup included 167K+ TikTok impressions and 29.4K clicks.

06Where is Fahmid based and how can I contact him?

Fahmid is based in Toronto, Canada. The direct contact address is fahmid.me@gmail.com.

Contact / Toronto, Canada

Bring the messy operating problem.

For forward-deployed engineering, applied AI product systems, founding-team work, or client delivery conversations.

fahmid.me@gmail.com