Condo and HOA Management Software: When Custom Makes Sense

Most Canadian condo corporations, strata corporations and HOAs should buy SaaS; custom condo management software makes sense for management companies running many buildings with workflows SaaS will not model, or for PropTech founders building a product. The market is large: 1.92 million Ontarians live in condos, and US community associations house 78.1 million residents. Custom starts to pay when per-door fees and workarounds cost more than a build.

The figures come from the Condominium Authority of Ontario and the Foundation for Community Association Research's 2025 Fact Book, which counts 373,000 US community associations. This guide is for boards, condo and strata management companies, and PropTech founders deciding whether to build. It covers what Ontario and British Columbia rules mean for the software, which features need to exist, and when to walk away from a custom build. Legal points here are general information; confirm with your adviser.

Should a condo board or HOA build its own management software?

Usually not. A single association with a few hundred units has ordinary needs: collect fees, handle maintenance, run meetings, keep records. Several SaaS products do that for a monthly fee, and the board's time is better spent governing than managing a software project.

Custom earns its cost in a narrower set of situations:

Your situation	Lean towards	Why
One self-managed association, standard needs	SaaS	Monthly fee is small next to a build and its upkeep
A management company with many corporations and a service model SaaS cannot express	Custom, or a custom layer over SaaS	Per-door fees scale with the portfolio; the workflow is the business
A PropTech founder building a condo or HOA product to sell	Custom	The software is the product, so you have to own it
Operations split across Canada and the US	Custom, if no SaaS handles both rule sets well	Per-jurisdiction rules need to be configuration, not workarounds
SaaS works but reports and integrations are missing	SaaS plus a small integration	Pull data through the vendor's API before replacing everything
A board unhappy with its current vendor	Switch SaaS	A different product is cheaper than a first build

The question to answer honestly: is the thing SaaS cannot do something your owners, residents or clients would pay for, or would leave you over? If yes, build that part. If not, switch vendors.

What does condo software need to handle in Ontario?

Records, returns, meetings and disputes, all with an audit trail. The Condominium Authority of Ontario (CAO) publishes the obligations boards deal with, and each one becomes a feature or a report.

