Listings & Marketing
Letting a unit is a step in managing it, not a separate business. A vacancy publishes from the same property record the ledger bills, viewings are booked against real slots, applications arrive attached to the listing, and the tenancy that results is already linked to everything upstream of it.
What it does
Only people who may let, can let
Creating a property is restricted to landlords, property owners and property managers at the database level. Estate agents cannot insert themselves between an owner and a renter here, because the rule is a policy rather than a screen.
A publication gate with a written override
A listing cannot go live until the account has a reachable Ghana mobile number and somewhere to be paid. Staff can waive a requirement for a case it does not fit — a diaspora owner with no local mobile, rent going to a managing company's account — but a waiver carries a written reason and an author.
Viewings against real availability
Slots carry a capacity, and requests book into them, so two renters cannot be promised the same half-hour.
Remote viewings for diaspora renters
A scheduled video walkthrough with recording consent recorded separately for each side. Only the person showing the property sets the provider, time and joining link, and the link has to be a link — the database refuses anything that is not http or https.
Duplicate photography detection
Listing images are fingerprinted perceptually, so the same photograph reappearing under a different account raises a signal for a person to look at.
Applications attached to the listing
An application belongs to the listing it was made against, so accepting one produces a tenancy already joined to the property, the unit and the ledger.
How it works
The sequence an operator actually follows, not a feature list rearranged into steps.
- 1
A property and unit already exist in the console — the listing is published from them, not typed again.
- 2
The publication gate checks the account can be reached and paid; if not, it says which, and staff can waive with a reason.
- 3
Viewing slots open; renters book, or a remote walkthrough is arranged for someone abroad.
- 4
Applications arrive against the listing; accepting one creates the tenancy and its rent schedule.
What the database guarantees
These hold whether or not the interface remembers to check.
- Only a landlord, property owner or property manager can create a property. There is no agent role, and adding one would be a schema change, not a setting.
- A listing cannot reach the public site until the publication requirements are met or explicitly waived by a named person with a written reason.
- A remote viewing's joining link is constrained to http or https at the column, so it holds however the row was written.
- The tenant of a viewing cannot set the arrangement the landlord is then shown and expected to click.
What it does not do yet
You will ask this in an evaluation, so here it is without being asked.
- No syndication to third-party property portals.
- No paid promotion or ranking boosts — search order is driven by verification tier and completeness, and cannot be bought.
- Application scoring is presentational; nothing automatically rejects an applicant.
Works with
These share the same database, so nothing is re-keyed between them.
See listings & marketing against your own portfolio
Forty minutes, a property you actually manage, and a written quote after. No card at any point.