Home Sectors Ventures What we do Teams Insights Contact
Insights

Field notes from inside the studio.

What we're reading, building, and getting wrong. A standing record of how the studio thinks about the work.

Field notes · 6 min read

Why hardware is the next AI frontier

The next decade of AI products won't be chat windows. They'll be embedded in things you hold, wear, and live with.

We've spent the last year watching this shift happen in the supplier network. The factories that used to make Bluetooth speakers are now making AI-first hardware. The contract manufacturers who built the first generation of smart home devices are quietly adding edge inference to their reference designs. The change is happening at the manufacturing layer, not the software layer, and most of the consumer-facing brands haven't caught up yet.

What we're seeing in the supplier network:

  • Edge AI silicon is dropping in price faster than cloud inference
  • Reference designs from major ODMs now include neural accelerators as standard
  • MOQ for AI-enabled hardware is approaching MOQ for non-AI equivalents
  • Lead times on prototype runs are down from 12 weeks to 6

The interesting question isn't whether AI belongs in hardware. It's which product categories have AI as the point, and which have it as the marketing layer. We're skeptical of products where the AI is removable without changing the user experience. We're interested in products where the AI is load-bearing.

Examples we'd point to from the studio's work:

  • A wearable that adapts coaching based on what it learns about your patterns
  • A home device that runs everything on-device because privacy is the product
  • A classroom tool that adjusts to each student without sending data to a server

These are products where removing the AI breaks the product. That's the bar we're holding ourselves to.


Filed under: Field notes · Sector: AI Applications · Written by the studio leadership team.

More from the studio

Five more pieces.

A mix of operations notes, sector thinking, and the lessons we're still learning.

Operations · 8 min read

Lessons from prototyping in Shenzhen

Three years of supplier conversations distilled into the questions we now ask before we sign anything. Most of them aren't technical.

We've run prototype projects with 40+ manufacturers in Shenzhen, Dongguan, and Suzhou. The pattern that emerges: the suppliers who are best at the technical work aren't always the ones you want to build with long-term. Here's what we ask first.

Studio model · 5 min read

How a small studio ships physical products

A walkthrough of what we actually do in a typical week, from concept testing on Monday to supplier QA on Friday.

Most venture studios treat physical products as a future problem. We're trying to make them a current one. Here's a snapshot of a recent week — what we shipped, what we killed, what we put on the back burner.

Sector: EdTech · 7 min read

Why our EdTech work is anchored in North America and Europe

Institutional buyers, not philanthropy budgets. Why the mature markets are where the real EdTech buying decisions happen — and where we're building.

The narrative that emerging markets are the "obvious" EdTech play misreads who actually writes cheques for classroom software. Districts in the US, MATs in the UK, chartered networks in Canada, and ministries across the EU are already procuring AI-native tools at scale — with real budgets, real RFPs, and real safeguarding frameworks. That's where the durable products get built. Our Southeast Asia line stays smaller and deliberately harder — a stress test for scale, class sizes, and thin infrastructure that keeps the core roadmap honest.

Sector: EdTech · 6 min read

Safer screens for kids and toddlers: a dedicated line of work

Most children's software optimizes for time-on-app. We're funding a set of prototypes that inverts the metric — more learning per minute, less compulsive engagement, and a design bar friendly to developing brains.

Parents in North America and Europe are the most sceptical audience in consumer software right now — and they're right to be. The default children's app optimizes for retention using loops borrowed from casino design. We think there's a large, underserved product surface for the opposite: apps for ages 2–7 that make each minute meaningfully more educational, are honest about screen time, and are engineered with paediatric development advisors from day one. Our early-childhood workstream sits inside the EdTech sector but is treated as a distinct programme, with its own advisory bench and safeguarding review.

Sector: Algo Trading · 9 min read

Building systematic strategies for non-tier-1 markets

The infrastructure for systematic trading in Asia assumes HFT-era US equities. Most of it doesn't fit local markets.

A working note from the Quant team on the gaps in existing tooling for non-tier-1 markets, and what we're building to fill them.

Studio model · 4 min read

Why we deploy capital in tranches

No venture gets the full build budget up front. Here's why that discipline matters more than the headline investment.

Tranching isn't just risk management — it's how you keep the studio honest. It forces every venture to re-earn its next round of capital against something the team actually shipped.

Sector: Wellness · 6 min read

What we learned shipping a wellness wearable

Health-adjacent products have a regulatory ceiling. Here's how we think about what we can and can't claim.

An honest post about the parts of wellness hardware that surprised us — what the regulators actually care about, what claims we can defend, and where we draw the line.

Quarterly digest

A short note, four times a year.

We send a short digest of what we've shipped, what we've killed, and what we've learned. Roughly four times a year. No marketing, no sales pitches. If we have nothing to say, we don't send one.

Have something to share

If you're working on adjacent problems, we'd like to compare notes.

We talk to a lot of operators building in our sectors. The conversation usually starts with what they're working on, not what we are.