Web agency for NRW. Websites your team can work with.
We connect websites, content and systems. With clear responsibilities for your CMS, integrations and development after launch.
Web agency from Wuppertal
A website up front. A clear workflow behind it.
Your editors need understandable fields. Sales needs current information. Developers need clear interfaces and documented decisions. We plan websites around these connected tasks. Design, content and technology are aligned early.
Our team is based in Wuppertal and works with businesses across NRW. Projects for MARTOR in Solingen and STAHLWILLE in Wuppertal show our digital product platform work. For Metalshub in Düsseldorf, we delivered brand and website work. Together, we define the foundation your team needs.
:quality(80):format(webp))
Selected projects
What we work on
The building blocks behind your website.
:quality(80):format(webp))
CMS and editorial work
Fields, components and approvals need to fit daily work. We plan the website from your editors’ perspective.
:quality(80):format(webp))
Content models
Products, services and knowledge need clear structures. Reusable content receives a defined place.
:quality(80):format(webp))
Integrations
We define which system owns each dataset. Data flows and failure cases are described before implementation.
:quality(80):format(webp))
Migration
We review existing content and URLs. Transfer, mapping and necessary redirects are planned.
:quality(80):format(webp))
Quality assurance
We check core functions and editorial workflows. Responsibilities and approval criteria are agreed before launch.
:quality(80):format(webp))
Handover and ongoing operations
Your team receives clear documentation. Maintenance, access and further tasks are explicitly agreed.
Related services
The right services for your digital foundation.
Working together
From requirements to a usable website.
We separate decisions, implementation and approvals into clear steps. Your team stays involved in the important questions.
Clarify requirements
We identify user tasks, content and existing systems. Together, we define responsibilities, dependencies and scope.
Plan the foundation
We agree the content model, components and integrations. Technical decisions are checked against your workflows and available resources.
Implement and test
We develop the agreed functions and test them with real content. Your editors test the relevant editing workflows.
Launch and handover
We agree approvals, access and documentation. Post-launch tasks are handed over with named contacts and clear responsibilities.
Discuss your website project
Make your website easier to work with.
Show us your website and the systems behind it. We discuss content, your team and technical constraints. This defines a suitable project scope.
- Discuss systems and requirements
- Clarify scope and responsibilities
Talk to our team
:quality(80):format(webp))
A web agency for NRW needs to understand your team.
A new website also changes internal workflows. Who edits content, checks product information and approves changes? We clarify these tasks before choosing systems. A small editorial team has different needs from several specialist departments. Our Wuppertal team coordinates with your contacts. Technical scope follows your tasks, not the other way around.
Every dataset needs a clear owner.
Products, images and contact details may live in different systems. We identify which source is responsible for each piece of information. Integrations and update paths can then be planned. Missing data and failed connections also need to be described. We resolve these questions with your technical contacts. An integration alone cannot replace a reliable maintenance process.
A relaunch needs a plan for existing content.
We assess which pages should be retained, combined or rebuilt. Existing URLs and internal links belong in that review. Content is not replaced simply because the design changes. We agree mappings, redirects and approvals for changes. Real content also shows early whether components and fields meet editorial needs.
Responsibility does not end at launch.
Before publication, we clarify operation, access and how future changes will be handled. You know which tasks stay internal and what support is agreed. Documentation and training reflect your team’s needs. Maintenance and further development are separate services with a defined scope. Responsibilities remain clear after launch.
Our Websites service explains the work around content, CMS and technical implementation.
Web agency for NRW
Questions about technical collaboration.
pechschwarz® is based in Wuppertal. We work with businesses across NRW and beyond. Meetings, workshops and technical reviews are planned around your team.
Web design addresses user journeys and visual design. This service focuses on the technical website, its CMS and connected systems. Both are planned together, with each scope clearly defined.
Not automatically. We review requirements, available functions and technical limitations. We can then decide whether the current system is sufficient or a change makes sense.
We review interfaces, available data and responsibilities. Possibilities depend on your systems and access. Scope, data flows and error handling are agreed before implementation.
We inventory content and URLs before migration. Then we agree transfer, consolidation and necessary redirects. Important entry points are checked before and after launch.
We plan CMS fields and components for the agreed editorial tasks. Your team tests these workflows before launch. Training and documentation are agreed according to the project scope.
We agree that before publication. Operation, maintenance and further development each have their own tasks and responsibilities. You know your contacts and the scope of agreed support.
You describe your website, systems and main requirements. We review open questions and dependencies. Then we agree scope, phases, approvals and responsibilities.
Ready to unlock your website’s full potential?
: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))