Is Lucy Labs raising?
Lucy Labs is in design-partner development with founder/family pre-seed funding. Round shape, terms, and timing firm up in conversation, not on this page. Talk to Lucy on the site, then write to the founder.
Investors
A 20-year operating model translated into software at the moment AI made the translation possible.
The right investor right now is someone who can see a real problem and back the team running the operating model that solves it.
We're not pitching a tool. We're pitching a 20-year operating model translated into software at the moment AI made the translation possible.
The bet. Lucy is the architectural layer that governs how human capability forms when AI is in the work. The window. Desktop AI can now reason about specific work, in real time, in the flow. That's what makes the layer possible. The category is new because the conditions are new.
From Information Economy to Capability Economy.
We are transitioning from the Information Economy into the Capability Economy.
When information is free and models are commodities, the scarce resource becomes the human capability to apply them.
AI literacy will be the universal professional competency of the next decade, the way computer literacy became baseline in the 1990s. The countries, companies, and people who get there first compound advantage every year afterward.
Capability is what Lucy turns from tribal knowledge into infrastructure.
Lucy doesn't fit existing categories. Not L&D, not RPA, not horizontal AI tool, not consultancy, not productivity suite.
For the long-form Capability Economy thesis, see the company story's Theory of Change section.
The gap 95% of generative-AI pilots are stuck inside.
AI is already everywhere. What's missing is the operating layer that turns access into capability.
The mechanism. MIT NANDA attributes the failure gap to a learning gap. Not model quality, not regulation, not talent. Pilots fail because tools don't learn from feedback, don't retain context, and don't integrate with workflows. Lucy is exactly that operating layer.
"The core barrier to scaling is not infrastructure, regulation, or talent. It is learning."
MIT NANDA, "GenAI Divide," 2025
Microsoft Mar 2026 + Directions on Microsoft Jan 2026
3.3%
Paid M365 Copilot seat penetration across ~450M commercial M365 subscribers. The 96.7% who haven't paid are the population Lucy is built for.
Distribution alone doesn't earn capability.
BCG AI Radar 2026 · n=2,360 executives, 16 markets, 9 industries, 640 CEOs
~1.7%
AI investment as a share of revenue on a forward-looking 2026 basis — up from ~0.6% in 2024 and ~0.8% in 2025.
The capital is moving. The learning gap determines whether it converts.
MIT Project Iceberg, 2025
$1.2T
Technical AI capability exposure in US wage value — versus $211B visible adoption. Iceberg sizes the gap Lucy closes at the task layer.
11.7% Iceberg Index vs 2.2% Surface Index.
For the long-form macro evidence on adoption, spend, value capture, and shadow-AI pressure, that's investor conversation. Reach out →
Not new money. Misallocated money.
Our market is not new money. It is misallocated money.
Lucy redirects existing spend across four categories that don't compound.
Phase-1 ICP. NAICS 52 / 541 (US) and NACE K / M (EU) — finance, insurance, professional services. Selection criterion stays constant across geographies: budget-dense knowledge work × governance sensitivity × workflow repeatability.
Mission scope vs execution sequence. The mission is universal — every person on Earth. Knowledge workers come first because that's where Lucy's coaching surface lands at workforce density today, the regulatory tailwind is most acute, and the cohort-scale data flywheel forms fastest. Universal scope, sequenced execution.
For the EU AI Act treatment in buyer voice, see the business compliance posture. For the trust-architecture EU sub-section, see the public-sector EU trust posture.
Spend Lucy redirects
-
L&D and enterprise training
Out-of-context learning that doesn't transfer to real work.
-
Consulting and transformation programs
Episodic; knowledge doesn't compound in-house.
-
AI governance and security
Enables blocking risk, not building capability.
-
Needs discovery and tool selection
Surveys measure opinion, not behavior.
Regulatory tailwind — EU AI Act
EU regulation makes the capability gap visible earlier and clears procurement permission. Article 4 (AI literacy) entered application Feb 2, 2025; enforcement from Aug 3, 2026. Article 14 (human oversight) is part of the Aug 2026 wave for high-risk systems. Lucy's architecture already meets the human-oversight and aggregate-only requirements both regimes contemplate.
The software every team can run without depending on a single person.
Most companies that figured out how to change had a person doing it manually. They didn't have software for it. We're building the software so every team can run the sequence without depending on a single person.
The Evolutionary Framework as the spine. Trust → Personal value → Adoption → Capability → Scale. The operating model itself is what compounds; tools change every 18 months, the operating model and the people who internalized it stay.
External validation. BCG's 2026 "AI Transformation Is a Workforce Transformation" states effective AI upskilling is embedded in daily work, uses real tools on real tasks, and includes feedback and measurement.
For the full Coaching Loop, the substrate layers, and the methodology grounding, see how Lucy works.
Lucy Labs runs on Lucy
This is proof, not theory. The company is a system of agents running the operating model we sell. Travis and an agentic team — governance, IT-ops, project-mgr, researcher, security — compress the back-office work that would otherwise need a 5–10-person team. The product, the platform code, the marketing content, and the legal/compliance scaffolding were built by one person + AI in months, not years. The org chart IS the operating model.
Pre-AI, the same work would have required 5+ PMs and architects working 6+ months minimum. This isn't a gap to apologize for; it is the existence proof for the workforce-scale bet.
20 years running the framework before naming it.
// founder portrait — production photo TK
Our founder ran the Evolutionary Framework — Trust → Personal value → Adoption → Capability → Scale — in human-only mode for 20 years. Lucy is the AI-native version of that operating model, built because it was the system he wished he'd had.
Track record (proof, not moat). The same Trust → Personal value → Adoption → Capability → Scale pattern landed at scale across a 20-year chain of senior technical-sales and technical-sales-leadership roles, with near-zero attrition.
Virtustream
Solutions Architect & GTM Lead, Public Sector
Built the $0 to $50M ARR US Government cloud-services line of business that contributed to Dell's $1.2B acquisition.
Zscaler
Transformation Architecture Lead, EMEA
$98M ARR FY24 impact at 25× ROI on team cost; deals closed with TA involvement were ~50% larger ($32M ACV uplift) and saw 42% lower churn.
Nayara
Chief Operating Officer
9-month operational turnaround.
Why software, not services. Our founder spent 20 years running this operating model with people. He could have built a consultancy: there is a $1T+ global market that hires the same posture out by the hour. He chose to build software because the mission is universal. Services scale linearly with the people who deliver them; software is the only thing that can land the operating model at the scale of every person on Earth.
For the longer-form founder chronology, see the company story.
The operating model itself, plus the data flywheel that proves it works.
The moat is not a model or a feature. It's the operating model itself, plus the data flywheel that proves it works at every customer.
The thesis. What compounds is the combined claim — operating model + data flywheel + boundary + compliance + founder pattern recognition. No single one is the moat alone.
Sovereignty as architecture. Privacy-first by architecture, not by policy add-on. Regulatory tailwinds compound the moat; surveillance buyers self-disqualify, which is the design, not a tradeoff.
For the full V·C·C contract, the audience anchors, and the refusal scene, see the trust architecture.
The data flywheel
Capability-formation data is structurally different from task-completion data: capability-formation data captures what coaching nudges produced what behavior change in what role context; task-completion data captures what completed in what time. Different layers.
The 95% pilot-failure rate is a learning-loop problem. To replicate Lucy's data layer, a competitor has to ship a coaching surface, earn observation permission with a trust posture they don't have today, and build cohort scale before their flywheel improves.
Day-1 moats
-
Privacy-first architecture · V·C·C
Visibility, Confidence, Control — manager-aggregate-only, read-only against customer data and systems. Built before the regulatory tailwind made it table stakes.
-
The Evolutionary Framework codified into product
Trust → Personal value → Adoption → Capability → Scale, running inside every coaching loop.
-
Early-mover as shipped product
The Coaching Loop, the Knowledge Graph + Tools and Techniques Repository, desktop-in-flow architecture, and the Lucy / human / agent agency model are what being first looks like as shipped product.
One conversation. The investor who can pattern-match the bet is the one we want.
Lucy Labs is in design-partner development. We are a lab — and that means always discovering, learning, and growing.
Stage honesty. Some capabilities shown or described are planned, in active development, or pilot-scope dependent. Examples are illustrative and may change as Lucy is built with design partners. We are not pretending to be a mature enterprise suite. We won't quote ARR or customer counts that aren't true.
Round shape, terms, and timing firm up as we firm up. Reach out for the current state. The detail is conversation, not content.
The call. Talk to Lucy on the site, then write to the founder. The investor who can pattern-match the operating-model bet from the lede + the moats + the founder profile is the one we want.
Market risks acknowledged
Microsoft bundles coaching into Copilot; training vendors add AI modules; horizontal AI tools commoditize and add coaching as a feature. Each has a structural answer — business-model conflict, behavior-vs-completion measurement, substrate calibration. The detail is investor conversation.
Frequently asked questions.
What stage is Lucy Labs at?
Design-partner stage. We have a working desktop-agent product surface, a 20-year operating model translated into the methodology, design-partner deployments in onboarding, and a small founding team. We don't have at-scale customer revenue or audited certifications yet.
What is the category?
The Capability Economy operating layer. Lucy doesn't fit existing categories — not L&D, not RPA, not horizontal AI tool, not consultancy, not productivity suite. Lucy is the architectural layer between AI capability and useful human value.
Who is the founder?
Travis Sheppard. 20 years running the Trust → Personal value → Adoption → Capability → Scale operating model in human-only mode across senior technical-sales and technical-sales-leadership roles, with near-zero attrition. Track record above; longer chronology on /about.
What are the moats?
The operating model itself, plus the data flywheel that proves it works at every customer. The combined claim — operating model + data flywheel + boundary + compliance + founder pattern recognition — is what compounds.
How can I dig deeper before reaching out?
Read /about for the founder chronology and the long-form theory of change; read /trust for the V·C·C architecture and the refusal scene; read /business for the buyer-shaped depth on the operating model. Or talk to Lucy on the site — Lucy IS the product, and talking to Lucy is part of the evaluation.