Operational core first
Leasing, ledgers, renewals, notices, maintenance, reports, and portal continuity anchor every plan.
Self-serve pricing
Create a private demo workspace, test Blocora with sample rental data or your own setup, then choose Starter, Growth, or Pro when workflow fit is clear. Custom remains scoped for 300+ units, migration-heavy rollouts, or unusual governance.
Leasing, ledgers, renewals, notices, maintenance, reports, and portal continuity anchor every plan.
More users, tighter permissions, and stronger onboarding show up as operator complexity rises.
Starter, Growth, and Pro stay self-serve after the demo proves fit. Custom stays scoped for 300+ units, migration, or unusual governance.
Unit count helper
Pick the unit band first, confirm workflow fit in a private demo workspace, then subscribe when the operating model matches your team.
Trial rule
Trial access never bypasses organization scope, permissions, or server-side subscription checks.
For smaller operating teams
Free demo first
The operating core for portfolios moving out of spreadsheets, folders, and informal inbox workflows.
Team scope
Limited team size
Includes the V1 reports layer without heavier governance overhead.
For scaling portfolios
Free demo first
Extends the operating core for teams that need more users, throughput, and coordination support.
Team scope
More users
Adds more automation and more team control without turning Blocora into an ERP.
For larger management groups
Free demo first
Built for teams that need stronger governance, structured operating discipline, and onboarding support.
Team scope
Broader team governance
Introduces stronger governance and stronger onboarding support for higher-complexity rollouts.
For enterprise-shaped rollouts
Custom sales motion
Reserved for portfolios that need custom pricing, structured onboarding, migration planning, and rollout support.
Team scope
Custom rollout design
Used when the delivery motion and onboarding scope need to be shaped around the operator.
Scope notes
Payments, screening, signatures, notifications, migration help, and integrations can shape implementation scope, but public clicks do not open add-on billing or provider marketplace behavior.
Custom CTA
If you're planning migration, rollout, or unusual governance, Blocora should be scoped as an implementation conversation, not a checkbox purchase.
Demo and trial
Every normal buyer starts with an organization-scoped demo workspace. The public CTA creates a private trial, not shared demo access or portal activation.
Test the rental operating chain with sample records, or set up your own portfolio structure from the beginning. Sample data proves workflow shape only.
During trial, choose Starter, Growth, or Pro from the app when workflow fit is clear. After expiration, the workspace becomes read-only until a paid plan is selected; FAQ clicks and plan interest never verify a subscription.
Pricing FAQ
Pricing FAQ activity groups commercial objections for copy review. It does not count as plan selection, subscription verification, or approval to add package mechanics.
Blocora packages by managed-unit band and operating complexity, not from page views alone. Starter covers 5-20 units, Growth covers 21-100, Pro covers 101-300, and Custom is reserved for 300+ units or unusually governed rollouts.
Start trial
Starter, Growth, and Pro stay self-serve after the private demo proves workflow fit. Custom remains scoped for 300+ units, migration-heavy rollouts, or unusual governance needs.