D&B Directory Checklist

Need to do

• Confirm the exact D&B product or directory access needed for the business.

• Identify who will own the D&B account setup and billing.

• Gather the business details likely needed for setup, such as legal company name, address, contact information, and website.

• Decide what the directory will be used for first, such as company lookup, vendor verification, credit review, or data integration planning.

• Save the correct public D&B pages for later review: D&B Business Directory and D&B Credibility Directory.dnb+1

• Make a note to check whether the business already has a D-U-N-S-related record or public listing once access is available.dandb+1

Need to wait on

• Wait until the D&B listing, account, or access is live before trying to search or manage the business entry.

• Wait for any D&B verification, onboarding, or profile publication steps to finish before making final updates.

• Wait to confirm what data fields and editing options are available inside the actual D&B workflow, since the public directory pages only indicate searchable business records and profile access at a high level.dnb+1

• Wait to decide on any YachtWave integration work until the exact D&B product, permissions, and data access level are confirmed.dnb

For the checklist, here is a concise, full‑scope set of bullets you can print and literally tick line‑by‑line. Then I’ll address the JEMSMarine domain.

Business identity & strategy

• Define the exact business name spelling and capitalization you want to lock in (JEMS Marine vs JEMSMarine, etc).

• Decide the core positioning in one sentence (what JEMSMarine is and who it serves).

• List primary services and offerings in 3–5 short bullets.

• Decide on primary geography/market (local, US‑wide, global, specific regions).

• Decide if JEMSMarine is a brand under YachtWave or a standalone entity.

Legal, tax, and compliance

• Confirm legal entity status is set or planned (LLC, corp, DBA, etc).

• Confirm business registration and any marine‑specific licensing requirements for your jurisdiction.

• Decide who is responsible for ongoing compliance (annual filings, licenses, etc).

• Verify you are clear to use the JEMSMarine brand in your jurisdiction (no obvious conflicts).

D&B / data and credit profile

• Decide whether you want a D&B profile for JEMSMarine at all (credit, vendor trust, etc).dnb+1

• Gather legal name, address, phone, website, and key contacts in one place for any D&B or similar registrations.dandb+1

• Confirm whether a D-U-N-S or existing D&B record already exists before creating anything new (search later when access is ready).dnb+1

• Decide who will own the D&B account login, billing, and future updates.

• Note that detailed setup and editing steps must wait until you have actual D&B product access.dandb+1

Domains, email, and branding

• Decide primary domain naming (jemsmarine.com vs variants like jemsmarine.co, .net, etc).

• Use a domain search/WHOIS tool (e.g., Instant Domain Search, nic.com, registrar of choice) to check availability of jemsmarine.com and close variations.instantdomainsearch+1

• If jemsmarine.com is taken (it currently resolves to an existing Singapore marine company site), decide whether you will: pick a different TLD, modify the name, or try to acquire the existing domain.jemsmarine+1

• Register the chosen domain(s) under your preferred registrar once you decide.

• Decide on email pattern (info@, support@, first@, etc) for the business.

Website & content

• Choose initial website scope: basic brochure, services list, contact form, or more advanced (booking, quotes, dashboards).

• Draft a simple sitemap: Home, About, Services, Contact, plus any must‑have pages.

• Write short copy blocks for each page (headlines + 2–3 lines per section).

• Collect any existing photos, logos, or branding assets you want on day 1.

• Decide whether the first version will be static marketing site, or if you want any direct integration with YachtWave (even if later).

Operations & customer workflow

• Define exactly what you want users to do on the site (call, email, form, schedule, sign up, request quote).

• Decide who receives inbound leads (email routing, phone routing, notifications).

• Define a simple lead handling flow: new inquiry → response time target → next step.

• Decide what data you want to capture from leads (name, boat info, port, budget, etc).

Integration & future data plans

• List any external systems you might later integrate with (YachtWave, D&B data, CRM, payment processor).

• Decide whether any data from JEMSMarine needs to flow into YachtWave now, or only in future versions.

• Note any dependencies that must wait (D&B product choice, APIs, legal approvals) before you design technical integrations.dnb+1

Practical “wait on this” items

• Wait on any D&B profile setup/editing flows until you’ve selected a specific D&B product and have account access.dandb+1

• Wait on technical integration work with D&B until product, API, and permissions are defined.dnb

• Wait on any branding that hard‑locks the exact domain spelling until you finalize the domain strategy.

• Wait on advanced website features (logins, dashboards, embedded YachtWave functionality) until the basic marketing site and messaging feel right.

JEMSMarine website / domain availability

• The domain jemsmarine.com is currently active and in use by “JEMS MARINE PTE LTD,” a marine and offshore support company based in Singapore, with a live website at that address.jemsmarine+1

