Oxford Harrison

Building:

[Oxford Harrison @Ox_Harris]

An early demo of my months-long work on LinkedQL.

Below is a basic TODO app that runs on LinkedQL live queries and sync. (More details in the README: https://t.co/4dF8qfrAEo)

[@jason @Jason]

Business AI is here.. for your business! 😂

[Saurav Shroff @SauravShroff_]

i skate to where the puck is going to be, not where it has been

[Harry Stebbings @HarryStebbings]

I have interviewed 1,000s of the world's best founders over the past decade. Few have impressed me like @ShivdevRao at @AbridgeHQ.

He navigated a brutal 5-year wilderness before exploding into one of the most dominant forces in vertical AI.

Today, Abridge is a $5.3BN powerhouse.

I sat down with Shiv to unpack exactly how he did it and condensed my notes below:

🚀 6 Lessons on Building a $5.3B Vertical AI Juggernaut

1. Survive Long Enough for Market Timing to Catch Up:

Abridge spent 5 years in the "wilderness" before hitting a tidal wave of adoption. When you have an absolute true north thesis, your primary job in the early days is simple: stay standing and don’t die. You must be alive when the sky finally opens up.

2. Pivot the Product, Never the Core Thesis:

Shiv was willing to pivot on features, go-to-market strategies, and business models. But he refused to budge on his core thesis that healthcare is ultimately powered by the spoken human signal. Die on the hill of your thesis; adapt everything else.

3. Target the Concentration of Scale Early:

A massive trap for healthcare and enterprise founders is staying down-market too long for "fast feedback loops". In the US, the vast majority of clinicians are concentrated within large, integrated delivery networks. Time your "YOLO shot" to go up-market the moment the market inflects.

Single biggest advice to founders on when to go up market @bhalligan @dharmesh?

4. Own Your Stack to Protect Your P&L and UX:

While many AI startups rely entirely on frontier systems, 40% of Abridge's model outputs are generated by in-house models. Milliseconds matter in high-stakes enterprise workflows. Building your own models gives you insane performance gains, lower latency, and ultimate control over your P&L.

When should you vs should you not build your own model @matanSF @MaxJunestrand @antonosika?

5. Don't Fight Foundation Models—Counter-Position Instead

If you try to fight the frontier model giants directly, you've already lost. You win by going millions of miles deep into regulated industries with proprietary datasets and workflows they can't easily replicate. Find ways to coexist and leverage their tailwinds.

Reminds me of what @bradlightcap said on his 20VC.

6. Move Toward the "Flat Company" Era:

With the explosion of AI agents and advanced tooling, the traditional management layer is compressing. Shiv’s latest idealistic shift is building a hyper-flat organization: fewer managers, and highly leverageable "Super ICs" who can move in lockstep and cover massive surface area.

(link in comments)

[Oxford Harrison @Ox_Harris]

@hnasr It's mad how that literal says LinkedQL 😅

That's a real thing I built:
https://t.co/4dF8qfrAEo

[Oxford Harrison @Ox_Harris]

@TosinOlugbenga https://t.co/4dF8qfrAEo

[Oxford Harrison @Ox_Harris]

@antl3x @theo Yes, 100%
We do intend to be more "automatic" about typesafety, however, as with TanStack's approach.

[Oxford Harrison @Ox_Harris]

Today, I've put LinkedQL up for design review. Curious what engineers think of our Live Query implementation:

https://t.co/G1CATevTs7

@theo #PostgreSQL #SQL

[Oxford Harrison @Ox_Harris]

@antl3x @theo One thing LinkedQL doesn't provide yet is code-level typesafety. But this is planned.

Focus so far has been building the core idea: a query engine that lets you do more with SQL.

[Oxford Harrison @Ox_Harris]

@antl3x @theo The idea instead is: object-relational mapping as a SQL feature. LinkedQL let's you traverse foreign keys from table to table all within the query, using simple arrow notations: ~>, <~.

That's covered here: https://t.co/mjsNCbW7Yz

[Oxford Harrison @Ox_Harris]

@antl3x @theo Yes RLS 100% – See here: https://t.co/EjAw2GjOFH

And yes, just PostgreSQL for now

[Oxford Harrison @Ox_Harris]

@TosinOlugbenga For this too, we built DeepRefs:

https://t.co/vDOLCU8WZ3

[Oxford Harrison @Ox_Harris]

@TosinOlugbenga 10mins in the rest room also often did magic

[Oxford Harrison @Ox_Harris]

@MadeinNGOSS Coming soon to the list: LinkedQL
https://t.co/4dF8qfrAEo

[Oxford Harrison @Ox_Harris]

@Una This is crazy.
Long awaited

[Oxford Harrison @Ox_Harris]

@TosinOlugbenga Thank you @TosinOlugbenga .
We're at design review stage. And my ask would be:
could you help us get more engineers in your network to review the current shape? (I'd be more than glad.)

[Oxford Harrison @Ox_Harris]

@LeaVerou @openjsf Congrats Lea. Well deserved

[Oxford Harrison @Ox_Harris]

@EmmanuelBuilds @OPay_NG Wow. HTML & CSS? That's significant.
Should u want an upgrade? OOHTML gives u just that. (https://t.co/AOR7gyf9MB)