maritimemarketing . agency
Smart port with digital twin showing simulations future operations
Web Design 4 Dec 2025

Writing maritime service pages that pass procurement scrutiny

A service page that wins the technical sponsor still has to survive procurement. Here's what to put on the page so the deal doesn't stall at vendor review.

A service page on a maritime corporate website has to do two jobs at once. It has to convince the technical sponsor (a fleet director or superintendent) that you have the capability, sector experience and depth to be on their shortlist. And it has to convince procurement, finance and risk that you’re a credible vendor to actually contract with.

Most maritime service pages do the first job adequately and the second job badly. Capability statements are well written. The “buy from us” half is missing or hidden behind generic language. The deal stalls at vendor review for reasons the marketing team doesn’t see.

What procurement is actually looking for on a service page

Procurement scrutiny doesn’t mean a procurement officer reads your service page from top to bottom. It means that when the technical sponsor sends a shortlist of three vendors over for review, procurement opens each website and looks for specific signals. The signals that pass are signals that say “this vendor will be straightforward to onboard”.

Company scale and tenure. Years in business, number of staff, revenue order of magnitude (turnover bracket if you’re not publicly disclosed), office locations. A service page that mentions “our team” without ever indicating whether the company is 20 people or 500 fails this immediately.

Named, recognisable clients. Where charter parties, NDAs and consultancy contracts permit. Where they don’t, specific descriptors (“a top-five tanker operator”, “an FTSE 250 ports group”) still work. Generic “trusted by leading maritime companies” does not.

Standardised credentials. ISM, ISO 9001, ISO 14001, ISO 45001, MLC compliance. ISO 27001 and SOC 2 if you handle data. Insurance levels (PI, PL, EL with named values where commercially appropriate). Memberships (BIMCO, Intertanko, Intercargo, ICS, Intermanager). A list of these on the service page itself, not buried two pages deep.

Commercial engagement model. Are you a fixed-fee retainer, day rate, per-vessel pricing, project-based? What’s the typical commitment length? What’s the minimum engagement size? Procurement is comparing you against your competitors on these dimensions whether you state them or not. Stating them up front makes you easier to shortlist.

Onboarding and exit posture. Implementation timelines, transition from incumbent vendors, contract notice periods, data portability on exit. Often missing from service pages entirely. Adding even a paragraph signals professionalism.

What technical sponsors want on the same page

The capability case has to be specific to the maritime sector and to the buyer’s segment within it.

Sector specificity. Tankers, dry bulk, container, gas (LNG, LPG), offshore, specialised. A service page that talks about “vessels” generically signals that the vendor doesn’t know how different a VLCC is from a feeder containership. Name the vessel types you serve, the tonnage ranges, the ages of fleet you typically work with.

Regulatory currency. EEXI, CII, IMO 2020, MARPOL Annex VI, FuelEU Maritime, EU ETS, BWMS compliance, MLC, SOLAS amendments. A service page from 2019 reads as a service page from 2019. Reference current regulation in the language a fleet director would use.

Process specificity. Don’t tell me you “deliver excellence”. Tell me what your monthly reporting looks like. Tell me how you handle a vessel arrest, a port-state inspection, a fuel quality dispute, a crew incident. Process detail signals that you’ve actually done the work.

Named team. A photo and biography of the team lead for the service. Real name, real role, real LinkedIn link, real maritime experience. Anonymous “our experienced team” is anti-credibility in a sector that trades on personal trust.

Structure that serves both audiences

A service page that serves both audiences without forcing each to read content meant for the other:

  1. Hero with specific positioning. What service, for which buyers, with what scope.
  2. Capability detail by sub-segment. Tanker technical management, bulker technical management, container technical management as distinct sub-sections if you do all three.
  3. Approach and process. What it actually looks like to work with you, in clear steps.
  4. Team. Named individuals with real backgrounds.
  5. Case studies and references. With the same sub-segment alignment.
  6. Commercial and engagement model. Pricing posture, contract length, minimum scope, onboarding.
  7. Compliance and credentials. Certifications, memberships, insurance, regulatory posture.
  8. FAQ. The specific questions buyers actually ask, answered specifically.

A buyer can scroll, an evaluator can scan, a procurement officer can ctrl-F for “ISO 27001”. Each gets what they need without each having to read everything.

Send the page to a procurement contact

Send your top service page URL to a procurement contact at a current or former client and ask: “If you saw this page during a vendor review and didn’t know us, what would your three open questions be?” The answers are your gap list. Most service pages have five or six gaps. Closing them is high-value work that pays back across every campaign and every shortlist for years.

Frequently asked questions

How long should a maritime service page be?
1,200 to 2,500 words is the working range. Below 1,000 and you can't cover capability, scope, references and commercial posture with enough depth. Above 3,000 and procurement stops reading. Use clear sub-sections so each audience reads only what they need.
Should we list pricing on a service page?
Pricing posture, yes. Specific pricing, rarely. A range or engagement model (typical retainer scale, per-vessel pricing band, project minimum) sets expectations and qualifies. Hiding everything behind 'request a quote' loses procurement-led shortlists.
Should every service have its own page or share a parent page?
Each commercially distinct service gets its own page. A combined page that tries to cover technical management, crewing and commercial management at once will be too thin to satisfy any of the three audiences. Sub-segments within a service (tanker, bulker, container technical management) can sit as anchored sections on a single service page.
Share

Want help putting this into practice?

We work with maritime companies on exactly this kind of programme. Tell us about yours.