Monument Reviews & Product Details

Monument is a facility management platform built for self-storage operators running multiple locations — typically portfolios of ten or more facilities, third-party management companies, and institutionally or private-equity-backed ownership groups. Most self-storage software was designed around a single facility and scaled up from there. Each location ends up configured and reported on as its own system, so growth means repetition: the same rule entered forty times, the same report rebuilt per site. Monument is organized around the portfolio instead, and that single choice shapes everything below it. **Portfolio segmentation with Navigator** Navigator lets an operator define a set of facilities — by region, market, strategy, brand, leasing stage, acquisition vintage, or any custom grouping — and treat that set as the unit of work. Reports run against it. Automation rules attach to it. Rate changes apply across it. Segment selection carries through the entire platform, including analytics, so a regional director and a CFO are working from the same definition of the portfolio rather than reconciling two versions of it. Which facilities appear in Navigator is governed by each user's own access, so permissions and segmentation stay consistent without a separate map to maintain. **Operations** Monument handles tenant and unit management, move-ins, move-outs, transfers, reservations, waitlisting, quoting, and merchandise, alongside a site map builder with occupancy and delinquency views. Gate access management includes guest access, with codes issued automatically on the day of a scheduled move-in. Delinquency runs as a structured, staged lifecycle — Overdue, Overlock, Lien, Foreclosure, Auction, and Paused — rather than as notes and reminders. Each stage is a real, timestamped field, and notice timing accounts for the fact that lien law varies by state. The Delinquencies page shows every delinquent unit across the selected segment, sortable by days overdue, stage, days until next stage, and balance, and filterable by unit type, facility, stage, and balance so a regional team can isolate a population and act on it in bulk. Auctions run through a governed workflow covering scheduling, buyer details, photos, and payment collection. **Automation** All automation is built on one structure: triggers, actions, and variables. Triggers are what cause a rule to fire — a lead created, a lease signed, an invoice reaching a set age, a payment failing, an overdue balance paid. Triggers can be time-adjusted ("five days after an invoice is past due") and grouped with AND/OR logic ("current rent 30% or more below web rate AND in a stabilized facility"). They also stand down once a precondition is met, so a promotion doesn't reach a lead who already became a tenant. Actions are what follow: send an email or SMS from a template, generate a letter, apply fees, change delinquency stage, create a task, block tenant portal payments on a unit, adjust a balance. One trigger can fire several actions together. Variables populate those actions with situation-specific detail — a tenant's name and balance, the date their delinquency advances, a link back to an unfinished lease. Every rule attaches to a Navigator-defined facility set, so a rule written once reaches exactly the locations it should. **Leasing** The rental website is native and mobile-first rather than an embedded iframe, with real-time inventory and pricing sync, tiered unit merchandising at checkout, digital lease signing, and tenant protection enrollment. Abandoned checkouts are captured as high-intent leads and can be routed into automated recovery sequences. An automatic card updater refreshes expired or reissued cards in the background to preserve autopay enrollment without tenant outreach. **Revenue management** Rate settings support manual or percentage-based pricing, with dedicated street and web rate controls and per-tier markups. Existing Customer Rent Increases (ECRI) run as a governed process rather than a quarterly exercise. Eligibility rules — minimum tenancy, minimum time since last increase — are defined centrally, and tenants appear the day they qualify. The eligible units table shows current rent, unit group average, street rate, variance, unit group occupancy, autopay status, tenure, prior increase count, and paid-through date side by side. Increases can be applied in bulk or unit by unit, with an optional ceiling so no increase exceeds current street rate. Automatic ECRI Scheduling evaluates eligible units continuously against configurable conditions — rate variance against street or web rate, increase frequency over the past twelve months, unit group occupancy threshold, and tenant standing (excluding delinquent tenants, scheduled move-outs, active military, tenants on promotions, multi-unit or business tenants, or including only tenants on autopay). Qualifying increases either schedule automatically or route to an approval queue where a manager can edit, approve, or deny them individually or in bulk. Retention impact is measured afterward. ECRI churn reporting is cohort-based, anchored on effective dates, breaking out move-outs at 0–30 and 0–90 days, the share of increases that pushed tenants above street rate, and the churn rate for that above-street group specifically. **Analytics, accounting, and reporting** The Insights module contains more than 100 business graphs organized into named collections spanning revenue, marketing, operations, facilities, third-party management, and investor reporting. Dashboards are configurable by role, and Navigator scope applies throughout. GAAP-compliant accrual accounting runs natively alongside cash-basis on the same underlying transactions, with automated daily journal entries, separate accrual and cash journal entry reports, and jurisdiction-level sales tax reporting on both bases. Month-end close doesn't require restating accrual figures by hand. Owner-facing reporting includes a 12-month trailing Owner's Summary Report and a multi-facility Management Summary Report covering collections, rental activity, coverage enrollment, liabilities, delinquency over 30 days, concessions, length of stay, last rent increase, and occupancy. **Third-party management** Third-party managers get a dedicated dashboard with global-to-property drill-down, configurable per-brand and per-property KPI targets, and stabilized-versus-lease-up benchmark logic. Owner-facing dashboards and reports are white-labeled, carrying the manager's brand rather than Monument's. **Open architecture and integrations** Monument is API-first, with more than 20 integrations spanning access control, payments, accounting, and marketing — including PTI, Nokē, OpenTech, SpiderDoor, PDK, QuickBooks, Xero, Yardi, NetSuite, G5, and StorTrack. Custom integrations are built before go-live at no additional cost. Payment processors are the one stated exception to this openness, due to security and reconciliation controls. **AI connectivity** Monument ships an MCP (Model Context Protocol) server at no additional cost, giving AI assistants such as Claude, ChatGPT, or Gemini secure, read-scoped access to live portfolio data — no exports, no custom development, no vendor lock-in to a particular assistant. Underneath it sits a semantic layer that defines how each metric is actually calculated: physical versus economic occupancy, delinquency aging buckets, lien compliance stages by state, ECRI effective dates, and lead attribution by facility, unit type, and channel. Because those definitions are explicit, a connected assistant interprets Monument data the same way Monument's own product does rather than inferring meaning from raw tables. Operators can ask in plain language which accounts are approaching a lien deadline, which unit groups are due for an increase, or what NOI looks like for a facility set, and get answers consistent with their own dashboards. Connection credentials are held by the MCP server and never passed to the AI assistant, and an operator's assistant only ever sees that operator's own portfolio data. **Security and permissions** Roles are built from granular per-module permissions at four levels — View, Edit, Create, and Delete — with no permission meaning no access to that feature. Financial reporting, auction actions, delinquency management, and automation authoring are each separately gated, so a facility manager, a regional director, and a controller see appropriately different products. **Implementation and support** Implementation is run by a US-based team through a phased model: discovery and mapping, migration design, integration validation, and phased rollout. Payment tokens transfer directly, so tenants remain enrolled in autopay rather than re-entering card details — the single largest source of avoidable delinquency during a platform switch. Timelines vary with portfolio size and complexity, generally ranging from a few weeks to a few months. Ongoing, the model includes quarterly business reviews and platform releases every two weeks. White-glove US-based client success & support jointly own the outcome with out customers. **Pricing** Monument is priced per storage unit across three tiers — Core, Pro, and Enterprise — rather than per seat, so cost scales with portfolio size rather than team size, and user counts are unlimited. Within a selected tier there are no hidden fees or required add-on purchases, though included capabilities differ between tiers. **Where Monument fits Monument is built for operators who have outgrown facility-by-facility management: portfolios of roughly ten facilities and above, third-party managers running multiple brands and owners, and ownership groups preparing for a refinance, capital raise, or institutional exit. Automation, AI, focus on optimizing economic occupancy while reducing costs, and white-glove services are the main differentiators.