
We built the Essack Enterprise site — the holding company Riyp sits inside. Same brand family, same standard of craft, same team.
So this proposal skips the introductions. We already understand the group, the portfolio and the way you present it. What follows is what we found when we turned that same attention to Riyp.
Four-page corporate site covering the enterprise, the founder and the full portfolio — Riyp, NUKE, Xpresso, PostNet and Tamr.
Essack Enterprise needed to be presented. Riyp needs to be run — it has buyers, seasons, enquiries and shipments. That needs software, not a brochure.
Everything in this proposal follows from that single sentence.
A produce importer in Dubai or Kinshasa moves through six steps before money changes hands. The current site helps with two of them.
Searches "South African citrus exporter" or asks a trade contact.
Is this a real exporter? Certifications, memberships, press, history.
Is what I want available, and in which weeks?
Currently one static page and a "View Citrus" link.Which variety, which counts, which pack, which carton?
Currently a paragraph of prose per category.Send volume, destination port, incoterm, target window.
Currently a short form that becomes an email.Come back next season, track the shipment, pull the documents.
Currently nothing at all.A rebuilt riyp.co that answers the season question and the spec question before a buyer has to ask — and turns the enquiry into a structured request for quote instead of an email.
A CRM where every enquiry becomes a tracked record, a quote builder that issues branded proformas, a CMS you control, and a buyer list you can broadcast seasonal availability to.
Demand by country and by produce, conversion and time-to-quote, win/loss by market, and content attribution — so next season is planned on evidence instead of instinct.
They are the real thing, running live inside this deck. Click them, filter them, fill them in. This is what we would ship.
Their own brand, their own photography — rebuilt around the black export carton rather than stock fruit. The chip on the hero image is live: it reads the current week and names what is shipping right now.
49 varieties across the 52-week year. Filter by category, month or brand; click any bar for counts and pack specs. If a window has not opened, it captures the buyer's email and tells them the week it does — that is a lead with intent.
Produce, variety, volume, frequency, pack, destination port, incoterm, freight mode, window. The panel on the right builds the record as they type. What arrives is a qualified brief you can price — not "please send price list".
Turn a lead into a branded proforma PDF, sent and tracked from the platform. You see when it is opened.
Harvests posts, the produce catalogue, the season calendar and country pages — all editable without a developer.
One click: email every buyer who asked about Star Ruby that the window just opened. The highest-ROI channel you have.
Illustrative figures. But read the heatmap: the DRC wants vegetables and pome, the Netherlands wants berries, the Gulf wants citrus and subtropical. That is a sourcing plan you cannot buy anywhere else — and today it is invisible.
A brochure is worth the same on day 500 as on day one. This is not a brochure.
40 country pages plus ~49 variety pages, each targeting a real buyer search. Today riyp.co has 49 pages in total — this roughly triples the surface.
Every season alert and every RFQ adds a named buyer with a known interest. No platform can take that away or charge you for reach.
Season two compares against season one. By season three you know what each market asks for before the harvest starts.
Existing customers log in for live availability, shipment status, phyto certificates and invoices. Buyers do not leave a portal.
Francophone Africa — DRC, Gabon, Cameroon, Chad — and the Gulf are already your markets. Almost no SA exporter serves them in their language.
Riyp is the proof. The same engine can carry NUKE, Xpresso and Tamr under Essack Enterprise once it is built once.
Each phase is independently valuable. You can stop after any one of them and still be ahead of where you are today.
We would begin with Phase 1 — the storefront — because it is the phase that starts generating the data every later phase depends on. The season calendar and the RFQ flow are already built; you have just used them.
Phases 2 and 3 are quoted separately so you can decide once you have seen Phase 1 live and watched the first enquiries land.
We confirm the variety list and the real export windows with your technical team, agree the Phase 1 page list, and lock a start date.
Confirmed season windows and pack specs, access to your photography library, and one person on your side who can approve copy.