🏢 Company Signal · Grammarly Acquisition
Coda was acquired by Grammarly in December 2024. The remaining team is lean, focused, and operating inside a larger enterprise. Grammarly's group-level infrastructure investment and consolidation conversations open a new angle — this isn't a cold pitch, it's a post-acquisition platform alignment opportunity.
Prior Experience
- Senior Program Manager @ Microsoft — PowerPoint, Bing News China (2006–2017)
- Product Lead @ Coda since August 2017 (founding team era)
Talking Points
- Nathan has been at Coda since August 2017 — founding team tenure means he's one of the few who knows the full product history
- 11 years at Microsoft (PowerPoint, Bing) means he's deeply fluent in enterprise software design and the friction between power-user tools and broad adoption
- Product leads at acquired companies carry the continuity brief — what stays, what evolves, what gets consolidated into Grammarly's roadmap
- Coda's document-as-software vision has always had frontend complexity — Netlify's platform for web experiences is a natural infrastructure conversation
- Long-tenure product leaders are the ones who influence infrastructure bets that last 5 years, not 5 quarters
LinkedIn Engagement Flow
Step 1
Engage content – like or comment on a recent post about product strategy, developer tooling, or enterprise software design. Signal presence before the direct approach.
Step 2
Publish post – share the suggested draft below, referencing Coda's Grammarly acquisition story and what it means for platform decisions.
Step 3
Direct connect – send connection request referencing your post. Nathan left Microsoft after 11 years to join Coda as founding-team product lead — he's been shaping the product through every phase, including the Grammarly acquisition.
✏️ Virio Post Talking Points
- •Seventeen years building software — 11 at Microsoft, 8 at Coda.
- •Nathan Penner joined Coda in 2017 when it was still finding its shape. He helped define what documents-as-software actually means as a product.
- •Now he's navigating that vision inside Grammarly's orbit. That's a different kind of product challenge — not just what to build, but what survives the merge.
- •The infrastructure bets that survive acquisitions are the ones that were already doing real work. Not the ones added for optics.
