The sale ends. The relationship begins.

The wallet opens in an underground car park too.

All of a resident's vouchers in one place, in three clear groups: active, redeemed, expired. A voucher card opens to its QR code, its validity and its redemption branches, and the terms of use and the buyer's rights are shown inside the wallet rather than only at the moment of purchase — the voucher carries a validity of its own, at the statutory minimum Israeli law requires, and the resident is notified before it lapses. In the branded iPhone and Android app, which is a full app and not a reduced version of the site, active vouchers are kept on the device and the code is displayed with no network connection at all. The redemption itself is still recorded on the server, so even a voucher opened offline cannot be redeemed twice.

• Three groups · active, redeemed, expired
• The voucher's own validity, at the statutory Israeli minimum
• Terms, participating branches, and buyer rights · at purchase and in the wallet
• A branded iPhone and Android app, not a reduced version
• The code is displayed with no network connection
• Redemption is recorded server-side · an offline voucher cannot redeem twice

The offer transfers to a partner. The entitlement holds.

A family buys an apartment as two people, and the club works that way too. The resident adds the members of their household themselves, and an offer transfers to them in one click — without creating a second voucher and without duplicating the entitlement. The recipient can redeem, and eligibility keeps deriving from the registered buyer. Who transferred it and who redeemed it are both on the record.

• The resident adds their household members themselves
• Transfer in one click · no second voucher, no duplicated entitlement
• Eligibility keeps deriving from the registered buyer
• Who transferred and who redeemed · both on the record
• Works from inside the app as well

Their home, stage by stage.

Seven stages from the contract to living in the apartment: contract, planning, construction, approaching handover, handed over, warranty, resident. Each carries the date it was reached, and the current one is marked. Your team publishes updates from the site onto that same timeline — text and photos from the project — and beside them sit the offers matched to exactly the stage the resident is at. The question of what is happening with my apartment is answered before it is asked.

• Seven stages · from contract to resident
• Each stage with the date it was reached, the current one marked
• Updates from the site · text and photos from the project
• The offers matched to the stage they are at
• The same timeline on the web and in the app

Every document for the apartment, held by the resident.

The contract, the technical specification, the payment schedule, the handover protocol, the warranty certificates and the project documents all sit in the resident's own vault, each one tied to them, to their apartment, or to a whole project, according to who needs to see it. A download goes through a short-lived one-time link, so no file has a permanent address, and a resident sees their own documents and nobody else's. Beside them sit their order history and the receipts they download themselves, so nobody has to ask you for another copy.

• Contract, technical specification, payment schedule, handover protocol
• A document tied to a resident, an apartment, or a whole project
• Download via a short-lived one-time link · no permanent file address
• A resident sees only their own documents
• Order history, and a receipt the buyer downloads themselves

Points that accrue, tiers that unlock.

Points accrue on a paid purchase, on a referral that converted, and on attendance at an event, at an accrual rate you define per club. Tiers have a points floor, and the better offers unlock only at a given tier — a mechanism that raises basket value and return frequency rather than simply issuing discounts. Each resident also holds a permanent personal referral link: a friend who signs up through it is attributed automatically, and when the referral converts the referrer receives the gift voucher you defined. No reward for a self-referral, and no double reward for the same friend.

• Points for a paid purchase, a converted referral, and event attendance
• The accrual rate is your setting, per club
• Tiers with a points floor · the better offers unlock by tier
• Balance, progress to the next tier, and accrual history
• A permanent personal referral link for every resident
• No reward for a self-referral, no double reward for the same friend

A residents' event that runs itself.

Open an event with its date, place, description, image and capacity, and the rest runs itself: registration up to capacity, a waiting list once the places are gone, and automatic promotion when one frees up. The resident sees their own registrations and can cancel, a reminder goes out before the event, check-in at the door marks attendance against the list, and whoever came receives club points. No registration table in a WhatsApp group.

• An event with date, place, description, image, and capacity
• Waiting list, with automatic promotion when a place frees up
• The resident sees their own registrations and can cancel
• A reminder before, and check-in at the door against the list
• Club points for whoever came

The suppliers you chose — and a portal of their own.

A supplier directory with a logo, description, category, branches and contact details, where each supplier's offers gather on their own page and an enquiry from that page creates a documented lead. Behind it, every supplier has a portal of their own: they fill in the offer and submit it for your approval, work three inboxes of their own — leads, orders and vouchers, filtered to them alone — redeem at the point of sale from the phone of whoever is at the counter, and receive a settlement report at month end. They do not see your residents and they do not see the other suppliers, and a supplier who stops working with you leaves the club in one click.

• Supplier directory · logo, category, branches, and contact details
• An enquiry from the supplier's page creates a documented lead
• A portal per supplier · leads, orders, and vouchers, filtered to them alone
• The supplier submits an offer, and you approve it
• Redemption at the counter from the staff phone, and a settlement report after
• A supplier sees neither your residents nor the other suppliers

Existing buyers arrive from the system they are already in.

Import from an Excel or CSV file with column mapping, or straight from the company's existing back office, instead of retyping. Duplicates are identified by the buyer's identity, so a repeated import does not create a second record for the same person. The error report is precise per row, and a valid row always goes in even when another row failed — which is what turns bringing a club of thousands of buyers live into a day's work rather than a project.

• Import from Excel or CSV with column mapping
• Import from the existing back office, with no retyping
• Duplicates identified by the buyer's identity
• A precise error report, row by row
• A valid row goes in even when another row failed

