Baltimore is a renter's city built out of other people's rowhouses. More than half the occupied housing in the city is rented, and the great majority of those units sit in small buildings owned by small operators — not REITs with an IT department, but people running thirty or eighty doors scattered across a dozen neighborhoods. Property management software is happy to serve them, at a price that is quietly metered per door and payable forever. What it will not do, at any price, is understand that a rowhouse in Patterson Park needs a city rental license on one clock, a state lead registration on another, and a housing-authority inspection on a third. This is a guide to that gap: what renting really costs once you count the minimums and the per-payment fees, why the compliance layer is the part a national platform will never model, and when a custom system you own outright — rent roll, maintenance, turnovers, owner reporting and a compliance calendar that knows your actual doors — becomes the better buy. Fixed price, shipped in weeks.
A renter's city, built one rowhouse at a time
Baltimore's housing stock tells you almost everything you need to know about how property management works here. Something over half of the occupied housing in the city is renter-occupied — roughly 137,000 renter households — which already makes this a more tenant-heavy city than most of its peers. But the fact that actually shapes the daily work is the shape of the buildings. Baltimore is a majority-rowhouse city in the most literal sense: single-family attached homes make up just over half of every housing unit in it. This is not a city of towers. It is whole blocks of rented rowhouses and two- and three-unit conversions, and it is old — more than forty percent of the city's housing was built in 1939 or earlier.
Those facts — attached houses, old houses, a great many of them — produce a very particular kind of business. The landlords and managers we meet here are almost never running one property with two hundred doors. They are running scattered-site portfolios: forty units across thirty addresses in a dozen neighborhoods, a few of them across the line in Baltimore County, one or two in Anne Arundel. Every address has its own quirks. This one has a shared water meter with the house next door. That one has a lockbox and a temperamental back gate. This block floods. That property has a boiler that needs looking at every October, and the one three doors down has a lead certificate that has to be refreshed before anybody new moves in.
National property management software is not designed for that shape of business, and it is worth being clear about why. It is designed for the statistical middle of the American rental market — a garden apartment complex in a Sun Belt suburb where two hundred units are identical, sit under one roof, and answer to one set of county rules. Almost every product decision follows from that assumption. Scattered-site portfolios in an old, jurisdictionally complicated Mid-Atlantic city are an edge case to those platforms, and edge cases are where the workarounds start.
Where the rented platform starts to pull against you
Let me be fair to the tools first, because they are genuinely good software and most portfolios should be on one. AppFolio is a serious platform that runs a great many professional management companies well. Buildium is capable and reasonably priced for small and midsize operators. DoorLoop is well-liked, Yardi Breeze is solid, and for a landlord with a handful of doors something as simple as Innago or TurboTenant is very often the correct and cheapest answer. If one of these fits the way you lease, collect, maintain and report, you should keep it, and we will tell you so on a call. Nobody should commission custom software to do what a subscription already does well.
The trouble is what "fits" is doing in that sentence. In property management the fit rarely breaks dramatically. It breaks in the same handful of quiet places, and once you have seen a few portfolios you start to recognize them immediately.
The first is the owner statement. If you manage for third-party owners, the monthly statement is the single most visible thing your business produces — it is the document that either makes an owner trust you or makes them call. It is also, reliably, the thing managers tell us they rebuild by hand. The platform produces something technically accurate and unreadable, so somebody exports it, reshapes it in Excel, adds the notes the owner actually asked for, and sends a PDF. That is a skilled person spending two or three days a month reformatting a report the software was supposed to produce.
The second is maintenance triage. A tenant texts a photo of a leak. Somebody decides whether it is urgent, whether it is the tenant's responsibility, which of your three plumbers is closest and cheapest, whether the owner needs to approve the spend, and whether this is the fourth time that unit has had the same problem. Almost none of that decision-making lives in the software. It lives in a group chat and in one person's head, and the work order gets created afterwards as a record of a decision that was made somewhere else.
The third is the turnover. A unit going from notice to re-rented is the most expensive week in property management, and it is a genuine pipeline — notice given, inspection scheduled, deposit reconciled, make-ready scoped, contractors booked, lead certificate refreshed if the building is old enough, listing published, applications screened, lease signed, keys handed over. Most platforms model perhaps half of that and treat the rest as free-text notes, so the real turnover process ends up on a whiteboard or in a shared spreadsheet that only works because one person maintains it.
And the fourth is compliance, which is important enough that it gets its own section below. What all four have in common is the tell we look for in every industry we write about: you are paying a person to bridge the gap between how the software works and how your business actually works. When that becomes a real slice of somebody's week, you are already buying custom software — you are just buying it in salary, and getting nothing you own at the end. If you want the general version of that decision, we wrote a whole framework on custom build versus SaaS versus no-code; the short version is that it depends far less on how big you are than on how particular your operation is.
What renting property management software really costs
Property management platforms almost universally charge per unit, per month. As a headline that sounds fair — it scales with the business, and small portfolios pay less. The complications sit underneath it, and they are worth understanding precisely, because this pricing model is unusually good at growing faster than you notice.
The first complication is the minimum. Nearly every per-unit platform sets a monthly floor, and below that floor the advertised rate is fiction. AppFolio is the clearest illustration. Until the fall of 2024 it published its rates openly: $1.49 per unit per month on the Core tier, against a $298 monthly minimum and a 50-unit minimum portfolio. Divide one by the other and the floor tells you something the pricing page never did — $298 at $1.49 a unit is exactly 200 units. You pay for two hundred doors until you actually have two hundred doors.
For a Baltimore operator, that gap is the entire story. At AppFolio's own 50-unit entry point, $298 a month works out to $5.96 per door — four times the advertised rate. Propertyware runs the same structure at $1.00 per unit against a $250 floor, and bills in 50-unit increments regardless of your real door count. Yardi Breeze is the gentlest of the three, at $1.00 per residential unit against a $100 minimum. Here is what those floors actually cost a portfolio of a given size.
| Portfolio | AppFolio Core $1.49/unit · $298 floor | Propertyware Basic $1.00/unit · $250 floor | Yardi Breeze $1.00/unit · $100 floor |
|---|---|---|---|
| 25 doors | not sold under 50 units | $250 → $10.00/door | $100 → $4.00/door |
| 50 doors | $298 → $5.96/door | $250 → $5.00/door | $100 → $2.00/door |
| 100 doors | $298 → $2.98/door | $250 → $2.50/door | $100 → $1.00/door |
| 200 doors | $298 → $1.49/door | $250 → $1.25/door | $200 → $1.00/door |
On AppFolio you reach the advertised rate at two hundred doors, and not a moment sooner. Everywhere below that, you are paying for units you do not own. That is not a criticism of AppFolio, which is straightforward about being built for professional managers at scale — it is simply a mismatch, and it is the most common one we see in this city.
Worth noting about those AppFolio figures: they are the last ones the company published. In September 2024 it removed its printed pricing altogether, and a footnote that had read "$298 minimum spend per month, and 50 unit minimum" became "Minimum spend and 50 unit minimum apply. Contact us for details." You can draw your own conclusion about which direction a price tends to move once it stops being printed.
The second complication is that the subscription is rarely the whole bill, and the extras attach to the thing you do most. Buildium's entry tier starts at $62 a month, which is genuinely reasonable — but on that tier it charges $2.35 for every incoming electronic rent payment. A hundred doors paying rent by bank transfer is $235 a month in transaction fees on top of the $62, so the payments line quietly grows to nearly four times the software line. Add $99 for each bank account that receives rent, $5 per document for e-signatures, screening fees and whatever modules you end up needing, and the real monthly number lands well above the advertised one.
The third complication only bites when you try to leave: on several of these platforms, getting your own data out is a paid upgrade. Buildium's open API sits on the Premium tier, a $400-a-month floor. Propertyware charges an extra dollar per unit per month for API access — a 100% surcharge on its base rate. AppFolio's 2023 feature sheet listed data export as a Plus-tier feature and the database API as Max-only. Your rent roll and lease history are the operating record of your business, and on a rented platform the price of reading them programmatically is set by somebody else.
None of this is scandalous — it is how the category prices, and these platforms deliver real value for the money. It is also worth saying plainly that the flat-rate end of the market exists precisely because of all this, and for a small landlord it is very often the right answer: RentRedi starts at $5 a month for unlimited rentals, and Innago is free. A sixty-door landlord weighing $5 a month against a $298 minimum is not facing a close call, and we would not pretend otherwise. We took a software quote apart line by line in a separate piece on what a custom app really costs, and the same logic runs in reverse for a subscription: the sticker price is only ever part of the picture.
The point is narrower than "subscriptions are bad." It is that the meter is attached to the exact thing you are trying to grow, and none of that spending accumulates into anything you own. A custom system inverts that arithmetic: you pay once, you own it outright, and the only ongoing cost is hosting plus whatever changes you actually choose to make. Adding your fifty-first door costs nothing. The software stops being a function of your growth and becomes an asset on your side of the ledger.
The question everyone asks first: what about the license, the lead cert and Section 8?
This is the part of the article I would keep if I had to throw the rest away, because it is the thing that makes Baltimore genuinely different from the market these platforms were built for — and it is the reason a custom system can be worth building here at portfolio sizes where it would not be worth building in, say, suburban Texas.
A Baltimore landlord is not managing one compliance calendar. They are managing at least three, on different clocks, run by different authorities, with different consequences for missing them.
Start with the city. Baltimore City requires every non-owner-occupied property to be registered annually, due on the first of January, and requires a rental license backed by an inspection from a state-licensed home inspector registered with the city. Registration fees are charged per unit — currently $30 a unit for one- and two-unit properties and $35 for multi-family. And the licensing rules just changed underneath everybody: as of January 2026, the old tiered system, under which a clean compliance record earned you a longer license, has been replaced by a flat two-year term for everyone, and licenses no longer transfer when a property is sold. A new owner now has sixty days to apply for their own.
The consequence of letting any of it lapse is not a polite reminder. Since 2019 an unlicensed rental in Baltimore City has no legal right to collect rent, and to win a failure-to-pay-rent case a landlord has to plead and prove a valid license and put the number in the complaint. It is also a rule a great many people are quietly on the wrong side of: the city estimates there are more than 66,000 rental properties here, and by its own reckoning more than 40% of the properties expected to be licensed are not. For a scattered-site portfolio this is not one date in a calendar. It is one date per property, times thirty properties, each with its own inspection to schedule and its own renewal to file.
Then add the county. Baltimore County is a completely separate jurisdiction from Baltimore City — they have been separate governments since 1851, which surprises people who are not from here — and it runs its own rental registration and licensing regime, on its own multi-year cycle, with its own per-unit fees that differ depending on whether the property is owner-occupied. A portfolio that straddles the city line, which a great many do, is therefore running two entirely independent licensing calendars with different rules, different forms and different renewal dates.
Then add the state, which is where the housing stock comes back to bite. Maryland's lead law covers every rental built before 1978 — it was expanded from pre-1950 properties back in 2015 — and in this city that is not a niche category but the overwhelming majority of the market: roughly seven in ten of Baltimore's renter-occupied units sit in buildings that predate it. Owners of affected units must register them with the Maryland Department of the Environment within thirty days of purchase and keep that registration current. That fee changed in January 2026 too, from $30 per unit annually to $75 per unit covering two years — worth knowing, because most of what you will read online still quotes the old number.
The operationally painful part is not the registration, though. It is that the property must meet the lead risk-reduction standard and pass a lead-dust test by an accredited inspector at every change of occupancy. That is not an annual task you can batch. It is attached to every single turnover, in an old-stock portfolio where turnovers happen constantly, and it sits directly on the critical path between one tenant moving out and the next one legally moving in.
And for many Baltimore landlords there is a fourth layer, because housing-choice vouchers are a significant part of this market. A voucher tenancy means a housing-authority inspection on its own schedule, an annual recertification that can change the rent split, and — the detail that breaks most software — a single month's rent arriving as two separate payments, from two different payers, often on two different dates. Generic platforms model that badly. They tend to treat it as one rent charge with a partial payment against it, which is why voucher reconciliation is so often the spreadsheet that lives next to the property management system.
And then there is ground rent, which is close to a perfect illustration of the whole problem. In Baltimore the land beneath a rowhouse can be owned separately from the house standing on it, with the owner of the house paying a small sum every year to whoever holds the ground lease — a form of tenure that has largely died out everywhere except Maryland. It is a real obligation with real paperwork and real consequences if it goes unpaid, and there is not a national property platform on the market with a field for it. Every Baltimore operator who deals with ground rent tracks it somewhere off to the side.
Now put yourself in the position of a national software vendor. Would you build first-class support for Baltimore City's licensing cycle, Baltimore County's separate one, Maryland's lead registry and the local housing authority's inspection calendar? Of course not. It would be a substantial engineering investment that is worthless to your customers in Phoenix and Atlanta, and you have a thousand higher-value features to build. This is not a failing of AppFolio or Buildium. It is a rational product decision that happens to leave every Baltimore operator holding the same spreadsheet.
That spreadsheet is the specification. A custom system can attach the real obligations to the real doors — this property's city license expires in March, this one's MDE registration renews in December, this unit needs a lead clearance before the next tenancy starts, this one has an HQS inspection booked — and then do the one thing a spreadsheet cannot, which is tell you about it before it becomes a problem rather than after. That is a modest amount of software. It is also, for a portfolio of any size in this city, the difference between compliance being a background process and compliance being the thing that ruins somebody's February.
What custom property management software costs in Baltimore in 2026
This is what everybody actually wants to know, and the honest starting point is that the numbers you will find online are enormous and mostly unhelpful. Development shops will tell you a custom property platform starts around fifty or sixty thousand dollars and runs well into six figures, with a fifth of the build cost again every year for maintenance. Those numbers are real, and they describe a real way of working — but the price is a description of how the work is staffed rather than a property of the software.
A traditional agency price is high for reasons that have little to do with your portfolio. You are renting a team — a project manager, a couple of engineers, a designer, an account lead — each holding a slice of the context, each billing by the hour, plus the overhead of every handoff between them. We think that model is broken for work at this scale, so we do not use it. We put one senior builder with AI in the loop across the whole job, freeze the scope before we start, and attach a fixed price to it: a real number you agree to before any code is written, not an estimate that drifts through the fall. For most Baltimore portfolios it lands like this.
| What you're building | What it is | Fixed price | Timeline |
|---|---|---|---|
| Prototype Sprint | One core flow — a maintenance-request intake or a clean owner statement, clickable and deployed | $3,500 | ~1 week |
| Tenant Portal / Online Store | A branded portal for applications, rent payments, documents and maintenance requests | from $6,000 | 1–2 weeks |
| Custom App / Internal Tool | The leasing, maintenance or inspection tool your team runs on, usable on a phone in the field | from $12,000 | 2–4 weeks |
| Operations System | Rent roll, maintenance, turnovers, compliance and owner reporting end to end | from $12,000 | 2–5 weeks |
Every one of those is a fixed price against a fixed timeline — half to start, the balance when it ships — and you own every line of the code, the keys and the accounts at the end. The full breakdown of what is and is not included lives on the pricing page. The two packages most portfolios land in are the Custom App and the Operations System, because what a management business needs is rarely one screen — it is the rent roll, the work orders, the turnover pipeline and the compliance calendar working as one system instead of a platform plus four spreadsheets. And the Tenant Portal is the same engine as our online store package, pointed at a different job: applications, payments, documents and requests under your own brand, on your own domain, owned outright rather than rented per door.
What we'd actually build
"Custom property management software" sounds like a blank check when it is really a short list of quite specific things, so it helps to be concrete about what these budgets buy.
The most common first build is the maintenance and work-order system, because it is where the daily chaos lives. Tenants report a problem through the portal with photos attached, the request lands in a triage queue with the unit's history beside it, somebody assigns it to the right vendor, the owner-approval threshold is applied automatically, and the whole thread — photos, quotes, invoices, sign-off — stays attached to the unit rather than scattered across three phones. It is the same principle we describe in the piece on internal tools teams actually adopt: software that mirrors the real workflow gets used, and software that asks people to change how they work gets quietly worked around.
Close behind it is the compliance calendar described above — every door carrying its own city license, county registration, MDE lead status, inspection dates and certificate expiries, with warnings that arrive early enough to act on. On its own, that is often the piece that pays for the build.
Then there is owner reporting, which matters enormously if you manage for third parties. A proper owner portal gives each owner a live view of their own properties — statements that read the way owners actually think, maintenance history with photos, occupancy and arrears at a glance — and it replaces both the monthly Excel ritual and a good share of the phone calls. Managers routinely tell us this is the feature that wins them new business, because most of their competitors are still emailing PDFs.
Beyond those, the usual list is a leasing and application pipeline with screening built in, a turnover board that runs the make-ready as a real process, and a mobile inspection tool that does move-in and move-out walkthroughs with timestamped photos — the single best defense in a security-deposit dispute. Underneath all of it sit the integrations, which is where a build either becomes genuinely useful or stays a toy: QuickBooks for the books, Stripe or ACH for rent, a screening provider, e-signature, listing syndication, and clean exports for your accountant at year end. If you want to see the kind of thing these budgets buy, we keep five real apps running live in the browser on the demos page, including an operations tool, a booking marketplace and an online store.
Build or buy: how to tell which side you're on
You do not have to take anyone's positioning on faith, ours included. The useful test is not "custom or SaaS" in the abstract — it is a few plain questions about your own operation, and the answers usually point clearly one way.
- Are you paying people to bridge the software? If a real slice of somebody's month goes to rebuilding owner statements, reconciling voucher payments or maintaining the compliance spreadsheet, you are already paying for custom software in salary — and getting nothing you own for it.
- What is the true monthly number? Add the subscription, the per-payment fees on every door, the add-on modules and the screening charges. Multiply by the years you plan to hold the portfolio. Compare that to a one-time fixed price for something you keep.
- Is your operation ordinary or particular? Single jurisdiction, similar units, no third-party owners, no vouchers — buy the subscription, genuinely. Scattered sites across the city line, pre-1978 stock, owners to report to, vouchers to reconcile — that is a shape no template expresses well.
- Who owns the record? Your rent roll, lease history and maintenance record are the operating history of the business. On a rented platform they sit in someone else's schema behind an export button whose quality you discover only when you leave.
If those questions mostly land on "the platform is fine and we barely think about it," keep the platform — that is the right and cheaper answer, and we will say so on the call. If they mostly land on "we have built a whole shadow operation to make this work," that shadow operation is the specification for the thing worth building. For how the timeline collapsed from the industry-standard months down to weeks, and why AI is the reason, we wrote separately on how long it really takes to build a custom app. And this whole discussion sits inside a broader local one — our guide to custom software development in Baltimore covers the trades, the Port logistics economy, healthcare and the rest of the city's small businesses alongside property.
Built in Baltimore, yours to keep
We are a small studio of ex-founders based here in Baltimore, and we build custom software for small and growing businesses — custom apps, internal tools, online stores and operations systems — roughly the way we wish someone had built it for us when we were running our own companies. Fixed price, fixed timeline, direct with the builders, and fully yours at the end. There is something we genuinely like about building the software that runs the buildings our own city lives in, though the work runs entirely remotely, so portfolios outside the metro are no harder to take on.
If you run a portfolio that has outgrown the platform around it — owner statements rebuilt every month by hand, maintenance living in a group chat, a compliance spreadsheet nobody wants to be responsible for — the way to find out what it would take is a free thirty-minute call. Bring the portfolio, or the tangle of tools and workarounds you have been holding together, and we will tell you honestly what we would build, what you should keep renting, how fast it could ship, and the fixed price that goes with it.
Common questions from Baltimore landlords and property managers
How much does custom property management software cost in Baltimore?
Our fixed prices make a useful anchor. A one-week Prototype Sprint — a single flow such as a maintenance-request intake or an owner statement, clickable and deployed — is $3,500. A branded tenant portal for applications, rent payments and requests starts at $6,000. A custom leasing, maintenance or inspection app, or a full operations system covering rent roll, work orders, turnovers, compliance and owner reporting, starts at $12,000. Each is a fixed price agreed before any code is written, and you own the code, the keys and the accounts at the end. Most portfolio builds land in the $12k–$35k range, against a national market where a custom property platform is commonly quoted from $55,000 upward.
At how many units does building beat renting?
There is no magic unit count, and anyone who gives you one is guessing. The honest trigger is not portfolio size but how much human time you spend bridging the gap between the software and your actual operation. That said, the arithmetic tends to turn somewhere around the point where your platform bill plus per-transaction payment fees passes roughly $300 to $500 a month and you are still keeping a compliance spreadsheet, rebuilding owner statements by hand, or running maintenance out of a group chat. At that point a one-time fixed price for something you own usually pays for itself inside two to three years, and everything after that is upside.
What is the minimum number of units for AppFolio?
AppFolio requires a minimum portfolio of 50 units and also enforces a monthly minimum spend. The last rates it published, before removing printed pricing in September 2024, were $1.49 per unit per month on the Core tier against a $298 monthly minimum — which makes the floor equivalent to exactly 200 units. At AppFolio's own 50-unit entry point that works out to $5.96 per door, four times the advertised rate, and anywhere below 200 doors you are paying for units you do not own. Buildium and DoorLoop start lower and are friendlier to small portfolios, but they meter you differently: Buildium's entry tier charges $2.35 for every incoming electronic rent payment, a charge that recurs on every door every month.
Can custom software track Baltimore City rental licenses and Maryland lead-paint registration?
Yes, and this is usually the single strongest argument for building. Baltimore City requires annual registration plus a rental license backed by an inspection, and as of January 2026 that license runs on a flat two-year term and no longer transfers when a property is sold — a new owner has sixty days to apply for their own. Since 2019 an unlicensed rental has had no legal right to collect rent. Baltimore County runs an entirely separate registration and licensing system on its own cycle and its own fees. On top of both, the Maryland Department of the Environment requires owners of pre-1978 rental units — roughly seven in ten of this city's rental units — to register with the state, renew on a two-year cycle at $75 per unit as of January 2026, and meet the lead risk-reduction standard at every change of occupancy. No national platform models any of this, because it is worthless to a customer in Phoenix. A custom system can attach the real dates to the real doors and warn you before a certificate lapses.
How does custom software handle Section 8 and housing-choice-voucher payments?
It handles them the way your business actually experiences them, which is precisely where most off-the-shelf tools struggle. A voucher tenancy splits one month's rent into a housing-authority portion and a tenant portion that arrive separately, on different schedules, and often in different amounts after an annual recertification. Generic software tends to treat that as one rent charge with a confusing partial payment, which is why so many managers end up reconciling vouchers in a spreadsheet. A custom rent roll can model the split natively — two expected payments per unit per month, each tracked and aged on its own — alongside the inspection dates the housing authority sets.
How long does it take to build custom property management software?
Weeks, not months, for most portfolios — a clickable prototype of one core flow in about a week, a tenant portal in one to two, and a custom leasing, maintenance or inspection app or a full operations system in two to five. The industry-standard estimate of two to six months for a property platform mostly measures agency coordination rather than the actual work; with AI doing the repetitive volume under a senior builder, that overhead is what disappears.
Do I own the code, and what happens to my data?
You own all of it — the source code, the repository, the hosting accounts and the database, handed over at the end of the build. This is a sharper question in property management than in most industries, because your rent roll, lease history, maintenance record and owner ledger are the operating history of the business, and on a rented platform they live in someone else's schema behind an export button whose quality you only discover on the way out. When you own the system, the data sits in your database on your infrastructure, and migrating, reporting on or extending it is a decision you make rather than one you negotiate.
When is off-the-shelf property management software still the right choice?
Often, and we will say so on a call rather than sell you a build you do not need. If you run a straightforward portfolio in a single jurisdiction, your units are broadly similar, you do not manage for third-party owners, and the platform's workflow genuinely matches yours, then AppFolio, Buildium, DoorLoop or Yardi Breeze is the cheaper and faster answer — nobody should commission custom software to do what a subscription already does well. Building starts to make sense when your operation is unusual in a way the template cannot express, when compliance across jurisdictions is a real burden, or when you are paying staff time purely to bridge the gap.