Case study, client anonymised
3x portfolio growth on the same team: a coliving startup's scaling story
100 beds to 300+ beds across 8 properties in 12 months, on a founding team of four, with no additional operations hire. The platform grew a module at a time.
At a glance
3x
Portfolio growth with same team
70%
Tenant queries handled by AI
21
Days to initial deployment
4
Modules added over 4 months
The client
country not named in source; the source says only 'a major South Asian metro'. Named details withheld at the client’s request.
A venture-backed coliving startup operating in a major South Asian metro, targeting young professionals with community-focused shared living. They started with 100 beds across 3 properties and grew to 300+ beds across 8 properties in 12 months.
The founding team was four people, handling operations, finance and community management between them. there was no dedicated operations manager, no finance hire and no support desk; the founders did all of it alongside fundraising and site acquisition. That constraint is the whole story here. Growth had to come out of the system, because it was not going to come out of headcount.
Spreadsheets that broke at eight properties
As the startup scaled from 3 to 8 properties, their spreadsheet-based operations completely broke down.
The four-person team was drowning in manual invoicing, WhatsApp-based maintenance requests and paper-based onboarding. They were spending more time on admin than on growth and community building. Every new property added exponentially more manual work. They needed a system that could scale with them without requiring proportional headcount growth.
Invoicing done by hand, property by property
Rent invoices were raised manually. each property had its own sheet, its own rent roll and its own set of move-in dates, so a single billing cycle meant working through eight separate files and reconciling them against the bank statement afterwards. at 300 beds this ran to several hundred invoices a month, all produced by the same person who was also handling finance for the business as a whole.
Maintenance requests lived in WhatsApp
Residents reported problems by WhatsApp message. some to a property group, some directly to whichever founder they had a number for. A message is not a ticket. There was no owner, no timestamp anyone was accountable to, and no record afterwards of what had already been fixed in which room. requests were regularly missed entirely when a chat moved on before anyone acted on them.
Onboarding was paper-based
New residents were onboarded on paper. identity documents, agreements and deposit records were collected physically at the property and filed there, which meant the founding team had no single view of who had signed what, and no way to onboard a resident without someone being on site.
Every new property multiplied the work
This is the part that matters most for an operator reading this. The load did not grow in a straight line with the portfolio. Every new property added exponentially more manual work, because each one added its own invoicing cycle, its own chat group, its own paperwork and its own set of exceptions to remember. by the sixth property the team had started declining or delaying new sites they had already sourced, because they could not see how to absorb the operational load.
Admin was crowding out the actual business
They were spending more time on admin than on growth and community building. For a venture-backed coliving startup, those two things are the business. Community is the product, and growth is what the funding was raised against.
What JumboTiger built
JumboTiger deployed an initial configuration in 21 days with the Booking and Onboarding and Payments modules. As the operator scaled, they added the Tenant Portal in month 2, the AI Layer in month 3, and the Listing Website in month 4.
This modular approach let them start simple and add capabilities as their portfolio grew. Worth being explicit about why that sequencing mattered: a four-person team could not have absorbed a full platform rollout in one go, so each module was introduced only once the previous one was in daily use.
Days 1 to 21: Booking and Onboarding, plus Payments and Rent Collection
The initial configuration went live in 21 days and covered the two workflows that were failing hardest: getting a resident in, and getting paid.
Booking and Onboarding replaced the paper process. application, document upload, agreement and deposit are completed digitally before move-in day, so nobody has to be on site to onboard a resident
Payments and Rent Collection replaced manual invoicing. invoices are generated automatically from the rent roll on a fixed cycle across all properties at once, rather than sheet by sheet
payments are matched to residents automatically, and overdue rent is flagged and chased by the system instead of by a founder
Initial deployment took 21 days from start to live
Month 2: Tenant Portal and mobile app
The module that took maintenance out of WhatsApp.
residents raise maintenance requests in the portal instead of messaging a group chat, so every request has an owner and a status
residents can see their own ledger, invoices and payment history without asking anyone
community announcements and house information moved into the app, which removed a recurring source of repeat questions
Month 3: AI Layer and advanced analytics
The module the founders single out. In their own words, the AI chatbot alone saved them from needing a full-time support hire.
The AI chatbot now handles 70% of tenant queries automatically
the queries it absorbs are the high-volume, low-complexity ones: rent due dates, Wi-Fi details, house rules, notice periods and how to raise a maintenance request
anything it cannot answer is escalated to the team with the conversation history attached, so the resident does not repeat themselves
analytics gave the founders their first live view of occupancy and collections across all 8 properties in one place
Month 4: Listing Website and Booking Engine
The module that changed where demand comes from.
The listing website generates direct bookings that bypass expensive aggregator commissions
prospective residents can see live availability by property and room type, and book without an email exchange
the operator has not shared a direct-booking percentage or a commission saving figure, so this study makes no numeric claim about the channel
The results
| Metric | Before | After |
|---|---|---|
Portfolio size | 100 beds across 3 properties | 300+ beds across 8 properties |
Operations headcount | 4-person founding team | 4-person founding team, no additional operations hire |
Tenant queries handled without a person | None | 70% |
Time to initial deployment | N/A | 21 days |
Rent invoicing | Manual | Payments and Rent Collection module |
Resident onboarding | Paper-based | Booking and Onboarding module |
Maintenance requests | WhatsApp messages | tracked requests in the Tenant Portal, each with an owner and a status |
Direct booking channel | none; demand came through aggregators and referrals | Own listing website and booking engine |
Portfolio-wide occupancy visibility | compiled by hand from per-property sheets | live, in one dashboard |
Three times the portfolio on the same four people. Seventy percent of tenant queries answered without anyone picking them up. First configuration live in 21 days, then four modules added over four months as the portfolio grew. the operator has not supplied hours-saved or revenue figures, so this study deliberately makes no financial claim.
The takeaway
The number that matters here is not 3x. It is 3x on four people. Most operators scale a coliving portfolio by hiring against it, one operations coordinator per few hundred beds, and the cost base grows with the bed count. This team went from 100 to 300+ beds and did not add a single operations person. the modular rollout is what made that possible; had the platform arrived as one large implementation, a four-person team would have had to stop operating in order to adopt it. Start with the workflow that is bleeding, get it live, then add the next one.
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.