×
![Modal Image]()
What started as a fast MVP build evolved into product development inside a much larger engineering organization, across a new technology stack and production systems already serving existing users.
That range is what makes the engagement significant.
Amplified was there when OfficeTogether was still an early product concept. The team helped turn it into a production application, stayed involved as OfficeTogether built its own engineering organization, and continued working after the acquisition introduced a fundamentally different technical environment.
Inside Envoy, the work expanded into mature production systems, including a backend migration for Rooms that had to preserve the customer experience while changing the infrastructure underneath it.
The collaboration started with a clear delivery problem.
OfficeTogether had early wireframes, product direction and an enterprise demo approaching. It needed a functioning product in four weeks.
Amplified assembled the engineering team and turned that initial direction into the first working version of OfficeTogether. The MVP was ready for the demonstration.
OfficeTogether was addressing a broader workplace problem: how companies could coordinate people, desks, shared spaces and office resources as hybrid work became part of day-to-day operations.
Over roughly the next two years, the initial MVP developed into a production web application. Amplified remained part of the product team, continuing feature development while OfficeTogether hired engineers internally and helped new engineers get up to speed with the product and codebase.
Envoy acquired OfficeTogether in 2022 and they asked the Amplified team to continue working after the acquisition.
The challenge wasn’t their new stack. Amplified had to become productive inside an engineering system it had not built.
At OfficeTogether, Amplified had worked on a product and codebase it helped shape from the beginning. Inside Envoy, the same engineers entered an established organization with existing architecture, deployment practices, services, conventions and decision-making processes.
The job was no longer to create the engineering environment around a new product. It was to understand an existing one quickly enough to contribute inside it without creating a parallel way of working.
One of Amplified's major engineering responsibilities inside Envoy was replacing the backend behind Rooms.
Rooms supported the experience around shared meeting spaces and were already being used by customers. Its backend also operated inside a larger environment of interconnected services maintained by multiple engineering teams.
That made the migration more than a backend rewrite. The new implementation had to work without changing the experience customers already depended on.
The migration had to preserve existing behavior while changing the system underneath it. That meant compatibility with the existing Rooms experience, enough observability to detect problems early, controlled rollout, and recovery paths for unexpected failures.
Most importantly, customers should not have needed to know the migration happened.
The engineering problem was therefore broader than replacing one implementation with another. It required understanding not only what the new system should do, but everything the existing system was already expected to keep doing.
Amplified's work on Rooms extended into the tablet experience as well.
The team worked on capabilities including creating meetings, booking rooms in advance, surfacing attendees and room amenities, and improving how the physical meeting-room experience connected with Envoy's wider workplace product.
On the surface, tablet UX and backend migration are very different engineering tasks. The constraint behind them was similar: both involved changing parts of a product customers already relied on.
New implementation decisions had to fit the existing experience rather than forcing the rest of the product to adapt around them.
The move from OfficeTogether into Envoy changed the scale at which engineering decisions had to be made.
At OfficeTogether, Amplified had been involved from the first MVP. Inside Envoy, the team was operating across multiple services, more stakeholders and established production practices.
The production model included practices such as daily deployments, feature flags and system-design RFCs. Individual engineering decisions now existed inside a wider system: a change to one service could affect others, architectural decisions involved more stakeholders, and release discipline mattered because more teams and products depended on shared infrastructure.
Amplified had to become productive inside that environment without requiring Envoy to create a separate process for an external engineering team.
The OfficeTogether-to-Envoy engagement spans two very different stages of product engineering.
At the beginning, the challenge was speed: take an early product concept, assemble the engineering capability around it and deliver something real in four weeks.
Later, the challenge was almost the opposite: work inside a mature platform with existing customers, established engineering standards, multiple interconnected services and infrastructure that could change only if the customer experience remained dependable.
Amplified worked across both. The team built OfficeTogether's first working product, stayed as it developed into a production application, continued through the acquisition by Envoy, adapted to a new engineering organization and stack, and took ownership of production work inside an existing platform.
Amplified entered when OfficeTogether was still at the wireframe stage and stayed through product growth, team expansion, acquisition and engineering inside Envoy. Few engagements span that much change.
That continuity is the strongest proof of the relationship and of the kind of engineering partner Amplified aims to be.
