Appearance
Website Copy Deck — Sign-Off Draft
Source: Kaya Sync Website Optimisation — Next Iteration Execution Brief (Nenyi).
This document captures the approved copy for each page, the open decisions that must be made before build, and the forms/fields. Please review the open questions first — they block Sprint 2.
Decisions Locked
| # | Question | Decision |
|---|---|---|
| 1 | Lead destination | Per-segment email distribution lists via Resend. Lists configured per form (see Forms section). |
| 2 | WhatsApp number | +233242313385 (Ghana). Stored as a config value, single source of truth. |
| 3 | /investors gating | Request form + manual reply with NDA link. No auto-send of any materials. |
| 4 | Privacy / Terms | Initial drafts written by Claude; legal review required before public launch. |
| 5 | Lead-segment routing | Per-segment distribution lists (different recipients per form). |
| 6 | Country field | ECOWAS dropdown (Benin, Burkina Faso, Cape Verde, Côte d'Ivoire, Gambia, Ghana, Guinea, Guinea-Bissau, Liberia, Mali, Niger, Nigeria, Senegal, Sierra Leone, Togo) + free-text "Other" option for non-West-African leads. |
| 7 | Release structure | Multi-page from day one. Dedicated URL per audience for outreach, SEO and analytics. Built in Astro with shared layout/components so ~80% of each page is reusable shell. URL structure: /, /pilot-partners, /government, /settlement-partners, /operators, /execution-capability, /investors, /privacy, /terms. |
| 8 | Cookie / consent banner | Required. Build a minimal banner with accept/decline. Cloudflare Web Analytics is cookieless so only third-party scripts (if any) gate behind consent. |
Tagline & Master Positioning
| Element | Locked Copy |
|---|---|
| Fixed tagline | From Anywhere, to Everywhere |
| Master positioning | Kaya Sync turns fragmented informal logistics into a coordinated, auditable delivery network — from anywhere, to everywhere. |
| Institutional explanation | Kaya Sync coordinates existing transport operators across first-mile, mid-mile and last-mile routes, helping goods move through fragmented markets with video-verified custody, offline-ready workflows and settlement-ready evidence. |
| Settlement-safe sentence | Kaya Sync verifies delivery integrity; licensed partners move the money. |
Homepage
Build order: Hero → Problem → What Kaya Sync Does → Built for Field Reality → Who Should Talk to Us → Pilot Status → Market Relevance → Execution Capability → Trust & Compliance → Final CTA.
Hero
| Element | Copy |
|---|---|
| Headline | From Anywhere, to Everywhere. |
| Sub-headline | The trust and orchestration layer for informal logistics. |
| Body | Kaya Sync coordinates existing transport operators across first-mile, mid-mile and last-mile routes — helping goods move through fragmented markets with video-verified custody, offline-ready workflows and settlement-ready evidence. |
| Primary CTA | Partner on a Pilot |
| Secondary CTA | Request Controlled Briefing |
| Tertiary CTA | Join Operator Pilot List |
Problem
Heading: Informal logistics already moves the economy. It is just hard to see, trust and coordinate.
| Card | Copy |
|---|---|
| Fragmented movement | First-mile, mid-mile and last-mile operators work separately, often without shared visibility. |
| Weak custody evidence | Goods move through informal handoffs with limited proof of who handled what, when and where. |
| Limited institutional visibility | Enterprises and public institutions struggle to understand route behaviour, operator reliability, delivery integrity and corridor demand. |
What Kaya Sync Does
Heading: One coordination layer across existing operators.
| Card | Copy |
|---|---|
| Coordinate | Link existing operators across first-mile, mid-mile and last-mile movement. |
| Verify | Capture evidence at origin, handoff and delivery. |
| Confirm payout eligibility | Validate custody events and create payout instructions for licensed settlement partners. |
| Build network intelligence | Convert fragmented movement into corridor, operator and reliability data. |
Do not expose: detailed aggregation logic, AI scoring, trust-tier logic, fraud thresholds, settlement-gating rules or optimisation rules.
Built for Field Reality
Heading: Built for low-literacy, low-connectivity logistics environments.
Body: Kaya Sync is designed for real market conditions: intermittent connectivity, low-end Android devices, noisy loading points, visual workflows, voice-led guidance, market-day congestion and operators who should not need to read long instructions to complete a job.
Bullet list (short, icon-led):
- Voice-first, visual-second workflows
- Guided video evidence capture
- Offline capture with later synchronisation
- Phone-number cargo anchoring
- Market facilitator support
- Simple operator status prompts
- Server-side validation before payout eligibility
Who Should Talk to Us
Heading: Built for the parties who need trust across fragmented movement.
| Audience | Copy | CTA |
|---|---|---|
| Enterprise & agribusiness partners | Reduce delivery disputes, improve corridor visibility and coordinate informal transport capacity without owning fleet assets. | Discuss Enterprise Pilot |
| Government & regulators | Support formalisation, auditability and better data on informal economic movement — aligned with jobs, productivity, revenue discipline, institutional trust and inclusive growth. | Request GovTech Brief |
| Settlement & infrastructure partners | Kaya Sync verifies logistics integrity. Licensed partners execute money movement. | Partner on Verified Settlement |
| Investors & funders | A controlled pre-MVP opportunity to back the trust, evidence and orchestration layer for fragmented logistics markets. | Request Investor Pack |
| Operators & market facilitators | Join the pilot list. Get verified for pilot work. Record handoffs simply. Build a reliability record. | Join Operator Pilot List |
Pilot Status
Heading (replaces "Coming Soon"): Preparing controlled pilot deployment in Ghana.
Body: Kaya Sync is moving from prototype into MVP readiness. The next phase is controlled field validation: custody evidence, operator activation, corridor density, settlement eligibility and enterprise visibility.
Visual progression: Prototype → MVP Readiness → Controlled Pilot → Proof Metrics → Partner Scale-up
Market Relevance
Heading: Designed in Ghana. Built for structurally similar markets.
Body: Kaya Sync starts from Ghana's informal logistics reality, but the same operating pattern exists across many fragmented markets: high transport density, low coordination, informal handoffs, weak delivery evidence and limited institutional visibility.
Optional line: Relevant market patterns exist across West Africa, East Africa, North Africa, South Asia, Southeast Asia and Latin America.
Execution Capability
Heading: Built for controlled execution in difficult logistics environments.
Body: Kaya Sync is Ghana-led and supported by a controlled execution network across platform architecture, field operations, legal and regulatory structuring, finance discipline, behavioural design and programme delivery.
The platform is being built for environments where field users may have limited literacy, connectivity may be intermittent, cargo is physically identified by phone number, and trust must be enforced through evidence rather than assumptions.
| Capability | Copy |
|---|---|
| Platform architecture | Event-driven logistics infrastructure designed to coordinate fragmented first-mile, mid-mile and last-mile movement without owning vehicles or warehouses. |
| Field execution | Workflows shaped for real market conditions: intermittent connectivity, low-end Android devices, noisy loading points, market-day congestion, visual prompts, voice-led guidance and assisted onboarding. |
| Legal and regulatory structuring | A compliance-aware model that separates logistics verification from regulated money movement, with licensed settlement partners responsible for payment execution. |
| Finance and control | Disciplined operating controls for pilot execution, partner reporting, cost tracking and funder-facing accountability. |
| Behavioural adoption | Operator and facilitator workflows designed around trust, habit formation, low literacy, local authority structures and practical earning incentives. |
| Public-sector readiness | Structured evidence, audit trails and market-level visibility that can support formalisation, planning, accountability and inclusive growth. |
Disclosure line: Detailed team information is shared only during controlled partner, funder or investor briefings.
Do not add: public "Meet the Team" carousel, named profiles, CV downloads, LinkedIn links, personal photos or personal contact details.
Trust & Compliance Posture
Heading: Built for trust, evidence and controlled growth.
Body: Kaya Sync is designed to support auditable logistics records, partner-executed settlement, operator verification and controlled access to sensitive materials. The platform verifies custody events and payout eligibility; licensed settlement partners execute regulated money movement.
Bullet list:
- Asset-light orchestration
- Evidence-led custody
- Partner-executed settlement
- Controlled disclosure
- Privacy-aware lead handling
- Low-literacy field design
- Offline-ready operation
Avoid "fully compliant with all regulations" unless legal has approved that exact claim. Use "designed to support" and "compliance-aware".
Sub-Pages
Enterprise Pilot Partners (/pilot-partners)
Lead with: Reduce delivery disputes, improve corridor visibility, coordinate informal transport without owning fleet assets.
Form: Enterprise Pilot (see Forms section).
Government & GovTech (/government)
Frame as: formalisation, simplified participation, informal-sector visibility, mobile-first/low-tech environments, low-literacy participation, market logistics data, public trust, fiscal discipline, value for money, inclusive growth, improved service delivery.
Do not present Kaya Sync as a tax enforcement tool. Present it as an infrastructure, evidence and formalisation-support layer.
Form: Government / GovTech (see Forms section).
Settlement & Infrastructure Partners (/settlement-partners)
Lead with the settlement-safe sentence: Kaya Sync verifies delivery integrity; licensed partners move the money.
Form: Settlement Partner (see Forms section).
Operators (/operators)
Operator-facing language must be plain. No institutional jargon.
Section line: Do the job. Record the handoff. Deliver well. Kaya confirms. Partner pays.
Form copy (above form): Want pilot work? Leave your name, town and phone number. We will call or WhatsApp selected operators.
Form: Operator Pilot (see Forms section).
Execution Capability (/execution-capability)
Already covered in homepage section above — repeat content on dedicated page.
Investors & Funders (/investors) — Gated
Thank-you message: Thank you. Investor and funder materials are shared after internal review and, where appropriate, NDA clearance.
Do not auto-send: pitch deck, investor memo, SAFE terms, valuation cap, financial model, pilot corridor strategy, detailed architecture, technical roadmap, team annex, CVs.
Form: Investor / Funder Request (see Forms section).
Lead Routing Configuration
Stored as config so recipients can be updated without code changes. Lists are per-segment (even when recipients currently overlap) so they can diverge later.
| Segment | Notification Recipients |
|---|---|
| Pilot Partners | cto@kayasync.com, kobby.andah@kayasync.com |
| Government | cto@kayasync.com, kobby.andah@kayasync.com |
| Settlement Partners | cto@kayasync.com, kobby.andah@kayasync.com |
| Investors | cto@kayasync.com, kobby.andah@kayasync.com |
| Operators | cto@kayasync.com, kobby.andah@kayasync.com |
Public Contact Configuration
| Key | Value |
|---|---|
whatsapp.public | +233242313385 |
email.privacy | cto@kayasync.com |
email.legal | cto@kayasync.com |
email.general | cto@kayasync.com |
email.sender (from address for transactional/form notifications) | forms@mailer.kayasync.com |
Forms
Every form captures the standard fields (in addition to segment-specific fields below):
lead_segment, name, organisation, role, email, phone_or_whatsapp, country, city_or_town, interest_area, message, utm_source, utm_medium, utm_campaign, utm_content, utm_term, landing_page, referrer, timestamp, consent_version
Do NOT collect: Ghana Card numbers, biometrics, bank details, payment details, cargo receiver phone numbers, live cargo data, CVs, identity documents, internal team docs.
Enterprise Pilot
- Organisation name
- Contact person
- Role/title
- WhatsApp/phone
- Sector: Agribusiness / FMCG / Processor / Commodity buyer / 3PL / Marketplace / Other
- Main movement problem: Delivery disputes / Limited visibility / Informal operator coordination / Market-to-town fulfilment / First-mile aggregation / Last-mile reliability / Other
- Main corridors/towns
- Approximate monthly shipment volume: Under 100 / 100–500 / 500–2,000 / 2,000+ / Not sure
- Preferred next step: Pilot discussion / Technical demo / Commercial discussion / Field assessment
Notification subject: [Kaya Sync][Enterprise Pilot] — —
Government / GovTech
- Institution
- Department/unit
- Contact person
- Official email
- Phone
- Area of interest: Informal-sector formalisation / Operator registration / Licensing support / Tax registration support / Market logistics data / Audit trail and compliance / District planning / Pilot briefing
- Preferred engagement: Briefing note / Demo discussion / Technical meeting / Policy alignment session
Notification subject: [Kaya Sync][GovTech] —
Settlement / Infrastructure Partner
- Institution name
- Institution type: PSP / MNO / DEMI / Bank / Telco / Device partner / Cloud or infrastructure partner / Identity or KYC partner / Other
- Regulated status (if applicable)
- Partnership interest: Payout instruction integration / Mobile money settlement / Bank payout integration / Device financing / Telecom or data support / Cloud or security support / Identity or KYC support
- Technical contact
- Commercial contact
- Phone
Notification subject: [Kaya Sync][Settlement/Infrastructure] —
Investor / Funder Request
- Name
- Organisation
- Investor/funder type: Angel / Family office / Venture fund / Catalytic funder / Grant/challenge fund / Strategic corporate / Development finance-linked partner
- Phone
- Area of interest: Investor pack / Controlled demo / Funding conversation / Strategic partnership
- Checkbox: I understand that detailed materials may require approval and, where appropriate, NDA clearance.
Notification subject: [Kaya Sync][Investor/Funder Request] —
Operator Pilot
- Name
- Phone / WhatsApp
- Town
- Vehicle or role: Tricycle / Motorbike / Taxi / Pickup / Small truck / Loading or market facilitator / Station coordinator / Other
- Main route
- Can you use WhatsApp? Yes / No
- Do you want pilot work? Yes / No
Notification subject: [Kaya Sync][Operator Pilot] —
Wording Guardrails
Approved
From Anywhere, to Everywhere · trust and orchestration layer · informal logistics · fragmented logistics markets · video-verified custody · evidence-led movement · settlement-ready evidence · verified payout eligibility · payout instruction · licensed settlement partner · offline-ready workflows · low-literacy design · phone-number cargo anchor · market facilitator · controlled pilot · MVP readiness · asset-light orchestration · network intelligence
Forbidden in Public Copy
automated settlement · automated payout · AI-gated settlement · Kaya wallet · Kaya balance · Kaya escrow · Kaya pays operators · Kaya releases funds · Kaya processes payments · instant settlement · guaranteed payout · payment processor · merchant aggregator · trust-tier algorithm · fraud scoring thresholds · aggregation scoring · settlement-gating logic · carbon scoring formula · full architecture · launched across Africa · operating globally
Direct Copy Replacements (current site → new site)
| Current | Replace with |
|---|---|
| Coming Soon | Preparing controlled pilot deployment |
| Logistics that moves with you | From Anywhere, to Everywhere |
| Real-time, AI-driven chain-of-custody for informal transport operators | The trust and orchestration layer for informal logistics |
| Video-verified handoffs, automated settlement, and resilience built for low-connectivity environments | Video-verified custody, offline-ready workflows and settlement-ready evidence for fragmented logistics markets |
| AI-Gated Settlement | Verified Payout Eligibility |
| Automated payouts triggered by verified delivery milestones | Validated custody events create payout instructions for licensed settlement partners |
| Low-Connectivity First | Offline-Ready Field Workflows |
| USSD/SMS fallback and offline scanning for any environment | Capture evidence in low-connectivity market conditions, synchronise later and validate before payout eligibility is confirmed |
| Dynamic Load Aggregation | Smarter Coordination of Existing Transport Capacity |
| Real-time aggregation while operators are in motion | Coordinate informal operators across routes, handoffs and delivery legs without owning fleets, depots or warehouses |
| Get Early Access | Partner on a Pilot |
| Be first to know when we launch — and help shape the product | Tell us which pilot, partnership or briefing you want |
SEO Metadata
| Page | Title | Meta Description |
|---|---|---|
| Home | Kaya Sync | From Anywhere, to Everywhere | Kaya Sync is the trust and orchestration layer for informal logistics, coordinating existing operators with video-verified custody, offline-ready workflows and settlement-ready evidence. |
| Pilot Partners | Enterprise Pilot Partners | Kaya Sync | — to draft — |
| Government | Government & GovTech | Kaya Sync | — to draft — |
| Settlement Partners | Settlement Partners | Kaya Sync | — to draft — |
| Operators | Operator Pilot List | Kaya Sync | — to draft — |
| Investors | Investor & Funder Request | Kaya Sync | — to draft — |
| Execution | Execution Capability | Kaya Sync | — to draft — |
Keywords: informal logistics Ghana · verified delivery Ghana · logistics orchestration Africa · chain of custody logistics · agribusiness logistics Ghana · informal transport operators · low connectivity logistics · GovTech informal sector · settlement-ready logistics evidence · logistics trust layer
Sign-Off Checklist (Pre-Sprint-2)
Before any code is written for the rebuild, confirm:
- [ ] All eight Open Questions above have answers
- [ ] Nenyi signs off on this copy deck as accurate to the brief
- [ ] Legal signs off on the settlement wording rules and forbidden-terms list
- [ ] Evanson signs off on form lead routing and notification destinations
- [ ] Privacy policy and Terms of Service drafted (or stubbed with a clear "draft" notice)
- [ ] WhatsApp number provided
- [ ] Investor route gating mechanism chosen
- [ ] Decision on single-page vs multi-page first release