Property management portal development usually means building a resident-facing portal for rent, maintenance and lease records, an owner-facing portal for statements and reporting, or both. Custom launch-phase builds are typically estimated at $45,000 to $65,000, with growth features often adding $25,000 to $40,000. Recurring commercial platforms commonly start between $65 and $420 per month before per-unit pricing applies. The right choice depends on your unit count, how quickly you expect to grow, and whether your workflows fit a packaged product.
Greensboro projects also carry local design requirements. North Carolina’s security deposit statute requires a landlord to deliver an itemized accounting within 30 days after a tenancy ends and possession is returned, so a portal should record deposit activity and dates from the start. The state’s electronic transactions law applies only when each party has agreed to transact electronically, so consent capture belongs in the build plan. Phasing the work, with resident essentials first and owner reporting added once data is clean, keeps early costs predictable.
Key Takeaways
- A custom property management portal typically costs $45,000 to $65,000 to launch, and growth features such as owner portals and trust accounting typically add $25,000 to $40,000, so test that range against your own requirements.
- Commercial property management platforms commonly start between $65 and $420 per month before per-unit pricing applies, so a $420 monthly plan totals $5,040 per year.
- Resident features should launch first in a property management portal because rent and maintenance records supply the figures that owner statements depend on, and inconsistent resident records produce inconsistent owner reports.
- A North Carolina landlord must deliver an itemized security deposit accounting within 30 days after a tenancy ends and possession is returned, so a portal should store the move-out date and possession-return date as separate fields from the start.
- A North Carolina resident portal needs a consent step at sign-up that records who agreed, the date and time, and the delivery channel, because the state’s electronic transactions law applies only when each party has agreed to transact electronically.
Which Portal Do You Need: Resident, Owner or Both?
A resident portal is the right starting point if residents need to pay rent, submit maintenance requests and reach their lease records. An owner portal becomes necessary once owners want their own reports. Resident scope typically covers rent payments, maintenance requests, access to lease and document files, and messaging with the office. Owner scope covers monthly statements, income and expense reporting, and property-level performance views that show how each building is doing.
Commercial platforms usually bundle both sides, so residents and owners get separate logins from the first day. A custom build can take a different route. It can launch with one side and add the other in a later phase, which spreads spending over time and lets you check the data before owners rely on it.
Resident features often come first because rent and maintenance records supply the figures that owner statements depend on. If those records are inconsistent, owner reports will be inconsistent too.
The best way to decide scope is to count who will log in and what each group must do each week. A portfolio where most tenants pay rent online or file repair requests every week needs a resident portal built for speed and reliability. A portfolio where owners check results only at month end may need a simpler owner view added later. Write down each user group, how often it logs in and its top three tasks. That list shows which features must exist at launch and which can wait for the next phase.
How Much Does It Cost to Build a Property Management Portal?

