We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
1. Funding & Deals
Airbound announced a $37M Series A led by Greenoaks to make “all movement” airborne. The company rejects the premise that flying is inherently more expensive; investor Leo Polovets called its manifesto unusually clear and described Airbound as a company to watch for the future of logistics and transportation. For a VC, this is a transport-tech thesis bet on modality and system-level economics; the underwriting question is whether the company can turn that thesis into lower-cost, broadly deployable movement.
2. Emerging Teams
Suhail’s still-unnamed venture is a high-compute bet on autonomous AI research. The founder’s build log says the venture has secured seed funding, is building an “autonomous AI scientist,” and has validated a basic RLVR post-training stack. The team grew from one to three, made its first hire, is looking for another specialist in post-training or low-level model optimization, and says it acquired 64 B300s. A current update says the software around the harness is becoming “the new browser” and that supporting customers requires testing multiple implementations to ensure their APIs work consistently. The signal is unusually concrete resource commitment, but the financing terms and company identity remain opaque; the diligence test is whether automated post-training produces repeatable gains rather than simply consuming scarce compute.
FretTrack is a clean vertical-SaaS signal: a guitar-repair operator turned an internal tool into a tenant-isolated product and got its first paid annual subscriber. The founder started from direct workflow knowledge, rebuilt the product around a real database, authentication, shop-level data separation, permissions, subscriptions, and migrations, and had a UK shop process an actual customer job. The founder explicitly distinguishes the payment from beta compliments or sign-ups, while noting that AI accelerated development and also created technical debt that had to be addressed with security and reliability checks. The investable lesson is domain-specific workflow ownership plus willingness to pay, not a generic AI wrapper.
Applied Compute released AC2 in private beta with a “model factory” thesis. It argues that fast model progress makes attachment to one set of weights less valuable and positions AC2 as infrastructure around models to train, run inference, and continuously improve them on a team’s target work. This is an infrastructure thesis rather than proof of traction, but it is a useful early signal that applied-AI teams may buy continuous model operations instead of a one-time model choice.
3. AI & Tech Breakthroughs
Perplexity’s Portable Computer makes local-first agents a full-stack operating mode rather than a smaller-model demo. It launched on NVIDIA DGX Spark with the orchestrator model, subagent model, and harness running on local hardware; the primary research describes the model, harness, conversation, and trajectory as local by default, with web search, connectors, and stronger-model escalation gated by the user. It also argues that the model and harness must be co-designed. The boundary is implemented, not merely promised: tools run in an OS-level sandbox, the harness disables itself if isolation is unavailable, and a deterministic orchestrator retains authority over approved tool calls.
The reported results support a hybrid rather than fully offline thesis. On a 53-task knowledge-work benchmark, base Qwen 3.8 27B in the Computer harness scored 82.6%, versus 77.6% for Pi and 74.0% for Hermes; post-trained PPLX 27B reached 85.4%. On harder coding tasks, user-approved escalation to Claude Opus 5 raised the score from 59.6% to 73.0% at an estimated $0.415 per rollout, versus 82.4% and $0.65 for Claude alone. The implication for investors is a product and infrastructure wedge combining local privacy and cost control with selective frontier access—not the immediate elimination of cloud models.
Ramp’s Inspect shows why enterprise coding agents are becoming internal platforms. Inspect combines remote sandboxes and unlimited concurrency with internal tools and context, then verifies backend changes through tests, telemetry, and feature flags and frontend work through screenshots and live previews. Ramp reports that 75% of merged PRs come from Inspect sessions, the system has passed one million sessions, its team numbers 5.5 people, more than 150 Ramp engineers have contributed, and more than 80% of Inspect itself was written in Inspect sessions; more than 200 additional agents run on the platform. This is internal-adoption evidence rather than a startup KPI, but it points to context, verification, and orchestration—not code generation alone—as the durable control-plane layer.
Evaluation tooling is moving from static benchmarks toward executable task factories. LangChain’s eval-engineering process separates human judgment about what a task should measure from agent-automated task construction, using versioned specs, real-agent trajectories, and multiple model tiers to catch design flaws and calibrate difficulty. The authors frame continuously refreshed environments built from production data as infrastructure for prompt tuning, harness tuning, post-training, and deciding where cheaper models are sufficient. In parallel, LlamaIndex’s ExtractBench tests 14 systems across 370 enterprise documents, 67 document types, and more than 4,800 pages, explicitly targeting the messy forms, nested tables, and long reports that clean-invoice demos avoid. The investable opportunity is evaluation tied to representative work and operating cost; the benchmark announcement itself is not evidence that any extractor has won.
4. Market Signals
Enterprise AI is reallocating software budgets before it creates a new vendor category. SaaStr’s account of a 141-CIO Redpoint survey says 45% of respondents fund AI from existing software budgets, 54% are running vendor-consolidation programs, only 3% expect AI to create more vendors, and 58% say AI feature additions are the leading driver of software-spend increases. The same survey says 46% expect usage- or outcome-based pricing to become more common and 29% expect seat-based pricing to decline.
That repricing creates concrete product requirements: consumption vendors need buyer-set hard caps, rollover blocks, threshold alerts, and an agent-readable budget API; resolution pricing instead bills for a countable completed result rather than an API attempt. Allie Miller’s reported examples of F500 and digital-native businesses imposing monthly token limits—from roughly $75 to $3,000 in cited cases—come from online threads, so they are directional, but they reinforce that AI spend governance is becoming part of procurement rather than an afterthought.
Agent security is shifting outside the model. A post summarizing UK NCSC guidance says containment should match autonomy, deployments should choose among different human-oversight modes, sandboxing should be layered, and activity should be logged with attribution; it also says model-level safety training can be bypassed once an agent has tools, credentials, and a goal. A practitioner describes the corresponding runtime pattern: middleware tracks token spend and revokes scoped API keys or tool access mid-run, with process termination as a last resort. That makes identity lifecycle, sandboxing, observability, and kill-switch infrastructure plausible investment wedges, while the underlying security post is still a secondary summary and the implementation account is anecdotal.
The capital layer is concentrating even as local products try to decentralize inference. Steven Sinofsky and Martin Casado describe computing as “capital-bound,” arguing that a team of about 20 can put $1B to productive use; Casado says he underestimated how long scaling laws would hold and warns that a $100B training run could concentrate resources in ways whose consequences are difficult to control. At the hardware boundary, Sarah Guo’s formulation is that AI can compress chip-design cycles but cannot fix supply, while Bindu Reddy argues that OpenAI, Google, and Amazon’s proprietary chips—and an expected Anthropic chip—are pushing Nvidia to build a broader AI-startup ecosystem. The resulting barbell is clear: open-weight and local-first systems can reduce inference dependence, but power, silicon, and capital remain concentrated bottlenecks.
5. Worth Your Time
Read — Perplexity’s Portable Computer research. The primary write-up has the sandbox boundary, on-device document results, the 53-task knowledge-work benchmark, and the user-gated advisor cost tradeoff needed to separate local-first architecture from “fully offline” hype.
Read — Why Ramp built Inspect. The useful detail is not the coding-agent label but the remote execution, internal integrations, verification loop, and adoption metrics behind an internal agent platform.
Read — How we Build Agent Environments & Tasks. This is a practical blueprint for separating human-reviewed task specs from automated environment construction and keeping evals aligned with production behavior.
Read — The 3 New Pricing Models in B2B. It connects budget reallocation to consumption controls, outcome pricing, and resolution pricing, with concrete implications for new entrants versus installed-base vendors.
Watch/listen — the lab-economics discussion. Treat it as scenario thinking rather than market data, but it is a useful frame on compute concentration, inference-to-training shifts, capex, and the possibility of centralization around a few labs.