Trajectory raises $45M to make AI model training accessible to nontechnical experts
- ID
- 42207
- Status
- summarized
- Published
- 03 Nov 2026, 7:13 AM
- Fetched
- 03 Nov 2026, 7:45 AM
- Provider
- TechCrunch
- Category
- technology
- Original URL
- https://techcrunch.com/2026/11/02/trajectory-raises-45m-to-make-ai-model-training-accessible-to-nontechnical-experts/
- Source URL
- https://techcrunch.com/feed/
Summary
- Score
- 4.0
- Created
- 03 Nov 2026, 7:46 AM
- Tags
- Audience
- ai_ml_learnerssaas_foundersdevelopers
What happened
Trajectory, an 18-person startup founded about a year ago by three Stanford classmates with experience at Google DeepMind and Apple, raised a $45M Series A at a $300M valuation led by Sequoia, with Nvidia, Bessemer Venture Partners, and Bain Capital Ventures participating. Its pitch is 'continual learning': connect the platform to your applications, collect feedback on model outputs, and it retrains an open source base model so specialists like lawyers and doctors can improve it themselves — instead of hiring a research team or paying forward-deployed engineers. Harvey and Rogo are named as users post-training open source models for legal and financial analysis work.
Why it matters
The concrete claim to test is economic, not technical: Trajectory is selling continual learning as a substitute for the internal research team or FDE contract you'd otherwise need to fine-tune a model for a domain task. No pricing, eval numbers, latency, or data-handling details are disclosed, so the only decision available to you right now is whether to treat 'feedback loop into retraining' as a build-vs-buy line item in your next AI feature — and if you do, ask vendors for before/after task accuracy and where your customer feedback data lands before you wire production traffic into a retraining loop.
Discussion angle
Continual learning vs. fine-tuning vs. hiring an FDE: for a domain-specific feature, which would you actually pick, and what minimum evidence (accuracy delta, cost per retrain, data residency) would a vendor need to show before you pipe real user feedback into their loop?