BasePro
THE INSTITUTIONAL CASE

The institutional case for the operating system real estate runs on.

If you're evaluating real-estate platforms against enterprise ERPs, or running a Cross-LLC portfolio on Excel and channel-manager glue, this page is written for you.

From 5 properties to 400. Same operating system.

Schedule diagnostic call

DOES THIS SOUND FAMILIAR

Your investment committee meets Thursday. By Monday afternoon you have seven spreadsheets open, three different totals for the same occupancy figure, and an analyst burning the day reconciling exports from three systems before anyone can call the numbers presentable.

Thursday goes well. The numbers tie out. Nobody sees the four hours that made them tie out — only the polished version.

This page is written for the operator who has lived that Monday.

WHY THIS FEELS DIFFERENT

Three lead pillars that change the operator experience.

Institutional buyers in 2026 assume compliance-grade infrastructure exists in any serious platform. What they have not seen is a real-estate-asset-management platform that feels as good to use as the tools their team already trusts.

Intuitive UX

An enterprise solution evolved for 2026, not an ERP translated to the browser.

  • Built for 2026, not 2010

    Every screen on phone, tablet, desktop. No ERP-paradigm relics. Your team uses BasePro like the consumer apps they already trust.

  • Guided tours, not training programs

    First-time users see a walkthrough on every module. New hires onboarded the same day, not week three.

  • Self-serve configuration

    Your team adjusts roles, currencies, country-aware behaviour, notification preferences without filing a consultant ticket.

  • Onboarding in a single flow

    Sign-up → country → payment → org setup → dashboard. Linear. No discovery call required to enable a feature you already paid for.

  • No "training week"

    The interface teaches the work; the documentation backs it.

Days to first booking. Not quarters. Not consulting SOWs.

Easy Team Collaboration

How the team actually works together across roles, entities, and regions.

  • Granular permissions without consulting

    Give your accountant access to finance without giving her access to tenant PII. Set it yourself; revoke it the same day.

  • Inline team management

    Invitations, session visibility, bulk imports, audit-trail filtered views. Onboarding a new property manager is a five-minute self-serve task.

  • Enterprise SSO when the team needs it

    Single sign-on with your identity provider. User provisioning and deprovisioning automated. Plan-gated to institutional tier.

  • Approval workflows that route the right call to the right person

    Multi-step routing for role changes, off-boarding, and sensitive operations. Step-up authentication on the actions that matter.

  • Institutional knowledge stays with the operator

    When staff rotates, the operating record stays put. Five years of inspection notes, vendor history, decision rationale — in BasePro, not in someone's inbox.

When someone leaves, your operation does not start over.

Mobile-First Mission-Critical Insights

High-visibility operational data, available wherever the work happens.

  • The full platform on the phone

    Not a companion app with a feature subset — the 16-module platform, mobile-responsive, on whatever device your team has.

  • Field-first inspections

    Tap the room, photo the issue, dispatch the maintenance order. From the job site, not from the desk after.

  • Operator notifications when work is mission-critical

    Issues your team must see now — failed bookings, missed inspections, expiring documents — surface in the right channel, on the right device, to the right person.

  • Weekend ops without a laptop

    Sign-offs, approvals, escalations work from the phone. The work follows the operator; the operator doesn't follow the laptop.

  • No app-store dependency

    Every patch ships instantly. No "update your app" notice on a Saturday before a check-in.

Your operation in your pocket, current and in sync.

THE STRUCTURAL PROOF

Three layers. In this order. No shortcuts.

Every pillar above rests on the same architecture. The operation runs on a ledger that reconciles. Intelligence is what becomes possible once both layers are clean — not before.

Operations

The 16-module platform that runs the day.

Bookings, leases, inspections, maintenance, banking, finance, compliance — all native, all in one operating system. The work happens here.

Financial

The reconciliation ledger underneath.

