The PropTech
Advisory
Build a brief

Independent multifamily technology advisory

Make proptech
work in the
real world.

For founders building for multifamily, and operators choosing what to adopt. Start with how the work actually gets done.

THE OPERATOR'S VIEWPRODUCT / PEOPLE / PROCESS

Our starting point

Understand the workflow. Remove what doesn’t need to happen. Automate what repeats. Leave judgment with people.

Advisory

Get clear before
you commit.

Most technology decisions aren’t really about the feature list. They’re about how a new tool changes who does the work, where the data lives, and what happens when the process breaks.

For founders

Build for the job, not the demo.

Find the buyer, the user, and the workflow your product can improve. Get a short decision memo on what fits, what could stall adoption, and how to run a pilot an operator can actually own.

  • Product and workflow fit
  • Pilot scope, measures and decision criteria
  • Integration and rollout questions operators will ask
Build a founder brief

For operators

Choose what fits. Know how it goes live.

Assess the work first, then compare vendors against your real requirements. Make migration, training and ongoing ownership part of the decision.

  • Requirements and a vendor scorecard
  • Implementation and data readiness
  • Handoff, exception and sign-off planning
Build an operator brief

The good, the bad & the ugly

The field journal.

Practical tests and independent product reviews. Reviews will distinguish what was tested from what a vendor says. Paid placements, when offered, will be labeled and kept separate from editorial judgment.

Field note · Leasing operations

Who actually talks to the renter?

A leasing automation can finish a task in one system without handing the work to anyone in the next. Here’s a test that shows where responsibility lands.

Read the handoff test

Run one synthetic leasing journey.

In a sandbox, have a made-up prospect ask about a unit after hours, book a tour, reschedule it, then ask for a human to confirm a detail the system can’t answer. Run the same scenario once through a listing marketplace and once through a direct property inquiry. Don’t use real applicant data or send real messages.

  1. Follow the record. Does the same prospect and appointment stay linked across the tools? Is the old slot freed?
  2. Follow the responsibility. Does one clearly assigned person get the request and the context to act, without duplicate follow-ups? Time the first substantive human response, not the automated acknowledgment.
  3. Check the renter’s view. Does the confirmation reflect the actual appointment? Does the renter know what happens next?

Pass: one prospect, one current appointment, and one named owner for the exception. If one of those is missing, solve that before scaling.

In development

Better ways to find
the right partners.

An opt-in network for operators, founders and specialists interested in working together. Participation and submissions aren’t open yet.

Partner network

A place to signal interest in pilots, integrations and collaboration, without a public directory of anyone who hasn’t opted in.

Paid placements

Clearly marked sponsorship opportunities are planned. Paying for exposure won’t buy a review, rating or recommendation.

The next step

Put the problem
on one page.

Choose the perspective that fits. Copy the starter brief into your own notes and make it yours. Nothing is submitted or stored here.

Founder brief

Who uses the product, and who buys it?
Which workflow are we trying to improve?
What is the current workaround?
What does a first pilot need to prove?
Which integrations or handoffs must work?
What would make the operator say no?