What US maritime founders can learn from YC user discovery

Find the problem behind the feature request

US maritime startup customer discovery should establish how a shipping task is performed, where it becomes difficult and who cares enough to change it. A request for an AI dashboard is a starting point for investigation, not a complete product specification.

Y Combinator makes user learning a visible part of its educational material: Gustaf Alströmer's official YC page includes a presentation titled How to Talk to Users. That emphasis is a useful inspiration for founders entering a specialist industry. It does not remove the need to understand the commercial meaning of what a maritime user says.

Enterprise commercialization has a broader support ecosystem as well. Alchemist's official program overview includes customer discovery and enterprise sales in its workshop subjects. These are relevant disciplines for maritime founders because a helpful tool and a purchasable business solution are not necessarily the same thing.

The interview approach below is an original maritime application. It is not a reproduction of either organization's curriculum, nor does it imply that Zeaclub participates in either program.

Start with a recent task, not a proposed screen

Ask a chartering professional to describe a recent enquiry from arrival to the next meaningful decision. Use a permitted example or a fictionalized reconstruction. The objective is to understand the sequence, including what the person checked outside the main system.

Listen for the moments at which the task changed character. A broker may begin by collecting candidate vessels, then discover that the cargo owner has not settled the discharge option. The apparent search problem has become a decision problem. Improving search speed might leave the real obstacle untouched.

Ask what happened next. Did someone call a colleague, reopen an attachment, wait for the principal or create a personal spreadsheet? Each action reveals something about the work. A workaround may be inefficient, but it may also preserve flexibility or confidentiality that a proposed replacement must respect.

Do not turn the interview into a contest over whether existing tools are outdated. The founder needs to learn why they remain useful. If an informal note carries a condition that the formal record cannot represent, removing the note without replacing its function could make the process worse.

Map user, buyer and affected colleague

A US maritime software purchase can involve several perspectives. For a particular prospective customer, identify the person doing the task, the person controlling the purchase and the people who consume the result. Confirm these roles instead of assuming they follow job titles.

The broker may value faster reconstruction of an enquiry. The operations colleague may value a reliable statement of outstanding conditions. The manager may want a repeatable process that new staff can understand. These needs can reinforce each other, but the founder should discover the connection rather than blend them into a vague promise of efficiency.

Interview subject Useful question Product decision it can inform
Task performer What did you have to check before acting? Which context must remain accessible
Recipient What did the handoff leave unclear? Whether output is useful outside its creator's desk
Purchase owner What would justify changing the current process? Whether the problem supports a buying decision
Specialist reviewer Which questions should remain with your function? Where the product needs a referral boundary
New team member What was difficult to interpret without background knowledge? Whether the design depends on unwritten expertise

Treat the answers as evidence about that organization. One interview does not establish a universal maritime requirement, and enthusiasm from a friendly contact does not establish demand across the US market.

A hypothetical interview that changes the product idea

Imagine a founder speaking with a small US brokerage about an AI inbox. The initial request is automatic classification of cargo emails. During the interview, the broker explains that classification is easy; the difficult task is determining whether a forwarded message supersedes an earlier condition.

The founder asks the broker to reconstruct an example. The original sender revised the loading period, but an intermediary forwarded only part of the exchange. The desk spent time comparing messages and calling the originator. The broker did not need another folder. The broker needed a clearer indication that the available record was incomplete.

The founder then speaks with the colleague who received the resulting summary. That colleague assumed the loading period had been confirmed because the summary presented a single date range. The same problem affected both preparation and interpretation.

The next prototype therefore focuses on showing conflicting conditions and the missing confirmation. Its test question is whether the recipient can identify what still needs to be asked. This is a materially different product decision from building more classification categories, and it came from investigating the work rather than collecting feature votes.

Turn observations into a testable hypothesis

After the interview, separate what the user said from what the founder inferred. A useful note might record that the broker reopened several messages to establish the current condition. The hypothesis might be that a source-linked comparison would reduce reconstruction. The latter still needs testing.

Describe the proposed test in ordinary commercial language. Give a reviewer an authorized sample, show the proposed output and ask what action they would take. Compare that response with the task's actual unresolved questions. Do not ask only whether the output looks professional.

Preserve inconvenient findings. If experienced users prefer the current process, determine why. The proposed tool may remove context, require too much setup or solve a rare problem. A founder learns more from that explanation than from treating every objection as resistance to innovation.

Also identify what evidence would change the founder's mind. If the task is too infrequent, the buyer has no reason to replace the workflow, or the needed information is unavailable, a different initial problem may deserve attention. Customer discovery is useful because it can change a plan.

Connect the learning to Zeaclub's direction

Zeaclub's founders describe YC as an inspiration. For its US agentic shipbroking direction, that influence is most credible when commercial users help shape the problem definition before broad product claims appear. Shipping knowledge is not an obstacle to innovation; it is the material from which a useful product can be built.

A cargo owner or broker approaching Zeaclub can make the discussion productive by bringing a recurring decision problem, describing the current workaround and identifying the recipient of the resulting information. No confidential negotiation needs to be disclosed without authorization. An anonymized or hypothetical example can begin the conversation.

The practical next step is to agree what a better outcome would look like and how it could be observed. That gives both sides a clear basis for discussing current capabilities, development priorities and human involvement. Positive startup ambition becomes more persuasive when the founder can explain exactly what has been learned from the people doing the work.

Sources

Related articles