We can't find the internet
Attempting to reconnect
Something went wrong!
Hang in there while we get back on track
1. Funding & Deals
Google’s Australia–New Zealand accelerator is the clearest capital-adjacent early-stage signal, rather than a disclosed priced round. Google selected 15 startups for a 10-week, equity-free hybrid program aimed at Seed and Series A companies using AI and machine learning; the announcement describes the program but does not state an investment amount or investor syndicate. The cohort includes Blunge’s AI design agent, Bower’s research operating system, Eyes of AI’s dental-imaging product, Mentana’s autonomous supply-chain manager, Merchmix’s inventory operating system, RossOps’ manufacturing memory layer, Totex Energy’s flexible-grid tooling, and Unseen’s commercial-real-estate trust layer.
The sourcing thesis is vertical workflow infrastructure—research, supply chain, manufacturing, health, energy, and auditable real estate—rather than another general-purpose chatbot. Treat the accelerator as ecosystem validation and a deal-sourcing map, not as financing proof.
2. Emerging Teams
Baukompass is the strongest domain-first team signal. An unnamed founder working at a German insulation and fire-protection contractor is building the product at night with a small AI-agent team, using the employer as its first pilot in a market dominated by two incumbent vendors. The founder learned that the real product is decades of domain rules, GAEB tender exchange, calculation history, and price books—not the incumbents’ dated interfaces—so Baukompass became a sidecar: measurement data and a tender go in, a quote draft comes out, and the customer finishes the job in its existing system. The pilot has exposed the execution risk: the parser handled the official specification but failed on the third real customer file, estimators still check every generated position, and current time savings are estimated at roughly 30%, versus an initial 80% expectation. The investable signal is domain expertise plus incumbent-compatible distribution; the first pilot and manual review mean repeatable traction is not yet demonstrated.
A previously exited SaaS/IoT founder is using AI to operate as a much more capable solo builder. The founder says a prior company was acquired by a listed French group, and that the new fractional-C-level marketplace in Europe reached beta after about five months of solo work. They report building authentication, onboarding, admin, GDPR, and audit features with Claude Code despite spending the previous 15 years mainly on sales, marketing, fundraising, and legal, and say most new signups report that ChatGPT or Claude recommended the platform. That acquisition signal is promising but not clean attribution: commenters argue that AI discovery captures existing demand and can obscure the comparison pages, directories, or other web sources that actually generated it.
An unnamed brand-strategy product offers a useful activation-before-monetization case. Its founder reports 1,300-plus signups, more than 300 completed brands, and about 12 paying customers across 16 purchases; every payer had completed a full brand before paying. The product gates exports, downloads, and team access rather than the work itself, while subscriptions, one-time unlocks, and credit packs have all seen early use. The traction remains small and self-reported: on one day, Reddit supplied 74% of referred traffic from a base of 82 visitors, but the founder could not attribute a single payer to a channel. The founder’s prior branding leadership at DivX and roughly 20 years shipping applied AI add relevant pedigree, but not yet venture-scale proof.
Ceadly is an early control-plane wedge for agentic software. The new project positions itself as an authorization and governance layer that requires named human approval before consequential actions. Its proposed operating model starts with a short list of refunds, external emails, production writes, and permission changes; routine actions can later be policy-approved with timeouts and audit trails, while repeated unchanged approvals become candidates for relaxation. The product’s own framing identifies policy calibration—not merely adding an approval button—as the hard part: broad controls create approval fatigue, while narrow controls can miss the damaging action.
3. AI & Tech Breakthroughs
The Station is a meaningful step toward open-ended, multi-agent scientific discovery. The linked paper reports an environment where agents from different model families pursue a shared mathematical goal without a central coordinator or scripted pipeline, choosing research directions, running experiments, collaborating, and building a shared literature. Across 12 AlphaEvolve construction problems and two additional case studies, it reports results novel relative to prior literature on five problems, plus new infinite families for Book Ramsey numbers; the agents also produced explanatory theorems and analyses and released raw dialogues, proofs, and verification code. The results should be treated as reported claims until the released proofs and code are independently reviewed, but the important paradigm is that the environment delegates research direction and collaboration—not just a fixed sequence of model calls.
TUFF shows a practical local-inference trade: storage bandwidth in exchange for RAM. The solo builder’s native Swift/Metal macOS app keeps shared mixture-of-experts components resident and streams needed experts from SSD, claiming that a 61GB model can run on a 16GB MacBook Air without swapping. The project reports more than 1 token per second for an open-source 120B model and more than 7 tokens per second for Qwen3.6 35B-A3B and Gemma 4 26B-A4B on a 16GB M2 Air; these are README benchmarks, not independent validation. The opportunity is wider private, device-local access to models that exceed conventional memory limits; the diligence question is whether SSD latency and older-device performance preserve a usable experience.
Visual verification is becoming a first-class agent capability. A solo AI-video builder says the previous system shipped after a tool returned { success: true }, even when text overflowed, scenes were blank, or layers were stacked invisibly. The new loop renders the live editor at 2, 7, and 13 seconds, sends the actual pixels back to the agent, and patches the HTML/GSAP source in place; if the browser capture flag is unavailable, it returns an explicit error rather than passing a blank frame as success. This is a useful harness pattern beyond video: tool-level success is not output-level correctness, so agents need access to the artifact they actually produced.
4. Market Signals
AI is moving the moat away from implementation and toward distribution, trust, data, and domain context. A current founder discussion argues that one competent developer can now build in days or weeks what previously took a small team months, while successful implementations can be reproduced just as quickly; it names distribution, brand, proprietary data, network effects, domain expertise, and existing customers as the scarcer assets. Replies add that selling, deployment, maintenance, security hardening, scaling, and requirements remain substantial bottlenecks. Andrew Chen compresses the sentiment into “100x side projects, 0x actually shipping,” while another founder observes that the expanding AI-product field contains many similar promises with unclear differences until users spend hours testing them.
Agent operations are becoming a control-plane market. A booking workflow that handled flights, hotels, Gmail, and SMS in a stateless sandbox reportedly double-booked, skipped notifications, or hung in production because four-plus external APIs could fail silently while state was only partially committed; mocked dry runs did not reproduce the real behavior. Security operations show the same exposure at higher stakes: agents are being given endpoint controls, threat-intelligence feeds, and incident-response tooling comparable to a privileged service account, while RBAC can confirm entitlement without judging whether the action is appropriate in context. The adjacent FinOps gap is similarly concrete: multi-provider dashboards do not connect spend to teams or workflows, so instrumentation needs to tag requests before they leave the application and include retries and failed calls before joining usage to revenue.
Compute demand remains strong in the bullish case, but infrastructure underwriting must separate utilization from asset quality. An a16z post argues that moving from chatbots to reasoning, agents, and multi-agents multiplies the tokens required per task and leaves the industry constrained by GPUs, power, and the ability to create supply. An Investing in AI analysis argues that generalized models are commoditizing while specialized models, inference-specific chips, and better harnesses can reduce costs; it reports cutting some customer inference bills by more than 80% and says lower costs could make projects uneconomic in 2025 viable in 2027. The same analysis warns that a demand drop need not create a compute glut, but that poorly located data centers, bad power contracts, and rapidly depreciating hardware can still produce write-downs.
AI-native distribution is now showing up in operating metrics, not only product demos. A SaaStr account says Owner.com, a vertical SMB software company, has passed $100 million ARR with triple-digit growth and reports that more than 83% of new customers now begin inside an AI product. The company replaced a sales-led demo and onboarding path with a free five-minute AI build that produces a website, photography, video, and SEO/CRO audit. Its claimed moat is outcome data from thousands of live restaurant sites and tens of millions of consumers, linking product decisions to order volume rather than merely accumulating a public corpus. The relevant diligence question is revenue impact: the same account reports more than $2 million ARR per rep and roughly four times direct SMB competitors, rather than stopping at time-saved metrics.
Automation projects are also becoming labor and permitting products. A quoted WSJ account says resistance to data-center construction has broadened from electricity, water, and noise into jobs, with politicians halting approvals or tightening oversight and unions warning that thousands of building-related jobs are at risk. In Atlanta, the rideshare drivers’ union says drivers have seen lower pay, longer waits, and fewer fares since Waymo’s rollout and is asking for a $0.50–$1 robotaxi impact fee. For infrastructure and robotics investors, local political support and worker-transition costs belong alongside power availability and model economics.
5. Worth Your Time
- Watch — Lenny’s Podcast: AI’s third era, the rise of persistent AI coworkers. The strongest segment frames persistent agents as coworkers that work at higher levels of abstraction and eventually collaborate across users, while stressing that cloud agents need data access, infrastructure, and reliability—not only better models.
Read — How To Think About The Negative ROI on AI Investment. Use the essay for its separation of model-lab valuation from long-term viability, its cost-curve thesis around smaller models and better harnesses, and its warning that useful demand can coexist with bad data-center bets.
Thread — Sriram Krishnan on open models and the Hugging Face incident, with Clement Delangue’s response. The exchange is a concise case for open-weight models in private cyber investigation: Sriram says Hugging Face was blocked from using closed models, while Delangue says GLM helped identify planted backdoors and enabled analysis without sharing confidential data or asking a provider’s permission.
Read — Autonomous Mathematical Discovery in an Open-World Multi-Agent Environment. Read the primary abstract before treating the Station’s novel-result claims as investment-grade evidence; its distinctive contribution is the combination of open-ended agent coordination, explanatory mathematics, and released verification artifacts.
Read — Owner.com’s AI rebuild. It is a useful operator case on replacing a sales funnel with a free outcome, turning deployment data into a moat, and directing agents at coordination overhead rather than only code generation.