Case study, client anonymised
A premium coliving launch: 112 pages of thinking before a line of code
250+ rooms. Premium coliving. New market. The operator had 20 years of real estate experience. They had zero coliving technology. We built everything from a blank page.
At a glance
112+
Pages of product documentation
27
User stories documented
30
Communication templates
8 weeks
To complete the specification
The client
United Arab Emirates. Named details withheld at the client’s request.
A premium coliving operator based in the UAE, launching their first properties in a Gulf capital city. The operator brought 20+ years of real estate development experience, deep local networks and significant capital. What they did not have was any coliving-specific technology, operational workflows or resident communication infrastructure.
Their properties were being built to a premium standard: private studios and ensuite rooms priced at $1,500-$3,000 per month all-inclusive. At that price point, residents expect everything to work seamlessly. Not just the apartment. The entire experience: booking, communication, community, maintenance, billing.
Building the invisible infrastructure
Most people think about coliving technology and picture a PMS dashboard. That is the visible layer. But underneath it are hundreds of invisible decisions that determine whether the operation runs smoothly or breaks on contact with residents.
Corporate group bookings
What happens when a corporate client wants to book 15 rooms for a 3-month employee rotation? How does the system handle group bookings, corporate rate cards and split invoicing?
Maintenance at 2 AM
What happens when a resident requests a maintenance repair at 2 AM? Who gets notified? What is the escalation path? How quickly is it resolved? How does the resident know it has been received?
Smart lock access
What happens when a resident’s smart lock access code expires? Can the system auto-generate a new one? Can the community manager issue a temporary code for a guest? What about the cleaning staff?
The resident communication lifecycle
What sequence of emails does a resident receive from the day they inquire to the day they move out? Is the day-3 check-in automated? Is the lease renewal reminder sent at 60 days or 30?
What JumboTiger built
The operator knew these questions needed answers before the first resident walked through the door. They did not want to improvise. They wanted a blueprint.
So we did not write code first. We wrote the thinking first. Everything else followed from the specification.
Product specification: user stories and workflows, 57 pages
Every operational scenario the operator would encounter, documented as a user story with a detailed workflow.
“As a prospective resident, I want to book a room online and receive instant confirmation so I don’t have to wait for an email response.”
“As a community manager, I want to see all maintenance requests for my property sorted by urgency so I can prioritise my day.”
“As a corporate client, I want to book 15 rooms for my team and receive a single consolidated invoice so my accounts payable process is simple.”
“As a resident, I want to receive my smart lock access code automatically when I sign my lease so I can let myself in on move-in day without waiting for a key handoff.”
27 user stories in total. Each one includes the actor, the goal, the acceptance criteria, the edge cases and the workflow diagram. This level of documentation means developers can build without ambiguity: no guessing, no assumed behaviour, no rework
Design specification, 28 pages
Wireframes for every screen in the platform
Data model covering how properties, rooms, tenants, leases, tickets and payments relate to each other
API architecture for integrations: payment gateway, smart locks, building management
Technical requirements per module
15 open decisions documented for leadership sign-off, including payment gateway selection, maintenance escalation thresholds and the notification matrix
Communication templates, 30 in total
Every touchpoint in the resident journey, designed and written before the first resident arrived.
Inquiry auto-response with availability and pricing, sent within 2 minutes
Application received confirmation with timeline expectations
Booking confirmation with a complete move-in checklist: what to bring, what is provided, building access information
Pre-move-in email sequence: 7 days before for logistics, 3 days before for local tips, 1 day before for access codes and final details
Welcome email with house rules, Wi-Fi credentials, emergency contacts and a neighbourhood guide
Day 3 check-in and day 7 satisfaction survey
Maintenance: request received, assigned, in progress, resolved, four automated touchpoints per ticket
Event invitations, community announcements and a monthly newsletter template
Renewal sequence at 60 days, 30 days and 14 days before expiry
Move-out instructions, deposit return process, post-departure feedback and referral ask
Not a single resident interaction is improvised. The experience feels personal because the system handles the logistics, freeing the community manager to focus on relationships
Smart lock integration architecture
The properties were built with SALTO smart locks. The PMS needed to communicate with the physical building.
API specification for the PMS-to-SALTO bridge
Access code auto-generation on lease signing, so the resident gets their code before move-in day
Automatic revocation on lease end date, with no manual deactivation needed
Temporary access codes for guests, maintenance staff and cleaning crew, time-limited and auto-expiring
Emergency override protocol for building management
Full audit trail of all access events for compliance and security
The results
| Metric | Before | After |
|---|---|---|
Product documentation delivered | 0 pages | 112+ pages |
User stories documented | 0 | 27 detailed stories |
Communication templates | 0 | 30 (covering full lifecycle) |
Integration specifications | 0 | 3 (SALTO, payments, BMS) |
Time to complete specification | N/A | 8 weeks |
Development rework estimated savings | N/A | 6-8 weeks / $45,000-$60,000 |
Open decisions surfaced for leadership | Untracked | 15 decisions documented |
Rate combinations in pricing engine | N/A | 50+ |
The operator launched on time. The development team built from the specification with minimal rework. Not a single resident touchpoint was improvised on opening day. The 112 pages of documentation saved an estimated 6-8 weeks of engineering time and $45,000-$60,000 in development costs that would have been spent on iteration, miscommunication and rebuilds.
The takeaway
Most technology projects fail not because of bad code, but because of bad specification. “We’ll figure it out as we build” sounds efficient. In practice it means: build, discover it is wrong, tear it down, rebuild, discover a different thing is wrong, repeat. The specification-first approach costs 8 weeks upfront and saves months of rework downstream. Designing the thinking is what makes the technology work.
Want a system built around how you operate?
Book a 30-minute call. We will be honest about whether a custom build is the right answer for your operation.