Raptors Delivery marketing site review and improvement recommendations

raptors-marketing-site-review.md

Raptors Delivery Marketing Site Review

Reviewed: https://delivery.runraptors.com/

Scope and verification

This review is based on direct browser inspection of the public marketing site in Arabic and English.

Verified interactions:

• The site rendered successfully after starting a clean browser session.
• Arabic RTL and English LTR locale switching worked immediately.
• Header navigation moved between the capabilities, workflow, pricing, and FAQ sections.
• Monthly, quarterly, and yearly pricing tabs were interactive.
• The yearly prices and 17% savings were displayed correctly.
• FAQ accordions expanded and exposed their answers.
• No CAPTCHA or browser verification challenge appeared.
• No JavaScript console errors were observed during the inspected flow.

Note: the browser screenshot tool produced vertically repeated hero content when stitching long captures. DOM and accessibility inspection showed that the actual page contains the expected sections once. The repetition should therefore be treated as a capture artifact, not a confirmed site defect.

Executive summary

The site has a strong foundation. Its positioning is specific, operational, and relevant to Egyptian delivery offices. The Arabic voice feels native, the RTL implementation is deliberate, pricing is transparent, and the custody and reconciliation story gives Raptors a meaningful point of differentiation.

The main weakness is a proof gap. The site makes strong product claims, but it does not provide enough visual product evidence or external trust evidence to support them. Visitors understand what Raptors promises before they can see how the product delivers that value or why they should trust it with orders, drivers, cash, and custody.

This does not require a full redesign. The highest-value improvements are stronger product proof, clearer audience definition, more explicit plan differentiation, and credible trust signals.

What should be preserved

1. Clear operational positioning

The Arabic hero statement is direct and useful:

شغّل الطلبات والسواقين والنقدية من مساحة واحدة واضحة.

It immediately identifies the three operational concerns the product unifies: orders, drivers, and cash. It avoids generic SaaS language and communicates a real workplace outcome.

Recommendation: preserve this direct, outcome-led positioning. Any revision should remain equally concrete.

2. Native Arabic voice and RTL execution

The Arabic copy sounds appropriate for the Egyptian target market rather than mechanically translated. The page structure, brand placement, CTA order, text direction, and navigation all behave appropriately in RTL. The English version also reads naturally and the layout switches to LTR correctly.

Recommendation: continue treating Arabic as a first-class product language. Keep future screenshots, testimonials, diagrams, and product previews properly localized rather than reusing English-only assets.

3. The instant demo as a conversion mechanism

An immediate demo with realistic data and no registration is a strong differentiator. It lets buyers evaluate a complex operational system without committing to onboarding first.

Recommendation: keep the live demo as the primary CTA and make its low-friction nature even more explicit.

Suggested Arabic CTA:

افتح ديمو فوري، من غير تسجيل

Suggested English CTA:

OPEN INSTANT DEMO

4. Custody and reconciliation as the central differentiator

The sections around custody, cash movement, double-entry accounting, audit history, zero reconciliation, and explained variance are the most distinctive part of the story. They separate Raptors from a basic dispatch or order-tracking application.

The message "Every pound accountable" is especially strong because it expresses an operational outcome rather than a technical feature.

Recommendation: preserve this story and support it with real product evidence. It should remain one of the site's central narrative pillars.

5. Transparent pricing and billing interaction

The monthly, quarterly, and yearly tabs are understandable and interactive. Yearly pricing displays the original amount, discounted total, monthly equivalent, and 17% savings. The pricing comparison makes the included capability groups easy to inspect.

Recommendation: retain the transparent prices and visible savings. Avoid forcing smaller offices to contact sales before they understand the likely cost.

6. Functional visual identity

The black, white, and Raptors Golden Yellow palette is distinctive and disciplined. Yellow is primarily used as a functional signal for the main CTA, selected state, or highlighted plan. The site avoids generic gradients, soft card clutter, and excessive decoration.

Recommendation: retain the Swiss-inspired clarity, typography, strong contrast, rectangular components, and restrained use of the accent color.

Problems and improvement opportunities

1. Insufficient product proof near the hero

Problem

The first viewport relies heavily on typography and copy. It explains the value proposition, but it does not immediately show the product performing the promised work.

A new visitor cannot see:

• what the operations workspace looks like;
• how an order moves through dispatch;
• how a driver is assigned;
• how custody and cash are represented;
• how reconciliation reaches zero;
• how exceptions or variances are explained.