What is waiting, what is happening, and what it brought in.

One console for the team. The board opens on what needs attention — offers awaiting approval, new leads, refund requests — on what is happening now, and on the period's figures, with a direct link from every measure to the screen that handles it. From there: a resident table that works on tens of thousands of records, with a record drawer that opens without leaving the table; the real-estate tree from project to building to floor to apartment, which is what feeds eligibility, the stage, and the documents; one lead inbox with dated notes that cannot be edited after the fact; and an audit log of every sensitive action that can neither be changed nor deleted.

• What needs attention · offers to approve, leads, refund requests
• A resident table with a record drawer, without leaving the table
• Real-estate tree · project, building, floor, apartment
• The buyer-to-apartment link feeds eligibility, stage, and documents
• One lead inbox · notes that cannot be edited after the fact
• An audit log of every sensitive action · not editable, not deletable

Audiences that update themselves.

An audience is built from rules rather than from a list of names — project, building, stage, tier, city, dates — and the recipient counter updates while the rule is being built, so you see the size of the audience before a single message goes out. A resident who moves a stage enters or leaves the audience by themselves, with no maintenance, and that same audience then targets offers, posts, events, and campaigns. The segmentation is built once and keeps working, instead of going stale after a week.

• An audience from rules · project, building, stage, tier, city, dates
• The recipient counter updates as the rule is built
• A resident who moves a stage enters or leaves by themselves
• The same audience targets offers, posts, events, and campaigns
• Built once · no lists to maintain

No offer goes live without approval.

An offer runs a defined route: draft, submitted, in review, approved, active, ended. The supplier submits; you approve, reject with a reason, or send it back for correction — and an update to an offer that is already live goes through approval too. One approval queue gathers everything waiting for you, and every offer carries its audience targeting, its redemption cap, its validity, its price, and its commission. Before publishing you can view the club through a chosen audience's eyes exactly as they will see it — and that preview produces nothing at all: no purchase, no lead, no message, no voucher.

• A defined route · draft, submitted, in review, approved, active, ended
• A rejection returns to the supplier with a reason, to correct and resubmit
• An update to a live offer goes through approval too
• Per offer · audience targeting, redemption cap, validity, price, commission
• Preview through an audience's eyes · produces no purchase, lead, or message

Every send passes one gate. There is no back door.

Every send — an automation, a campaign, an in-app notification — passes through one checkpoint that verifies marketing consent, and a resident who withdrew marketing consent will not receive marketing, not even as a notification inside the app. There is no bypass route for an edge case; it simply does not exist in the system. Necessary service messages keep working — voucher, payment, handover — by email, SMS, and WhatsApp from approved templates. Behind the gate sit eleven built-in automations, from a welcome for a new member to a reminder about a voucher that is about to expire, each switched on and off separately, each with a message template you edit. And a visual builder lets your team add one more without a developer.

• One checkpoint that verifies marketing consent · every channel, every send
• Withdrawing consent stops marketing · including an in-app notification
• There is no bypass route; it does not exist in the system
• Service messages always pass · voucher, payment, handover
• Eleven built-in automations · each switched on separately
• A visual builder for one more automation · without a developer

The money closes in a report, not on the phone.

A settlement report per supplier shows what was sold, what was redeemed, and what the commission is — and because every amount is held as a whole number of agorot, it carries no rounding errors. Each paid purchase produces a receipt for the buyer, and each supplier receives a commission invoice carrying the Israeli reporting requirements. Refund requests run an orderly approval route rather than happening automatically, and an approved refund cancels the voucher and takes back the points granted for it, so no refund leaves an active voucher behind. Month end with the suppliers becomes an hour's task.

• A settlement report per supplier · sold, redeemed, commission
• Every amount held as a whole number of agorot · no rounding errors
• A receipt for the buyer on every paid purchase
• A commission invoice per supplier, to Israeli reporting requirements
• An approved refund cancels the voucher and takes back the points

And what it actually did.

A full conversion funnel — exposure, offer view, purchase started, payment, redemption — and beside it turnover, order count, average basket, and commission revenue, per period and broken down by project, supplier, category, and offer. Above them the club's own measures: active residents, redemption rate, churn, and referral growth. Every measure links straight to the screen that handles it, and the budget conversation runs on data instead of on impressions.

• A full funnel · exposure, view, purchase started, payment, redemption
• Turnover, order count, average basket, and commission revenue
• Broken down by project, supplier, category, and offer
• Club measures · active residents, redemption, churn, referrals
• Every measure links straight to the screen that handles it

Their club. Your brand. Your data.

Your logo, your colours, your club name and your cover images — equally across the web club and the app, including the icon and the splash screen, in light mode and dark, so the buyer downloads your company's app and not a software vendor's. Hebrew is the default language rather than a translation pasted over a Latin system, direction reversal is complete, and text and focus contrast stay enforced even when the brand colour is unusually light or dark — alongside an external body's audit against IS 5568. An additional club goes up in minutes from a setup form and a first admin invitation, and starts clean: every record is scoped to its club, and the separation is enforced in the database itself rather than only in application code. Vesta derives club identity from the authenticated session and not from a URL or a parameter, and dedicated tests attempt to escape a club and are required to fail.

• Logo, colours, club name, and cover images · on web and in the app
• Icon and splash screen in your branding, light and dark
• Full Hebrew and English, with a real direction flip
• No brand colour can make the system inaccessible
• Separation enforced in the database, not only in the application