Ajackus embedded a specialist engineering team with VTS — the leading commercial real estate platform connecting owners, operators, brokers, and tenants globally — to deliver a complex third-party access control integration under tight feature timelines, enabling building administrators and staff to manage physical access entirely through Apple Wallet.
Engagement Model
Team Augmentation
Your team, supercharged — every Ajackus engineer comes AI-native, shipping 40–60% faster from day one
Managed Delivery
Tell us the problem. We handle everything — discovery, architecture, build, testing, deployment — at AI speed
BOT Model
We build your offshore engineering center with AI-trained teams, operate it to maturity, then transfer ownership to you
Expertise
AI Development
Custom AI agents, LLM integrations, RAG pipelines, and AI enablement — from strategy to production
Web Development
Enterprise web applications built with AI-augmented engineering for 40-60% faster delivery
Mobile Development
Native and cross-platform mobile apps built at AI pace with rigorous automated quality
DevOps
Infrastructure that scales automatically, deploys safely, and costs less
Low-Code/No-Code
Airtable, Glide, Shopify, and WordPress solutions with AI automation layers — built in days
Data Analytics
Turn raw data into decisions that drive revenue — 80% faster with AI-assisted analytics
UI/UX Design
User-centered interfaces designed with AI-powered speed — 3x faster iteration, sharper insights
How VTS Closed a Critical Third-Party Integration Gap with Embedded Ajackus Engineers
Services
Web Development
Technologies
Zero
Physical Access Cards Required
Apple Wallet
Enabled for Building Entry
Multiple
Third-Party Providers Integrated
Overview
Executive Summary
Client
Challenge
Goals
Journey
Results
Technology
Takeaways
FAQ
Executive Summary
The Problem
VTS needed to ship a new physical access management product feature within strict timelines, but previous engineering partners had underdelivered, and the complexity of integrating with multiple third-party access control systems — each with entirely different APIs, entity structures, and naming conventions — was creating compounding delays.
The Solution
Ajackus embedded a specialist engineering team with VTS, rapidly ramping on an unfamiliar codebase, establishing Architecture Design Records, running proactive pair programming sessions with senior VTS engineers, directly engaging third-party API providers to resolve integration ambiguities, and providing additional pull request review capacity to unblock delivery.
The Result
VTS successfully launched its physical access management product, converting building administrators from legacy third-party systems and enabling employees and staff to enter buildings using Apple Wallet — eliminating the need for physical access cards entirely.
Client
VTS is the operating system of the commercial real estate industry. Its platform serves as a unified hub for property owners, operators, brokers, and tenants — giving each stakeholder real-time visibility into leasing activity, space performance, and asset operations. The engagement with Ajackus was a team augmentation, with Ajackus engineers embedded directly into VTS’s existing product and engineering workflow to accelerate delivery on a feature that had already fallen behind with prior agency partners.
| Industry | Commercial Real Estate |
| Platform Scope | Enterprise SaaS — multi-stakeholder CRE operating system |
| Headquarters | New York, USA |
| Engagement Model | Team Augmentation — embedded engineers within existing VTS teams |
| Relationship | Ongoing multi-engagement partnership with Ajackus |
Challenge
The Bottom Line
VTS needed engineers who could join mid-stream, master a complex unfamiliar codebase fast, and deliver a working third-party access control integration without disrupting existing product delivery cadence.
Strict Timelines and Insufficient Prior Resourcing
VTS had firm feature delivery commitments and needed contributors who could begin shipping within days, not months. Previous agency partners had failed to meet the technical bar required, leaving the project behind schedule. Finding engineers with the right skills who could operate independently — without extended handholding — was non-negotiable.
Integration Complexity Across Disparate Third-Party Systems
Connecting VTS’s platform to multiple physical access control providers proved technically demanding. Each provider used distinct entity schemas, naming conventions, and API architectures. A single integration model could not be reused across providers — each required bespoke configuration, which multiplied the engineering surface area and the risk of inconsistencies in behaviour and user experience.
Knowledge Gaps and Review Bottlenecks
As a new team embedding into an established codebase, the Ajackus engineers had to build comprehensive product understanding from zero. Additionally, VTS’s existing PR review capacity was insufficient for the accelerated delivery pace, creating a bottleneck that threatened to negate the speed gains from adding new engineers.
Goals
The project focused on embedding engineers who could contribute immediately and deliver a complex multi-provider integration on time.
| Goal | Outcome Required |
|---|---|
| Rapid codebase onboarding | Contributing production-quality features within the first sprint |
| Third-party API integrations | Seamless integration with multiple access control providers, each handled distinctly |
| Architecture documentation | Architecture Design Records to support knowledge transfer and future maintainability |
| PR review capacity | Additional senior review bandwidth to unblock delivery pipeline |
| QA support | Guide QA team new to the product through testing the integration end-to-end |
| Feature delivery on time | Meet VTS’s committed product launch timelines |
Journey
Ajackus embedded engineers with VTS across five structured phases, from rapid onboarding to full delivery augmentation.
Phase 1: Rapid Codebase Familiarisation
Rather than wait for formal knowledge transfer sessions, the Ajackus team proactively connected with developers from other agencies and VTS teams who were familiar with the integrations product area. This cross-team collaboration enabled the Ajackus engineers to build a functional understanding of the codebase structure quickly, moving from orientation to active feature contribution within days.
Phase 2: Direct Third-Party Provider Engagement
Rather than routing all API questions through VTS’s internal teams — which would have created delays — the Ajackus team engaged directly with third-party access control providers to clarify API structuring, authentication flows, and entity mapping. This direct communication significantly reduced integration ambiguity and avoided the back-and-forth that had slowed progress with prior partners.
Phase 3: Architecture Documentation and Pair Programming
The Ajackus team worked alongside VTS engineers to create detailed Architecture Design Records (ADRs) covering the integration patterns, decision rationale, and system dependencies. Proactive pair programming sessions with senior VTS team members served dual purposes: accelerating knowledge transfer and raising the skill level of the broader team. This investment in documentation also reduced future maintenance risk.
Phase 4: Pull Request Review Augmentation
The Ajackus team supplemented VTS’s internal PR review capacity, taking on additional review workload to clear the delivery bottleneck. This directly accelerated the pace at which code could be merged, tested, and shipped — translating additional engineering hours into actual delivery throughput rather than review-queue delays.
Phase 5: QA Guidance and Dependency Management
The Ajackus team guided VTS’s QA team — which was new to the integrations product — through the testing process, identifying service dependencies and managing their impact on test stability. This minimised disruption to the QA cycle and ensured that integration behaviour was validated end-to-end before production deployment.
Results
VTS successfully launched its physical access management product, with Ajackus engineers contributing across integration development, architecture documentation, code review, and QA guidance.
What went well:
Technical Achievements
- Successfully integrated multiple third-party physical access control systems into the VTS platform, each with distinct API architectures handled independently
- Architecture Design Records created and handed over to VTS, supporting long-term maintainability and future integration work
- Pull request pipeline unblocked through additional Ajackus review capacity, enabling faster merge-to-production cycles
- QA team successfully guided through end-to-end integration testing for a product area they had not previously tested
Business Impact
- VTS’s physical access management product launched successfully, converting building administrators from legacy third-party systems to the VTS-managed platform
- Employees and staff now access building amenities using Apple Wallet — physical access cards eliminated entirely
- VTS’s commitment to its product delivery timelines was met despite the challenges inherited from prior engineering partners
- The Ajackus team became a trusted contributor to the VTS engineering ecosystem, with the engagement continuing across multiple product areas
Why It Worked
Context Before Code
The Ajackus team prioritised understanding the VTS platform’s structure before writing a line of production code — engaging proactively with other teams and pair programming with senior engineers rather than guessing. This investment in context meant that contributions, when they came, were aligned with existing architecture rather than adding to technical debt.
Provider-Direct Communication
Rather than waiting for VTS to mediate every API question, the Ajackus team communicated directly with third-party providers. This removed an entire layer of latency from the integration process, allowing ambiguities to be resolved in hours rather than days.
Documentation as Delivery
Architecture Design Records were treated as a first-class deliverable, not a post-project afterthought. By documenting decisions as they were made, the Ajackus team ensured that every integration choice was explainable, maintainable, and transferable — protecting VTS’s investment in the work beyond the engagement itself.
Frequently Asked Questions
How did Ajackus integrate with systems that each had different API structures and naming conventions?
Each third-party access control provider was treated as a distinct integration project rather than a variation on a common template. The Ajackus team communicated directly with each provider to clarify their specific API schemas, authentication requirements, and entity structures, then built bespoke integration configurations for each. This provider-specific approach — rather than forcing a generic model — produced more reliable and consistent behaviour across the full integration set.
How quickly can Ajackus engineers become productive on an unfamiliar enterprise codebase?
In the VTS integration engagement, the Ajackus team moved from zero familiarity to active feature contribution within the first sprint. This was achieved through proactive pair programming with senior VTS engineers, direct collaboration with other teams who knew the codebase, and a deliberate orientation strategy focused on the parts of the system most relevant to the delivery target. Ajackus engineers are selected in part for their ability to operate in unfamiliar technical environments with minimal ramp time.
What is the Ajackus team augmentation model and how does it differ from traditional outsourcing?
In the team augmentation model, Ajackus engineers embed directly into a client's existing engineering structure — attending standups, participating in code reviews, working within the client's sprint cadence, and contributing to the same product backlog as internal engineers. Unlike traditional outsourcing, there is no separate "Ajackus workstream" — the embedded engineers become part of the client team operationally, while Ajackus maintains responsibility for engineer quality, continuity, and performance. Ajackus can typically embed engineers within 2 weeks of engagement confirmation.
How does Ajackus handle knowledge transfer when embedding into an existing engineering team?
Knowledge transfer is bidirectional in Ajackus team augmentation engagements. The Ajackus team actively seeks product context through pair programming and cross-team collaboration, whilst also contributing to knowledge preservation through documentation — in VTS's case, Architecture Design Records that codify integration decisions for future maintainers. This approach ensures that the value of the engagement outlasts the engagement itself.
Can Ajackus support both feature development and code review capacity simultaneously?
Yes. In the VTS integration, the Ajackus team contributed both new feature work and additional pull request review capacity. For teams where the review bottleneck is limiting delivery throughput, embedding engineers who can both build and review is one of the fastest ways to increase effective output without restructuring the engineering team.
Let’s Build your Project Together
