Thanks Paul, nice to see someone else who actually knows what they’re talking about amidst this sea of ignorant talking heads with no experience, that have somehow amassed followings…
I fully dropped out of using Reddit because of the level of ignorance; unfortunately pervasive here too.
Here are 3 things I’ve built recently as a non-engineer (product -to- Director AI). These are for my friend’s company not where I work.
1. his Sales guys go to heaps of trade shows this is like an intel app — it uses Hubspot + scrapes to create dossiers on everyone attending
2. a Vercel/Slack scoring pipeline pulls ~50 datapoints to prioritise leads (Hubspot, Quickbooks, Shopify)
3. a video player for a product they sell which is a TV inside an MRI room — Electron app on a tablet via HDMI to the TV — plays 5min clips that display on the TV
I’m a bit ahead because of my technical product background, but domain experts will be REQUIRED to express their value as software. I have zero doubt.
This is effectively the #1 problem for AI agents in the enterprise.
As we go from agentic coding (where a large amount of context is in the code base, and users are technical enough to get the rest to the agent easily) to a world of knowledge work agents, the context problem becomes much more acute.
We see this every day with customers at Box. For existing digital knowledge, it’s often fragmented across legacy systems or environments that don’t play nice with agents, and have access controls that don’t map to the real work that needs to be done, which become a huge hurdle for getting agents the context they need. This has to all get moved to modern, secure cloud environments.
But also, companies often haven’t captured and digitized some of the critical context that agents need to work with. Decisions, processes, and workflows often live in people’s heads and tribal knowledge that need to get turned into unstructured data for agents.
This is actually one of the biggest points of leverage for applied AI companies, because they can work to specialize in getting agents exactly the information and domain expertise they need. But it’s also one of the reasons why FDEs and new system integrator plays will also work so well right now.
The companies that figure this out will be able to get the most out of AI going forward.
This is the actual bottleneck. The models are smart enough already. What is missing is the company-specific context locked in senior people heads. Whoever cracks knowledge extraction at the company level unlocks the rest.
As you work on this, please consider using GBrain as your OSS retrieval layer
https://t.co/0F5uDQzPHu
Hi @levie we could have a great conversation about this. We have a complex org with legacy systems; consolidating to Databricks, Triple whale, Netsuite and other systems. We have a monolith CMS that’s archaic and unfortunately deeply embedded. Instead of migrating we’ve built an abstraction system on top of it which uses Playwright scripts to control it! Bit of a monster but that abstraction is super agent friendly and has enabled huge efficiencies and quality improvements.
Claude Opus 4.8 is out today. It's our strongest coding model yet: up on SWE-bench Pro (from 64.3 to 69.2) and noticeably more honest about its own work. It tells you when it's unsure and catches its own bugs instead of declaring victory early. Same price as 4.7.
@KaiXCreator Yeah super regularly but probably not what you’re thinking eg we create workout programs, I built a system to handle that process, and say I’m building 3 at once, may have 4 agents working on each at same time
@garrytan Domain experts being able to express their ideas as novel software rather than be limited by the form and features of existing software. I have a growing passion for helping people do this