Estate management software · A Caramel Cove product
In developmentKnow who is at your gate and who has paid your levy
Manorlogic is estate management software for Nigerian estates. Residents issue visitor passes, guards check them at the gate, and managers see levies, parcels and notices in one place.
Opens an email to our team. Nothing is submitted until you press send.
Manorlogic is in development. We are preparing a first pilot estate in Nigeria; the resident and security apps are not yet in the app stores.
A resident invites a visitor
Adaeze (sample) fills in a name and a time window. She can make the pass single-entry.
The resident shares the pass with the visitor
The pass has a QR code and a six-digit code. She shares it from her phone.
The guard scans it, or types the code
The guard points the camera at the QR code. If it will not scan, the guard types the six digits.
The guard sees a clear yes or no, then logs the entry
The app shows who the visitor is, which unit they are visiting and whether the pass is valid. The server checks the pass again when the guard logs the entry.
The resident is told their visitor has arrived
Adaeze's phone shows an alert when the visitor arrives.
Gate entries and exits are on the record
The manager sees the entry in the gate log, with the time and who logged it.
An illustration of a visitor pass, from a resident creating it, through a guard checking it at the gate, to the entry being recorded. Sample data.
Many estates run on four things that never agree
- Gate book
- WhatsApp group
- Excel sheet
- Transfer screenshots
When something goes wrong, nobody can say who came in, who paid, or who approved.
Keep WhatsApp for chat, and for sharing a visitor pass. Manorlogic keeps the record WhatsApp cannot: who entered, who paid and who approved.
Roles
The same estate, seen by the people who run it
A guard cannot see finance. A resident cannot see another estate. Pick a role to see what each can and cannot do.
Manager
See what needs attention today, from payments to the gate log.
You can
- Set fee schedules and generate the month's invoices
- See who has paid and who owes, and for how long
- Read gate entries and exits with the time and who logged each one
- Announce to the whole estate, one building or a group of households
You cannot
- Edit a gate entry. A correction is a new entry.
- Change a payment or a pass without it being recorded
- Make another manager, unless you are the estate admin
Resident
Let visitors in without a phone call, and see what you owe without a screenshot.
You can
- Create a pass for a visitor, with a time window
- Be told when your visitor arrives
- See your invoices and your payment history
- Pay an invoice through PaystackBeing finalised: built, and not yet proven in a live estate.
- Message the estate office (web app)
You cannot
- Set the estate's fees or settings
- See another estate's records
Guard
Say yes or no at the gate.
You can
- Scan a pass or type its six-digit code
- Ask a resident to approve a visitor who has no pass
- Log a parcel with photos
- Hand over the shift with notes
You cannot
- See invoices or payments
- Open estate channels
Make a sample pass, then check it as the guard
You choose how long a pass works and whether it works once. Nothing you type here is sent or stored.
An example pass
Chidi (sample)
Six-digit code
482 913
Valid
| If the guard checks it | The app says |
|---|---|
| Within the window, first time | Verified |
| A second time, on a one-entry pass | Already used |
| After the window ends | Expired |
Turn on JavaScript to make your own sample pass.
From a visitor's invitation to the entry log
The resident makes a pass with a name, a time window and, if they like, a single-entry rule.
The resident shares it from the phone's share sheet, WhatsApp included.
The guard scans it or types the six-digit code.
The server gives the verdict. An expired, cancelled or used-up pass is refused, even if the guard's screen is out of date.
The resident is told, and the entry is logged with who logged it and when.
No pass? The guard sends a request and the resident approves or declines from their phone.
From a levy schedule to a clean statement
Set the schedule once: the amount in naira, how often, and who pays. Preview who will be billed.
Generate the month's invoices in one step. The manager presses the button.
Residents see what they owe in the app.
Record cash and transfers, or upload the bank statement and match its credits to invoices. Online payment through Paystack is built into the product. It has not yet been used in a live estate.
Read the arrears report to see who owes what and for how long.
Close the month. Late fees follow your rule and each one is recorded. Download a household statement or export to a spreadsheet.
From invoice to arrears, without the screenshots
SampleSample estate: 40 units, monthly levy ₦25,000. These numbers are sample inputs, not results.
Step 1 of 5 The manager generates the month's invoices
What the manager does. Pick the fee schedule and press Generate invoices. It is one step, and the manager presses it.
What the system records. Each invoice, the schedule it came from and who generated it.
Step 2 of 5 Residents see what they owe
What the manager does. Nothing more. Residents open the app.
Pay through Paystack: Being finalised: built, and not yet proven in a live estate.
What the system records. The invoice is issued, and the household sees its balance.
Step 3 of 5 Payments arrive
Card or transfer through Paystack Being finalised: built, and not yet proven in a live estate.
A resident pays on Paystack's page. When Paystack confirms, the invoice shows as paid.
Bank transfer Built: this works in the product today.
The manager records the transfer against the invoice, or imports the bank statement.
Paying online through Paystack is built. It has not yet been used in a live estate. Recording transfers and importing a bank statement is the other route.
What the system records. The payment, the invoice it settled and who matched it.
Step 4 of 5 Payments match invoices
Sample figures
Sample estate, October Status Units Amount (₦) Paid 34 850,000 Pending 4 100,000 Overdue 2 50,000 Expected 40 1,000,000 - Unit 7B · ₦25,000 · matched to invoice
- Unit 12 · ₦25,000 · matched to invoice
- Unmatched credit · ₦25,000 · create invoice or skip
What the manager does. Upload the bank statement. Matched credits settle invoices, and the manager decides what to do with the rest.
What the system records. Each row of the import has a result.
Step 5 of 5 Arrears and late fees are visible
What the manager does. Open the arrears report and follow up with the households on it.
- 7B₦25,0006 days late
- 12₦50,00038 days late
Late fee: applied once to each overdue invoice, and each one is recorded.
What the system records. Each late fee, the invoice it applies to and when it was applied.
With JavaScript you can change the sample.
In this sample month: 40 invoices, 34 paid, 4 pending, 2 overdue. Each step was recorded.
These are sample numbers. They show how the screens work, not what an estate will collect.
Opens an email to our team. Nothing is submitted until you press send.
The record
A record of who did what
Changes are logged.
Changes to payments, invoices, passes, gate entries and roles are logged with who made them.
Each estate is kept separate
from every other estate.
Each role sees its part.
A guard does not see finance. A resident does not see another estate.
Cards are handled by Paystack.
Manorlogic does not store card details.
Built with the Nigeria Data Protection Act in mind: residents can ask for a copy of their data or for their personal details to be erased.
Status
What is built today
- Visitor passes, guard check and the entry and exit logBuilt: this works in the product today.
- Live approval for visitors without a passBuilt: this works in the product today.
- Parcels logged at the gate, and the resident panic buttonBuilt: this works in the product today.
- Fee schedules, invoices, late fees and the arrears reportBuilt: this works in the product today.
- Cash, transfer and bank-statement matchingBuilt: this works in the product today.
- Online payment through PaystackBeing finalised: built, and not yet proven in a live estate.
- Announcements, messages and repair ticketsBuilt: this works in the product today.
We update this list when something ships, not before. Read what is not built yet.
Check how ready your estate is
Eight questions, one minute. Your answers stay on this page unless you choose to email them to us.
- Do you keep a gate record of who enters? A paper book counts. We do this today.
- Do you know whether a visitor was expected before they arrive? For example, a call from the resident. We do this today.
- Can you tell, today, which households have paid this month? Without asking around. We do this today.
- Do you match bank transfers to households without screenshots? A spreadsheet counts. We do this today.
- Can you produce a list of overdue levies in a few minutes? Who owes, how much, for how long. We do this today.
- Do residents get estate notices in one place that everyone reads? A WhatsApp group counts if everyone is in it. We do this today.
- Do you log parcels and deliveries at the gate? Who received it and when. We do this today.
- If a resident asks “who approved this?”, can you show them? A gate approval, a payment or a change of fee. We do this today.
Reply to us with your answers. info@caramelcove.com
Start small, with a pilot
We are choosing a small number of estates for our first pilot. We would rather get a few estates working well than promise everything to everyone.
Pilot estates use Manorlogic free while we learn together. Terms, and what happens after the pilot, are agreed in writing before you start.
Talk
A walkthrough, on a call or at the estate. You tell us how the estate works today.
Set up
You decide what to switch on first: households, fee schedules, gate rules.
Run
Guards, residents and the office use it.
Review
Together we check what worked and what did not. You decide whether to continue.
What we ask of you
- A named contact at the estate who can decide
- A few residents and guards willing to try it
- Honest feedback, including what annoys you
- Agreement in writing on how your estate's data is used in the pilot
- Your written permission before we ever name you or show your screens
What you can expect from us
- Plain answers about what is built and what is not
- Terms in writing before anything is switched on
- Honesty about the apps: they are not in the app stores yet, and we agree with each pilot estate how guards and residents get them
- No payment to request access
Opens an email to our team. Nothing is submitted until you press send.
Questions managers ask first
Is Manorlogic live anywhere?
Not yet. It is built and tested, and we are preparing a first pilot estate in Nigeria.
What if the network drops at the gate?
The gate app needs a connection today. Guards use your existing paper process until it returns.
Our guards are not used to phones.
A guard scans a pass or types six digits and sees a colour-coded yes or no.
What does it cost?
Pricing is not set yet. Pilot estates get the terms in writing before they start.
Where to look next
What it does
Visitor access, gate security, collections and communication
Who it is for
For estate managers, residents associations, residents and security teams
Want Manorlogic at your estate?
Tell us about it. We will reply with a plain next step.
Opens an email to our team. Nothing is submitted until you press send.