marcura.com
success
Claude Code
intent

What does marcura.com do and who is it for? Explain it back to me.

17steps
71.0sduration
$0.9324cost
189,939tokens
20 steps3 reasoning steps6 searches
home
docs
/solutions
docs
/products
/features
docs
search
/manage-port-calls
/procure-supplies
search
search
/pay-crew
search
/compliance
search
search
73%
on-site discovery
73%
reliability
18%
link following
path origin
  • previous resource18%
  • web search27%
  • prior knowledge55%
insight

The agent successfully assembled a comprehensive explanation of Marcura's business, products, target customers, and competitive positioning by combining website content (homepage, product pages, about) with web search results that filled gaps left by incomplete site documentation. However, the task was only partially satisfied because pricing information—a core requirement—was completely absent from the website; the agent had to acknowledge this gap rather than deliver it. The site's navigation was straightforward but thin on detail; the agent relied heavily on prior knowledge and search to contextualize what the site presented.

  • ›The homepage ([1]) and About page ([2]) provided high-level context (950+ customers, $21.6B payments, 200k port calls, 53 countries) but lacked granular business model and competitive positioning details that the agent only found via web search ([9], [10], [13], [15], [16], [17]).
  • ›Product/brand pages ([5], [11], [12], [14], [18]) each described one offering in isolation—DA-Desk, ShipServ, MarTrust, compliance—but the site did not expose integration, bundling logic, or how these products work together as a platform; the agent inferred this from the /products page description and search results.
  • ›No pricing page exists; the agent attempted /pricing ([3]) and got a 404. The site offers no SaaS pricing tiers, per-user costs, or licensing information, forcing the agent to flag this as a major gap and rely on search for business model hints (MCaaS Services reference in [17]).
  • ›Web search results ([9], [10], [13], [15], [16], [17]) were content-bearing and explicitly cited: they provided acquisition history (Marlin Equity, ShipServ, VesselMan), competitor names (Signal Group, Pole Star, Veson Nautical), and business model context (MCaaS, service-as-software hybrid) that the site itself did not surface.
  • ›The site's structure (direct product URLs guessed correctly, but failed on /solutions, /features, /pricing) suggests incomplete IA; the agent had to probe multiple URLs before finding the /products brand index, indicating weak discoverability of the portfolio.
  • ›Meta descriptions and page titles were present and descriptive but not comprehensive enough to eliminate the need for search; the site relies on direct navigation rather than searchable content or structured data to communicate differentiation.

Help the next agent finish on marcura.com

Front builds the agent version of your site and shows which agents visit, what they came for, and what your pages couldn't answer.

or talk to us about agent readiness →