Back to perspectives

PERSPECTIVES

The Operating Layer for Frontline Work: Why We’re Backing Firstwork

Frontline workers power some of the world's largest industries, yet the systems supporting them remain fragmented and manual. Firstwork is building an AI-powered operating layer to automate complex workforce processes and turn operational complexity into a scalable advantage. Here's why we're backing the team.

Oct 21, 2026

9 Min Read

Portfolio News

Share

For frontline workers, the path from application to first shift is often far more complicated than it should be. Despite representing the majority of the global workforce, they still have to navigate fragmented systems, repeated checks and layers of compliance that were never really designed around the realities of frontline work. These are the people who keep hospitals, warehouses, shops, restaurants and essential services running every day, making their ability to start work quickly and compliantly critical far beyond HR operations. Identity verification, right-to-work checks, licenses, insurance, background screening, payroll setup, training and client-specific requirements can all sit between accepting a role and actually being cleared to start, often across government portals and systems that do not talk to each other.

In high-volume frontline sectors, every unnecessary delay creates another opportunity for a candidate to drop out before their first shift, turning an administrative problem into a staffing problem. That complexity sits behind one of the largest labour markets in the world. Frontline workers represent the majority of the global workforce, yet the systems supporting them remain manual and heavily dependent on internal operations teams and BPOs. 

That gap between hiring and actual workforce readiness is where Firstwork operates.

The software budget is the wrong place to look

The traditional HR software market captures only part of the opportunity. The higher cost sits in the operational layer required to make those systems work together. A frontline employer may already use an ATS, HRIS, background-screening provider, e-signature tool and payroll system. Yet teams still spend significant time transferring information between them, reviewing documents, navigating government portals, resolving exceptions and confirming whether a worker is actually ready to start.

Most HR systems are designed to record a worker’s state; they were never built to carry out the operational work required to change it. Firstwork moves into that gap. Rather than adding another interface to the stack, it takes responsibility for the workflows that sit between systems and turns them into an auditable, automated process. Its pricing is benchmarked against the operational effort removed, rather than the number of software seats sold. The value, therefore, is less about giving teams another tool and more about reducing the manual coordination, handoffs and repetitive checks that make frontline operations so costly and difficult to scale.

From application to first shift, and everything around it

Firstwork starts with the journey from application to first shift, where worker data, compliance requirements and operational friction are most concentrated. From there, the same infrastructure follows the worker through recurring compliance, credential renewals, training, payroll readiness and other operational workflows across the employment lifecycle.

Underneath the product is a combination of AI agents and deterministic infrastructure. Document agents extract and validate information across dozens of document types. Browser agents operate government and third-party portals where APIs do not exist. A compliance engine translates thousands of jurisdiction- and customer-specific rules into fixed runtime decisions, while every check is logged and timestamped for auditability. The worker object graph then maintains the live state of each worker across an otherwise fragmented technology stack.

By design, Firstwork does not ask an LLM to make the final compliance call. AI is used where it is strongest: understanding processes, configuring workflows and interpreting messy, unstructured inputs. Once a case reaches a compliance decision, execution moves onto deterministic, customer-approved logic. In workforce operations, where an incorrect decision can lead to regulatory penalties, payroll errors or a worker being wrongly cleared, reliability and traceability have to be designed into the system rather than added afterwards. At scale, that translates into faster access to work for frontline workers and more resilient staffing for the hospitals, logistics networks, retailers and services that rely on them.

Complexity becomes an advantage

Multi-jurisdiction workforce operations have historically been difficult to automate because the complexity sits in the exceptions. Every new geography adds another layer of regulation, integrations and local practice, and traditional software has struggled to keep up with that variability. Firstwork’s model differs from that: each deployment captures new workflow logic, edge cases and compliance knowledge that can be reused across the platform. The system becomes faster and more capable as it encounters more real-world operating conditions.

That compounding effect is already visible in deployment speed. Firstwork’s first major customer took several weeks to reach near-fully autonomous processing; a later customer reached a comparable level within its first week, benefiting from the compliance and operational knowledge accumulated beforehand. Customers are also starting to build their own automations on top of the platform, which moves Firstwork closer to becoming part of the underlying operating infrastructure rather than remaining a standalone vendor.

Europe provides an especially strong proving ground for this model. Although Firstwork initially went to market in the US, a large share of its revenue already comes from Europe, where operating across countries means dealing with materially different employment rules, verification requirements and local processes. That complexity raises the value of a platform that can encode and reuse compliance knowledge across markets, while making the category harder for horizontal HR tools to address.

The team has lived both sides of the problem

Vardhan Kapoor and Shubham Choudhary came to the problem from opposite sides of the same system. Vardhan had spent years operating businesses where getting large numbers of workers hired, cleared and productive was a daily constraint, first at Deliveroo and later while scaling Remitly across APAC. Shubham had spent his career building the employment infrastructure underneath those processes, first as one of Rippling’s earliest engineers and later as Director of Engineering at Deel.

That combination shaped Firstwork from the beginning. Vardhan knew where workforce operations break in practice; Shubham knew how the systems underneath them had been built, where they stopped, and what would be required to create a new execution layer across them. The team they have assembled since, with experience from Rippling, Deel, Fountain, SAP and Google DeepMind, adds depth across applied AI, enterprise deployment and workforce technology.

Customer references reinforced the same picture. Across staffing, logistics and beyond, users consistently pointed to measurable reductions in manual work and turnaround time, strong integration into fragmented systems, and a workflow layer that is significantly harder to reproduce than the individual AI agents underneath it.

What’s at stake for the frontline workforce

Frontline workforce software has historically been built in silos: recruiting, screening, payroll, scheduling and training each handled by separate systems, vendors and teams. In practice, those processes form one continuous worker journey, and the gaps between them create much of the operational friction employers still manage manually. Firstwork has the opportunity to connect those silos around the worker, rather than forcing the worker through a stack designed around individual functions.

As more workflows move onto the platform, the worker object graph becomes a persistent record of what has happened, what still needs to happen and what a worker is currently eligible to do. The accumulated compliance library makes subsequent deployments faster, while integrations and customer-built workflows embed Firstwork more deeply into day-to-day operations. Over time, this creates a shared operational layer across processes that have historically been fragmented across vendors, teams and geographies.

The broader value goes beyond software consolidation. For employers, it means fewer manual handoffs, faster onboarding and a more reliable way to manage workforce readiness at scale. For workers, it means less friction between accepting a role and being able to start it. And for sectors such as healthcare, logistics, retail and essential services, that can translate into more resilient staffing and fewer delays in getting people where they are needed.

We believe Firstwork can become a new kind of workforce infrastructure company: one that sits across the HR stack, coordinates the operational work across it and gives employers a much clearer view of workforce readiness. 

That is the future Vardhan, Shubham and the team are building toward, and the reason we are backing them.