Every operational event creates a traceable financial record. Bank feeds, tax filings, multi-currency, Cross-LLC reporting all reconcile against the same ledger.

Intelligence

The substrate that makes future intelligence trustworthy.

The clean event stream and verifiable audit trail are the substrate intelligence runs on. We do not claim AI live today. We claim the ledger underneath that any future intelligence will have to trust.

The operation first. Intelligence second. In that order. No shortcuts.

WHAT BASEPRO DISPLACES

The dual-displacement frame.

Institutional buyers face two paths today: enterprise ERPs adapted to real estate by consulting firms, or stitched point-tools that break at scale. Here is the same eight-axis comparison institutional evaluators actually run — written factually, not snarkily.

Implementation time

Enterprise ERPs
6–18 months (licensing + SOW + consultants + integration + UAT)
BasePro
3–4 weeks (self-serve signup + guided onboarding + country-scoped config)

Implementation cost

Enterprise ERPs
$100k–$500k+ (typical mid-market SAP/NetSuite rollout)
BasePro
Included in subscription; no consulting dependency

Niche fit

Enterprise ERPs
Generic accounting/ops, adapted to real estate by consultants
BasePro
Purpose-built for real estate from day zero — bookings, leases, inspections, maintenance, compliance, banking identifiers, tax engines all native

LATAM regulatory

Enterprise ERPs
CFDI / LFPIORPI / CLABE / SPEI require add-on modules + consultants
BasePro
Native: country registry + CFDI Path B + ARCO workflow + LFPIORPI detection + CLABE/IBAN/SWIFT/ABA in one banking schema

UX era

Enterprise ERPs
Desktop-first paradigms from the 2000s–2010s
BasePro
2026 responsive-first UI: every module renders cleanly on phone, tablet, and desktop. Field-team tap targets, modern bottom-sheet patterns, in-product guided tours.

Customisation model

Enterprise ERPs
Consultant-driven, months per change
BasePro
Self-serve: per-user permission overrides, organisation and per-property config, country-aware behaviour. No consultant SOW required for ordinary configuration.

Audit and compliance

Enterprise ERPs
Module-dependent, often bolt-on
BasePro
Native: every state-advancing action is logged in a cryptographically chained, append-only trail — defensible to your external auditor. NOM-151 10-year retention available. Architecture detail at /platform/security.

Mobile

Enterprise ERPs
Afterthought companion apps with subset features
BasePro
Full platform is mobile-responsive; no app-store dependency; every patch ships instantly

Same operations spine at five properties or four hundred. Institutional governance is additive, not a different product.

TRAINING IS THE PRODUCT

Training, capacitación, and support — at every tier.

Enterprise ERP implementations bill $50,000 to $200,000+ for training alone. BasePro ships guided tours, module walkthroughs, and capacitación at every tier.

Three layers per tier. The amount you pay scales the depth of what's included; the operating system underneath stays the same. Training is what your users learn how to do. Capacitación is ongoing skill-building. Support is help when something breaks.

Starter

Training
Guided product tour, module walkthroughs, Getting Started checklist, contextual mini-tours.
Capacitación
Monthly webinar access, knowledge base.
Support
Email, business-hours response.

Professional

Training
Everything in Starter, plus a personalised onboarding call and role-specific tour tracks.
Capacitación
Monthly webinar + quarterly office hours + advanced workflow templates.
Support
24/7 chat + email.

Portfolio

Training
Everything in Professional, plus Cross-LLC governance walkthroughs and partnership-ops workflow training.
Capacitación
Monthly webinar + quarterly office hours + dedicated specialist for Cross-LLC setup.
Support
24/7 chat + email + named-account support.

Enterprise

Training
Everything in Portfolio, plus white-glove onboarding, custom training curriculum for staff ramp, and certification path.
Capacitación
Quarterly business review + dedicated Academy track + stakeholder workshops.
Support
Dedicated success manager + priority SLA + SSO/SAML support.

Hard support SLAs

