Apartment List~4 min read

What happened when we stopped writing off a $50k segment?

SMB and mid-market had no platform, reporting, or internal advocate. When enterprise growth stalled, it had four weeks to become a second engine.

  • Role: Product design and research
  • Timeline: 4 weeks
  • Team: 1 engineer, me (design + product)
  • Impact: $50k → $350k revenue
  • Platform: Web
The SMB ad-tech dashboard displayed on a laptop beside a swimming pool.

How the segment got another look

For years, Apartment List treated small and mid-market landlords as noise. Enterprise was where the revenue came from, everyone knew it, and nobody had revisited that assumption lately. Then enterprise growth stalled, and the company needed a second engine in four weeks.

This segment had no platform, reporting, or workflow of its own. We shipped a listing MVP instead of the proposed full property management system, then rebuilt reporting around the decisions partners needed to make, not everything the database could show. Run-rate revenue moved from $50k to $350k.

What I owned

I owned

  • Iterative research with 6 subject matter experts and 6 small-business partners, plus Sales, revenue, and Finance stakeholders
  • The argument that SMB/MM was a growth channel rather than noise
  • The build-versus-buy audit, and the case for a lean MVP
  • The reporting rebuild
  • Product direction after the PM left, including holding the metrics

Shared with the engineer

  • What was feasible in four weeks
  • The anonymization that made the market view shippable at all

Problem

What if the segment was not low-value? What if we had simply never built anything that treated it as valuable?

Four things were true inside the company, and none was a product problem. We poorly understood the segment’s supply-side drivers. Its core workflows were logged as edge cases. It was formally flagged as low-value. And no internal story challenged any of that.

The result was guesswork on both sides. Partners could not see how their listings performed, and the company could not see what those partners were worth.

Before

0%

Retention

0%

Churn

0%

Reporting adoption

Retention and churn are both as recorded in the source deck. They do not reconcile as complements, which means they measure different populations or different periods, and the labels do not currently say which.

Can an MVP prove the segment?

Could a listing MVP do the job of a property management system?

The choices were a full property management system, buying and integrating an existing one, or a lean listing MVP. With four weeks and one engineer, an audit of core versus differentiating features put the full system at multiple quarters with heavy technical-dependency risk.

We chose a lean, testable MVP to establish viability within a month. An underserving MVP could confirm the belief that the segment was not worth serving, with a negative result read as proof rather than a scoping artefact. We focused on the one workflow partners called blocking in interviews, so a null result would speak to demand rather than coverage. Run-rate revenue moved from $50k to $350k in the segment the company had written off.

The SMB/MM acquisition and retention funnel.
We mapped where the segment leaked before building anything. That map set the MVP scope.

Privacy changed the market view

What was left after privacy ruled out the named market view?

We could show named competitive performance, anonymized market benchmarks, or no market view. The first version exposed identifiable information about partners, carried real performance cost, was hard to implement, and exposed personal data they had no right to see; shipping it would trade a segment problem for a legal one.

We anonymized the view and accepted the weaker feature. Anonymized benchmarks are a commodity, while the named version was why a partner might have opened the tool weekly. Nothing recovered that difference. The feature shipped without the legal exposure or the first version's performance cost.

Four questions, not every metric

Why not let partners configure the dashboard?

The options were a configurable dashboard, metric-per-chart reporting, or four fixed views answering named questions. The PM left mid-project and teams disagreed about which metrics mattered; configurability would defer that disagreement into the product instead of settling it.

We built four views: trend clarity, comparative performance, actionable recommendations, and retention-risk signals. Fixed views are wrong for anyone whose question is absent, and no PM remained to arbitrate the list, so the four came from the twelve research participants rather than internal preference. Reporting adoption moved from 2% to 75%; the first iteration was rejected as costly to implement and hard to understand, while the second shipped.

The rebuilt reporting view with trend charts and comparative metrics.
What shipped: trend, comparison, and recommendation in one view. The first iteration held the same content, but was rejected for build cost and legibility.

What changed

$0k

Segment revenue

up from $50k

0%

Reporting adoption

up from 2%

0%

Renewals

up from 20%

Targets I set and reported against. Held through the rest of my time at Apartment List, to 2024. Revenue is run-rate rather than cumulative. Still missing: which system produced each figure, and the account counts behind the two percentages.

The feature partners might have opened weekly did not ship

The named market view was the feature. Anonymized benchmarks are a commodity; the named version was what a partner might have opened weekly on its own merits. Privacy exposure ruled it out, correctly, so we shipped the weaker version.

The $50k-to-$350k move is real, but I cannot separate the product from the market around it. Enterprise growth stalled while this work was underway, giving the company a reason to care about a segment it had ignored, and Sales had reason to sell into it. I do not know how much of the change belongs to either. The revenue figure should not settle that question.

Sam Cusano