This creates a gap between the strength of the claim and the amount of visible evidence.

Suggested improvement

Add a real, localized product composition beside or immediately below the hero. It should show a connected operational story rather than a decorative dashboard screenshot.

Recommended composition:

1. An order awaiting dispatch.
2. A driver assignment or status transition.
3. A custody period containing collections and purchases.
4. A final settlement with a zero variance.

Use actual UI, realistic synthetic data, and Arabic screenshots for the default Arabic locale. Avoid floating generic cards that do not resemble the application.

Acceptance criteria

• A visitor can identify orders, drivers, and cash in the first product visual.
• The visual is readable on desktop and has a deliberate mobile alternative.
• Arabic and English assets are both available.
• Sensitive production data is not used.
• The primary CTA remains visible without scrolling on common desktop sizes.

2. Limited external trust evidence

Problem

The page makes claims about handling operational cash, driver custody, immutable financial events, and reconciliation, but there is little visible external validation.

The inspected page did not present strong customer proof such as:

• named customer testimonials;
• delivery-office logos;
• case studies;
• verified operational metrics;
• implementation or support commitments;
• security and access-control reassurance.

This matters because financial custody requires more trust than a basic task-management product.

Suggested improvement

Add a compact trust section using only verifiable evidence. Possible components include:

• one strong quote from a real pilot customer;
• a short case study describing the previous workflow, the Raptors workflow, and a measurable result;
• accurate aggregate metrics such as orders processed, reconciliations completed, or offices onboarded;
• concise trust points covering role-based permissions, audit history, data ownership, backups, and onboarding support.

Do not invent metrics or use anonymous quotes that feel fabricated.

Acceptance criteria

• Every public claim can be verified internally.
• Testimonials include a real role and company when permission exists.
• Security and reliability statements link to supporting documentation where appropriate.
• The section remains concise and does not turn the site into an enterprise compliance brochure.

3. The ideal customer is implied rather than declared

Problem

The copy references offices, operators, managers, and drivers, but the intended buyer is not defined early enough. A visitor may still wonder whether Raptors is built for:

• independent delivery offices;
• last-mile logistics companies;
• retailers with internal couriers;
• restaurants;
• multi-branch chains;
• marketplaces.

Unclear audience definition can reduce conversion even when the feature set is relevant.

Suggested improvement

Add one explicit audience sentence near the hero or at the start of the capabilities section.

Suggested Arabic copy:

رابتورز معمول لمكاتب وشركات التوصيل في مصر اللي بتدير الطلبات والسواقين والعهدة اليومية.

Suggested English copy:

Built for Egyptian delivery offices and last-mile teams managing daily orders, drivers, custody, and settlement.

If the actual target includes retailers or chains operating their own fleets, state that separately rather than broadening the main line until it becomes vague.

4. The hero description is dense

Problem

The supporting sentence lists many functions in sequence. The breadth is useful, but the copy requires effort to parse and can feel like a compressed feature inventory.

Current themes include shopping, pickup, delivery, dispatch, driver custody, reconciliation, analytics, reports, and exports. Presenting all of them in one sentence weakens the hierarchy between the core value and secondary capabilities.

Suggested improvement

Shorten the supporting copy and move the capability inventory into three scan-friendly groups.

Suggested English hero copy:

Manage shopping and pickup orders, dispatch drivers, reconcile cash, and export operational reports from one workspace.

Suggested supporting groups:

• ORDERS: shopping, pickup, customer details, and status tracking.
• DRIVERS: dispatch, permitted transitions, and custody.
• CASH: collections, purchases, commissions, variance, and settlement.

This reinforces the hero's orders, drivers, and cash structure.

5. Demo and trial differentiation depends on small supporting text

Problem

The page provides two actions:

• a disposable one-hour live demo;
• a persistent seven-day trial for the visitor's own office data.

The difference is explained, but primarily through a small line beneath the CTAs. Some users may click without understanding which path matches their intent.

Suggested improvement

Make the distinction part of the CTA labels or add one short line directly associated with each action.

Suggested structure:

• Primary: OPEN INSTANT DEMO
  • Realistic data, no sign-up, available for one hour.
• Secondary: START 7-DAY FREE TRIAL
  • Create your office workspace and retain your data.

If accurate, explicitly state whether the trial requires a credit card.

6. The secondary CTA may be too visually weak

Problem

The trial action is visually subordinate to the yellow demo button, which is appropriate, but its text-link treatment may be overlooked or interpreted as supporting navigation.

Suggested improvement

