A platform built around 21 years of real marine logistics expertise — plus the online bookings, payments and reporting the phone-and-email process can't give you.
The operation is real and specific. The website is a 2010s site-builder template with no way to book or pay.
Twenty-one years meeting ships at the gangway in Durban and Richards Bay, twenty-two named daily-trip routes, a tracked and insured fleet, and a tour offering built around Zulu village visits, game drives and the Durban city bus — that's a genuinely credible, specific operation. None of it is easy to find on the current site: the entire services list is a flattened image, the FAQ page has no FAQs, the Documents page is empty, and the header phone number is missing a digit on every page.
More importantly: bookings and payments — the two things your own About page says are “essential” — still happen entirely by phone and email. This proposal is about building the platform around your real routes and fleet, with booking and payment built in from day one.
Checked live on 21 September 2026 against the public site at vipmarine.co.za. Every item below is verifiable, not an impression.
The About page states bookings need “minimum one hour in advance for daily tours, and at least one day prior for special tours” — but the only booking method anywhere on the site is a phone call or an email. No form, no calendar, no confirmation.
There is no payment gateway, invoicing link or deposit flow anywhere on the site. Every transaction happens off-platform, which also means there's no automatic record of what's been paid.
The Services page's only content is Core.jpg, a 538×761px print-flyer graphic. Google can't read a single word of it, it needs pinch-zooming on mobile, it's invisible to screen readers, and it displays an even older phone number and a different address format than your own Contact page.
The number shown site-wide reads +27 31 205 001. Your real number, confirmed on the Contact page, is 031 205 0017. It's the single most visible piece of contact information on the site, and it's wrong.
Every script and stylesheet loads from a platform called Kwikwap (kwikweb.co.za) — including jQuery 1.11.0 (2014, unpatched for over a decade, loaded four separate times on one page), Bootstrap 4.1.0, and an abandoned parallax library last updated around 2016. The About page even pulls decorative template graphics from other unrelated clients' folders on the same platform (justjuniors, atties) — VIP Marine has no distinct, owned design.
The homepage loads a dead advertising.jpg link, and the Gallery page's only photo — captioned “Durban City Tours” — fails to load and shows a broken-image icon.
It's a blank “ask a question” form with no answers published anywhere — despite the site clearly having real, repeatable questions (port documents required, booking notice periods, group size limits).
“Nothing added yet, please check back later!” — presumably meant for the crew-list and passport-stamp templates the About page says every booking requires.
No way to publish a seasonal tour special, a schedule change over the festive season, or a port advisory — content that would also be indexable, unlike the flattened services page.
The description tag reads “...Marine Services amp; Tours...” — a literal unescaped HTML entity, visible in Google search results. There's also no Open Graph image, so a link shared on WhatsApp or Facebook shows no preview at all.
The Contact page lists “28 Rick Turner Road”; the Services flyer image lists “28 Francios Rd (Rick Turner)”. Same building, two spellings.
The big background image is a generic open-vehicle safari photo. VIP Marine's core business — and its 21 years of expertise — is professional crew transport: sedans and minivans, gangway pickups, customs and immigration. The tour side is real, but it's the smaller half of the business.
A platform built around the routes and fleet VIP Marine already runs — with booking and payment as first-class features, not an afterthought.
The demo at the bottom of this page is that homepage, built live with your real logo, your real services, your real review and your real contact details — plus a working preview of the booking flow and dashboard concept.
A route/date/passenger booking flow that mirrors the notice-period rules already stated on your About page — replacing the phone-and-email process without removing it; WhatsApp and calls stay available for anyone who prefers them.
Card and Instant EFT via a South African payment gateway (PayFast, Yoco and Peach Payments are the usual fit for a business your size — happy to work with whichever you already hold a merchant account with, or help set one up).
One screen for your team showing bookings, payment status and route performance — instead of five separate inboxes (info@, accounts@, ops@, rbay@, vipmarine@telkomsa.net) and a diary. Open the back-office demo → — it is clickable, and every record in it is dummy data.
Estimated in working days for the recommended option.
| Work | Days |
|---|---|
| Discovery, content audit, route & service taxonomy | 2.0 |
| Design system and homepage (per the demo) | 5.0 |
| About, Services (grouped), Tours, FAQs and Documents | 3.0 |
| Blog / news / specials — listing page, post template, publishing tool | 2.5 |
| Booking flow — route/date/passenger selection, availability rules | 4.5 |
| Payment gateway integration (card + Instant EFT) | 3.5 |
| Admin dashboard — bookings, payment status, reports | 4.0 |
| Contact, WhatsApp integration | 1.0 |
| SEO layer: metadata, OG tags, sitemap, robots, favicon | 1.5 |
| QA, mobile, performance, launch and handover | 2.0 |
| Total | 29.0 days |
| Care plan — hosting, backups, security updates, up to 2 hours of support a month | R2 000 / month |
| Content partner — 2 blog/specials posts a month, written and published from your notes and photos | R1 500 / month |
Content partner is optional and only makes sense once the blog exists — happy to start it a month or two after launch rather than day one.
| Week | What happens |
|---|---|
| Week 1 | Discovery, route/content audit, design system signed off |
| Week 2 | Homepage, services, tours and about built and reviewed |
| Week 3 | Booking flow, blog structure, FAQs, documents, contact |
| Week 4 | Payment gateway integration, admin dashboard |
| Week 5 | QA, mobile pass, SEO layer, launch and handover |
Assumes your payment gateway preference and merchant account details arrive during week 1 — that's normally the thing that determines whether week 4 slips.
Two of them. A working homepage concept, built with your real logo, your real services, your real review and your real contact details — and a clickable back office showing the bookings, payments, tariffs, content and reports side, filled with dummy data.