The problem arrived in spreadsheets. Sascha Konietzke was developing mobile apps, and clients sent him the information they wanted inside them: product details, announcements, help text. Changing that information could mean finding the latest file among fifteen versions, importing it into an app, submitting the app to Apple, and waiting for approval. Then the customer’s customer had to install the update. Somewhere in this procession, a simple edit had acquired the administrative dignity of an international shipment.
Konietzke’s response became StorageRoom, then Contentful, the company he co-founded with Paolo Negri. Its premise was understandable even without the eventual industry vocabulary: keep information separate from the screen displaying it, so the information can change and travel. An app, a website, and another device ought to be able to use the same underlying material without each demanding its own little publishing empire.
There is a useful way to read his career through that first irritation. He kept asking which parts of a system needed to stay together, and which would work better apart. Eventually, that question reached his own job.
A teenage webmaster, then a traveller
Konietzke grew up in Stuttgart. At fifteen, he was already working as a webmaster for Vircinity, a hardware startup backed by venture capital. The early job put programming into a practical setting: somebody needed a website to work. Later, his studies in Business Information Technology at Stuttgart’s University of Cooperative Education combined computing with business. His parents had encouraged him to add the latter to his technical interests.
He joined Hewlett-Packard in 2005. Its published place in his biography matters because Contentful did not emerge from a career spent entirely inside young companies. He had seen a large organization from within before leaving HP in 2008. Travel followed, along with Tagcrumbs, a service for bookmarking places by geographical location.
That earlier venture is a revealing detail. A place, like a piece of app content, can be stored as information and used in different contexts. It would be too neat to turn Tagcrumbs into a secret blueprint for everything that followed. It does, however, belong to a career in which Konietzke repeatedly built software around how people collect, organize, and retrieve things.
A working service goes back to the drawing board
By 2010, he was building the mobile-content service in his living room. In August 2011, he introduced StorageRoom to a PhoneGap discussion group. He explained that the team had encountered the same problem repeatedly while developing iOS apps. He wanted feedback and asked whether the service belonged on PhoneGap’s tools pages. It was a modest request, addressed to people who might actually use the thing.
“I would love to get your feedback.”
Sascha Konietzke, introducing StorageRoom, 2011
Investors began to enter the picture. Christoph Janz later recalled receiving a cold email from Konietzke and backing the company alongside Balderton in 2012. At that point, StorageRoom had twenty-eight paying customers and monthly recurring revenue measured in hundreds of euros. The commercial evidence fitted inside a small envelope. There was nevertheless something to examine: customers were paying for a way out of a recurring problem.
Funding made a rebuild possible. In June 2013, Konietzke announced Contentful, constructed from scratch around the same underlying idea. Customer feedback had persuaded the team that a fresh architecture could serve it better. Existing StorageRoom customers were promised continued service through the end of 2014 and help with migration. A product announcement is more persuasive when it remembers the people still using yesterday’s product.
The editor deserves half the effort
The architecture gave developers access to structured content through APIs, the interfaces software uses to exchange information. Content no longer had to arrive dressed as a finished web page. The application could decide how to display it. That separation became familiar under the label “headless CMS,” with the presentation layer being the missing head. Software terminology occasionally rewards a perfectly sensible idea with an unfortunate anatomy lesson.
A 2014 snapshot catches Konietzke before the company’s later scale. Contentful had thirteen people in Berlin. He described development time as split roughly equally between the APIs and the editing interface. Mobile applications were a typical use, while agencies and publishers were finding other possibilities. The editor still needed work; workflow and permissions were among the next challenges.
Those details complicate an easy account of a company built only for programmers. Someone also had to enter and change the content. Freedom for the developer would be of limited comfort if the person maintaining the information found the editor unusable. The division of effort recognized both sides of the desk.
Text · images · information
A conceptual illustration of the separation between content and presentation.
In September 2014, Contentful released tools for iOS and Android developers, including software development kits. The original inconvenience was being translated into things other engineers could install and use. Architectural conviction had to meet ordinary development work.
An ocean changes the conversation
Contentful began in Berlin, but its customer base pushed it west. American businesses were among the early adopters of its cloud approach. Serving them from Europe meant evening work across the time difference. In 2016, the company opened a San Francisco office, choosing proximity to the Silicon Valley software ecosystem despite the easier clocks of the East Coast.
By 2020, that office had more than a hundred team members. Konietzke described a consequence less glamorous than a new address: the organization had to communicate better. Decisions could no longer depend on conversations everyone supposedly overheard in one office. A company can move information around the world and still struggle to tell its own colleagues what happened in a meeting.
The financing history had similar complications. Ahead of the 2016 Series B, investors hesitated despite progress. Existing backers provided a convertible loan, buying time. Benchmark then led the round as conditions improved. In Konietzke’s account, conviction about the product and supportive shareholders helped the company through the interval. The eventual financing announcements look orderly when arranged by year; the experience between them was rather less obliging.
A search for a COO becomes something else
In 2019, while interviewing candidates for chief operating officer, Konietzke reconsidered what the company needed. The question widened into whether another chief executive would bring the experience required for its next stage. Working with the board, he began the search. Steve Sloan, previously Chief Product and Marketing Officer at Twilio SendGrid, became the choice.
The announcement came on November 7. Contentful reported more than two thousand paying customers and expected its team to approach three hundred people by year’s end. Konietzke would remain on the board and become Chief Strategy Officer. His stated focus was a closer understanding of customers’ problems and the evolution of the product.
“I am a product person at heart.”
Sascha Konietzke, 2020
He later explained that day-to-day operations had crowded out the time needed to consider the longer term. He enjoyed learning to run the company, yet wanted to return to product questions. The admission gives the succession its human scale. Founding a business had made him responsible for a job whose expanding demands pulled him away from the work he most wanted to do.
Hiring a successor is also a decision about other people’s strengths. Konietzke brought the history of the product; Sloan brought experience operating larger businesses. The arrangement made room for both. It required a founder to regard his own job description as something that could be revised.
A lunch that filled in the missing piece
His interest in the surrounding software ecosystem extended beyond Contentful. In 2017, he met Gatsby founders Sam Bhagwat and Kyle Mathews for lunch in San Francisco. They shared frustrations with older, tightly bundled web systems. Gatsby supplied a way to build the presentation layer that a headless content platform deliberately left open.
Konietzke later wrote the foreword to Bhagwat’s book about modular web architecture. The appeal was a system assembled from components, each doing its own job, rather than one platform prescribing every part. The same thinking that had freed content for mobile apps could help website teams choose how to build and change their front ends.
This way of working also asks something of a founder’s temperament. At Contentful, Konietzke publicly emphasized humility and openness to colleagues’ ideas. His account of an early mentor’s advice kept grand discussions of culture and vision tied to getting a usable product out the door. A lovely concept does not pay the office bills. Customers have an irritating habit of wanting the software to work.
The company carries on
The figures grew. Contentful’s 2021 Series F raised $175 million at a valuation above $3 billion. By its June 2026 acquisition announcement, the company reported handling an average of 180 billion API calls per month. These describe the business and its usage; they say little on their own about the founder’s daily contribution. For that, the changes in his role are more revealing.
Salesforce’s agreement to acquire Contentful put the structured-content approach into another setting, with plans to make it available across Customer 360 and to Agentforce. In his announcement, Konietzke connected the company’s early architecture to that future. Information designed to travel between applications could also be assembled and delivered by agents.
Salesforce completed the acquisition on September 1, 2026. In a subsequent public announcement, Konietzke said he had left Contentful after the acquisition closed and the board dissolved. He thanked the people who had built the company and described lessons in forming teams and letting go. The departure followed a career that had already included one deliberate handover. This time, he was stepping away from the organization itself.
The fifteen spreadsheets are still a useful place to end. They explain why the work began without making the outcome look inevitable. Konietzke found a recurring nuisance, built a service, accepted feedback, rebuilt it with colleagues, and changed his own role as the company grew. The practical question survived each change: how can the information get where it needs to go?