Nothing in this deck is a generic recommendation. Change any one of those and the plan changes with it.
I came in assuming I'd be telling you that you need a separate database outside Wix. Your numbers say you don't.
A thousand records per query. You'll be at two hundred. Five times the headroom before it's a conversation.
Collections over ten thousand items stop being eligible for translation. You'll be at two hundred. Nowhere near.
External database infrastructure, a second hosting bill, a second thing to keep running. All of it unnecessary at your scale.
So I'm not selling you infrastructure you don't need. If another quote includes a separate backend for a two-hundred-listing directory, they either didn't ask how big it gets or they're padding the invoice.
Menus, buttons, page copy, category names. Three or four hundred phrases you write in the editor. Translated once, done.
It also requires every collection to have a dynamic page attached, and any collection created after setup has to be added by hand.
A hotel owner in Puerto Viejo logs into the dashboard you're building and types his description in Spanish, six months after that translation workflow ran.
At two hundred listings that's roughly thirty thousand words of your most valuable content, existing in one language only. A German visitor gets a German menu wrapped around Spanish listings.
The fix is a write path, not a plugin. When an owner saves, the backend translates and stores all four versions in the record before it publishes, with owner override on each. A few dollars a month to run. But the record needs four language fields from the first entry, because adding them across a hundred and eighty live listings means re-entering every one by hand.
An owner won't pay to join a directory with no travellers. Travellers won't use a directory with no listings. Every marketplace hits this wall.
You launch with an empty map. Every sales conversation asks a business to take a leap of faith on something unproven. Most decline. The ones who don't churn when nothing happens.
You seed every business on the coast yourself as a free basic listing before launch. Then you're not selling presence, you're selling the upgrade. Photos, ranking, the TOP PICK badge, promotions. Each owner gets a claim-your-listing link. Claiming is free. Upgrading isn't.
Not in your spec, and it reshapes the data. Listings need an owner state of unclaimed, claimed or subscribed, plus verification and an admin queue. Free if it's in the schema now. A migration across every record if it isn't.
Wix Studio pages. Presentation only. Renders what it's handed.
Who ranks where, what each tier unlocks, translating on save, approving reviews, verifying claims, search. Every rule written once, here.
Calls the same layer via Wix's REST APIs and JavaScript SDK. New front end, no new logic.
Rules get written into page code because it's faster and works fine on a website. Then the app needs every one of them written again, in a second language, kept in sync forever.
Ranking must be a stored score that recalculates when a subscription or review changes, never a live page-load calculation. And your TOP PICK badges are the product you're selling, so they come off the tier automatically with an override you control.
Christmas fills Puerto Viejo and pushes rates to their yearly peak. Then February to April is the driest, most reliable stretch, running into Easter. You'd launch just ahead of your market's best run.
Businesses renew on what they saw in their first season. Slip past April and you're billing Caribbean owners through May, June and July, their quiet months. Next good window is September.
Every guide online says visit Costa Rica December to April. On your coast that's wrong for three months a year. Being the platform that gets this right is the argument that sells subscriptions in Puerto Viejo.
Twenty-five dollars blended, not forty. Small businesses on the Caribbean coast are not paying US directory prices, and I'd rather show you a number that survives contact with reality than one that flatters the proposal.
Fifty listings does not pay for a business. Two hundred does. So every decision serves the road from fifty to two hundred, and nothing gets built for the state of fifty. That's what shapes the plan on the next slide.
The whole database is designed now, including the fields German, French and the map will need later. Empty fields are fine. Missing ones are what cost you a rebuild.
Everything needed to seed the coast, sign businesses and take recurring payments. English and Spanish.
German and French switch on across the whole catalogue. Map, itineraries, promotions.
Why not all at once? A French translation pipeline is worth nothing until you know fifty Costa Rican businesses will pay. An itinerary builder is worth nothing across fifty listings. Building those in October is guessing. Building them in April is responding to what actually happened.
Nothing signed. You tell me whether the sequencing makes sense to you.
Blueprint agreement and invoice. Two weeks from the day it clears.
We go through the finished architecture together and you decide on run one with the whole thing visible in front of you.