When something breaks, the response time is contractual — not aspirational.

P1 critical

< 1 hour

System-wide outage, data integrity issue, security event. Engineering escalation path is hard-wired into the on-call rotation.

P2 high

< 4 hours

Module-specific failure, blocked workflow, high-impact bug. Triaged the same business day.

P3 normal

< 1 business day

Configuration questions, training requests, low-impact bugs. Documented response within one business day.

P1 / P2 SLAs apply at the institutional tier. Earlier tiers receive best-effort response within published support windows.

ON PRICING TRANSPARENCY

Honest pricing is consultative, not opaque.

We don't quote per-property rates publicly because the actual commercial relationship varies by entity count, governance overlay, and SSO tier. Starter is $35/month, self-serve, with adaptive currency. Everything above Starter routes through a sales conversation — not because we're hiding the number, but because the right number depends on questions a contact form can't answer.

MONTHLY WEBINAR

Live walkthrough with the founder, first Thursday of every month.

Audit-trail demo, governance configuration, cross-border setup, and Q&A. Included at every tier — not gated behind a sales call.

DATA RESIDENCY + CROSS-BORDER BANKING

The platform crosses currencies. Your data does not cross borders.

Region-locked from the moment you create your organisation. Data lives in your region's cloud and does not cross borders without your explicit configuration. Banking identifiers — CLABE, IBAN, SWIFT, ABA — live in one schema underneath. Multi-currency, multi-jurisdiction reporting renders the same shape regardless of where the trustee is filing. LPs see the same numbers from Mexico City or New York; the database does not move.

Region-locked at organisation creation

Region selection happens once, at organisation creation. One organisation, one region, no silent egress.

Cross-border banking, single ledger

Trustee filing in MXN, LP reporting in USD, one ledger underneath. Bank feeds reconcile against operational events in any currency.

Country-aware tax engines

CFDI in Mexico, IRS-shaped exports in the United States. Identifier validation runs at entry, not at filing time.

Cross-border reporting, region-bound storage

Your auditor sees one source of truth in one place. The platform crosses currencies; your data does not cross borders.

LIVE REGIONS

Mexico
Live
United States
Live

Live regions. Storage anchored to your jurisdiction. The map is not a roadmap promise — it's the regions BasePro currently serves.

Architecture detail at /platform/security and /platform/iso-compliance.

BUILT FOR EVERY INSTITUTIONAL ROLE

Pick the seat closest to yours.

The operations spine is identical across roles. The view changes; the system underneath is the same.

app.basepro.io

Good morning, Maria

3 items need attention

Active Bookings

23

+3

Revenue (MTD)

$47.2K

+12%

Maintenance

5

2 urgent

Compliance

98%

1 expiring

PRP-104 check-in tomorrow · AC repair in progress · Fire cert expiring in 14 days

CalendarBookingsFinanceMaintenanceCompliance

Property Managers

  • Daily cockpit — bookings, maintenance, exceptions, today's tasks
  • Approve, dispatch, escalate without leaving one screen
  • Mobile-ready: your team operates from the phone
View property-manager case →
app.basepro.io

Portfolio A

4 properties · Exclusive portfolio

Portfolio Bank Account

Chase **** 4821

$42,000

TRR-12

Occupancy

87%

Monthly Rev

$12,400

COA-04

Occupancy

72%

Monthly Rev

$9,800

SUN-19

Occupancy

45%

Monthly Rev

$5,200

COA-22

Occupancy

91%

Monthly Rev

$14,600

Avg. Occupancy: 74%
Portfolio yield: 18.2%

Investors

  • Per-asset returns with monthly distribution detail
  • Read-only portal — view, never edit
  • Branded statements ready for monthly delivery
View investor case →
app.basepro.io

Inspection — PRP-104

In Progress

Floorplan

Room 1
Room 2
Kitchen
Room 3 ●
Bath
Living
📷

Tap to capture photo

Finding: AC Unit — Not Functioning

