Nikita Shamgunov - founder of Neon: storytelling, pricing and hiring execs
Neon founder Nikita Shamgunov explains how narrative, product-led growth, pricing architecture and executive hiring fit together when an open-source database moves from developers toward the enterprise.
Nikita Shamgunov is the founder of serverless Postgres company Neon. He previously co-founded MemSQL, now SingleStore, worked at Khosla Ventures, and held engineering roles at Microsoft and Meta.
We talk about databases as systems engineering, telling a company story people can defend, treating product-market fit as a gradient, introducing a sales machine carefully, pricing infrastructure, competing credibly and hiring an executive team that complements the founder.
The Q&A below is experimental — extracted from the episode transcript with AI. If you spot a mistake, let us know at jack@scalingdevtools.com.
Why did databases become your life’s work?
They combine operating systems, algorithms, data structures and query optimization — computer science in a box. Competitive programming led me toward systems work, then six years on SQL Server deepened the pull. Building SingleStore from scratch added scars too: system-software cycles are long, and reversing a wrong foundational decision is expensive.
What did you learn about telling a company’s story?
A team needs a high-level narrative it can explain under pressure: the grand context, the obvious work required and the few secrets it believes that the market does not yet share. When the Neon story is clear, people understand why the company should exist and root for it. Narrative helps everyone connect detailed decisions to the same destination.
Why was Neon the company you felt compelled to build?
I had both passion for the underlying database technology and a stronger connection with software developers than with the big-data buyer. Neon puts a polished developer experience on top of hardcore systems work. That combination — deep reliability and performance serving people who write and deploy code every day — fits what I want to obsess over.
How do you think about product-market fit in a PLG company?
It is a number on a continuum, not a binary state. Its strength controls growth and eventually the revenue ceiling where attrition catches acquisition. Better latency, observability, onboarding and moment-to-value improve retention; as more users stay and recommend the product, the product-led motion compounds.
When should a company add sales?
Do not hire a pile of account executives in isolation. Build a machine: create awareness, observe where users can no longer self-serve, then introduce humans at those points and generate a real pipeline. Each step up from small businesses toward the Fortune 2000 has different product, compliance and sales requirements, so graduate through the market deliberately.
How should an infrastructure company price storage and compute?
In data and analytics, make storage inexpensive because it is close to an S3 pass-through and encourages customers to bring data in; compute is where heavy workloads create value. Operational databases still charge for both. Neon's elastic architecture supports consumption pricing, though packaging also needs a clear paid threshold so the model is understandable.
What framework do you use when pricing a new DevTool?
A truly unique product has to discover a price, but a product with competitors should study their market closely. If an architectural advantage creates obvious extra value, anchor pricing to it. Otherwise remain near the competitive range: buyers barely notice a modest difference, while a product that costs twice as much must prove why.
How do you talk about competitors without losing credibility?
Be competitive but accurate. In developer tools, anybody can test a dismissive claim in seconds; if the rival is better than you said, your credibility disappears. Give credit where it is due and frame genuine deficiencies carefully. Strong ideas will be copied, so the durable advantage is the part of the architecture that remains genuinely hard to reproduce.
What should a founder look for in an executive hire?
Begin with an honest inventory of your strengths, weaknesses and non-negotiables, then identify what the organization needs now. We hired an engineering leader with experience improving reliability, but also valued empathy and the ability to make people want to work with him. The right leader supplies a missing superpower in a style compatible with the founder and team.
Is a high-quality executive recruiter worth the cost?
For a consequential executive search, optimize for output rather than the cheapest route. Senior candidates face real risk and opportunity cost, so a trusted intermediary gives both sides a more serious process and reaches talent a founder will miss through direct messages. I tried cheaper firms, VC recruiting help and LinkedIn; proven recruiters produced the reliable result.
Links & references
This episode is brought to you by WorkOS.