Connecting the Property Technology Stack Behind Roughly 8,000 Rental Homes
Conrex depended on a homegrown Quickbase ecosystem for lead, tenant, renewal and vendor operations while MRI remained a core property and financial system. When the employee who uniquely understood the custom environment left, Knowtion became the application and integration layer—stabilizing inherited systems, reconnecting data and owning the workflows between platforms from 2021 through 2024.
Approx. 8,000 residential rental homes during the engagement · 2021–2024
The business did not run on one property management system. It ran across an ecosystem.
Conrex, later known as Maymont Homes, used Quickbase as a configurable operating layer across lead management, tenant management, renewals and vendor management. MRI remained central to property and financial operations. Website leads, secure applicant documentation, document storage and vendor workflows all had to connect around those systems.
That is the core property-technology problem Knowtion now solves as a service line: the platform may be capable, but the business still depends on what happens between platforms.
A mission-critical custom layer had outgrown its original owner.
The employee who created and uniquely understood the environment left for a competitor. The business still depended on the applications every day, but knowledge of the data model, workflow logic, integrations and failure points was concentrated in one person.
Key-person dependency
Institutional knowledge about application logic and integrations left the organization, creating immediate continuity and support risk.
Low trust in cross-system data
Conrex had limited confidence in information flowing back toward MRI, so important financial and operating handoffs remained manual.
Duplicate entry and manual transfers
Vendor, lead and operating data often had to be re-entered or manually moved between systems because the integration layer was incomplete.
A six-month transition horizon
Knowtion was initially asked to keep the inherited Quickbase environment viable for roughly six months while the business planned to move away from it.
We became the technical layer between the business process and the vendor platforms.
Knowtion reconstructed how the applications worked, learned how leads, tenants, renewals, vendors and financial systems interacted, and then improved the environment from the inside out. The priority was not “more features.” It was restoring confidence in the operating model and making every new integration supportable.
As a Quickbase Certified Partner, Knowtion also brought platform, licensing and architecture expertise, but the larger value came from understanding the entire workflow across Quickbase, MRI, websites, documents and custom APIs.
Stabilize the applications. Reconnect the ecosystem. Remove friction around the core platforms.
Reconstructed the inherited application environment
Knowtion learned the data model, application logic, automations and dependencies after the original internal expert left, then corrected high-risk issues and created accountable ownership.
Integrated Quickbase with MRI
Controlled integration connected the operating application layer with MRI so approved information could move more reliably between systems instead of depending entirely on manual handoffs.
Connected website lead flow
Website leads were integrated into the operating environment so inbound demand could enter the workflow without separate re-keying.
Protected sensitive applicant information
SendSafely was integrated with the lead-management process so prospective tenants could submit financial documentation through a secure file-transfer workflow.
Expanded vendor dispatch and reporting
Vendor-management capabilities were improved with dispatch workflows, reporting, pricing and bid handling designed for property operations at scale.
Strengthened rent and renewal workflows
Knowtion added notifications, custom reporting and workflow automation around rent and renewal processes.
Reduced public-form licensing exposure
A public-facing Quickbase form was replaced with an HTML front end connected through API, avoiding a costly licensing pattern tied to public internet usage.
Moved large files to SharePoint
Photos, videos and other large attachments moved outside Quickbase storage while users retained access through the operational application layer.
Each system did the job it was best suited to do.
Quickbase did not need to become the property management system, file repository, secure document portal and website. It became the operating and workflow layer that connected those specialist systems.
→
↔
A six-month bridge became three years of useful operating life.
Knowtion’s original mandate was to stabilize an inherited platform long enough for Conrex to transition away from it. Instead, better integrations, improved workflows, stronger reporting, licensing optimization and ongoing application stewardship made the environment useful enough to remain a core part of operations through 2024.
The result was not “Quickbase for three more years” as an end in itself. It was business continuity, time to make better platform decisions, and an integration layer the operator could trust while the broader technology strategy evolved.
“We are appreciative of Knowtion’s expertise and support in maintaining our toolset in Quickbase.”
Scot KellyCOO · Conrex / Maymont Homes
Questions this engagement answers for large residential operators.
What did Knowtion do for Conrex / Maymont Homes?
Knowtion took over a mission-critical Quickbase environment supporting roughly 8,000 residential rental homes, stabilized inherited applications, integrated MRI and website leads, improved lead, tenant, renewal and vendor workflows, added secure document intake, moved large attachments to SharePoint and reduced licensing friction.
How was MRI used in the Conrex / Maymont environment?
MRI remained a core property and financial system while Quickbase handled important operating workflows. Knowtion built controlled integration between the application layer and MRI so data could move more reliably instead of depending entirely on manual handoffs.
How long did the Conrex / Maymont engagement last?
Knowtion supported and modernized the environment from 2021 through 2024. The Quickbase platform had initially been expected to remain for about six months but stayed useful for roughly three years after takeover and improvement.
What property management workflows did Quickbase support?
The environment supported lead management, tenant management, renewal management and vendor management, with additional reporting, dispatch, notifications, automation and integrations around those operating areas.
How did Knowtion handle sensitive applicant documents?
Knowtion integrated SendSafely into the lead-management process so prospective tenants could submit sensitive financial documentation through a secure file-transfer workflow rather than a conventional public form.
How did Knowtion reduce Quickbase licensing and storage costs?
Knowtion replaced a costly public-facing form pattern with an HTML and API approach and moved large photos, videos and other attachments to SharePoint while keeping the operational record in Quickbase.
Can Knowtion take over a property technology application built by someone else?
Yes. The Conrex engagement began after the employee who uniquely understood the homegrown environment left. Knowtion reconstructed the application logic, documented dependencies, stabilized the system and became the technical owner across applications and integrations.
Does Knowtion only work with Quickbase for property management companies?
No. The broader Property Management Technology & Integration Services practice connects core platforms such as MRI and Yardi with leasing technology such as Rently, custom applications, websites, analytics and vendor systems. Quickbase was one important component of the Conrex / Maymont architecture.
It does have to work like one system.
Bring us the core PMS, the custom application, the leasing platform, the brittle sync job or the workflow that still lives in spreadsheets. We will start by mapping what the business needs to happen between them.