• Because the .com is taken and associated with an existing marine business, securing exactly jemsmarine.com would require either buying it from the current owner or choosing a different extension or variant (e.g., jemsmarine.co, jemsmarine.us, jems-marine.com), which you can check in real time with any domain search/WHOIS tool (e.g., Instant Domain Search, nic.com).nic+1

For the domain, do you prefer to pursue the exact .com from the current owner if possible, or would you rather pick a clean, available variant (e.g., different TLD or slightly adjusted name) and move fast?

Done — I created the minimal jems-marine.com holding page using theONE-style palette, with “Site in progress”, the JEMS Marine, LLC name, a tie-in to theONE Vessel Command Center, and the official tagline you’ve already established for the brand.

The page is styled in the dark Tide-family direction with the same teal/cyan accent logic already used in the app and marketing materials, which keeps the legal/company page visually aligned with theONE without turning it into the full product marketing site.Memory+1

Interesting — "No projects found" in Workers & Pages. So theonevcc landings weren't deployed via Pages here. I see a new tab opened titled "jems-marine-coming-soon" — that's where the system staged a project for me.

Important decision point: To deploy a Cloudflare Pages site, we need a Git source (GitHub/GitLab) or to upload assets via Direct Upload / Wrangler CLI. I can't actually create a GitHub repo or upload files end-to-end inside this Cloudflare UI without:

• You connecting your GitHub account to Cloudflare Pages, OR

• Running Wrangler CLI from your Mac, OR

• Using the "Direct Upload" path and you dragging in a ZIP of the HTML.

Given that theonevcc has no Pages project either, I suspect those landings might be hosted elsewhere or just via Cloudflare redirect rules.

To keep momentum without blocking on me

I recommend we do a fast 2-step now:

1. Today: Set SSL/TLS to Full and Always Use HTTPS (I can do this).

2. Coming Soon page: I'll prepare the HTML file. You either (a) drag-drop it into a new Pages project via Direct Upload, or (b) tell me how theonevcc landings are deployed so I can mirror exactly.

Question for you (one line): How did you deploy theonevcc.com / .io / .app landing pages? GitHub→Pages, Direct Upload, Worker, or external host? Once I know, I'll mirror jems-marine.com the same way.

Meanwhile, want me to proceed with SSL/TLS Full (strict) + Always Use HTTPS now for jems-marine.com?

This is where I hit a real limit: I cannot drag files from your Mac into Cloudflare — that requires you to physically drop or click-upload the HTML file from your local machine. I also can't access your filesystem.

So you have two clean paths. Tell me which:

Option A — You upload (fastest, ~2 minutes)

I'll give you the HTML file contents below. You:

1. Save it as index.html on your Mac.

2. Drag it into this upload box.

3. Click Deploy.

Here is the file — copy everything between the lines into index.html:

xml
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8" />
<meta name="viewport" content="width=device-width,initial-scale=1" />
<title>JEMS Marine — Coming Soon</title>
<meta name="description" content="JEMS Marine — Marine services. Launching soon." />
<style>
  :root { --bg:#0b1e2d; --ink:#eaf2f8; --accent:#7fb3d5; }
  *{box-sizing:border-box} html,body{margin:0;height:100%}
  body{font-family:-apple-system,BlinkMacSystemFont,"Segoe UI",Inter,Helvetica,Arial,sans-serif;
       background:radial-gradient(1200px 600px at 50% -10%,#13344c 0%,var(--bg) 60%);
       color:var(--ink);display:grid;place-items:center;padding:32px}
  .card{max-width:680px;text-align:center}
  h1{font-size:clamp(36px,6vw,64px);margin:0 0 12px;letter-spacing:.5px}
  p{font-size:18px;line-height:1.55;opacity:.9;margin:0 0 24px}
  a.btn{display:inline-block;padding:12px 20px;border-radius:999px;
        background:var(--accent);color:#0b1e2d;text-decoration:none;font-weight:600}
  .meta{margin-top:28px;font-size:14px;opacity:.75}
</style>
</head>
<body>
  <main class="card">
    <h1>JEMS Marine</h1>
    <p>Something new is launching soon. For inquiries, get in touch.</p>
    <a class="btn" href="mailto:info@jems-marine.com">info@jems-marine.com</a>
    <div class="meta">© JEMS Marine, LLC</div>
  </main>
</body>
</html>

Option B — Use GitHub

Connect GitHub and I can walk you through committing a repo we can wire to Pages.

What I'll handle automatically after your upload

Once the project is deployed (you'll see jems-marine-coming-soon.pages.dev or similar), I will:

1. Add the custom domain jems-marine.com (root) and www.jems-marine.com to the Pages project.

2. Verify DNS records were created automatically.

3. Go to SSL/TLS and set Full (strict) + enable Always Use HTTPS.

4. Confirm the site resolves over HTTPS.

Drop the file in the upload box and click Deploy — then say "done" and I'll take it from there.