← Work index
CASE 02 / Industrial field workUSED

Conduit

Bringing the customer environment into view

Factory-floor conversations became customer-specific knowledge for the internal team. The work connected operational context, technical requirements, and AI-assisted preparation.

CONTEXT
Field-deployed engineering internship
TOOLS / METHODS
Customer discovery · Knowledge workflows · NotebookLM
THE CENTRAL LESSON

Operational context is technical input. AI-assisted preparation is useful when it helps the team retain what people actually said and understand what the customer environment requires.

1 evidence recordRead the scope & limits ↓
THE QUESTION

How do you translate a technical product into something workable inside someone else’s operation?

Context

At Conduit, formerly FleetGlue, I worked as a field-deployed engineering intern. I visited factories and spoke with floor staff, purchasing, and others along the workflow. Those conversations exposed details that a product description alone could not supply.

What I did

  1. 01

    Gathered operational context directly from people working in industrial environments.

  2. 02

    Used AI-recorded conversations to build customer-specific knowledge bases, with a flow from calls into that material.

  3. 03

    Prepared customer presentations with NotebookLM and AI video tools, and worked on customer-oriented letters of intent.

Architecture / workflow

CONDUIT / SYSTEM STUDYFIRST-HAND ACCOUNT

Keep the context attached to the conversation.

What disappears when a conversation becomes a summary?

  1. 01
    HUMAN JUDGMENT

    Listen in the field

    Factory staff and purchasing explain the operation

  2. 02
    INFORMATION / ARTIFACT

    Capture context

    Recorded conversations and field observations

  3. 03
    MODEL ASSISTANCE

    Organize knowledge

    AI-assisted customer knowledge and presentations

  4. 04
    HUMAN JUDGMENT

    Interpret constraints

    The internal team considers deployment questions

INSPECT THE FAILURE BOUNDARYA summary erases who said something or treats an observation as a requirement.
WHAT FOLLOWS

The account supports a knowledge workflow, not a complete or independently verified model of a customer’s operation.

Author-reported workflow; exact implementation is not publicly evidenced. No customer identities or factory details are reproduced.

Where it gets difficult

Different people describe the same operation from different positions. A useful knowledge base must preserve that context instead of flattening it into an apparently complete summary.

The engineering team needs operational constraints, not just enthusiasm for a product. Preparation has to help the team ask better deployment questions.

THE BOUNDARY OF THE CLAIM

Limits & evidence

  • This case study is based on my first-hand account, recorded during the earlier portfolio review. The call workflow and letters are not independently verified by public artifacts.
  • No quantified reduction in meetings or deployment performance is claimed.
  • Customer identities, factory details, and private conversations are omitted.
First-hand account

Industrial field work and customer context

Fitz’s account, recorded in the November 2026 portfolio review, describes factory visits, customer knowledge bases, presentation tools, and work as a field-deployed engineering intern.

What this does not establish

Customer conversations and artifacts are not public. The workflow is author-reported, not independently verified by a public artifact; no quantified business outcome is claimed.

What this changed

Operational context is technical input. AI-assisted preparation is useful when it helps the team retain what people actually said and understand what the customer environment requires.

WHERE THIS LEADS

The next step was building systems that could carry useful context into the workflow itself, instead of leaving it in meeting notes.

NEXT CASEAvorth