Contentful agency for better content
Our awards
Results that count
Outstanding work for brands
Brands
From hidden champion to global player.
Ranking
1st place at the German Web Awards 2026.
Rating
Average rating from our clients.
Reviews
Customer reviews on ProvenExpert.
:quality(80):format(webp))
Content modeling
Model content as reusable entries and relationships. Products, solutions, and contacts are maintained independently of individual pages.
:quality(80):format(webp))
Live Preview & Studio
See changes in the frontend and design experiences with prepared components. We set up preview and the required Studio building blocks to fit your application.
:quality(80):format(webp))
Locales & approvals
Plan language versions, fallbacks, and editorial responsibility together. Not every market needs the same content or the same publication time.
:quality(80):format(webp))
Environments
Test changes to the model in separate environments. Migrations and environment configurations are transferred into operations in a traceable way.
:quality(80):format(webp))
AI & automations
Use AI Actions with your specifications and connect recurring workflows. Suggestions, review, and publication remain clearly separated.
:quality(80):format(webp))
APIs & integrations
Delivery, Preview, and Management API serve different purposes. CRM, PIM, search, and commerce are connected via defined data paths.
Brand, design & development
Digital projects from our practice
Insights into our work for finance, health, industry, and hospitality. The projects show our design and user guidance across different technologies.
Radiology Advanced
Explain teleradiology in an understandable way and clearly structure offerings. Corporate presence, journal, and academy create orientation for different target groups.
:quality(80):format(webp))
i-pointing
A presence for the presentation house from Munich. Services, portfolio, and consulting topics combine into clear paths through the offering.
:quality(80):format(webp))
GEBHARDT
Explain intralogistics for different markets and industries. Products, solutions, and references form interconnected entry points into complex topics.
:quality(80):format(webp))
Hotel Erasmus
Three houses, wellness, and culinary delights in one shared world of experiences. Offers and inspiration lead guests from the first impression to the right stay.
More from our web design practice
Contentful consulting
What should your platform do better with Contentful?
We check where content is maintained multiple times, which channels it needs, and how your editors publish new pages. From this we create a content model, matching experiences, and an architecture with clear data responsibility.
:quality(80):format(webp))
Your team for Contentful
We connect Contentful, brand, and frontend into digital experiences that grow with your content and markets.
Team
Strategy, design, development, and marketing under one roof in Wuppertal.
Experience
Over ten years of brands and websites for medium-sized businesses and corporations.
Awards
In seven independent award programs.
Contentful manages structured entries, assets, and relationships. The frontend turns them into websites, apps, or other outputs. We model recurring information separately from its presentation: a product can have its own data structure and appear in multiple experiences. Validation and understandable field names make this structure usable for editors. The clearer these foundations are, the fewer exceptional cases arise for new pages and channels.
Contentful manages structured entries, assets, and relationships. The frontend turns them into websites, apps, or other outputs. We model recurring information separately from its presentation: a product can have its own data structure and appear in multiple experiences. Validation and understandable field names make this structure usable for editors. The clearer these foundations are, the fewer exceptional cases arise for new pages and channels.
Live Preview connects the Contentful editor with the preview of your frontend. Contentful Studio adds a visual composition of experiences with prepared components and patterns. Both must fit the application: preview URLs, draft data, and components are consciously integrated. A freely definable content model does not yet create a finished design system. We therefore test a real campaign page with your editorial team before many templates are created.
Live Preview connects the Contentful editor with the preview of your frontend. Contentful Studio adds a visual composition of experiences with prepared components and patterns. Both must fit the application: preview URLs, draft data, and components are consciously integrated. A freely definable content model does not yet create a finished design system. We therefore test a real campaign page with your editorial team before many templates are created.
Contentful can provide content for a digital experience platform. Product data comes from the PIM, transactions from commerce, contacts from the CRM. Search and personalization complement the appropriate user journeys. We define source-of-truth systems, updating, and error handling. Contentful Personalization is an additional offering whose use requires data, target groups, and meaningful measurement. The necessary product and plan scope is clarified in advance.
Contentful can provide content for a digital experience platform. Product data comes from the PIM, transactions from commerce, contacts from the CRM. Search and personalization complement the appropriate user journeys. We define source-of-truth systems, updating, and error handling. Contentful Personalization is an additional offering whose use requires data, target groups, and meaningful measurement. The necessary product and plan scope is clarified in advance.
From maintenance to operations
Contentful features that matter in everyday work
Content modeling
Model content as reusable entries and relationships. Products, solutions, and contacts are maintained independently of individual pages.
Live preview & Studio
See changes in the frontend and design experiences with prepared components. We set up preview and the required Studio building blocks to fit your needs.
Locales & approvals
Plan language versions, fallbacks, and editorial responsibility together. Not every market needs the same content or the same publication time.
Environments
Test changes to the model in separate environments. Migrations and environment configurations are transferred into operations in a traceable way.
AI & automations
Use AI actions with your specifications and connect recurring workflows. Suggestions, review, and publishing remain clearly separated.
APIs & integrations
Delivery, Preview and Management API fulfill different tasks. CRM, PIM, search and commerce are connected via defined data paths.
Contentful Studio & Content Operations
Model cleanly once. Use in many experiences.
A campaign should not have to start from scratch for every language version. We connect central content with experiences and approved design components. This way, a product information item can be maintained centrally, while different markets receive suitable entry points and offers.
AI Actions can rework texts and prepare translation drafts. We define inputs, brand rules and review steps. Automations and workflows are added as appropriate; we check availability and quotas for the scope you have booked.
:quality(80):format(webp))
New fields, relationships and required information affect editorial staff and applications. We test model changes in a separate environment and keep migrations transparently documented. Environment aliases can simplify assigning an application to an environment. They do not replace checking content, frontend and integrations before switching.
New fields, relationships and required information affect editorial staff and applications. We test model changes in a separate environment and keep migrations transparently documented. Environment aliases can simplify assigning an application to an environment. They do not replace checking content, frontend and integrations before switching.
AI Actions can, for example, rework texts or prepare translation drafts. We define input fields, brand rules and a verifiable outcome. Automations and workflows can connect these tasks. Expert review and publishing rights remain part of the process; model choice, quotas and required products are checked against the specific plan.
AI Actions can, for example, rework texts or prepare translation drafts. We define input fields, brand rules and a verifiable outcome. Automations and workflows can connect these tasks. Expert review and publishing rights remain part of the process; model choice, quotas and required products are checked against the specific plan.
A different entry point makes sense if it helps a target group with a specific task. We plan variants, data sources and success criteria before the technical implementation. Contentful Personalization can support such experiences. Without sufficient data or a verifiable difference, a clear shared page is often the better first step.
A different entry point makes sense if it helps a target group with a specific task. We plan variants, data sources and success criteria before the technical implementation. Contentful Personalization can support such experiences. Without sufficient data or a verifiable difference, a clear shared page is often the better first step.
Our services for Contentful
From platform to outcome
A reliable plan starts with your workflows.
We record key pages, target groups and tasks together as a team. Requests, conversions and maintenance effort are considered separately. From this we derive priorities you can use to evaluate the success of the project.
Contentful is a good fit for companies that want to share structured content across teams, markets and channels. For a small website with little reuse, a simpler CMS may be sufficient. We compare model flexibility, visual editing, product scope and ongoing costs.
Entries are modeled according to their subject-matter meaning instead of only by page layout. References link products, services and contacts. Validations and allowed relationships limit errors. The model is tested with typical editorial tasks.
Contentful manages structured entries, assets and relationships. The frontend uses them to build websites, apps or other outputs. We model recurring information separately from its presentation: a product can have its own data structure and appear in multiple experiences. Validation and clear field names make this structure usable for editors. The clearer these foundations are, the fewer special cases arise for new pages and channels.
Effort arises from modeling, frontend, experiences, migration and integrations. On top of that come the required Contentful products and plans as well as hosting and support. Users, environments, content and delivery are considered together before choosing.
We define who prepares content, performs expert reviews and publishes. A test with a real page shows which permissions and guidance are needed. New workflows are trialed with your editorial team.
Your brand becomes an operable system.
We guide users from a specific question to the right offering. Navigation, search, and contact paths are aligned with your target audiences. Prototypes make these paths testable before development.
Colors, typography, components, and states are designed together. Your editorial team receives reusable elements with clearly defined degrees of freedom. This way, new pages remain part of the same brand.
Live Preview connects the Contentful editor with the preview of your frontend. Contentful Studio adds a visual composition of experiences with prepared components and patterns. Both must fit the application: preview URLs, draft data, and components are deliberately integrated. A freely definable content model does not yet create a finished design system. That’s why we test a real campaign page with your editorial team before many templates are created.
We review menus, forms, content order, and media on small screens. Touch targets, legible type, and short paths are part of the concept. The mobile version is approved with real content.
Keyboard operation, focus, contrasts, labels, and clear error messages are reviewed at the component level. The editorial team also receives rules for headings, links, and alternative texts.
Live Preview and Contentful Studio are connected to the frontend. Editors review content in the correct language and presentation. Reusable components require technical registration and an understandable design system.
Structuring content so people can find answers.
We map search queries to your services and products. Every important page gets its own task, suitable proofs, and a next step. Similar terms do not automatically lead to several almost identical pages.
SEO fields are maintained in the content model and output by the frontend. We plan page titles, canonicals, hreflang, structured data, and sitemaps. Draft content must remain separate from public outputs; a CMS setting alone does not replace checking the rendering.
Locales and fallbacks are planned by market. A shared entry with translated fields is not automatically suitable for every local offering. We review separate approvals, required fields, URLs, and editorial responsibility.
Texts, images, and videos are created from your actual offering. We clarify statements, responsibilities, and approvals early. Content is prepared based on real page formats and reviewed in the CMS.
Services, technical terms, use cases, and sources are explained in a traceable way. For AI search, the same statements require accessible pages and reliable evidence. Mentions and cited sources can be monitored; a recommendation by an AI system is not guaranteed.
We define events along the inquiry or purchase process. Analysis and consent are aligned with your setup. The decisive factors are actionable contacts and conversions, supplemented by usage and editorial effort.
Data should be maintained in the right place.
The Delivery API provides published content, the Preview API provides drafts, and the Management API is used for administration. GraphQL enables targeted queries. Webhooks can trigger further processes; caching and retries are planned in the overall system.
We plan required fields, validation, responsibilities, and the handover to the CRM. A successful submission must arrive in the target system. Error cases and feedback to users are co-tested.
Product data and transactions remain in the PIM and commerce system when needed. Contentful adds advisory and brand content. We link the data sets using stable identifiers and take availability and price freshness into account.
Search, filters, and sorting start from users’ tasks. We review typical terms, synonyms, and empty result lists. Updating and access rights are part of the concept for a connected search solution.
AI Actions can rework texts and prepare translation drafts. We define inputs, brand rules, and review steps. Automations and workflows are added as appropriate; we review availability and quotas for your booked scope.
For each connection, responsibilities, updating, and error handling are defined. Logs and notifications help detect interrupted transfers. Retries must not generate duplicate records or orders.
The transition is part of the project.
We capture content types, relationships, assets, and languages of the existing system. A trial import checks references and field mappings. Model changes and the final switchover are coordinated with the frontend, redirects, and editorial approvals.
We map existing URLs to specific new targets. Important content remains reachable; unnecessary redirect chains are avoided. After the switch, we review status codes, canonicals, internal links, and the sitemap.
We review editorial tasks, responsive display, search, and forms with real content. Key integrations are tested including error cases. Before go-live, responsibilities, acceptance criteria, and a rollback plan are defined.
Your team works on its own content during training. Field help, short guides, and responsibilities remain available after launch. New components are planned as further development.
We support the frontend, integrations, and the ongoing development of the content model. API usage, webhooks, and publishing paths are monitored as needed. Product limits, user rights, and environments remain part of ongoing planning.
After launch, we prioritize based on agreed KPIs and your feedback. New features receive a clear goal and verifiable acceptance. This keeps the platform connected to your business.
Additional services
More impact for your digital presence
:quality(80):format(webp))
Brand Strategy
:quality(80):format(webp))
Brand Identity
:quality(80):format(webp))
Brand Rollout
:quality(80):format(webp))
Brand Growth
:quality(80):format(webp))
Employer Branding
:quality(80):format(webp))
UX, UI & Design
:quality(80):format(webp))
E-Commerce
:quality(80):format(webp))
Platforms
:quality(80):format(webp))
APIs & Automation
:quality(80):format(webp))
Content Creation
:quality(80):format(webp))
Motion Design
:quality(80):format(webp))
3D & CGI
:quality(80):format(webp))
Photography
:quality(80):format(webp))
Digital Marketing
:quality(80):format(webp))
Ad Creatives
:quality(80):format(webp))
GEO
:quality(80):format(webp))
Social Ads
:quality(80):format(webp))
Copywriting
Architecture & data
Contentful as the connecting content layer
Content becomes usable centrally, while specialized systems keep their task.
Contentful
Structured entries and assets provide the editorial content.
Studio & Frontend
Components and experiences translate content into your brand.
PIM & DAM
Product attributes and media remain in the intended sources.
Search & Personalization
Orientation and variants are added based on user tasks.
Commerce & CRM
Purchases and inquiries are handed over to the responsible systems.
Workflows & measurement
Approvals, delivery and impact become traceable.
»Wir waren mit der Agentur Pechschwarz sehr zufrieden. Wir sind sicher, mit dieser langfristig einen guten E-Commerce- & Shop-Berater an unserer Seite zu haben. Eine starke Full-Service Agentur die tatsächlich alle Bereiche gut abdeckt, sowie durch Kreativität, persönliche Erreichbarkeit und ein gutes Preis-Leistungs-Verhältnis überzeugt.«
:quality(80):format(webp))
Ready for more?
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
Ready for more?
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
pechschwarz®
Brand, design and technology. One joint team.
A platform alone does not yet solve a task. We connect brand strategy, user guidance, content and development – with fixed contacts and clear decisions in every phase.
For your Contentful project, we combine strategy and design with a transparent implementation. You evaluate real content models, prototypes and user journeys. Editorial handover, interfaces and ongoing support are planned together.
:quality(80):format(webp))
Typical applications
Contentful for your requirements
Contentful becomes particularly interesting when the same information is needed in many places.
Which solution fits?
Content needs a shared model.
Which solution fits?
Content needs a shared model.
Contentful with pechschwarz®
Content, design and operations are developed together.
Implementation without a shared plan
Unclear rules increase the effort needed to maintain and extend the platform.
Our process
This is how your Contentful project comes to life
From the first workshop to launch: one fixed team, clear decisions and shared goals. You know what will be created next.
Goals & existing setup
We capture reuse, channels, languages and approvals. The most important editorial tasks determine the scope.
Concept & architecture
Content model, environments and frontend are planned together. One experience serves as a tangible prototype.
Design & editorial
We design real pages, content and interactions. Your team tests the editing process before the system is expanded to additional page types.
Implementation & transition
Components, APIs and migration are implemented. Drafting, publishing and updating are checked end-to-end.
Launch & further development
Acceptance, training and switchover interlock. After launch, we prioritize improvements based on your goals and feedback.
Contentful needs a domain-specific content model
A headline and a text field are not enough when multiple teams use the same product information. We start with the domain entities and their relationships. Only then is it decided which content will make up a page.
Environments are no substitute for release planning
A separate environment protects experiments on the model. The transition into operations still affects data, queries and frontend versions. We plan the sequence and check how changes can be rolled back.
Choose studio and personalization deliberately
Visual experiences only help if the prepared components fit the editorial needs. Personalization additionally needs a meaningful target group and measurable variants. Both are evaluated as their own use case and not planned solely because of a product name.
Insights for your digital platform
Use the arrow keys to browse. Home shows the beginning, End the last posts. Use Tab to select post links.
FAQ
Questions about your Contentful project
When content is to be reused across multiple teams, markets, or channels. Content model, frontend, and operations must be planned together. For a small initiative, an integrated CMS can be more economical.
Contentful Studio enables experiences with prepared components and patterns. Live Preview shows content in the frontend. Both require the appropriate technical setup and, if necessary, additional product components.
A Space organizes content and models. Environments allow separate states within a Space, for example for testing. Access, pricing, and the transition between environments are planned per project.
Contentful provides the content platform and complementary products. A DXP emerges together with frontend, search, commerce, CRM, and the appropriate data flows. Not every project needs all of the building blocks.
They can support recurring text tasks such as rephrasing or translation drafts. Inputs, approvals, and quality checks must fit the editorial workflow. Scope and limits depend on the setup.
Effort arises from modeling, frontend, experiences, migration, and integrations. In addition come the required Contentful products and plans as well as hosting and support. Users, environments, content, and delivery are considered together before making a selection.
We capture content types, relationships, assets, and languages of the existing system. A trial import checks references and field mappings. Model changes and the final transition are coordinated with the frontend, redirects, and editorial approvals.
We support the frontend, integrations, and further development of the content model. API usage, webhooks, and publishing workflows are monitored as needed. Product limits, user permissions, and environments remain part of ongoing planning.
Let’s achieve more with Contentful.
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))
:quality(80):format(webp))