Interview a US Charterer About an Enquiry That Went Nowhere

Start with the moment the enquiry stopped moving

A lost enquiry can teach a maritime software team more than a satisfied customer's general praise. The useful interview reconstructs what happened before the customer stopped progressing: what decision was pending, what information arrived, and what alternative became preferable. It does not start by asking whether faster AI would have secured the shipment. That question assumes the answer before discovering the problem.

For a US chartering desk, an enquiry might disappear because production moved, the receiver changed its plan, another transportation mode became attractive, or the commercial terms never worked. A software builder needs to distinguish those situations from preventable coordination failures. Otherwise, it can spend months automating a process whose speed had little influence on the customer's decision.

Select an enquiry recent enough for the participant to reconstruct and complete enough to discuss without exposing another party's confidential commercial details. Agree that names, prices, and attachments can be omitted. The purpose is to understand the decision sequence, not acquire the customer's private deal archive.

Use research to support a focused conversation

Nielsen Norman Group distinguishes interview accounts from directly observed behavior and recommends a concrete research goal. Recollection is useful evidence, but it is not a complete operational record. Its interview guidance supports that distinction.

For this exercise, write one research question: what prevented the customer from taking the next commercial step? Keep a separate column for what the participant remembers and what a permitted document or later observation corroborates. A statement such as “we waited all week” can express genuine frustration even when the correspondence shows a shorter interval. Investigate which part of the wait mattered instead of correcting the customer competitively.

YC's official Gustaf Alströmer page includes educational material about talking to users. That resource offers a relevant starting point for founders. The maritime interview structure below is an original application, not a claim that YC prescribes these shipping questions.

Reconstruct five decisions rather than every email

Begin with the trigger. What changed in the customer's business that created the need to move cargo? A replenishment order, project milestone, and speculative sale produce different tolerances for delay. Ask what had already been decided when the first enquiry went out. An apparently precise loading window may still depend on unfinished production.

Next establish the requested commitment. Was the customer seeking a budget indication, a credible shortlist, or terms it could take to an internal decision maker? This matters because a prompt vessel suggestion might be excellent at one stage and unusable at another. Do not classify a planning enquiry as a failed fixture simply because no contract followed.

Then examine the information exchange that changed the customer's view. Ask what the customer needed to understand before continuing, who could answer, and what arrived instead. A freight indication without a clear cargo basis may leave the central uncertainty unresolved. The interview should identify the missing decision input, rather than merely count unanswered messages.

Trace the alternative. Did the customer postpone, divide the shipment, change its destination, accept a different service, or cancel? Ask when that alternative became credible. A broker may remember losing the enquiry on Friday while the customer had moved toward another plan on Tuesday.

Finally ask what a useful next action would have looked like at that earlier moment. This is more informative than asking the participant to design an entire software product. The answer might be a single clarification call, an explanation of uncertainty, or a firm statement that the proposed route was unsuitable.

A hypothetical Gulf project-cargo interview

Imagine a US industrial exporter considering a Gulf departure for machinery. The customer recalls that the broker was slow to respond. The interviewer initially suspects an automated matching opportunity, but follows the chronology instead of presenting a demonstration.

The customer explains that a transport planner needed to compare shipping dates with factory release milestones. The broker sent several possible vessels, each with an estimated opening. The planner still could not tell which cargo release dates needed confirmation. Repeatedly enlarging the vessel list made the decision harder because it expanded the unresolved alternatives.

In this fictional case, the useful prototype is not necessarily a faster search engine. It could be a briefing that connects each provisional option to the specific production question the customer must answer. The builder would test whether the planner can select a next action from that briefing, without treating the planner's enthusiasm as proof of purchase intent.

The interview also reveals an economic boundary. If the factory cannot commit to readiness, no polished interface can manufacture that commitment. A helpful assistant could make the dependency visible and prepare a targeted question. It should not turn an assumed date into a confirmed input simply to deliver a completed recommendation.

Convert the interview into a falsifiable product idea

Write a short finding with three parts: the customer's decision, the missing input, and the observed consequence. Keep the proposed feature separate. “The planner could not connect options to release milestones” is a finding to investigate. “Build an intelligent vessel dashboard” is one possible response, and may be unnecessarily broad.

Test the finding against another participant with a different outcome. An enquiry that progressed despite similar uncertainty may reveal an effective human practice worth supporting. Comparing successful and unsuccessful cases helps prevent the team from treating every lost opportunity as evidence for its preferred solution.

Do not calculate a market loss from one story. The shipment's potential value is not the software's obtainable revenue, and the customer's stated frustration is not a signed buying commitment. The immediate output is a sharper hypothesis and a better next observation.

Put the learning to work with Zeaclub

Zeaclub's stated inspiration from Y Combinator fits this practical discipline: let the commercial problem shape the product. For its agentic shipbroking direction, a lost enquiry is an opportunity to learn which unresolved question deserved attention before the opportunity faded.

Bring one recent, appropriately anonymized enquiry to a discussion with Zeaclub. Identify the point at which the customer needed to decide, the information available then, and what happened next. That provides a concrete foundation for exploring useful AI assistance without pretending every lost shipment could have been won through automation.

Sources

Related articles