HIGH

Room 3 · Reported during routine walkthrough

Operations Teams

  • Field-first inspections — tap the room, photo the issue
  • Maintenance orders auto-routed to the right vendor
  • Every action ties back to the asset and booking
View operations case →

Audit Log

Today · 12 events
M
Bookings2 min ago

Maria updated booking #142 — Check-out date changed from Mar 15 to Mar 17

⚙
System15 min ago

System auto-created maintenance order #45 from inspection finding

C
Reports1 hr ago

Carlos generated P&L report for Portfolio A

M
Compliance2 hr ago

Maria uploaded fire safety certificate for PRP-104

⚙
System3 hr ago

System sent auto-reminder for expiring health license

Today: 12 events · This Week: 47 · Flagged: 2

FIBRAs

  • Multi-trust portfolio governance with separated permissions
  • Cryptographic audit trail — defensible to your auditor
  • CFDI Path B, LFPIORPI detection, ARCO 20-business-day workflow
View FIBRA case →
app.basepro.io

Portfolio A

4 properties · Exclusive portfolio

Portfolio Bank Account

Chase **** 4821

$42,000

TRR-12

Occupancy

87%

Monthly Rev

$12,400

COA-04

Occupancy

72%

Monthly Rev

$9,800

SUN-19

Occupancy

45%

Monthly Rev

$5,200

COA-22

Occupancy

91%

Monthly Rev

$14,600

Avg. Occupancy: 74%
Portfolio yield: 18.2%

Investment Funds

  • LP reporting from the same ledger your operators run
  • Capital call tracking with waterfall preference math
  • Cross-border banking identifiers (CLABE, IBAN, SWIFT, ABA)
View fund case →

Audit Log

Today · 12 events
M
Bookings2 min ago

Maria updated booking #142 — Check-out date changed from Mar 15 to Mar 17

⚙
System15 min ago

System auto-created maintenance order #45 from inspection finding

C
Reports1 hr ago

Carlos generated P&L report for Portfolio A

M
Compliance2 hr ago

Maria uploaded fire safety certificate for PRP-104

⚙
System3 hr ago

System sent auto-reminder for expiring health license

Today: 12 events · This Week: 47 · Flagged: 2

Family Offices

  • Generational governance with class-A/B voting overlays
  • Trust separation with consolidated portfolio reporting
  • Compliance-ready audit trail for tax and legal review
View family-office case →
app.basepro.io
🏡

Property Photo

Active

PRP-104

Calle Palmas 42, Zona Hotelera, Cancún, QR 77500

Owner: Portfolio A

4

Rooms

12

Assets

3

Active Bookings

Overview
Calendar
Finance
Maintenance

Recent Activity

Booking #142 confirmed — Rodriguez (Mar 3–7)

2m ago

Maintenance scheduled — AC Unit Repair

1h ago

Inspection completed — All items passed

3h ago

Real-Estate Developers

  • Pre-sale pipeline → unit handoff → operating asset, one record
  • Construction-stage cash flows feed the financial layer
  • Multi-project, Cross-LLC from a single org
View developer case →

PORTABILITY

Your data, your terms.

Three commitments operators ask about before they sign. Each one is contractual, each one is exportable on demand, each one survives whatever happens to BasePro.

Industry-standard exports

Standard CSV / JSON / XLSX exports of your operational and financial data. Banking identifiers, vendor records, lease contracts, cryptographic audit trail — all extractable in formats your auditor and your next operator can read without proprietary tooling.

Acquisition-continuity clause

The contract survives a change of control. If BasePro is acquired, the obligations transfer with the platform — service terms, data residency, support tiers, exit rights. You don't renegotiate from zero with whoever buys us.

Clean-exit grace window

Notice-and-export periods are written into every institutional contract. After termination, read-only access continues so your team pulls the final exports, hands binders to the new operator, and closes the books on schedule. The exact duration is sized to portfolio complexity.

