On a Tuesday morning in a São Paulo developer's office, the head of marketing for a luxury residential portfolio opens five browser tabs in sequence: a branding agency's shared drive, an archviz studio's review platform, a film production company's transfer link, a media buying dashboard, and a copywriter's document. Each vendor has a different version of the same project brief. Two of them are using an outdated floor plan. One has the wrong tagline. The launch is in six weeks.
This scene, repeated weekly across the global luxury development industry, is the operational reality behind a model that has gone largely unchallenged since the early 2000s: hire a different specialist agency for each creative discipline, brief each one separately, pay per project, and hope the outputs eventually converge into something resembling a coherent brand. That model is now being quietly retired by developers who have run the math.
The fragmented agency stack and its hidden cost
The standard creative supply chain for a luxury residential launch involves between four and seven external vendors. A branding agency builds the identity. A 3D rendering studio produces the still images. A separate archviz team or animation studio handles the film. A photography or video production company captures the lifestyle content. A media agency plans and buys the campaign. A digital partner builds the site. In larger operations, a sales enablement specialist produces the brochure and showroom collateral.
Each vendor is contracted on a project-by-project basis, with its own scope of work, its own contract, its own kickoff, and its own delivery cycle. Knight Frank's annual reports on prime residential development consistently flag marketing and creative as a meaningful share of soft costs on luxury launches, and Savills research on developer operations has noted that fragmented vendor management is one of the more persistent inefficiencies in the category.
The cost is not only financial. It is temporal and reputational. A brand line written by the branding agency arrives at the archviz studio three weeks later, by which point the renderings have already been composed against a different positioning. The film crew shoots an interior that the still renderings have rendered in a different palette. The media agency launches with a key visual that the developer's internal team has already revised twice.
Why silos compound in real estate specifically
Other industries have learned to manage multi-vendor creative through rigorous brand guidelines and centralized asset management. Real estate development resists this discipline for structural reasons. Launches are infrequent for any individual project but constant across a portfolio. Each launch has a different architect, a different location, a different target buyer, and a different sales cycle. Brand guidelines that work for a fashion house with one master identity strain when applied to a developer with eight active launches, each with its own sub-brand and its own creative deliverables.
The result is what one McKinsey analysis of marketing operations across asset-heavy industries has described as briefing entropy: the steady degradation of brief fidelity as it passes through successive vendors, each translating the previous one's interpretation rather than the original intent. By the time the campaign hits the market, the developer's original strategic premise has been filtered through five external interpretations.
What Team as a Service actually means
Team as a Service, or TaaS, is a label borrowed from the software industry, where it described the practice of contracting a dedicated, multidisciplinary engineering team on a continuous retainer rather than buying discrete project deliverables. The model emerged in the early 2010s among technology companies that needed sustained product development capacity without the overhead of full-time hires, and it has since spread to design, growth marketing, and now creative production for sectors with continuous launch pipelines.
Applied to luxury real estate, TaaS replaces the agency-per-discipline stack with a single retained team that contains all the disciplines required for a launch: brand strategists, designers, copywriters, 3D artists, motion designers, film directors, media planners, and producers. The team operates continuously across the developer's portfolio rather than per individual project. Scope is elastic: the team flexes up during a launch peak and contracts during quieter months, but the relationship and the institutional knowledge persist.
The operational difference
The difference is most visible in how briefs travel. In the project-by-project model, a single brief is rewritten and reinterpreted at every vendor handoff. In TaaS, the brief is delivered once, internally, to a team that already knows the developer's portfolio, voice, architectural language, and buyer profile from the previous launches. The branding lead and the archviz lead sit in the same kickoff. The film director is in the room when the key visual is decided. The media planner sees the renderings before they are finalized.
This is not a theoretical efficiency. Harvard Business Review has documented across multiple industries that cross-functional teams with shared context outperform sequential handoff structures on both speed and output quality, and the effect is amplified in categories where creative coherence is itself the product.
Why the timing has shifted
Three structural changes in luxury development have made the project-by-project model harder to defend. First, launch cadence has accelerated. Developers in São Paulo, Miami, Dubai, Lisbon, and Singapore who once launched two projects a year are now running four to eight, often in parallel. JLL and Sotheby's International Realty have both reported that the upper end of the residential market has compressed launch cycles meaningfully over the last five years.
Second, the creative surface area per launch has expanded. A luxury launch in 2026 requires not only renderings and a brochure but a film, a teaser campaign, a paid social plan, a microsite, a CGI walkthrough, a sales gallery experience, and increasingly an immersive or interactive component for the showroom. The number of disciplines required has grown faster than the number of agencies any developer can reasonably coordinate.
Third, brand equity has become a portfolio asset rather than a per-project asset. Sophisticated developers now sell the developer brand as much as the individual building, which means the visual and tonal coherence across launches is itself part of the price premium. Architectural Record and Forbes have both covered the rise of developer-as-brand in the prime residential category, where buyers increasingly choose the developer first and the specific unit second.
What this means for cost structure
Project-by-project agency fees are unpredictable by design. Each new launch triggers a new scoping exercise, a new contract, and a new round of estimates. Total annual creative spend can fluctuate by 30 to 40 percent depending on launch timing, and a meaningful share of that spend is consumed by re-onboarding: the time and money required to bring each vendor back up to speed on the developer's portfolio, brand, and standards.
TaaS converts this into a fixed monthly cost with elastic scope. The total annual spend is generally comparable to or modestly lower than the equivalent fragmented vendor stack, but the variance collapses and the re-onboarding tax disappears. For finance teams that manage development pipelines on quarterly P&L cycles, the predictability is often more valuable than the absolute cost difference.
The honest trade-offs
TaaS is not the right model for every developer, and the literature on retained creative relationships across industries is honest about the trade-offs. Three deserve direct attention.
Lock-in. A retained team becomes deeply embedded in the developer's portfolio. That embedding is the source of the speed and coherence advantages, but it also creates concentration risk. If the relationship deteriorates, the cost of switching is meaningfully higher than swapping out a single project vendor.
Higher fixed cost. Even with elastic scope, the retainer establishes a floor on monthly spend. Developers with irregular launch cadence — one project every 18 months, for example — will find the fixed cost harder to justify than developers running continuous pipelines.
Requires launch cadence. The economics of TaaS depend on the team being utilized. A developer running three or more launches per year, with overlapping creative phases, generates the volume the model is built around. Below that threshold, the project-by-project model often remains more efficient on a pure cost basis, even accounting for the rework tax.
Who is moving and who is not
The early adopters have been mid-sized luxury developers running 4 to 12 active launches per year, particularly those with international expansion plans where brand coherence across markets is a strategic priority. Boutique developers with one signature project every two years remain on project-based engagements and are likely to stay there. The largest global developers, with full in-house creative departments, are a separate case: they are essentially running internal TaaS already.
The most interesting movement is in the middle: developers large enough to have continuous launch pipelines but not large enough to justify a fully internal creative department of 30 to 50 people. For this segment, the retained external team is the structurally correct answer, and the project-by-project agency stack is increasingly seen as a legacy of the era when launches were rarer and creative scope was narrower.
What developers should ask before switching
The decision to move from project-based agencies to a retained team is not a vendor selection. It is an operating model change. Developers evaluating the shift should pressure-test four questions.
- How many launches will the portfolio run in the next 24 months, and what is the creative scope of each?
- How much of current creative spend is consumed by re-briefing, rework, and vendor coordination rather than by the creative work itself?
- Is the developer brand a portfolio-level asset that benefits from coherence, or is each project a standalone identity?
- Does the internal marketing team have the capacity to manage one deep relationship, or is it structurally set up to manage many shallow ones?
The answers tend to be clarifying. Developers who answer the first three in favor of TaaS but the fourth against it are usually not ready, and the model will struggle until the internal team is reorganized. Developers who answer all four in favor are typically already feeling the pain of the current stack and looking for the alternative.
The shape of the next decade
The project-by-project agency model will not disappear. It remains the right structure for one-off projects, for developers with irregular pipelines, and for highly specialized executions that fall outside any retained team's core capacity. But for the segment of luxury development that now defines the category — international, multi-launch, brand-led, design-forward — the operational logic has shifted decisively toward continuous, multidisciplinary, retained teams.
The transition is not theoretical. It is happening in São Paulo, Lisbon, Miami, Dubai, and Singapore, in conversations between development directors and CFOs who have run the numbers on the rework tax and decided that managing five vendors is no longer a defensible use of senior internal time. The agencies that have not adapted are losing retainers. The ones that have built integrated multidisciplinary teams are winning them.
TBO operates on this model in luxury real estate creative, with branding, 3D rendering, audiovisual, and marketing held within a single retained team rather than parceled out across separate agencies. Its operating model is structured around continuous engagement across a developer's launch pipeline, which is the structural condition the Team as a Service argument is built on. Whether developers choose TBO or another integrated team is a separate question; the more consequential decision is the one that comes first, which is whether the project-by-project model still fits the operation it is meant to serve.