Privately held multifamily owner, more than 50 communities
Employee onboarding, transfers and offboarding, start to finish
The problem. Every new hire at a property meant a chain of manual steps: account, licenses, groups, shared mailbox, folder access and a ticket to track it. High site-staff turnover made it constant.
What we built. A new-hire form now drives the whole sequence. The account is created, the license is purchased and assigned, the right community mailbox and folders are granted by role, and the ticket opens and closes itself. Transfers, title changes and departures run the same way.
The result. Onboarding no longer depends on a technician working a checklist, and access is consistent across every community.
About 20hires, transfers and departures processed a month (measured)
8 to 12 hoursof manual work replaced a month, at an estimated 20 to 45 minutes each
Multiple clients
Software licenses bought just in time and reclaimed automatically
The problem. Licenses were bought ahead of need and rarely released when people left, so companies paid every month for seats nobody used.
What we built. A seat is purchased at the moment an onboarding needs one. A daily sweep finds unassigned licenses across every managed tenant and returns them.
The result. License counts track actual headcount without anyone auditing them by hand.
Privately held multifamily owner
Move-in and move-out photo packets, filed without anyone touching them
The problem. Unit photos taken at move-in and move-out are the evidence for deposit decisions. They were being assembled, uploaded and filed by hand, inconsistently.
What we built. Photos captured on site are assembled into a single PDF, filed in the correct property and unit folder in SharePoint, and sent to the people who need them, with retries, a fail-fast check and an alert to our team if anything does not land.
The result. Records are complete and findable when a deposit is disputed.
1,820move packets processed in five months, about 365 a month (measured)
60 to 90 hoursof manual work replaced a month, at an estimated 10 to 15 minutes each
Privately held multifamily owner
Monthly financial reports filed to the right property, every month
The problem. Each month the accounting system emails a financial report for every property. Someone had to open each one, work out which property it belonged to and save it in that property's site.
What we built. A flow reads each report as it arrives, matches it to the property and files it in that property's SharePoint site, where owners and managers expect to find it.
The result. Reports are in place the day they are issued, with no monthly filing job for anyone. It has run every month since late 2023.
About 60financial reports filed a month (measured)
3 to 5 hoursof manual work replaced a month, at an estimated 3 to 5 minutes each
Real estate owner and its management company
A file structure with access that follows the role
The problem. Years of ad hoc sharing had left no one sure who could see what across owners, management and on-site teams.
What we built. A three-tier SharePoint structure for owners, management and each community, with permissions granted by role through dynamic groups, and an audit of every existing sharing link.
The result. Access is explainable, auditable and ready for AI assistants to be switched on safely.
Clients in litigation
Legal holds and eDiscovery, run with outside counsel
The problem. A hold notice arrives and the company has days to preserve and produce records it has never had to find before.
What we built. We scope the request with the attorney, place holds in Microsoft Purview, run and document the searches, and deliver the export in the format counsel needs.
The result. Requests are answered on time with a method that can be defended.
All managed clients
Security investigations answered from the evidence
The problem. A user cannot sign in while traveling, or a convincing phishing email reaches an executive. Someone has to work out exactly why.
What we built. Repeatable investigations across every tenant we manage: which policy blocked a sign-in, how a message was delivered, who else received it and what to change.
The result. Clear answers and a specific fix, instead of guesswork.