At lemlist, Nicolas Gromer, Growth, uses AirOps to automate the production of SEO and GEO content. In less than a month, the company created up to 300 articles and updated 500 pages, with organic traffic increasing by more than 140%. He explains his workflows, the savings made, and why lemlist is now considering leaving AirOps.
How lemlist created 300 articles and updated 500 pieces of content in less than a month
In less than 30 days,
lemlist produced 200 to 300 new blog posts and updated 500 existing pieces of content thanks to AirOps. The company has since maintained a pace of 50 to 80 pieces of content created, rewritten, or merged each week, for only three to four hours of weekly work according to Nicolas Gromer.
These volumes are accompanied by a more than 140% increase in organic traffic since the launch of this strategy. And lemlist has not formed a dedicated editorial team: Nicolas himself manages the automations alongside his other Growth missions.
“With AirOps, we created about 200 to 300 blog articles in less than 30 days and updated 500 articles. We estimated that we didn't need to have someone full-time for that.”
To achieve these volumes, Nicolas relies on AirOps, a platform that allows for the automation of creation, optimization, and updating of content with AI. But he didn't just settle for the default workflows. He gradually rebuilt part of it to reduce production costs.

Why lemlist chose AirOps for its SEO and GEO strategy
When Nicolas started using
AirOps, he was still quite unfamiliar with competing solutions. He specifically mentions
Profound, which he hadn't identified before making his choice.
His appreciation of the product is nonetheless very positive, especially for its ability to handle large volumes of content.
“AirOps is truly an incredible tool. It's very powerful because it's quite easy to update a huge number of pages in bulk, based on a content brief. The briefs and content creation are really well done.”
The appeal of AirOps lies in its reusable workflows. Instead of writing each article separately, Nicolas can chain several operations: identify a topic, gather the necessary information, prepare a brief, generate the content, and publish it. The same process allows updating hundreds of existing pages.
AirOps also offers GEO tracking, to monitor lemlist's visibility in AI-generated responses. Nicolas compares this feature to that of
Peec AI, a specialized solution he considers more comprehensive for monitoring. However, AirOps' capabilities remain sufficient for his needs.
The platform is also connected to
Semrush, to analyze keyword trends, and to Google Search Console, to retrieve the site's performance data in search results.

Tools in this section
The Context Center: how lemlist gives AirOps the right information
For Nicolas, a large part of the work takes place even before the articles are generated.
AirOps has a space called Context Center, where lemlist centralizes the information needed by the workflows: software features, client profiles, editorial guidelines, and keyword clusters.
The goal is to avoid asking an AI to write about a product it doesn't know well enough.
Documenting features and use cases
Each important feature of lemlist is described in the Context Center, with explanations on how it works.
Nicolas takes the example of an article dedicated to prospecting CFOs. The workflow can consult the product information, identify relevant features for this use case, and integrate them into the content. When the software evolves, this same information is used to update the relevant articles.
Adapting content to different customer profiles
The Context Center also contains editorial guidelines for the different ICPs of lemlist: Sales Leaders, individual salespeople (IC), RevOps, Growth, and Founders.
An article intended for a founder will not necessarily be written like content intended for an operational manager. For the former, Nicolas may favor a more direct or strategic angle. For the latter, he will request more practical details.
lemlist has also chosen to write its blog articles in the first person, a rule integrated into the workflow instructions.
Finally, the Context Center groups the keyword clusters defined for the SEO strategy. When an article is generated, AirOps can consult these clusters and integrate the relevant terms to maintain consistency across the site's various contents.
“In the AirOps Context Center, for each feature, we have put how it works. We also have the tones of voice by ICP: Sales Leaders, IC, RevOps, Growth, and Founders. The workflows will query all this context to produce the articles.”
How lemlist automates updating its old articles
One of the most developed uses at lemlist concerns the updating of existing content.
Nicolas built a workflow that starts by retrieving articles published more than six months ago. AirOps then analyzes them according to predefined criteria. It can, for example, identify information indicating that content is outdated, then select the relevant URLs.
The process then unfolds in several steps.

Rebuilding the brief and updating keywords
A first workflow takes the existing article to reconstruct its brief in Markdown format. This step allows for retrieving the structure and initial objective of the content without starting from scratch.
A second workflow conducts new keyword research, relying on the Context Center clusters and associated product pages.
AirOps can then rewrite the necessary passages, update the information on lemlist, and apply the editorial guidelines. The new version is published on the same URL, allowing the page to be retained while renewing its content.
Automating internal linking
AirOps also handles part of the internal linking. The workflows identify relevant pages on the site and add links between articles.
For a blog that has several hundred contents spread across different clusters, this automation avoids manually revisiting the linking with each update.
Nicolas also believes that this feature could be rebuilt with internal workflows, like a large part of the automations he uses today.
How AirOps finds new SEO topics for lemlist
Beyond updates, Nicolas uses AirOps to identify new editorial opportunities.
He developed a specific workflow, independent of production tables, that analyzes keywords from the Context Center and their recent trends. The tool can notably detect searches whose volume increases or decreases over the last three weeks.
Based on this data, AirOps suggests new topics. Nicolas explains that he can receive five or six keyword recommendations for a day, with a dozen editorial angles for each.
He then selects the angles that interest him before initiating the creation of briefs and articles.

