Skip to content

Engagement 05 · Real estate · Proptech operating system

A property operation became the proving ground for a connected operating system.

Tenant 365 is founder-led software built from the operational reality of running rental property. The public leasing experience, the CRM pipeline behind it, the internal operations platform, the integrations, the automation, and the compliance program were designed as one evolving system around a real portfolio.

  • 2026 — Current
  • Founder-led platform
  • Real estate · Proptech
  • Public experience + Ops

Live platform

tenant365.co

Tenant 365 website homepage.
The public leasing experience — one surface of a system that also runs operations, integrations, automation, and compliance.
Visit Tenant 365

At a glance

Public platform launch
Jun 4, 2026

tenant365.co

Ops platform published
Aug 5, 2026

ops.tenant365.co

Connected operating model
Website → CRM → Ops

One system across leasing and operations

Integration engineering
Test-driven

Permission-aware integration work with an accepted test suite

Dates reflect published platform milestones. Nothing here claims revenue, occupancy, conversion, or customer scale; the record is one of systems built, connected, and operated against a live rental portfolio.

01 — The operating reality

Property operations rarely fail because there is no software. They fail between the software.

A leasing site here. Inquiries in an inbox. Tours in a scheduler. Lease data in a tenant platform. Cleaners on WhatsApp. Check-ins and check-outs in someone's head. Compliance in a folder. Each tool works. The operation still leaks at the seams.

Tenant 365 was built from inside that problem — a founder-led platform whose requirements came from actually running the portfolio, not from a product brief.

The design decision was to become the connective layer rather than attempt to replace every specialist tool that already earns its place.

  • Fragmented by default

    Leasing, scheduling, documents, payments, and messaging each live in a different system with a different notion of the truth.

  • Handoffs are manual

    The work between tools — re-entry, chasing, reminding, reconciling — is where operator time actually goes.

  • Context disappears

    A lead's source, a unit's turnover state, and a compliance obligation rarely sit in the same place.

  • Connective layer

    Tenant 365 orchestrates the specialist tools and owns the operating model that runs across them.

02 — The connected system

One path from a stranger's first click to a turned-over unit.

The public experience, the pipeline, the leasing record, the operating surface, the automation, and the compliance layer are stages of a single system — with purpose-built tools attached where they are genuinely better than rebuilding.

Build around the tools that already work.

  1. 01

    Public experience

    Inventory, galleries, 360° tours, mobile inquiry

  2. 02

    Lead / CRM

    Blue pipeline, UTM and persona fields, stage progression

  3. 03

    Leasing data

    Tours, documents, and lease records in purpose-built tools

  4. 04

    Ops

    Calendar, checkouts, cleaner workflow, unit status

  5. 05

    Automation

    WhatsApp workflows, notifications, daily checkouts

  6. 06

    Compliance

    Portfolio scope, coverage, registration workflows

Specialist tools orchestrated

  • BlueCRM and leasing pipeline
  • LunacalGuided and self-guided tours
  • InnagoLeasing and tenant records
  • PandaDocDocuments and lease packets
  • Railway · Evolution APIWhatsApp operations
  • KeycafeIntegration-ready · feature flag off

Leasing pipeline

  1. New Inquiry
  2. Contact Attempted
  3. Qualified
  4. Follow-Up
  5. Lease Sent
  6. Lease Signed
  7. Converted
  8. Dead

Lead records carry source, medium, campaign, and persona, so leasing outcomes can be traced back to the demand that produced them.

03 — Two surfaces, one operating model

A customer product and an operator product, built as one system.

Most proptech work is one or the other. This engagement carries both — and they are designed against the same data, the same states, and the same day.

The leasing surface

tenant365.co

Tenant 365 public leasing website.
  • Furnished and unfurnished rental inventory
  • Property cards, photo galleries, and 360° virtual tours
  • Furnished and tour-state overlays with availability presentation
  • Mobile-first inquiry forms and clear leasing calls to action
  • Guided and self-guided tour scheduling through Lunacal
  • UTM-aware lead capture feeding a structured pipeline
Visit Tenant 365

The operating surface