Architectural detail at /platform/security.

TECHNICAL DEEP-DIVE

The validation layer institutional buyers walk in expecting.

Seven architectural commitments. Tier-C operational summaries here; the deeper schema and primitives live on /platform/security and /platform/iso-compliance.

  • Tenant data isolation

    Tenant data is isolated at the database layer. Cross-tenant lookups are not possible, by design. Auditors validating that one organisation cannot see another organisation's properties, vendors, or financial records get a one-line answer: the boundary is enforced below the application code.

    Architecture detail at /platform/security

  • Identity, MFA, and step-up authentication

    Multi-factor authentication on every account. High-risk operations — role changes, session revocations, off-boarding, SSO configuration — require a fresh challenge before they advance. The threshold is operational: actions that change who can see what get re-authenticated even from an already-signed-in session.

  • Audit trail

    Every state-advancing action is logged. The log is cryptographically chained, append-only, and verifiable end-to-end — defensible to your external auditor in writing, not just in policy. NOM-151 ten-year retention available for institutional accounts.

    Architecture detail at /platform/security

  • SOC 2 posture

    SOC 2 Type II — in progress. Target Q1 2027. The compliance roadmap (control coverage today, attestation timeline, what is already in place) is published openly so your committee can score the gap themselves. We are not SOC 2 Type II certified today; we say so on every surface that asks.

    Compliance roadmap on /platform/iso-compliance

  • ISO posture

    BasePro is not ISO-certified. BasePro's architecture is designed to aid your organisation in meeting ISO 27001 / 27701 requirements during your own certification process.

  • Uptime SLA + recovery objectives

    99.9% uptime commitment for the institutional tier. The status page at status.basepro.io is the source of truth — not a marketing page; it reflects the same probes our on-call rotation watches.

    UPTIME
    99.9%
    RPO
    ≤ 1 hour
    RTO
    ≤ 4 hours

    RPO and RTO targets apply to the institutional tier. Earlier tiers receive best-effort recovery within published windows.

  • Live today vs. shipping vs. roadmap

    What is actually in production, what we have committed to ship, and what is roadmap-but-not-committed. Honest separation, not Coming Soon badges that have not moved in a year.

    LIVE TODAY

    • Sixteen-module unified platform (Operations + Financial + Intelligence)
    • Cryptographically chained audit trail with NOM-151 ten-year retention
    • Multi-currency banking schema (CLABE / IBAN / SWIFT / ABA in one model)
    • Cross-LLC consolidated reporting foundations
    • Mobile-responsive web platform across every module

    SHIPPING — NEXT 6 MONTHS

    • Insurance claim evidence compilation — Q3 2026
    • Reconciled receivables flowing from bookings — Q4 2026
    • Onboarding redesign across operator personas

    ROADMAP — NOT COMMITTED

    • SOC 2 Type II completion — target Q1 2027
    • Tax compliance automation — target Q1 2027
    • Reconciled disbursements pipeline — target Q2 2027
    • Native iOS / Android apps — the responsive web platform serves this need today
    • Additional fintech rails beyond current Mexico / US scope

INSTITUTIONAL FAQ

Twelve questions every committee asks. Twelve straight answers.