A custom property management portal typically costs $45,000 to $65,000 to launch. A growth phase that adds owner portals, owner statements, trust accounting, vendor management and tenant-screening integration typically adds a further $25,000 to $40,000. The exact total depends on the number of user roles, integrations and reporting depth, so use these figures as a starting range to test against your own requirements.
Off-the-shelf platforms work differently. Their base plans commonly start between $65 and $420 per month, and higher tiers are often priced per unit, with some residential plans starting around $1.49 to $5.00 per unit per month. Most of these packages carry minimums, so a small portfolio can pay more per unit than a large one. A $420 monthly plan adds up to $5,040 per year, which means a $45,000 custom launch equals almost nine years of that subscription before any growth features are counted.
The comparison is not only about the first payment. A custom build carries ongoing hosting, security updates, feature changes and staff time, while a subscription bundles many of those into its monthly fee. A custom build makes sense when your workflows do not fit a packaged product, and that fit is easier to judge once you understand what drives the price. In a custom build, five factors shape the total:
- Number of user roles, since each added group such as residents, owners, vendors and staff needs its own permissions and screens.
- Payment integrations, including how many payment methods residents can use and how owner payouts are sent.
- Document storage, because lease files, inspection photos and deposit records grow quickly across a portfolio.
- Reporting depth, ranging from a simple monthly statement to property-level performance views with custom exports.
- Third-party connections, such as accounting software, tenant screening and listing sites, each of which needs testing and upkeep.
Payment fees deserve their own line in the budget. Card transactions usually carry a fee around 2.99%, so a $1,500 rent payment made by card incurs about $44.85 in processing fees. Many commercial platforms also charge per-transaction fees on electronic bank transfers, which can range from roughly $0.60 to $2.35 on some plans. These charges recur every month and grow with volume, so a portfolio of 200 units paying by card generates a far larger fee total than a portfolio of 20 units. Decide who absorbs these fees before you set rent policies or owner terms, because the answer changes your margin on every payment.
What Features Should Tenant and Owner Portals Include?
A tenant and owner portal needs five connected features: online rent payments, a maintenance request workflow, lease and document storage, threaded messaging, and owner reporting. Each one should write to the same unit record, and every user should see only the units and files that belong to them.
Rent payment is the foundation. A resident should see a complete payment history, set up autopay with a stored date and amount, and receive a receipt that links back to the ledger entry. Decide early who pays the processor’s fee, because card payments carry a percentage cost on every transaction. If receipts and notices are delivered electronically, the state’s electronic transactions law applies only after each party has agreed to transact that way, so the portal needs a consent step at sign-up.
The maintenance workflow should start with the tenant. A request should include a description, photos and the unit it concerns, then move through status updates that the tenant can view. The office assigns the job to a vendor. When the vendor marks the work done, the tenant confirms completion, which closes the ticket. Any repair cost recorded on the ticket can then flow to the ledger and the owner statement without retyping.
Role-based permissions keep that data contained. A well-scoped build usually separates four groups:
- Residents see only their own lease, ledger and maintenance requests.
- Owners see statements and read-only views of the properties they hold.
- Vendors see only the tickets assigned to them.
- Staff see every unit they manage, with edit rights limited by role.
Lease and document storage should hold signed leases, addenda, inspection reports and notices in one place, each tied to its unit and date. North Carolina’s Uniform Electronic Transactions Act says an electronic signature can satisfy a signature requirement when its conditions are met, and that an electronic record delivered in place of written information must be retainable and accurately reproducible. Deposit details belong here too, including the trust account or bond information that the state’s security deposit rules require you to give tenants in writing. According to the U.S. Census Bureau, 90.9% of Greensboro households had a broadband subscription and 95.8% had a computer in 2020 to 2024, so a resident view should work well on a phone as well as a desktop.
Messaging works best when each thread belongs to a unit or a maintenance request. A question about a leaking faucet then stays attached to the ticket, its photos and the vendor’s invoice, rather than living in a personal inbox. Staff can find the full history later without asking the tenant to repeat anything.
Owner portals draw from the same records. Monthly statements, income and expense exports, and property-level summaries should all be generated from the rent and maintenance entries residents already created. Owners get read-only access, so they can review results without changing a lease or a payment.
Dig Designs builds websites on WordPress, and its Website Management plans include daily off-site backups and daily malware and vulnerability scanning. Those protections matter once a portal holds lease files and payment records.
Build Versus Buy: When Does Custom Make Sense?

