The sixty-second answer
GoldenKey Property Management ran roughly fifteen residential units across a hosting account, a separate phone arrangement and a handful of disconnected tools. In April 2026 we consolidated all of it: domain and DNS, email on the company domain, a tenant portal with rent and maintenance pages, lease import and digital lease signing, the business number migrated onto our own phone platform, and expense and invoicing connected to the same account. Phase one went live on the committed date. The client gave notice in the summer and the paid services were wound down on 2 July 2026, with the account moved to the free tier rather than deleted.
The situation
Jamie Costain runs GoldenKey Property Management, a small portfolio of around fifteen residential units. Like most operators at that size, the business was not short of software - it was short of a single place where the software agreed with itself. The public website sat on one hosting provider, the phone arrangement somewhere else again, and the unit and lease records in whatever tool had most recently been tried.
This was our first paying client on a combined property-management and telephony bundle, which made it the engagement that would tell us whether the bundle was real or just a slide. The deadline was a hard one - a specific Sunday in April 2026 - and we hit it.
What we actually moved
Phase one was infrastructure and the things a property manager cannot operate without.
Domain and DNS. Name servers moved to our managed DNS, the company domain pointed at the new tenant portal, and the old hosting account retired only after the new arrangement was confirmed working. Retiring the old host first is the standard way small businesses take themselves offline for a day; we do it in the other order.
Email on the company domain. Mailboxes for the owner and staff on the business domain, with authentication records configured properly, so tenant correspondence comes from the company rather than from a free consumer address.
The business line. The company's existing number was migrated off its previous arrangement and onto our own phone platform, with extensions for the owner and staff, voicemail boxes with notification, and call handling built around what a property manager actually receives: maintenance requests, tenant enquiries and after-hours calls.
The tenant portal. All fifteen units verified in the account, the tenant-facing rent payment and maintenance request pages working, and lease import running - a feature that we fixed the day before go-live, which is exactly the sort of thing that only surfaces when real leases meet real code. Digital lease signing was wired in through our own document-signing product rather than a third-party subscription.
Money tools. Interac was set up as the tenant rent payment path. Expense tracking and invoicing were connected to the same account so receipts and rent invoices lived in the same place as the units they belonged to.
Later phases covered outbound calling and a late-payment notification chain - email first, then SMS, then a voice call for persistent cases. That sequencing matters more than it looks: a property manager chasing rent by hand loses hours a month to work that is entirely mechanical and entirely unpleasant.
How the engagement ended
The client gave notice a few weeks in advance. The July invoices were cancelled manually before they went out, and on 2 July 2026 we wound the paid services down.
We moved the account to the free tier rather than deleting it. The property-management portal dropped to its free plan and stayed active, the expense and invoicing tools were already on free plans and were left alone, the email account was retained, and the suite login continued to work. The telephony product has no free tier, so that subscription was cancelled and call routing disabled. We checked the billing history in both directions and confirmed nothing was owed either way - one invoice had been paid, and two later re-issues were duplicates that collected nothing and were cancelled.
One item remained genuinely outstanding: the direct-dial number associated with the business had not been released, and releasing or porting it is a decision that belongs to the client, not to us. It stayed registered rather than being dropped, because dropping a business number unilaterally is not something a vendor should ever do.
What it taught us, and what that is worth to the next client
The most useful thing this engagement produced was not the deployment. It was the wind-down.
Cancelling one small account surfaced six separate places in our own platform that independently recorded what a client was paying for - the central billing records, per-product subscription tables in three different applications, and a product-entitlement field that was still advertising the old plan after everything else had been changed. None of them wrote through to each other. A client cancelling could therefore be simultaneously cancelled, active and on a free trial, depending on which page they happened to open.
We found all six, aligned them, took a database backup before touching anything, and then treated the underlying problem as a platform defect rather than a one-off. That work drove a plan-code cleanup across the suite. Every client onboarded since has been onto a cleaner billing spine because this one left.
We also found a duplicate client record that could not be hard-deleted, because security audit events and a synchronisation queue referenced it and the audit retention period runs for seven years. It was marked as a duplicate instead of destroyed. That is the correct answer, and it is worth saying out loud: a system that lets you erase a client record cleanly is a system that is not keeping the audit trail it claims to keep.
Why we publish an engagement that ended
A portfolio page that lists only current clients is not evidence - it is a snapshot of who has not left yet. What a prospective client actually needs to know is what happens at the end: whether the invoices stop, whether the data survives, whether the number is held hostage, whether anyone argues about a refund.
Here the answer was: invoices cancelled before they issued, account downgraded rather than deleted, login retained, nothing owed in either direction, and the phone number left in place for the client to direct. That is the part of the story worth publishing.