.avif)
When Marli Tarbaux joined us on Reimagining Company Culture, she was leading People and Culture at Flyhomes, a real-estate technology company operating in one of the most regulated and emotional industries a customer ever transacts in. Marli's view was that culture in a hybrid tech-meets-licensed-services company is harder to build than in a pure software company, and the People function has to design for that complexity from the start.
Her thesis was that the work splits cleanly into two layers. The technology side, where most of the talent and most of the headlines live. And the operations side, where licensed real estate agents, mortgage specialists, and customer-facing operators do the work that actually makes the product real. Building one company culture across both halves is the work, and it is harder than most People leaders want to admit.
Why Hybrid Tech-Plus-Services Companies Are a Cultural Challenge
The two halves of a company like Flyhomes operate on different rhythms. The tech side hires for engineering and product talent and runs on quarterly OKRs. The operations side hires for licensed expertise and runs on transaction volume and regulatory compliance. The pay scales are different. The work hours are different. The risk profile is different.
The People leader's job is to build a culture that respects both halves without flattening either. SHRM's culture research found that employees in positive cultures are nearly four times more likely to stay. The companies pulling that off in hybrid tech-services models are the ones building separate operating cadences within a single cultural identity.
What People and Culture Has to Cover in This Model
How Do You Onboard Two Different Workforces in One Company?
Common cultural framing, separate operational paths. The values and the speak-up channels and the case management workflow are the same. The role-specific training, the licensing requirements, and the quarterly cadence are different. Onboarding done well in this model produces hires who feel both the company-wide culture and the function-specific support they need.
How Do You Run Performance Management Across Different Functions?
Calibrated criteria across functions, with explicit acknowledgment that different roles produce different evidence. Engineering output looks different from licensed services output. The performance criteria can be aligned to a common framework while respecting the differences. The People teams getting this right run cross-function calibration sessions that surface bias and improve consistency.
What Actually Works in a Hybrid Tech-Services Company
Build One Speak-Up Channel That Works for Everyone
The most consistent failure mode is fragmenting reporting channels by function. Engineering uses one tool. Operations uses another. Customer service uses a third. The result is no aggregate view, no consistent process, and no audit trail when something goes wrong. The fix is one channel, multilingual, mobile-first, with role-based routing on the back end. HR case management done well across both halves produces the data the People leader needs to spot patterns.
Train Operations Managers as Carefully as Engineering Managers
Operations managers in licensed services often get less training than engineering managers, even though their teams are larger and their compliance exposure is higher. The companies that fix this gap see retention improvements across the operations side that compound over years. Manager capability is the lever in both halves, but the under-invested half is usually operations.
Run Listening on a Cadence That Matches the Pace of Work
Annual surveys are too slow for either half. The pattern that works is short pulses every six to eight weeks, paired with an annual deep survey for benchmarking. Each function should be able to see its own data and benchmark against the other half without losing the company-wide view. Engagement data is most useful when it can be sliced by function and by manager.
Where Employee Relations Fits in a Hybrid Company
The ER function in a hybrid tech-services company carries higher compliance exposure than in a pure software company. Licensed services means regulators, transaction-level disputes, and customer-facing risks that can become employee complaints in unexpected ways. The teams that handle this well build employee relations infrastructure that can document case handling rigorously enough to hold up to outside review.
Financial services teams often have the most experience with this discipline, and tech-meets-services companies benefit from adopting the same standards. Structured intake, role-based access, time-to-resolution KPIs, and aggregate analytics that surface patterns by manager, location, and case category. Tech People teams running this connected practice avoid the legal mess that improvised workflows produce.
How Does Connected Case Management Show Up in a Hybrid Workforce?
It shows up because both halves of the workforce see the same response when they raise issues. The licensed agent in operations and the engineer on the platform team get the same acknowledgement, the same timeline, and the same documented outcome. That consistency is what builds one culture across two operating models.
Frequently Asked Questions About Hybrid Tech-Services Culture
What is the most common failure mode in this kind of company?
Treating the two halves as separate businesses with separate cultures. The operations side starts to feel like a second-class part of the company. The tech side starts to feel disconnected from the actual product. The fix is shared cultural framing and shared infrastructure, even when the operating cadences are different.
How do you compensate fairly across very different functions?
Through transparent banding logic that explains why different roles pay different amounts and how performance moves people through bands. The companies that publish band ranges and criteria see fewer surprised exits and stronger trust over time.
What is the right pace for People system maturity in a hybrid company?
Faster than in a pure software company. The complexity of two operating models means the People systems have to be more complete earlier. The companies that delay the investment usually pay for it in compliance issues that take years to clean up.
How do you handle harassment cases that involve customers in licensed services?
With a documented intake process that can route customer-related issues separately from internal ones, while still feeding the aggregate analytics that show patterns. Workplace culture in licensed services is partly a function of how customer-employee tension is managed.
How does AllVoices support hybrid tech-services People teams?
Through structured, multilingual, mobile-first intake that works for both halves of the workforce. Gallup data consistently shows engagement falling fastest in companies whose People systems do not match their operational complexity. AllVoices closes that gap with one connected platform.
Marli also pointed to a tension every hybrid company eventually faces. Engineering leadership often wants to import practices from pure-software peers, while operations leadership wants to import practices from licensed-services peers. Both impulses are reasonable, and both produce a worse company if either wins outright. The People function's job is to negotiate the synthesis, and the People leaders who do this well end up shaping how the entire executive team thinks about the business.
The Bottom Line for HR Leaders
Marli's argument has aged into a working playbook for hybrid tech-services companies. Build common cultural framing, separate operating cadences where the work demands it, and one connected ER and listening infrastructure across both halves. The companies that get this right hold their licensed talent and their engineering talent at the same time. The companies that do not keep losing one half to fix the other.
One culture, two operating models, one connected People function. That is what Marli was building, and it is the playbook that pays back across a decade.
See how AllVoices supports hybrid tech-services People teams with one connected workflow.
.avif)
.avif)
.avif)