ops.tenant365.co

ops.tenant365.co

Internal · operating surface

Operations calendar

Unit · check-in / check-out · reference ID

Status states

Paid · Unpaid · Overdue · Canceled

Cleaner workflow

Daily assignment and turnover readiness

Notifications

All · Unread · Acknowledged · Resolved · Dismissed

Systems + logs

Operational health and polling visibility

Compliance

Property and unit scope, coverage and registration

Interface abstraction, not a screenshot. The operating surface holds live property data and is not reproduced here.
  • Operations calendar with unit, check-in and check-out, and reference IDs
  • Status badges across Paid, Unpaid, Overdue, and canceled events
  • Cleaner workflow supporting the people doing daily turnovers
  • Notification states: All, Unread, Acknowledged, Resolved, Dismissed
  • Systems and logs views for operational health and polling
  • Compliance scope, coverage, and registration workflows

04 — Engineering for real operations

Software judged by a Tuesday, not a demo.

This platform runs against a live portfolio. A missed checkout, a broken lease sync, or a notification that never fires is an operational failure, not a bug report. That standard shapes how the integration work is built.

Engineering evidence · Innago integration

691 passing tests

The integration phase was accepted with a full passing suite alongside its migrations and permission controls. The number matters less than what it represents: leasing data moving between systems under tests that fail loudly before an operator ever sees a wrong unit, a wrong date, or a wrong balance.

Test-driven, permission-aware integration work · migrations, row-level security, and RPC-controlled access accepted with the phase.

  • Leasing data integrity

    Innago sits in the live operating stack; the integration is built so records reconcile rather than drift.

  • Messaging as infrastructure

    WhatsApp operations run through the Evolution API on Railway, with health and polling visibility and a 10AM “Today's Checkouts” workflow.

  • Documents and signature

    PandaDoc carries the document and lease stack rather than a rebuilt equivalent.

  • Controlled rollout

    A Keycafe webhook receiver exists and is integration-ready, held behind a feature flag that is currently off. PayPal OAuth, payouts, and a matching queue are planned, not live.

  • Compliance as a layer

    An evolving operational program covering audit and capture, desktop and mobile surfaces, taxonomy, property and unit scope, and registration and approval workflows.

Timeline

  1. June 4, 2026

    tenant365.co launches

    The public leasing experience goes live: furnished and unfurnished inventory, galleries, 360° virtual tours, availability presentation, and mobile-first inquiry.

  2. June — July 2026

    Leasing pipeline and demand operations

    Tour scheduling through Lunacal, UTM-aware lead capture into the Blue CRM pipeline, inventory and leasing UX iteration, and campaign landing pages with GA4/GTM, Clarity, Meta, and TikTok measurement.

  3. August 5, 2026

    ops.tenant365.co published

    The internal operating surface goes live: operations calendar, check-in/check-out states, cleaner workflow, payment status, notifications, and system visibility.

  4. August 2026

    Integration and compliance deepen

    Innago integration work reaches an accepted, test-driven state with migrations, RLS, and RPC controls; the compliance program completes audit, capture, desktop, mobile, and taxonomy work.

  5. Current

    Continuous stewardship

    The connected system keeps evolving against actual operating needs rather than a fixed product roadmap.

What this engagement demonstrates

A product built from operations, not assumptions.

  • 01

    Product built from operations

    Requirements came from real leasing and property-management workflows rather than a speculative roadmap.

  • 02

    Integration over replacement

    Purpose-built tools are connected and orchestrated instead of rebuilt for the sake of owning them.

  • 03

    Public + internal system design

    One engagement spans customer-facing leasing experience and the operational software behind it.

  • 04

    Continuous stewardship

    The platform keeps being iterated against live business needs, with rollout controlled by feature flags.

Start a conversation

Have an operation that needs a connected system?

Tell us what is changing, what is getting in the way, and what the digital system needs to accomplish.

Now Reviewing Select EngagementsSenior-led · Limited capacity

Choose your next move

Project inquiry

Step 01

Start with the Essentials

No sales maze. Your inquiry goes directly to the person who will lead the work.