Buy a packaged platform when your standard workflows fit, your portfolio is small, and getting online quickly matters more than custom features. Build when you need specific workflows, a branded resident experience, custom integrations or owner reporting that a bundled product cannot deliver without workarounds.
A packaged platform suits a portfolio whose rent collection, maintenance tickets and owner statements already follow standard steps. The vendor carries hosting, updates and security, so your team can start using the software sooner. The trade-off is that you adapt your processes to the product, and new feature requests depend on the vendor’s roadmap.
A custom build makes sense when your business depends on something a vendor does not offer, such as a lease approval step with your own rules, a resident dashboard styled to your brand, or a connection to a local accounting tool. Owner reporting that groups results by investment entity or unit type is another common reason, because standard statement templates rarely match how each owner reads a property.
A custom project involves five stack decisions. The front end is the interface residents and owners use, and it must be responsive so it works on a phone. The back-end database stores units, ledgers and tickets, and it enforces role permissions. The payment processor handles card and bank transactions and sets the fee structure. Hosting determines storage, backups and uptime. Finally, you decide whether the portal sits inside an existing website or runs as a separate application on its own address. A members area inside a WordPress site is one practical option, while a standalone application keeps resident records apart from marketing pages.
Settle data ownership before you sign with any vendor. Ask how you would export unit records, ledger entries, maintenance tickets, messages and documents, and confirm the export keeps the links between them, so a payment still points to its lease. Spreadsheet formats work for tables, while leases and inspection photos should come out as original files. Also ask how long the vendor keeps your data after cancellation.
| Factor | Buy (packaged platform) | Build (custom) |
|---|---|---|
| Cost pattern | Recurring subscription, often priced per unit with minimums | Larger upfront project cost, then ongoing hosting and upkeep |
| Customization | Limited to vendor settings and add-ons | Workflows, screens and reports designed for your portfolio |
| Integration control | Limited to the vendor’s supported connections | You choose, build and maintain each connection |
| Time to launch | Usually the fastest route to live use | Longer, typically phased in stages |
| Maintenance responsibility | Vendor handles updates, security and feature changes | Your team or developer owns updates, security and testing |
What North Carolina Rules Mean for Portal Design
North Carolina’s Tenant Security Deposit Act controls how residential deposits are held, so the portal needs fields that match those rules. A deposit must sit in a trust account at an authorized institution or be secured by a qualifying bond. The landlord must give written notice of that institution or insurer within 30 days after the lease begins. A portal that stores the lease start date, the deposit amount and the bank or bond details can generate that notice automatically and keep a dated copy on file.
The accounting deadlines are the second constraint. Under North Carolina General Statute § 42-52, a landlord must deliver an itemized accounting and any remaining deposit within 30 days after the tenancy ends and possession is returned. If a claim cannot be determined within that window, an interim accounting is due within 30 days and a final accounting within 60 days. The portal should therefore store the move-out date and the possession-return date as separate fields, because each deadline runs from a different event.
The deposit accounting itself should list each deduction next to the maintenance ticket, invoice or photo that supports it. The finished statement should be a file the resident can save and print at any time, not a screen that disappears when the session ends.
Electronic delivery depends on consent. North Carolina’s electronic transactions law applies only when each party has agreed to transact electronically, so the sign-up flow needs a consent step. That step should record who agreed, the date and time, the version of the consent text and the delivery channel chosen. A resident who declines must still receive notices another way, so the notice workflow has to branch rather than assume online delivery.
State law also sets a standard for the records themselves. An electronic record delivered in place of written information must be retainable and accurately reproducible. In practice, each lease, notice and statement should be stored as the exact file that was sent, with a version number. Corrections should create a new version instead of overwriting the original.
Signatures follow similar logic. Under § 66-317, an electronic record or signature cannot be denied legal effect solely because it is electronic, provided the Act’s conditions are met. The signing flow should capture the signer’s name, a timestamp and the document version signed, so the record shows what was agreed and when.
Greensboro’s high broadband and computer access makes online-first resident services practical for most households. Even so, keep a mailed or in-office option for residents who decline electronic delivery, because the portal cannot assume every tenant consents.
This section is general information about North Carolina law. Confirm how each rule applies to your leases and deposit practices with a North Carolina attorney before you fix the workflow in code.
Security, Accessibility and Testing Before Launch

