Product

One connected record per asset

Most tools in this market handle a fragment: a booking calendar, an accounting export, a document folder. ASTIN treats the asset as one record and keeps the fragments consistent with each other, which is where the operational cost actually sits.

Ownership Ledger Time Ledger Revenue & Cost Ledger Data Room Transfer workflow STAY / EARN / HOLD What sits outside the software

How information moves

The chain below is the product. Each step writes to the record and the next step reads from it — nothing is re-keyed, and every change leaves an event behind.

  1. OnboardingThe asset is described once: identification, ownership structure, operating budget, seasonality and documents.
  2. AllocationThe priced calendar is divided by ownership share into an allocation each owner can see and plan against.
  3. DecisionOwners set each period to STAY, EARN or HOLD. Rules catch conflicts before they reach the operator.
  4. OperationReleased periods go to the letting operator as structured inventory with an owner attached.
  5. SettlementRevenue and cost events land against the originating allocation and roll up into owner statements.
  6. TransferAn exit opens a case: valuation, pre-emption, document pack, external execution, updated ownership.

The five ledgers

Each module answers a question that co-ownership normally leaves unresolved.

Ownership Ledger

Who owns what, since when, and on what basis?

Ownership is held as interests in a specific asset, supporting unequal holdings and any number of changes over time. Every change is an event with a date, a reason and an actor, so the current state and the path to it are both retrievable.

  • Unequal interests (a single party may hold several shares)
  • Dated ownership-change history with the reason for each entry
  • Voting weight derived from holdings, not maintained separately
  • Mirrors the public register — it does not replace it
Time Ledger

Who gets which weeks, and is that actually fair?

The year is classified into peak, prime and standard periods with maintenance blocks removed, and each class carries a weight. Allocation then divides weighted value rather than nights, so a 12.5 % holder receives 12.5 % of what the calendar is worth instead of 12.5 % of its length.

  • Season classes with explicit weights, set per asset
  • Maintenance and operational blocks excluded before allocation
  • Allocation balance tracked in weighted units and in physical nights
  • Rotation supported so priority does not settle on one owner
Revenue & Cost Ledger

Whose week earned this, and who carries this cost?

Letting revenue attaches to the allocation that produced it rather than being pooled across owners. Fixed asset costs divide by holding; variable costs follow consumption. The value of an owner’s own stays is reported alongside cash, because for this asset class the two are not comparable in isolation.

  • Revenue attributed to period, owner and channel
  • Fixed costs by share, variable costs by consumption
  • Replacement value of personal use reported as a separate line
  • Owner statement assembled from events, not typed in
Data Room

Where is the current version of this document?

Asset documents are categorised, versioned and access-controlled. Each version carries an issue date, an author, a status and an access level, so a co-owner, a prospective buyer and an adviser can be given precisely the view each is entitled to.

  • Categories: title, financial, technical, regulatory, governance
  • Version metadata: number, issue date, author, status
  • Access levels from co-owner to controlled due diligence
  • Document sets assembled for a transfer case in one step
Transfer workflow

What actually happens when someone wants out?

An exit is a case with stages, not a phone call. Asking price, co-owner pre-emption window, buyer qualification, document pack, external legal execution and the resulting ownership update are all explicit — and the case records where it stopped if it does.

  • Pre-emption offered to existing co-owners first, on a clock
  • Due-diligence pack generated from the Data Room
  • External execution stage held open until the authorised party confirms
  • Completion writes a new ownership event, closing the loop

STAY / EARN / HOLD

Every allocated period carries exactly one status. That is the whole owner-facing model, and it is simultaneously the accounting event that drives settlement.

STAY

The owner uses the property. The system records the market replacement value of the stay so the benefit is visible next to cash.

EARN

The period is released to the licensed letting operator as inventory, with the owner attached for settlement.

HOLD

Undecided. Standing rules can release automatically at a chosen lead time so nothing is lost by inaction.

Rule validation runs on every change: releases inside the operator lead time, allocation overdrafts and conflicting claims are surfaced at the point of decision.

What sits outside the software

ASTIN is deliberately not the counterparty to anything. Brokerage, title registration, client money, escrow and licensed letting stay with authorised parties in each market — the system integrates them and records what they did.

FunctionPerformed byASTIN’s role
Property brokerageLicensed broker in the relevant marketPrepares documentation, coordinates, records the outcome
Title registration and transferNotary, land registry or DLD Registration TrusteeBrings the case to a ready state; records the confirmed result
Short-term lettingLicensed operator (e.g. DET-permitted holiday-home operator)Hands over structured inventory; ingests sales data for settlement
Payments, escrow and client moneyAuthorised payment or escrow providerNo role — ASTIN never holds client funds
Legal and tax adviceLocal advisersSupplies the document pack they need

This is why the product travels. Entering a new market means integrating local authorised parties, not acquiring a licence in every jurisdiction.

Everything leaves a trace

Ownership changes, allocations, decisions, document versions, settlement events and transfer stages all write to an append-only activity log with an actor, a role and a timestamp. The demonstration environment exposes that log directly, because an operator who cannot answer “who changed this and when” cannot run someone else’s asset.

See it running

The demonstration environment carries a synthetic asset through the entire life cycle, in four operational roles, with persistence — reload and the state is still there.

Open the product demo Talk to us