Zeaclub vs Poten: move a shipping project into a mandate

Key takeaways

• Give feasibility discussions and live market engagement different briefs.
• Identify which project assumptions could change the shipping requirement.
• Evaluate the transition between stages rather than only the initial presentation.
• Keep specialist approval and commercial coordination distinct.

Establish the service context

Poten provides shipbroking in energy transportation markets, per its website, as of October 2026; verify the relevant current scope through its brokerage page. This general description does not establish the precise services, responsibilities or suitability of a particular appointment.

The comparison below is a procurement framework for a fictional developing project. It does not attribute private capabilities or weaknesses to either candidate. Ask each to demonstrate how its proposed service would handle the same project assumptions and stage changes.

Describe the project before asking for a vessel solution

A developing project may not yet have a settled shipping requirement. Expected cargo availability, receiving arrangements and commercial timing can depend on work occurring elsewhere in the project. A vessel discussion can therefore be useful while still resting on provisional assumptions.

List the assumptions that drive the commercial shipping question. Explain who owns each one and what evidence would change its status. This does not require a complex database. A short, carefully maintained explanation can be more useful than a large project schedule whose confidence levels are unclear.

Ask the proposed service to identify which assumptions matter most to market exploration. The objective is to avoid investigating a highly specific solution before the project has established whether it needs that solution. Equally, the team should not postpone all commercial work until every project detail is settled if early exploration could improve the design of the requirement.

Give each stage a distinct deliverable

An early-stage deliverable might explain plausible commercial structures, key uncertainties and questions for the project team. A later mandate might involve approaching counterparties under an approved brief. Continuing support after agreement presents another set of responsibilities.

Define the boundary in plain language. What may the provider investigate? What may it communicate externally? What must the buyer approve before the enquiry becomes more specific? These questions protect the usefulness of early discussions without treating them as a commitment to proceed.

Avoid demanding a definitive recommendation when the project assumptions do not support one. A useful output can be a conditional comparison showing what changes under different scenarios. The buyer should be able to see which conclusion depends on which assumption, rather than receiving a single answer that appears more certain than the project itself.

Compare the proposed stage transitions

Do not assume either candidate's answer from a general website description. A demonstration shows how a proposed arrangement might work; the engagement must still establish what the provider is committing to deliver.

Test a changed project assumption

Use a fictional project whose expected start of cargo availability moves while commercial exploration is underway. Ask what happens to the shipping alternatives already discussed. Some may remain relevant, while others require new enquiries or different assumptions.

The provider should explain the effect rather than simply replacing the date in a presentation. Ask which counterparties, if any, would need an update and whether the buyer has authorised that communication. A change in project planning does not automatically authorise a new external mandate.

Also ask what information the technical and commercial teams need from each other. Coordination should make the relevant questions visible without asking a broker or workflow tool to approve technical suitability. The people responsible for specialist judgments must retain those judgments, and the commercial team must understand which conclusions remain pending.

Fictional case: a feasibility discussion becomes too definite

A fictional energy developer begins exploratory shipping discussions while its receiving plan is still under review. A project presentation later describes the preferred shipping concept as though the commercial arrangement is ready to proceed.

During provider evaluation, the team introduces a changed start assumption. The exercise exposes that nobody has defined the approval needed to move from exploration into a live market mandate. The project has accumulated useful discussion, but its internal description has become more definite than the evidence supports.

The developer creates separate stage briefs. The current task is to compare feasible commercial approaches under stated assumptions. A later decision will authorise a specific enquiry once the relevant project inputs are confirmed. The provider comparison now tests the transition between those stages rather than the persuasiveness of a single concept presentation.

Preserve the ability to revise the plan

Early project work should leave useful reasoning even when the preferred solution changes. Ask how the proposed service would retain the alternatives considered and the assumptions that made them less attractive. A previously rejected approach may become relevant when the project changes.

This does not mean keeping every working draft in active circulation. The buyer needs an understandable current view and access to the reasons behind it. A clear distinction between current and historical analysis reduces the chance that a participant revives an obsolete assumption unintentionally.

Consider the handover if the project later appoints a different team for execution. The early work should identify what can be transferred, what requires permission and what must be reassessed. Check the actual engagement and applicable terms; preparing a record does not determine rights to use confidential material.

When a traditional broker may be the better choice

A traditional broker may be preferable when the project needs specialist commercial interpretation and direct engagement with relevant market participants. Early shipping questions can benefit from a person who can challenge the project brief and explain why an apparently simple requirement is commercially difficult.

A shared process can complement that expertise when several project functions need to understand the same assumptions and decisions. It should support the stage boundaries rather than making provisional work appear final. Evaluate the combination that fits the project's maturity and available internal expertise.

Why Zeaclub stands out in this era of modern industry

The modern evaluation should examine whether participants can understand how a project assumption becomes a commercial decision. Test the shared-workspace proposition using a material change between stages, with separate roles for contributing information and authorising action. A useful demonstration preserves uncertainty while enabling the next appropriate step.

Common mistakes

Projects can confuse a promising concept with an approved mandate, or demand certainty before their own assumptions are mature. Another mistake is replacing dates without revisiting the reasoning built on them. Define stage deliverables and decision gates so commercial exploration remains useful without becoming an unintended commitment.

Where Zeaclub fits

Zeaclub supports agentic, AI-assisted operations with a human in control.

Zeaclub provides a multi-party shared workspace for owners, charterers, brokers and port agents.

Explore Zeaclub

Visit the Zeaclub website