Close more units. With less software.

A personal link. A code to the phone. And it is signed.

The deal is run as a ladder rather than as an email chain: purchase offer, the technical specification required under the Sale (Apartments) Law, contract, and then a signing order in which each party signs in turn. The link opens on the signer's phone, a one-time code proves it is them, and the signature is captured. What comes out the other side is a signing certificate carrying the document hash — and the signed document is the proof this is a transaction system and not a listings board.

• Purchase offer, buyer specification, contract
• The Sale (Apartments) Law specification, in its statutory wording
• A signing order — each party in turn
• Verification by one-time code to the phone
• A signing certificate carrying the document hash
• A stage indicator showing where the deal stands

Everything in one place. No seven tabs, no spreadsheet on the side.

The control centre opens the day with the metrics and the funnel, and from there you drop into the leads themselves — a table or a kanban board, drag between stages, and a card that holds the whole history. The pipeline is enforced rather than decorative: skip a stage and the system asks why, and the answer is recorded. Smart lists keep themselves current, and one bulk action handles everyone in them.

• A control centre with the metrics and the pipeline funnel
• Drag-and-drop lead pipeline — table or kanban
• Skipping a stage stops for a question
• A lead card holding its entire history
• Smart lists that keep themselves current
• Bulk actions — reassign, stage, campaign, task

Where did this lead come from?

Every inquiry is captured with a touch record — channel, campaign, page, and language. The record stays attached to the lead, so that question is still answerable two months later, with first touch and last touch side by side. Forms, ads, and messaging channels all land in the same place, and duplicates merge into one record instead of competing over the same buyer.

• A touch record on every inquiry that arrives
• First touch and last touch, side by side
• Attribution to channel, campaign, and page
• Intake from forms, from ads, and from messaging channels
• Duplicates merged into a single record

No lead is left without an owner.

Routing rules run in order and the first match takes the lead — by project, language, source, or queue. No owner free? The lead drops into the lead pool, and whoever claims it owns it from that moment on. And when the response clock runs out, the breach surfaces on a panel of its own instead of disappearing into a list nobody opens.

• Ordered routing rules — first match wins
• Route by project, by language, and by source
• A lead pool — claim it, and it is yours
• A response clock on every lead
• An SLA breach panel, not a list that keeps growing

A forecast built from what actually closes — not from a feeling.

Every agent has a target, and every deal has a stage, a probability, and an expected close date. The forecast is derived from those stages and from the real closing rate, not from an estimate written at the start of the quarter that nobody revisited. The dashed line on the chart is a forecast and not a report — and the gap between it and what actually closed is exactly what a sales manager needs to see.

• A target per agent, and progress against it
• Stage, probability, and expected close date
• A forecast derived from the real closing rate
• A leaderboard for the sales team

The right message at the right time — without the nagging.

A welcome after the form, a reminder before the tour, materials after the visit, a construction update after the deposit. Rules pause on holidays, on closure, and the moment the lead asks them to — because an automation that cannot stay quiet becomes spam. A meeting booked here shows up in the calendar and the other way round, and the campaign itself — launch, drip, or open house — is built in a wizard with milestones and tasks for the team.

• Automated follow-up over email and messaging
• Tour reminders, documents, and construction updates
• Pauses on holidays, on closure, and on request
• Two-way calendar sync for meetings
• Launch, drip, or open-house campaigns

And in the end — what worked.

The conversion funnel is built from the real stages of the pipeline, not from a file somebody maintains by hand between two meetings. Beside it sits channel attribution, carrying the attribution-model tag — because a report that will not say how it measured is an opinion. And next to that, lead response speed: how long it took before anyone answered, by team and by hour of the day.

• A conversion funnel from the pipeline's real stages
• Channel attribution, with the attribution-model tag
• Lead response speed, by team and by hour
• Breakdowns by project, by agent, and by language
• Export, and view permissions by role

Which channel brought a deposit — and which only brought leads.

A cheap lead is not necessarily a good lead, which is why the ad platform's own report is never enough on its own. Because the deposit and the contract live in the same system the lead arrived in, Aura attributes the spend not just to the inquiry but to the deal that came out of it — by channel, by campaign, by creative. The budget conversation stops being an argument about impressions.

