What is being built now, with how far along each one is.
Medical CRM
A CRM shaped for a medical practice rather than for a sales pipeline: the patient, the visit and the treatment history as the central records instead of the account and the deal.
Status: in design.
HoReCa guest loyalty
A guest loyalty programme for restaurants, cafés and hotels. Guests earn points on their bills and redeem them for rewards; the venue's own staff run the programme from the back office instead of from a separate vendor console, and guests are external members tracked in the programme's registry.
It is built on the platform's own ledger, which is what makes it a loyalty system rather than a points counter:
- Points are an issued asset. Earning debits issuance and credits the guest; redemption and expiry move it back. Liability is therefore a balance you can read, not an estimate.
- Earning is a batch. A shift or a day of till checks posts as one batch - which is the volume path, not a loop of single writes - and it is idempotent per check, so the same bill posted twice does not pay twice.
- A correction is a reversal. A mistaken award is reversed rather than edited away, so the record of what happened survives being corrected.
- Expiry is a sweep, balanced and auditable like every other movement instead of a rule somebody applies by hand.
- Every movement carries an actor, so any balance resolves to a statement of who did what.
- A guest can be registered provisionally at the till and claim the account later with consent, instead of the cashier completing a sign-up while a queue waits.
Status: the loyalty core - everything needed to earn points correctly, safely and compliantly - is designed and being built. Redemption with its controls, then tiers and the analytics that go with them
- liability, breakage and anomaly views - follow it as their own stages.
Campaign management
Email and SMS campaigns, built the platform-native way:
- A campaign is a process. Its preparation, approval and send steps are transitions you can see and change, with the same audit as every other process.
- The audience is a spreadsheet. Two sheets: the audience itself - contact, name, email, phone, segment, and a suppression flag - and a suppression list with the reason and the date something was added to it. So building a segment is formulas and lookups against your real data, not an exported list somebody re-uploads, and the suppression list is a working document, not a hidden setting.
- Results are an ordinary dataset. Campaign events feed the engine like any other data, with channels and event types as master data - so campaign reporting sits next to the rest of your reporting instead of inside a marketing tool.
- And a funnel dashboard on top of it.
Status: the scaffold exists - the audience and suppression workbook, the campaign process, the events dataset with its dictionaries, a one-shot send automation and the funnel dashboard. The sending and tracking surfaces are being built out.