An interface similar to Clay or Excel
To organize this production, AirOps uses grids, tables that Nicolas compares to Excel or the Clay interface. Each column can correspond to an operation or a workflow, allowing several dozen pieces of content to be processed in parallel.
Nicolas sometimes prepares CSV files containing all the data necessary for generation. He notably uses Claude to transform collected or scraped data, such as large JSON files, into tables directly importable into AirOps.
Once the columns are configured, he can launch the production of 50 or 60 articles in a single day when a specific need arises.
“AirOps is a bit like Clay in its use. A column corresponds to a workflow or content. I can ask Claude to prepare a CSV with the collected data, then run my flows on the 50 or 60 articles I want to generate in a day.”
AirOps also offers structured data processing features and an MCP server, which Nicolas finds useful for these operations.
How lemlist automates its comparison pages and limits SEO cannibalization
Comparative pages are another important use case for AirOps at lemlist.
Nicolas explains that he generated all the versus pages of lemlist with the platform, which compare the software to other sales prospecting solutions.
The workflow can search for information on competitors, notably their pricing, and then integrate it into the articles. But the interest extends beyond publication: prices change regularly and comparisons quickly become outdated.
With AirOps, Nicolas can schedule a price check every month, or every two to three months. When the information changes, the relevant articles can be updated.
“I created all the versus pages for lemlist with AirOps. For tool comparisons, it fetches the current prices and turns them into blog articles. You can then ask it to check every month or every two or three months to ensure the prices are still up to date.”
Producing so much content also poses another problem: several articles may end up addressing the same search intents.
Nicolas has thus developed a workflow to detect SEO cannibalization risks. He also uses AirOps to merge articles when their topics overlap.
This is an important distinction: the 50 to 80 pieces of content handled each week are not all new publications. Some are rewrites, updates, or mergers of existing pages.
What SEO results lemlist achieved with AirOps
Since implementing these workflows, Nicolas attributes a more than 140% increase in organic traffic to this new organization at lemlist.
The main results he shares are as follows:
Nicolas also notes that he has not observed any SEO penalty related to the use of AI-generated content. He emphasizes the importance of the context provided to AirOps and the organization of the workflows.
“We haven't had any SEO penalty using AirOps even though the content is AI-generated. Why? Because they ask you to set up a significant context around your product, all its features, and the tone of voice according to the ICPs.”
lemlist also observes impressions in generative search tools, complementing its visibility on traditional search engines.
How much does AirOps cost and how lemlist reduced its credits by 80%
Nicolas estimates the cost of AirOps at around €1,500 per month. At this price, he considers the platform remains attractive compared to the cost of a dedicated content production team.
But his opinion is much more critical regarding the billing of additional credits.
According to his experience, consumption was not capped by default. In case of overage, the fees could drive the bill up to two or three times the usual monthly amount, without sufficiently visible alerts.
“AirOps is very powerful, but you have to be careful with the product because there are some dark patterns in its use. When you become a client, the use of tokens is not limited by default and additional tokens are really overpriced. It can make your monthly amount two or three times higher.”

Replacing AirOps API calls with its own keys
To limit these costs, Nicolas began modifying the platform's preconfigured workflows.
AirOps offers ready-to-use automations, but these use its own credit consumption mechanisms. Nicolas chose to duplicate the workflows and replace certain steps with calls using lemlist's API keys.
It took him about a day to understand how the tool works and to rebuild the main workflows.
The result is significant: according to him, consumption has decreased from 60,000 to 12,000 credits per month, a reduction of 80%.
“With AirOps, I took an afternoon, duplicated everything, and put in our own API keys. We went from 60,000 tokens per month to 12,000. Once you understand the tool, it's not very difficult to recreate the flows.”
Nicolas believes that this method can significantly reduce generation costs, even mentioning a reduction by 400 times in some cases.
By directly using its own API keys, lemlist covers part of the costs of language models while consuming far fewer AirOps credits. The company can thus produce more content without proportionally increasing its budget on the platform.
Why lemlist is now considering leaving AirOps
Despite the results achieved and his very positive view of the product, Nicolas explains that lemlist is preparing a possible exit from AirOps.
The main reason is economic. Credit overruns and their billing have created significant dissatisfaction.
“We are already preparing our exit from AirOps. What they really succeeded in is that once everything is in place, it's very easy to use. But the workflows themselves are not too complicated to set up.”
For Nicolas, the great success of AirOps lies in the ease with which the platform allows organizing complex operations. Keyword research, brief preparation, article generation, internal linking, and publication: everything can be chained without developing each component.
But once these mechanisms are understood, he considers that a large part could be rebuilt with n8n or internal developments.
He particularly emphasizes the importance of briefs and the organization of generation, two elements that he believes contribute to obtaining articles capable of ranking on Google.
The goal would be to retain the production methods established with AirOps while regaining control over their execution and costs.
At the time of the interview, AirOps is still used at lemlist, but Nicolas is already exploring the possibilities of further internalizing these workflows.
Summary of the software this article mentions in lemlist's stack
| Status | Workflow | Tool | Usage |
|---|---|---|---|
| In use | SEO / GEO Automation | AirOps | Creation, updating, optimization, and publication of content. Replacement considered. |
| In use | SEO / Keywords | Semrush | Keyword research and trend analysis. |
| In use | SEO Analytics | Google | Performance tracking in Google search. |
| In use | AI Assistant | Claude | Transformation of JSON data and preparation of CSV files. |
| In use | Automation | n8n | Already used at lemlist, considered for rebuilding AirOps workflows. |










