When your best estimator retires, your senior project lead takes another job, or your dispatcher of twelve years decides to slow down, a specific and painful thing happens: the company loses a library it never wrote down. Bid instincts built over a decade. The vendor you call when a specialty part goes missing on a Friday. The unwritten rule about how tight to run labour on a particular type of mechanical scope. That knowledge doesn't live in your software. It lives in someone's head, and when they leave, it goes with them.
That's the institutional knowledge problem, and it has been a slow leak in most trade operations for years.
What Twin1 AI Just Announced
On August 20, 2026, a San Mateo-based startup called Twin1 AI emerged from stealth with a $20 million seed round co-led by Bessemer Venture Partners, Tribeca Venture Partners, and Aramco Ventures. Founded in 2025, Twin1 builds AI-powered "digital twins" for knowledge workers, systems that capture a professional's knowledge, judgment, relationships, and work context, then make that expertise accessible across the organization.
The twins operate inside tools people already use: Slack, Microsoft Teams, Gmail, Outlook, Google Drive, SharePoint. Early customers report the platform automates 30 to 50 percent of their knowledge workers' communications work. The funding will go toward expanding teams in San Mateo and London, accelerating go-to-market, and deepening the core technology.
Twin1's framing is privacy-first, which matters: the whole premise breaks down if professionals won't trust the system with their actual knowledge.
Why This Matters for Operations-Focused Businesses
Twin1 is aimed at knowledge workers in professional settings, but the problem it's trying to solve is just as real in field-service and project contracting, arguably more so.
Consider the mixed-model operator: a shop doing both reactive HVAC service calls and planned mechanical projects, somewhere in the 30 to 150 employee range. They have:
- An estimator who knows, from hard experience, that a particular type of job in a particular building type always runs 15% longer than the quote suggests.
- A project lead who knows which inspectors in which municipalities move fast and which ones need a follow-up call.
- A dispatcher who knows which technicians can handle a complex commercial call solo and which ones need a second pair of hands.
None of that is in a system. It's oral tradition. And every time someone senior leaves, a junior person learns it the hard way, usually at the company's expense.
The Real Operational Risk: Unbilled Work and Blown Margins
The knowledge problem in field-service isn't abstract. It shows up in the numbers.
When an estimator's instincts leave the building, the next quote might win the job and lose money on it. When a project lead's awareness of change order triggers doesn't get passed down, billable scope changes go undocumented, and margin evaporates. When dispatch intuition walks out the door, you end up with the wrong tech on a job, a callback, and a customer who's unhappy.
Institutional knowledge is, in practice, a margin protection tool. Losing it is a margin leak.
A Simple Framework for Capturing and Distributing Operational Knowledge
Whether or not AI digital twins become a tool your business eventually adopts, the underlying challenge of knowledge capture and transfer is one you can start working on now. Here's a practical framework:
1. Identify Your Knowledge Carriers
Map who in your organization holds knowledge that isn't written down anywhere. Don't limit this to senior leaders. Often the most operationally critical knowledge lives with a mid-tenure dispatcher, a lead technician, or a project coordinator who has figured out how the system actually works.
2. Translate Judgment into Process
For each knowledge carrier, pick the three decisions they make regularly that others get wrong. Document the logic: what are they looking at, what are the warning signs, what's the call? Even a one-page decision guide per person is a start.
3. Build It Into the Operational Layer, Not a Wiki
Documentation that lives in a shared drive gets ignored. Knowledge is only useful if it shows up at the moment of the decision. That means it needs to live inside the workflow, not alongside it. A checklist that appears when a technician opens a work order, margin thresholds visible in a project view, a prompt to document the change order before closing out a job.
4. Use Onboarding as a Test
Every time a new hire joins, treat their first 90 days as a stress test of your knowledge documentation. Where do they struggle? Where do they need to find a person to ask? That gap is undocumented institutional knowledge. Fix it in the system, not by assigning them a mentor who also doesn't have time.
5. Revisit After Every Near-Miss
When a job goes sideways, a missed change order, a billing dispute, a blown margin, ask what knowledge was missing and where it should have lived. Capture the fix systematically, not just in a post-mortem meeting.
The Operational Execution Layer Is Where Knowledge Has to Live
Systems like Twin1 are interesting precisely because they're trying to make expert knowledge operational, not archival. That's the right instinct. A knowledge base that nobody opens during the actual work is just an expensive document.
For field-service and project businesses, the operational execution layer, where quotes are built, work orders dispatched, field data captured, change orders documented, and invoices generated, is where institutional knowledge needs to show up or it doesn't show up at all.
That's the layer PolarPath is built to own. Not as an HR knowledge repository, but as the continuous workflow from customer intake through field execution to invoicing and workforce, where the decisions that protect margin actually happen. When the right information is structured into the work itself (margin visibility on a project, permit expiry reminders, change order prompts tied to field activity), institutional knowledge stops being something you lose when a person leaves and starts being something the business carries forward.
The Takeaway
Twin1 AI's launch is a useful signal: the market is taking seriously that expertise needs to be captured and distributed, not just hoped to survive in the heads of your best people. For field-service operators, the practical version of that insight doesn't require AI digital twins today. It requires building knowledge into your operational workflow now, before the next senior person walks out the door.
Start with one decision. Document the logic. Put it where the decision actually gets made.