Application security starts with a written baseline. OWASP’s Application Security Verification Standard (ASVS) 5.0.0, dated May 2025, sets security requirements for designing, developing and testing web applications and services. Use it as the checklist your developer signs off against before each release, not just a review of the features that were requested.
Payment and personal data need protection both in transit and in storage. Every page should load over HTTPS, and Dig Designs’ Website Management plans include a free SSL certificate for that purpose. Card numbers should stay with the payment processor, so the portal stores only a payment token and a masked reference. That keeps full card data out of your own database.
Access rules and session controls matter as much as encryption. Permissions must be checked on the server, because a hidden button does not stop a vendor from opening a lease URL. Every change to a ledger entry, deposit record or lease should write an audit log entry with the user, the date and the time. Staff accounts that can edit payments or export records should require multi-factor sign-in. Sessions should time out when idle, and repeated failed sign-ins should lock the account until it is reset through a verified email address or phone number.
Accessibility is the second check. WCAG 2.2 is the current W3C standard, published as a Recommendation on October 5, 2023, and it adds nine success criteria to WCAG 2.1. The W3C advises building to 2.2 so the work stays applicable for longer.
The ADA Title II web rule sets WCAG 2.1 Level AA deadlines of April 26, 2027 and April 26, 2028, but those deadlines apply to state and local government entities. A private property manager is not automatically bound by them. Building a resident portal to the same standard still helps tenants who use screen readers or keyboards.
Testing should follow the user groups you wrote down during scoping. Create a test account for each tenant, owner, vendor and staff role, and confirm each account sees only its own units, ledgers and tickets. Run payment test transactions in the processor’s test mode before any live charge. Then run load checks that simulate the first days of the month, when rent payments and autopay runs cluster. Test on the phones and browsers your residents actually use, since many will file repair requests from a phone.
Record the expected result for each failure case before testing begins:
- A declined card payment triggers a tenant notice with a retry option.
- A failed autopay leaves the ledger showing the balance as unpaid.
- A duplicate maintenance request is flagged rather than creating a second ticket.
- A vendor marking a job done twice closes the ticket only once.
- A session that expires during payment neither loses nor duplicates the charge.
How Long Does Portal Development Take and What Follows Launch?
Portal development runs from scoping through deployment and then into ongoing support. The length of each phase depends on how many user roles and integrations the build must support. Each added role needs its own screens and permissions, and each integration needs its own testing, so a portal with residents, owners, vendors and staff takes longer than one with residents alone. The steps below run in order, and each one should finish before the next begins.
- Discovery and scoping: list each user group, its weekly tasks and every outside system the portal must connect to.
- Design: map the resident, owner, vendor and staff screens, then approve them before any code is written.
- Development: build the unit, ledger and maintenance ticket records first, then the screens that read from them.
- Testing: run the role, payment and duplicate-request cases in a staging environment before any live data is loaded.
- Data migration: import unit records, leases and balances from your spreadsheets or old software, then reconcile totals against the source files.
- Staff training and user onboarding: train office staff on ticket and ledger workflows, and give residents a sign-up flow that captures electronic consent.
- Phased rollout: move a few units first, watch payments and tickets through a full billing cycle, then add the rest of the portfolio.
- Ongoing support: schedule security patches, backups and reports from the first day the portal is live.
After launch, the work shifts to maintenance. Security patches must cover the portal’s own application code, while the website layer needs its own schedule of plugin and theme updates. Dig Designs’ Website Management plans include weekly plugin and theme updates, daily off-site backups, daily automated malware and vulnerability scanning, a free SSL certificate and monthly care reports, which covers the WordPress site that hosts the portal. Uptime monitoring should run alongside these tasks so that an outage is noticed before residents report it.
Scaling starts with the data model. Store each building as its own record and link units to it, rather than writing a single property into rent schedules, bank settings or reports. A portal built this way adds a new building as new rows instead of new code. Storage also grows with every lease scan and inspection photo, so compare your expected file volume with the plan limits. Website Management plans range from $47 per month, with 10 GB of storage and 75 GB of bandwidth, to $497 per month, with 500 GB of storage and 2 TB of bandwidth.
Scoping Your Portal Build With Dig Designs
Start by writing down each user group, how often it logs in, its top three tasks, and how many units and owners you manage today. Add the accounting, listing and payment tools you want connected. That list gives a developer enough to decide whether a resident portal, an owner portal or both belongs in your first phase.
Dig Designs is a digital agency in Greensboro, North Carolina that builds conversion-focused websites on WordPress. If your portal will sit alongside a marketing site, the launch process has four steps: tell us about your business, choose a site style from the theme catalog, choose add-on services, and receive login details. Login details for the new site are sent within 3 days or less, so a scoping conversation can quickly turn into a working build.
If you are not sure how much hosting and upkeep your portal will need, look at the Website Management plans first. They include daily off-site backups, daily malware and vulnerability scanning and weekly plugin and theme updates. They also come with a 30-day money-back guarantee, so you can test the day-to-day support before committing to a longer schedule.
Send us your user-group list, your unit count and your target launch month, and we will tell you which phase to build first.
Frequently Asked Questions
1. Can a WordPress website support resident logins and online rent payments without a separate application?
A WordPress website can support resident logins and online rent payments by adding a members area and connecting it to a payment processor, so the portal sits inside your existing site. This approach suits a smaller or steady portfolio with simple ledgers. A standalone application becomes the better choice when unit counts grow, owner reporting becomes complex, or you want resident records kept apart from marketing pages.
2. Who owns the code, data and login accounts after a custom portal launches?
Ownership of code, data and login accounts is set by the contract and by how accounts are opened, so it should be settled before the scope of work is signed. Ask that the agreement names you as owner of the unit, ledger, maintenance ticket and document records. Also confirm that hosting, domain and payment processor accounts are registered in your business’s name, and whether you receive the source code if the working relationship ends.
3. What does ongoing support cost compared with the initial build for a portal?
Ongoing support is a recurring cost that continues after launch, while the build is a one-time project fee. Dig Designs’ Website Management plans run from $47 per month with 10 GB of storage to $497 per month with 500 GB of storage and 2 TB of bandwidth, and they cover the WordPress layer that hosts the portal. Changes to the portal’s own application code, new features and staff time for testing are separate costs that depend on how often the portal changes.
4. How should I size hosting storage for a portal that holds leases and inspection photos?
Hosting storage for a portal grows with every lease scan, addendum, notice and inspection photo, so the plan needs enough room for those files. Estimate how many documents each unit generates per year and multiply by the number of units you manage. Then compare that total with the storage limit on the plan you are considering, which ranges from 10 GB to 500 GB on Dig Designs’ Website Management plans.
5. What happens to residents’ saved payment details if I switch payment processors?
Saved card and bank details are usually held by the payment processor as tokens rather than stored in your own database. Changing processors generally means residents must re-enter their payment methods unless the old and new processors support a token transfer. Confirm that option, and check how scheduled autopay runs will be handled, before you make the switch.