Use a rectangular outlined secondary button with the same height as the primary button. Keep the background white and border black so it remains subordinate without losing discoverability.

On mobile, stack both actions full width and preserve a clear priority order.

7. Navigation feedback is understated

Problem

The header is clean, but navigation links are visually quiet. Users receive limited confirmation of the active section, and the hover or focus behavior is not prominent in a static inspection.

Suggested improvement

Add mechanical, high-contrast states consistent with the visual system:

• black underline or yellow block for the active section;
• clear keyboard focus outline;
• immediate color inversion or underline on hover;
• correct sticky-header offset for anchor destinations;
• optional URL hash updates so sections can be linked directly.

Avoid soft opacity-only interactions.

8. Pricing plans need clearer outcome-based differentiation

Problem

The plans are differentiated mainly by included capability groups. This makes the pricing technically understandable but leaves the buyer to infer which plan fits their operation.

The current descriptions such as "For smaller delivery offices" and "For complete operations" are useful but still broad.

Suggested improvement

Frame each plan around an operating stage and the result it enables.

Suggested positioning:

• STARTER: Run orders and dispatch for a small office.
• GROWTH: Run orders, cash custody, reconciliation, analytics, and the full team.
• ENTERPRISE: Coordinate multiple branches or chains with tailored controls and support.

Add meaningful limits or decision factors where they exist, such as offices, team members, drivers, order volume, exports, support, or onboarding. Do not display invented limits merely to create artificial differentiation.

9. The strongest promise is excluded from Starter

Problem

The page's most distinctive story is custody and reconciliation, but the Starter plan does not include finance. This can create a positioning and packaging disconnect:

1. The visitor is attracted by the promise that every pound is accountable.
2. The visitor reaches pricing.
3. The entry plan excludes the capability most associated with that promise.

This may be strategically correct, but the reason and upgrade threshold are not sufficiently clear.

Suggested improvement

Evaluate one of these approaches:

1. Keep finance in Growth, but make Starter explicitly a dispatch-only plan and explain that Growth is the complete Raptors operating system.
2. Include a limited finance experience in Starter, then reserve advanced custody periods, reconciliation controls, exports, or audit capabilities for Growth.
3. Make Growth the primary/default plan throughout the narrative and treat Starter as a deliberately reduced entry option.

This is a packaging decision, not only a copy change. It should be validated with actual buyer interviews and trial behavior.

10. The pricing comparison is too shallow to support a confident decision

Problem

The comparison currently focuses on four broad capability groups. Buyers may still have unanswered questions about important operational details, including:

• driver and team limits;
• number of offices or branches;
• order volume;
• role-based access;
• reporting and export limits;
• support and onboarding;
• retention and backups;
• API or integration access;
• custom configuration;
• whether taxes are included.

Suggested improvement

Add a more detailed comparison beneath the simple plan cards. Keep the cards concise, then let motivated buyers inspect the operational details in the table or an expandable comparison.

Include only differences that exist in the product and commercial model.

11. Missing product outcomes and measurable benefits

Problem

The site explains capabilities well but says less about the operational outcomes customers should expect. A buyer can understand what Raptors contains without knowing what should improve in the office.

Suggested improvement

Connect features to measurable operational pain:

• reduce end-of-day cash chasing;
• make driver handoffs traceable;
• explain shortages and overages;
• reduce spreadsheet reconciliation;
• identify unassigned or delayed orders quickly;
• preserve an audit history of cash events;
• close custody periods with clear variance ownership.

Use measured customer results when available. Until then, frame these as intended product outcomes rather than unsupported numeric claims.

12. The workflow section should use real product states

Problem

The four-step flow is logically structured, but a text-led workflow does not fully demonstrate how these steps connect inside the product.

Suggested improvement

Build the workflow around actual UI states:

1. CAPTURE: customer, store, items, fees, address, and instructions.
2. DISPATCH: workload, driver assignment, and allowed status transitions.
3. TRACK MONEY: purchases, collections, custody, and commission attached to operational events.
4. RECONCILE: close the custody period, explain variance, and inspect reports.

Each step should include a tightly cropped localized screenshot or short silent interaction. Use arrows or a visible grid to show continuity rather than four unrelated cards.

13. Trust messaging around the financial model could be more accessible

Problem

"Double-entry ledger," "immutable audit trail," and "operational ledger" are strong and accurate concepts for financially literate buyers, but some office operators may not immediately understand why they matter.

Suggested improvement

Keep the precise terminology and pair it with plain operational consequences.