• Returns to the CAO. Every corporation files an annual return between 1 January and 31 March, and a notice of change within 30 days when filed information such as directors or the management provider changes. Late filing carries a $200 fee (CAO: condo returns). Software can remind the board and hold the data, even if filing happens on the CAO's site.
• Owners' meetings. The CAO says hybrid meetings, and meetings held entirely by phone or virtually, are allowed under the Condo Act unless the corporation's by-law limits or prohibits them, and that voting must be fair, transparent and balanced whatever the format (CAO: owners' meetings). Meetings generally need a preliminary notice and a notice of meeting, so the software needs a notice schedule, not only a calendar entry.
• Records and disputes. The Condominium Authority Tribunal hears disputes about condominium records, pets and animals, vehicles, parking and storage, and nuisances such as noise and odour (CAO: file an application). Those are exactly the areas where a clear record of who asked, who answered and when is worth having.
• Managers. The CAO says boards can only work with managers or management companies licensed by the Condominium Management Regulatory Authority of Ontario (CAO: what condo managers do). Software for a management company should record which licensed manager is responsible for each corporation.

Deadlines and required contents for records requests are set by the Act and its regulations. Treat them as configuration your adviser confirms, not as numbers a developer copies from a blog.

What does strata software need in British Columbia?

BC strata corporations follow the Strata Property Act, and the provincial government's strata pages set out rules that translate directly into software requirements.

• Records with retention classes. Correspondence is kept for two years; minutes, financial books, budgets and bank statements for six years; resolutions affecting common property, legal opinions and depreciation reports permanently (BC government: strata information and record keeping).
• Access requests on a clock. Bylaws and rules within one week of a request, other records within two weeks, with copies at up to 25 cents a page. Owners, some tenants and authorized representatives can ask.
• Privacy. The same page says strata corporations must follow BC's Personal Information Protection Act (PIPA).
• Electronic meetings. Since 24 November 2022, all BC strata corporations may hold annual and special general meetings electronically or as hybrids with no bylaw required, and remote participants are deemed present in person (BC government: conducting a general meeting).
• Reserve fund votes. Stratas contribute at least 10% of the operating fund budget to the contingency reserve fund each year. Most spending from it needs a 3/4 vote, with majority votes allowed for a few purposes such as obtaining a depreciation report (BC government: the contingency reserve fund).
• Managers. The BC Financial Services Authority licenses strata property managers under the Real Estate Services Act (BC government: strata property managers).

Rules change, and these pages were checked on 30 September 2026. Confirm the current rule with your adviser before it becomes a hard-coded deadline.

How do you model rules that differ by province and state?

As data, with a source and an owner, never as constants in the code. A condo in Toronto, a strata in Vancouver and an HOA in Texas need different deadlines, vote thresholds and retention periods, and each can change. Engineering guidance for the records-request clock:

type Jurisdiction = 'bc-strata' | 'ontario-condo' | 'us-hoa'

interface RecordRule {
  recordType: 'bylaws_rules' | 'other'
  dueInDays: number | null   // null = not configured yet
  source: string             // where the rule came from
  confirmedBy: string | null // adviser sign-off
}

const RULES: Record<Jurisdiction, RecordRule[]> = {
  'bc-strata': [
    { recordType: 'bylaws_rules', dueInDays: 7, source: 'gov.bc.ca strata record keeping', confirmedBy: null },
    { recordType: 'other', dueInDays: 14, source: 'gov.bc.ca strata record keeping', confirmedBy: null },
  ],
  'ontario-condo': [],  // configure after legal review
  'us-hoa': [],         // varies by state and governing documents
}

export function dueDate(j: Jurisdiction, type: RecordRule['recordType'], receivedAt: Date): Date | null {
  const rule = RULES[j].find((r) => r.recordType === type)
  if (!rule || rule.dueInDays === null) return null // surface as "needs configuration"
  return new Date(receivedAt.getTime() + rule.dueInDays * 24 * 60 * 60 * 1000)
}

The confirmedBy field is the point. A deadline nobody has confirmed shows up in the admin as unconfirmed, instead of silently driving reminders. Store the rule version on each request, too, so an old request is judged by the rule that applied when it arrived.

What about HOAs in the United States?

The 2025 Fact Book counts 373,000 US community associations with 78.1 million residents, and puts 35.2% of US housing inside planned communities, condominiums and cooperatives. HOA rules come from state law and each association's governing documents, so there is no single national rule set to build to. The software pattern is the same as above: per-association configuration for dues schedules, late fees, notice periods, voting and records, with every rule traceable to a document someone has checked.

US fee collection usually means cards and ACH bank debits; Canadian associations usually want pre-authorized debit (PAD) and Interac e-Transfer. One codebase can serve both, but they are different flows with different timing, and the tests have to cover each.

What features does condo and HOA software need?

Feature	Main users	Usually covered by SaaS?	Where custom tends to earn it
Owner and resident portal	Owners, tenants	Yes	Branded experience for a management company's many buildings
Fees, levies and payments	Owners, manager	Yes, on the vendor's rails	PAD and Interac reconciliation, unusual levy schedules
Maintenance and common-area work orders	Residents, manager, contractors	Yes	Contractor routing across a portfolio, SLA reporting
Records and document requests	Owners, board, manager	Partly	Request clocks and retention classes per jurisdiction
Meetings, notices, proxies and votes	Owners, board	Varies	Hybrid meetings with vote thresholds per resolution type
Bylaw or rule violations	Board, manager	Varies	Evidence trail that survives a tribunal hearing
Amenity booking	Residents	Yes	Rarely worth building alone
Reserve fund and budget reporting	Board, treasurer	Partly	Depreciation-report tracking tied to approved spending

For the resident side in more depth, see tenant portal features and building a maintenance request system.

What roles and permissions does condo software need?

More than a rental product. Condo and HOA software typically needs owners, tenants or residents, board or council members, the property manager, contractors and a platform admin, and a management company adds a layer above all of them: many corporations in one system, each fully isolated from the others.

Two rules prevent most permission bugs. First, a person's role belongs to a membership in one association, not to the person, because the same owner can sit on one board and simply own a unit in another building. Second, isolation between associations should be enforced in the database as well as the application. The SaaS authorization and RBAC design guide covers the role model, and multi-tenant vs single-tenant SaaS covers how to isolate each corporation's data.

RAITHub's closest proof is PropDesk, a property management platform with 4 roles (landlord, tenant, contractor and admin), leases, maintenance, Stripe rent collection and 1,024 automated tests. PropDesk is a rental product, not condo software; a condo build adapts its role and maintenance model rather than reusing it as-is.

How should condo fees be collected in Canada?

Usually by pre-authorized debit, with Interac e-Transfer as a fallback. PAD suits fees that recur every month: Stripe lists it at 1% plus CA$0.40, capped at CA$5.00 per payment (Stripe Canada pricing). The timing is the catch. A PAD can take up to 5 business days to confirm, and a personal-account dispute can be filed up to 90 calendar days after the debit, with no way for the merchant to contest it (Stripe: Canadian pre-authorized debit). The ledger has to show "processing" and handle reversals long after an account looked paid.

RAITHub has shipped Stripe rent collection in PropDesk. It has not shipped PAD or Interac in production, so on a condo build those are scoped and tested as new work. The online rent collection guide covers the ledger design that both need.

What does custom condo software cost compared with SaaS?

Compare three years, not one invoice. Condo and HOA SaaS vendors often quote on request: Buildium asks community associations to call for pricing (Buildium pricing), and Condo Control prices by unit bands without publishing figures (Condo Control pricing). Get a written quote, then run this arithmetic with your real numbers:

Doors under management	At an assumed CA$2 per door per month, 3 years	At an assumed CA$4 per door per month, 3 years
500	CA$36,000	CA$72,000
2,000	CA$144,000	CA$288,000
5,000	CA$360,000	CA$720,000

The per-door figures are placeholders to show the arithmetic, not any vendor's price. Set them against a custom build's cost plus about three years of hosting, maintenance and support. At a few hundred doors, SaaS almost always wins. At thousands, with workflows the SaaS cannot model, the comparison can flip. The MVP cost estimator gives a starting figure for the build side, and what a SaaS costs to run per month covers the running side.

How does a Dhaka team work with Canadian and US clients?

Dhaka is UTC+6 with no daylight saving, so Toronto and Vancouver have almost no natural overlap with it. RAITHub offers a daily 2-hour window, 19:00 to 21:00 Dhaka time, which is 08:00 to 10:00 in Toronto in winter and 09:00 to 11:00 in summer; in Vancouver it falls at 05:00 to 07:00 or 06:00 to 08:00. Everything else is async, with a written handoff every day, and the working week is agreed per client.

Why RAITHub for this?

• Property software already built and measured. PropDesk: 4 roles, leases, maintenance, Stripe rent collection and 1,024 tests.
• Isolation between organizations. Multi-tenant design with database-level scoping, as described in the property management software development guide.
• Rules as configuration. Per-province and per-state rules modelled as data with a source and a sign-off, so your adviser, not the developer, decides the numbers.
• A fixed quote first. A free 15-minute technical audit, then a fixed written quote, as fixed scope or a dedicated monthly team. See the SaaS development service and the real estate and PropTech page.
• You own it. IP assigned to you and an NDA before detailed discussion.

When you don't need us

• You run one association with standard needs. Buy SaaS. If the current product frustrates you, try another before building.
• You need a native mobile app. RAITHub builds web applications and does not offer mobile app development.
• You need French-language delivery or on-site support. RAITHub works in English only and has no Canadian or US office.
• You need interpretation of the Condo Act, the Strata Property Act or an HOA's governing documents. That is an adviser's work. RAITHub builds the rules your adviser confirms.
• You need a supplier with SOC 2 or ISO 27001. RAITHub holds neither.

Sources checked on 30 September 2026. Legal points are general information; confirm with your adviser.

If you are weighing a custom condo or HOA platform, book the free 15-minute technical audit. Bring your door count, your current software bill and the three workflows it cannot handle.

Frequently asked questions

Is custom condo management software worth it for one building?

Rarely. A single condo corporation, strata or HOA with standard needs is usually better served by SaaS. Custom makes sense for management companies with many buildings and unusual workflows, or for founders building a condo or HOA product.

What records rules apply to BC strata corporations?

BC government guidance says bylaws and rules must be provided within one week of a request and other records within two weeks, with copies at up to 25 cents a page, and sets retention periods of two years, six years or permanently by record type. Confirm the current rule with your adviser.

Can Ontario condos hold virtual owners' meetings?

The CAO says hybrid, phone-only and fully virtual meetings are allowed under the Condo Act unless the corporation's by-law limits or prohibits them, and that voting must be fair, transparent and balanced. This is general information; confirm with your adviser.

How many roles does condo and HOA software need?

Typically owners, tenants or residents, board members, the property manager, contractors and an admin. A management company also needs each corporation isolated from the others, with roles attached to a membership in one association rather than to the person.

How should a Canadian condo collect monthly fees online?

Pre-authorized debit suits recurring fees, with Interac e-Transfer as a fallback. PAD can take up to 5 business days to confirm and can be disputed for up to 90 days on personal accounts, so the ledger must handle late reversals.

Has RAITHub built condo or HOA software before?

Not a condo or HOA product specifically. RAITHub built PropDesk, a rental property platform with 4 roles, maintenance, leases, Stripe rent collection and 1,024 tests. A condo or HOA build would adapt that role and maintenance model, and the quote says which parts are new.

Does RAITHub integrate with MLS for condo listings?

No. RAITHub has not built an MLS integration. Condo and HOA management software rarely needs one, since it manages existing owners rather than listings.