• Cost per lead, per tour, and per deposit in one place
• Attribution at channel, campaign, and creative level
• Connected to Meta, Google, and Yad2
• An alert when cost per lead leaves its range
• Channels compared on closed deals, not on clicks

Every channel, one inbox, attached to the record.

Email, chat, messaging, and calls arrive in one inbox and hang off the record they belong to, so a thread reads as a continuation rather than as a fresh start. And what the system could not attach does not vanish: it waits in an unassigned queue until someone pins it to the right customer. That is the difference between a shared mailbox and a communication history.

• Email, chat, messaging, and calls in one inbox
• Every thread hangs off its own record
• An unassigned queue — no message disappears
• Attach a conversation to a record in one click
• The history opens from inside the lead card

You take a conversation — it is yours.

Connect a business number and the whole team works from one inbox: claim a thread and it leaves everyone else's queue, so nobody answers it in your place. When the response window closes, the free-text field locks and an approved template is required — that is the channel's rule and not ours, and the system shows it to you up front instead of letting you find out the hard way.

• One business number, one inbox for the whole team
• A claimed thread leaves everyone else's queue
• The response window closes — an approved template is required
• Template build-out: draft, in review, approved
• Templates send with the record's variables filled in

Marketing mail passes through a gate. Always.

Before marketing mail goes out, the system checks each recipient's consent and the national do-not-call registry — and the registry is rescanned every fifteen days, so the check never leans on a stale copy. No consent? The send is marked blocked and the recipient counter drops in front of you, before delivery rather than after it. The consent log is kept read-only, because evidence you can edit is not evidence.

• Consent checked per recipient, before every send
• A do-not-call registry scan, with a freshness tag
• A send without consent is blocked, not warned about
• Consent carries an expiry date that is enforced
• A read-only consent log

The agent proposes. A human approves. Only then does it happen.

Ask a record a question in Hebrew and get an answer out of your own data, with a citation back to the record it was built from. The agent reads the CRM, ships with bilingual skill packages for the Israeli market, and connects to your systems — but it does not send on its own. The proposal lands in an approvals inbox, a person reads it and edits it if it needs editing, and only then does it go out. The default is suggest-only.

• Ask a record in Hebrew, get a cited answer
• Bilingual skill packages for the Israeli market
• An approvals inbox — propose, edit, approve
• Autonomy levels, and the default is suggest-only
• Checks re-run at the moment of approval
• Every run evaluated, drift against a threshold, rollback to a version

The site is edited from inside the system. No developer, no waiting.

The block library is organised by category: drag a block onto the page, save, and the site updates with no deploy and no ticket to an agency. The branding panel holds the palette, the typeface, and the logo, and swapping a palette shows on the site in real time. Every change carries a version, a preview, and a permission — who may publish, and who may only propose.

• A categorised block library, dragged onto the page
• A branding panel — palette, typeface, and logo
• Palette swaps that show in real time
• Preview before publish
• Version history and publish permission by role

A dashboard at the office, an app in the field, a portal for the buyer.

One system, three surfaces. At the office the team works in the full dashboard. The agent in the field opens inventory, the lead card, and the task from a phone and updates from the tour itself, not in the evening once they have forgotten half of it. And the buyer gets a portal of their own, branded in your colours, where the signing link opens on their phone and the alerts reach them.

• The full dashboard for the office team
• Inventory, lead card, and tasks from a phone
• Updated from the tour, not at the end of the day
• A buyer portal branded in your colours
• A signing link that opens on the buyer's phone
• Alerts on stage, on document, and on payment

Connects to what you already run — and works while you sleep.

The integration catalogue shows what is connected, and whatever is not yet connected is marked coming soon in so many words — so you know what can be switched on today rather than what might be possible later. The Priority ERP connector is verified against recorded responses, which is why it is presented as an existing, verified connector and not as a pipe carrying traffic in your deployment. Above them sits a public API with keys and scoped permissions, plus scheduled jobs that run overnight.

• An integration catalogue — what is connected, and what is marked coming soon
• A Priority connector verified against recorded responses
• A public API with keys and per-key permissions
• Scheduled jobs that run overnight
• Permissions in the database, and an immutable audit log