Examples:

• Double-entry ledger: every movement has a balanced source and destination.
• Immutable audit trail: previous cash events remain visible instead of being silently overwritten.
• Reconcile to zero: every collected, spent, retained, or missing pound is classified.

This preserves credibility while improving comprehension.

14. More reassurance is needed around onboarding and switching

Problem

Adopting an operations platform has switching costs. The site does not prominently answer practical buying questions such as:

• How long does setup take?
• Can existing customers or orders be imported?
• Is onboarding included?
• Can the team start gradually?
• What support is available during the trial?
• What happens to data after cancellation?

Suggested improvement

Add a concise "Starting with Raptors" section or expand the FAQ with verified answers. Focus on reducing adoption anxiety rather than adding generic marketing copy.

15. Public search indexing is disabled

Observation

The reviewed HTML declares noindex,nofollow, and public indexing is disabled in the current configuration.

This may be intentional during pre-launch. If the site is intended to acquire public traffic, this prevents search engines from indexing it and following its links.

Suggested improvement

Before public launch:

• enable indexing in the production marketing configuration;
• verify robots.txt and the canonical URL;
• publish a sitemap if additional public routes exist;
• use a proper social-sharing image rather than only the application icon;
• verify Arabic and English metadata and locale alternates;
• run an external SEO crawl after deployment.

Do not enable indexing until the team is ready for the site to be publicly discoverable.

16. Social-sharing presentation can be stronger

Problem

The current Open Graph and Twitter metadata use the application icon as the social image. An icon provides less context and impact when the link is shared in WhatsApp, LinkedIn, X, or messaging applications.

Suggested improvement

Create dedicated 1200x630 social images in Arabic and English containing:

• Raptors Delivery branding;
• the orders, drivers, and cash value proposition;
• a restrained product UI preview;
• high-contrast typography suitable for small previews.

Verify the rendered previews using platform debugging tools before launch.

Recommended implementation priority

P0: Before a serious public launch

1. Add a localized product visual near the hero.
2. Define the ideal customer explicitly.
3. Clarify the distinction between the instant demo and the persistent trial.
4. Review the Starter versus Growth packaging around custody and reconciliation.
5. Enable search indexing only when launch-ready, then verify SEO metadata and crawling.

P1: High conversion impact

1. Add credible customer or pilot proof.
2. Rewrite plan differentiation around operational outcomes.
3. Expand the plan comparison with real decision factors.
4. Convert the workflow section into an evidence-led product story.
5. Add onboarding and migration reassurance.

P2: Refinement

1. Strengthen navigation active, hover, and keyboard-focus states.
2. Improve the secondary CTA treatment.
3. Simplify the dense hero supporting sentence.
4. Pair financial terminology with plain operational explanations.
5. Create dedicated Arabic and English social-sharing images.

Suggested revised page narrative

A stronger page could retain the current visual identity and follow this sequence:

1. HERO

   • Clear orders, drivers, and cash promise.
   • Explicit target customer.
   • Instant demo and persistent trial actions.
   • Connected product UI evidence.

2. TRUST

   • Real customer or pilot proof.
   • Verified operational metric or concise security and audit assurances.

3. COMPLETE OPERATIONAL FLOW

   • Capture order.
   • Dispatch driver.
   • Track custody and money.
   • Reconcile and report.
   • Each step supported by actual product UI.

4. FINANCIAL DIFFERENTIATOR

   • Every pound accountable.
   • Double-entry model explained in plain operational terms.
   • Zero settlement and variance evidence.

5. PERSONA OUTCOMES

   • Owner or manager.
   • Operator or dispatcher.
   • Driver.
   • Finance or reconciliation role.

6. PRICING

   • Plans positioned by operating stage.
   • Clear decision rules and relevant limits.
   • Transparent billing and savings.

7. ONBOARDING AND FAQ

   • Setup, imports, support, trial expiry, billing, and data retention.

8. FINAL CTA

   • Open the instant demo.
   • Start a seven-day office trial.

Final verdict

Raptors Delivery already has a stronger product story than most generic logistics SaaS landing pages. It is specific, locally relevant, visually disciplined, and anchored by a genuine operational differentiator: connected custody and reconciliation.

The next iteration should focus on evidence rather than decoration. Show the product performing the workflow, prove that real operators trust it, and make the commercial packaging easier to understand. Preserve the direct Arabic voice, the instant demo, the financial accountability narrative, the transparent pricing, and the restrained Swiss visual identity.