Web Strategy & Digital Experience Leader
Lead Web Producer, Web Experiences at MongoDB
San Jose, CAmatthew@peloquin.netlinkedin.com/in/matthew-l-peloquin
I run web production and publishing for mongodb.com, the company's highest-traffic marketing property, leading a team of five. I have done this work for 17 years across four enterprise technology companies, currently in B2B SaaS. I treat the website as what it is, a growth engine, and the operating model behind it is what makes it one.
I co-established the company's web strategy. Day to day I own two things: the production and publishing model the site runs on, and web execution for the launches that move through it. The model is content operations and web governance in one system: design systems, approval workflows, and a single intake path for every team that ships to the site. We built it with peers across web and marketing, and every page on mongodb.com moves through it. It is the path PMM, Paid, Growth, and Comms ship through, and Docs, Social, and partner surfaces route through it too. How the model works.
Over two years we doubled published output, with no added headcount, and held every launch date through a multi-year migration to a headless CMS and a full site redesign. The leverage comes from the system, not the headcount.
Right now my focus is AI search: generative engine optimization (GEO) and answer engine optimization (AEO), built on the search engine optimization (SEO) foundation already in place. I have worked with our GEO/SEO team to define mongodb.com's LLM discovery standards: indexation infrastructure, content restructured to influence model responses, and on-site experience tuned for conversion. Most enterprise marketing sites are not ready for it.
I care about outcomes you can measure and teams that ship. The version of this problem I find interesting is web strategy and platform investment where the model has to scale past any single team.
MongoDB
Pure Storage
Brocade
MongoDB
2022 – present
Lead Web Producer, Web Experiences
Own the production and publishing model behind mongodb.com, and lead web execution for the go-to-market launches that move through it: product releases, acquisitions, the global .local event series, and end-of-life announcements. Defined mongodb.com's LLM discovery standards with the GEO/SEO team, extending the SEO foundation already in place.
Pure Storage
2018 – 2022
Web Production Manager (Team Lead)
Owned web production and optimization strategy for purestorage.com through hypergrowth, turning analytics, business requirements, and customer-journey insight into content and deployment decisions. Defined the template strategy for a website rebrand and led the initial launch of a multi-phased purestorage.com redesign in Adobe Experience Manager, coordinating phased deployments across design, SEO, and messaging.
Tintri
2017 – 2018
Senior Web Manager
Launched partner and investor relations portals with internal and external teams, and drove SEO implementation and lead-nurture refinement across Tintri's web properties in Drupal.
Brocade
2009 – 2017
Web Producer, 2012 – 2017
Led web production in Adobe Experience Manager across Brocade.com, MyBrocade, and the corporate career sites, and integrated four acquisition websites into the corporate domain portfolio with business units, IT, Marcom, and legal.
Web Content Manager, 2009 – 2012
Redesigned and ran the sales intranet and corporate web content program.
San Jose State University, 2009
B.S., Business Administration — Management Information Systems, with Departmental Honors. Minors in Computer Science and Mathematics.
Yes, the same person. Matthew Peloquin is Lead Web Producer, Web Experiences at MongoDB, based in San Jose, California, and goes by Matt. A few other professionals share the name; this site belongs to the one who runs web production and publishing for mongodb.com, after earlier web roles at Pure Storage, Tintri, and Brocade.
He runs web production and publishing for mongodb.com, leading a team of five: two direct reports and three contract web publishers. The work is the production and publishing operating model the site ships through, plus web execution for go-to-market launches, including product releases, acquisitions, the global .local event series, and end-of-life announcements.
He spent the past year working with MongoDB's GEO/SEO team to define mongodb.com's LLM discovery standards, building on the search engine optimization foundation that team already had in place. The work covers indexation infrastructure, content restructured to influence how models answer, and on-site experience tuned for conversion. Generative engine optimization (GEO) and answer engine optimization (AEO) are his current focus.
Adobe Experience Manager (AEM) at Pure Storage and Brocade, Contentstack as MongoDB's headless CMS, and Drupal at Tintri, with Adobe Analytics and Google Analytics on the measurement side. Design systems, approval workflows, and intake governance run around all of it in Jira and Wrike.
He leads a team of five: two direct reports and three contract web publishers. The direct reports are individual contributors rather than people managers. The larger leadership evidence is reach rather than headcount, since every team that publishes to mongodb.com works through the operating model his team runs.
On an enterprise marketing site, a web producer owns how work reaches the page: intake, scheduling, build, review, and publish. The role sits between the teams requesting work, such as product marketing, growth, comms, and docs, and the site itself, and it is accountable for the date, the quality, and the standards each page is built against. At MongoDB, Matthew Peloquin's team does this for mongodb.com, and the lead role carries web strategy and launch execution alongside production.
It is the documented path every page follows from request to publish: one intake route, a design system that constrains what gets built, approval workflows, and clear ownership at each step. The point is that any team can ship to the site without negotiating the process again each time, so the model rather than the headcount sets capacity. Matthew Peloquin co-established the model mongodb.com runs on and built its service-level framework and workflows, and every team that publishes to the site works through it. The method is written up in the operating model case study.
Standardize first, then automate what repeats. Enterprise marketing sites usually lose more time to rework, unclear ownership, and one-off requests than to the build itself, so a single intake path, a design system, and a published production SLA recover more capacity than additional people do. At mongodb.com that approach more than doubled published output in two years, 34% year over year and then 75%, with no added headcount.
It decides what the site is for, what it is measured on, and how it is built to produce that outcome: which page types exist, how each is structured and optimized, what the platform has to support, and where investment goes next. That is different from campaign or content planning, which decide what to say. Matthew Peloquin co-established MongoDB's web strategy and set the strategy for the company's product pages: which action each page leads with, how the researched page structure rolls out across every product, and how the pages are produced and optimized for conversion.
Launch execution is mostly sequencing and standards rather than authority. Define the web workflow for each launch type up front, name an owner for every dependency, keep one calendar, and make the date the thing everyone is accountable to. Matthew Peloquin leads web execution for MongoDB's go-to-market launches, coordinating contributors across marketing and partner teams he does not manage.
Keeping the site publishing while it happens. Migrations tend to fail on the content model and the interim path rather than on the platform choice, so settle which page types exist before mapping content, and run a parallel publishing route so launches do not queue behind cutover. Matthew Peloquin's team held every launch date through a multi-year migration to a headless CMS and a full site redesign at MongoDB.
Search engine optimization (SEO) is about ranking a page in a list of results. Generative engine optimization (GEO) is about influencing what a model says when it composes an answer. Answer engine optimization (AEO) is about being the source that answer cites. They share infrastructure, including clean indexation, clear structure, and machine-readable facts, but they optimize for different outcomes, and most enterprise marketing sites are still built only for the first.
Reach me on LinkedIn or at matthew@peloquin.net. Matt is fine.
Last updated