The questions sales hears most often from FIBRAs, fund GPs, family-office CIOs, and developer ops leads — answered at the depth institutional evaluators expect.

  • Why now? We've been on Yardi / Excel for years.

    Two reasons. First — the architectural pieces institutional buyers need are now live: cross-border banking schema, immutable audit trail, multi-currency reconciliation, multi-jurisdiction reporting. Second — the alternative is more visible than ever. Yardi rollouts run 12–18 months at $250k–$500k; BasePro is 3–4 weeks, implementation included.

  • What if our portfolio outgrows BasePro?

    Same operations spine at five properties or four hundred. Institutional governance — committee approval flows, cryptographic audit, Cross-LLC rollup — is additive on top of the same spine. There is no separate institutional product to migrate to when you scale. Per-user permission overrides, per-property configuration, country-aware behaviour are all self-serve.

  • What happens if BasePro gets acquired?

    Vendor-viability is part of our institutional contract: data portability commitment in writing, acquisition-continuity clause that survives change-of-control, clean-exit grace window. The architecture matters here too — your data is in standard formats, your audit trail is exportable as a chain-of-custody record, your operational state is reconstructable from the export. We're building this so that even in the worst-case acquisition, your team can continue running.

  • How do we migrate off if it doesn't work?

    Standard CSV / JSON / XLSX exports of your operational and financial data. Cryptographic audit trail exports as a chain-of-custody record. Banking identifiers, vendor records, lease contracts — all extractable. We support a parallel-running grace window so your team validates the new system before cutover.

  • What's the contract termination clause?

    Notice-and-export clause in every institutional contract. 60-day notice, configurable up to 90 for larger portfolios. Data export delivered before service termination, not after. The full clause is in the standard contract — your legal team can review before signing.

  • What about enterprise pricing bands?

    Three published tiers. Custom band for institutional accounts based on entity count, governance overlay needs, and SSO tier. Pricing is consultative for portfolios above the published-tier ceiling; quote delivered within 5 business days of intake. The custom tier never gates operations-spine capability behind portfolio size — it only adds institutional governance overlays.

  • Tell me the data residency story specifically.

    Region selected at organisation creation. Storage anchored to that region; no silent egress. Cross-border reporting renders the same shape regardless of where the trustee is filing. Architecture detail at /platform/security.

  • Do you support enterprise SSO and provisioning?

    Enterprise SSO via your identity provider, available at the institutional tier. Automated user provisioning and deprovisioning with a security audit trail. Step-up authentication on consequential changes. Architecture detail at /platform/security.

  • Can we migrate from our current ERP?

    We support migrations from Yardi, SAP Real Estate, MRI, Oracle NetSuite, and the spreadsheet-and-channel-manager stack. Standard intake: data extraction → mapping review → parallel-running window → cutover. Typical timeline: 3–4 weeks for portfolios under 50 entities, 6–8 weeks above that. Implementation cost is included in the institutional tier.

  • What's the policy on custom reporting?

    Six standard reports cover most institutional needs: investor statements, regulatory disclosures, Cross-LLC rollups, audit-trail exports, occupancy/NOI snapshots, distribution-cycle records. Custom reports are scoped at the institutional tier on a quarterly cadence. Standard exports are CSV / JSON / XLSX; custom presentations can be branded for your committee.

  • How do you handle Cross-LLC billing?

    Cross-LLC billing is the default at the institutional tier: separate invoices per legal entity, consolidated invoices for parent organisations, tax-ID handling per jurisdiction (CFDI in Mexico, IRS-shaped exports in the US, equivalents in supported regions). Your finance team picks the structure at organisation setup; the structure can change later.

  • Who can't BasePro serve?

    Three categories. First — non-real-estate asset managers (we're PropTech-vertical-bound by design). Second — operators below the operational-readiness threshold (you need at least one designated admin and one operations person). Third — operators in jurisdictions we don't yet serve (current: Mexico, US; expanding regionally). Honesty here saves both teams a quarter.

READY?

Three ways to take the next step.

Pick the path that fits where you are. Each one reaches the same team.

Schedule a diagnostic call

Thirty minutes. Walk us through your portfolio, the systems you're trying to replace, and the constraints you're operating under. We'll tell you what BasePro can do today, what's on the roadmap, and where we're not the right fit.

Book the call

Enterprise contact

FIBRAs, funds, family offices, developers. Direct line to our institutional sales conversation. Custom pricing, dedicated implementation, named-account support tier.

Talk to enterprise sales

Monthly institutional webinar

Live walkthrough with the founder. Audit-trail demo, governance configuration, cross-border setup, and Q&A. First Thursday of every month.