Accrod is designed to bring lease records, properties, tenants, key dates, document status and follow-up tasks into one clear workflow. The aim is to make the next action easier to see without adding an unnecessarily complex system.
The first customer segment being evaluated is independent commercial-property owners and lean in-house teams managing their own portfolio. The current preview is not designed for property managers who need isolated workspaces for multiple clients, staff permissions or tenant portals.
No. Accrod focuses on lease administration and operational follow-through. Accounting, rent collection, property maintenance and resident portals are separate workflows and are not included in the initial scope.
No. Accrod can help organize user-entered dates and follow-up, but it does not determine every legal obligation or guarantee compliance. Verify deadlines against the executed lease, amendments and applicable law, and seek qualified advice when necessary.
Email, yes; text messages, no. In a real account Accrod emails a digest 60, 30, 14, 7 and 1 days before each notice deadline and lease end date, once email delivery is switched on. The sample workspace sends nothing: no email, SMS, push or calendar notifications. A reminder is a prompt, not a guarantee, so keep your existing calendar until you have seen your first reminder arrive.
The current Documents area is a register for names, types and review status, not an upload interface. A private Storage bucket and workspace-scoped access policies are in the source migrations, but file upload, preview, download, deletion, scanning, retention and backup/recovery workflows are not released or tested.
The browser reads and validates the CSV locally; the original file is not uploaded. In a deployment connected to Supabase, only the lease fields you confirm are sent through the authenticated workspace sync flow. In sample mode, changes remain illustrative. The supplied deployment is not connected yet, so test with fictional records and keep your original file.
There is no trial clock, and no trial can be started because account creation is not open. The proposed Free plan is not time-limited. You can open the sample workspace with fictional data without an account.
The proposed plans are Free (up to 10 active leases and 3 properties), Core at $15 a month and Portfolio at $29 a month, or two months free when billed yearly. They are proposals under evaluation: none can be started or bought yet, and prices may change before launch. The pricing page shows what is proposed.
Not yet. Paid checkout is not open. When it opens, the full price, billing period, renewal, cancellation and refund terms will be shown before you pay. Those terms have not been written yet.
Yes. The sample workspace is available without creating an account. Its records are fictional and are not a connected customer portfolio.
The supplied deployment is not connected yet. After the operator configures Supabase, applies the migrations and completes staging tests, a signed-in workspace can load and save versioned records through the account backend. The interface does not provide live realtime collaboration, team invitations or multi-workspace switching; simultaneous stale saves are rejected for recovery rather than silently merged.
Use only information your organization is authorized to store. Before using confidential records, verify that the live deployment has passed the backend, workspace-isolation and access-control launch checks. A sample workspace uses fictional records, and a local preview may store changes only in this browser. Do not enter confidential agreements, tenant personal information, payment details or other sensitive data into an unverified deployment.
Not yet. The database includes workspace roles, but invitations, acceptance links, team management and user assignment are not implemented in the interface. The first-release onboarding is designed for one owner account and one workspace.
No. The currency is a display preference. Changing it does not convert or recalculate existing rent numbers. Verify every lease amount before changing the label, especially if your records contain more than one currency.
No. CSV export covers lease rows currently shown, and the JSON recovery file only preserves pending unsynced workspace changes. It is not encrypted by the export and is not an automatic restore. A scheduled backup, complete archive and tested restore process are launch requirements.
The searchable Help Centre and support-status page provide current self-service information. A monitored email, phone or ticketing channel has not yet been published, and these pages do not send a request.
A connected workspace uses browser storage for its working copy and pending-change recovery. Browser storage is not an encrypted backup and may be accessible to someone with access to your device or scripts running on the same site. Use a private, trusted device and sign out when finished. Do not enter highly sensitive information until the production privacy and security review is complete.
The Overview board brings open tasks and lease records marked for follow-up into one due-date-ordered view. The Tasks page groups work into overdue, due soon and coming up, with a List option for a compact view. Dates are planning aids only: verify contractual deadlines against the signed lease and amendments. The current workspace does not send external reminders.
Yes. The Follow-up date field is optional. Leave it blank rather than guessing; the task stays in the No due date group and can be found with the No date filter. Add a date only after an internal follow-up date has been agreed. This planning date is not a contractual notice or expiry date, and no external reminder is sent.
It lists open tasks without an owner label. Owner names are reference text only in this release; they do not invite a colleague, grant access, assign an authenticated user or send notifications.
