Objectives & Requirements
First, we clarify what the website is supposed to deliver: target audiences, priorities, and measurable signals. A clear set of objectives reduces revision loops later and creates a solid basis for decision-making.
Web Development
Websites, shops, and web apps
Web development today means more than “a new website”. What matters is whether users quickly understand what you offer, and whether your team can confidently maintain and evolve the site in everyday work.
What you get from us
Schaller Digital plans, designs, and develops websites, shops, and web apps so that structure, content, and technology are optimally aligned. So your web presence does not just go live - it delivers.
01
User-centered
Structure, content, and UI follow the context of use, not gut feeling.
02
Maintainable
Ongoing development without starting from scratch every time.
03
Solid web basics
Performance, technical SEO, and tracking fundamentals are considered from the very beginning.
04
Editors in mind
The CMS, roles, and workflows are set up so that content remains easy to maintain.
05
Operations are predictable
Go-live is a milestone, not an endpoint.
When this service is the right fit
Typical starting points
A good fit when …
- Your website has grown over the years. Content is hard to find, upkeep takes time, and changes carry risks.
- A relaunch is coming up that is not just about the look, but also about clarity, structure, and maintainability.
- Growth and internationalization create more content, languages, stakeholders, and complexity.
- Shop or product world: users cannot find their way around, and products are hard to compare.
- You want to get everything right from the start so that performance marketing, CRM/automation, or AI features do not work against the website later on.
Not suitable when …
- no one internally can take responsibility for content, approvals, and prioritization.
- “everything at once” is expected without prioritizing goals.
- only a “new look” is wanted, while structure and content are supposed to remain untouched.
- a fixed setup does not allow any clean standards, as effort and risks then increase unnecessarily.
How we work
From idea to running system
01
Decisions before details
Before design or development begins, we clarify goals, target audiences, and the first seconds of use: What needs to be immediately understandable? Which paths lead to the goal?
02
User guidance instead of a navigation maze
We translate complexity into clear entry points, understandable page logic, and unambiguous terminology. UX is not an extra here - it is the foundation for trust and conversion.
03
Implementation built for operation
A website is only as good as what happens after go-live. That is why we factor in components, roles, editorial workflows, and maintainability from the very beginning.
04
A clean foundation that will not slow you down later
Performance, technical SEO, and tracking fundamentals are part of web quality. This creates the basis for measurability, ongoing development, and scaling.
Three typical scenarios
When navigation paths have grown historically, it is not about “making it new”. It is about clarity: a clear layout, a logical content structure, and a CMS setup that works in everyday use.
When portals, self-services, protected areas, or interactive applications are needed, we sharpen requirements and usage scenarios and build a solution that runs reliably and remains extensible.
A good shop is more than just the checkout process. It creates orientation, comparability, and confidence in decision-making, so users can understand and choose, and your team can cleanly build campaigns and content on top of it.
Service modules
Structure & UX
We develop information architectures, entry strategies, and user flows. This creates orientation and a structure that stays stable even as content grows.
UI & Design System
We create a consistent system of components and templates. This ensures a calm, coherent appearance and upkeep that does not produce special cases every time.
Technical Implementation
We implement the solution so that it remains maintainable and easy for editors to manage. This also includes the CMS structure as well as templates, components, and the necessary integrations.
Quality Assurance Before Go-Live
Before launch, we check the points whose absence can become expensive later: functionality, presentation, and the most important fundamentals around performance, SEO, and tracking.
Operations, Maintenance & Ongoing Development
Together with you, we define an operating model that fits your team. Updates, security, backlog, and ongoing development happen in predictable iterations, so firefighting mode never sets in.
Optional (as needed)
- Content migration
- Multilingual setup
- Accessibility basics
- Tracking/consent fundamentals
- HubSpot integration (website side)
- AI-adjacent web features (e.g. search) when objectives and data foundation are a fit
Technology & systems
Choosing pragmatically
We do not choose systems based on the latest hype, but on your requirements. We take into account complexity, roles, maintenance effort, operations/security, speed, and extensibility.
TYPO3 or WordPress or an entirely different CMS
The decision depends on how complex the structure, roles, and governance are, and how much standardization or customization makes sense. If a system is already set, we optimize it.
Shops & platforms
Whether shop or platform: what matters is what users need (orientation, comparison, consulting, and service) and how your team maintains content and product range.
Integrations
We plan integrations (e.g. tracking, CRM, interfaces) as a building block, not as a “quick add-on at the end”. This keeps the website stable and maintainable.
Interfaces to AI, HubSpot, and performance
Web + Performance
Web provides the foundation: clear messaging, good UX, strong landing pages, and reliable measurability. Performance then ensures that campaigns are scaled, tested, and optimized.
Web + HubSpot
Web takes care of structure, UX, and clean integration. HubSpot handles the CRM and automation logic as well as processes and lifecycle journeys.
Web + AI
Web can enable AI-adjacent features (e.g. search, personalization) when content, structure, and data foundation are a fit. AI strategy, use cases, and enablement are covered in depth in our AI service.
Examples
Web projects (selection)
Coordinated relaunches: WSP
Multiple websites in one consistent setup: a clear structure, a clean maintenance logic, and an appearance that fits together across all sites.
TYPO3 relaunch with a product focus: MINUTO
We structured the product and service content so that users can understand and compare it faster, while the setup remains editorially sustainable.
Concept, implementation, support: SYBIT
A clear three-step process from objectives and structure to go-live and handover, including enablement so teams can continue seamlessly in day-to-day operation.
Interactive website formats: JUMO
When content is meant to be experienced and used rather than just read, interactive elements with a clear focus on orientation and user guidance are essential.
Collaboration & process
01
Concept
Goals, target audiences, page logic, content/UX. So it is clear early on what will be built and why.
02
Implementation
Design system/components and technical implementation in the agreed system, with a clean CMS structure and integrations.
03
Ongoing support
Go-live quality assurance, handover, training, and, if needed, operations/ongoing development.
What we need from you
Clear points of contact, decisions at reasonable intervals, access to existing content/data, and a realistic content and approval logic.
What you can expect from us
Transparent work packages, traceable decisions, structured handovers, and an implementation that does not fall apart at the next change.
Key terms in brief
Rebuilding or fundamentally reworking a website - not just visually, but also structurally and technically. A relaunch starts with goals, not with the design.
The system your team uses to maintain pages, content, and media - without developer knowledge. Whether TYPO3, WordPress, or a headless system: the choice depends on structure, roles, and governance, not on hype.
How easily users reach their goal - through clear structure, understandable paths, and unambiguous terminology. UX is not a design question, but a question of architecture and content.
The visible surface: components, layouts, interaction patterns, and the design system. Good UI makes UX decisions visible - it follows the structure, it does not create it.
The technical prerequisites for a website to be correctly indexed by search engines: load times, clean URLs, structured data, crawlability. Not a ranking promise, but a necessary foundation.
Updates, security patches, backups, and predictable ongoing development. Those who treat maintenance as a cost factor end up paying the bill later as an emergency sprint.
FAQ
The key decision questions
Included are the objectives, the UX/structure, the UI system, the implementation, and quality assurance before go-live. Not automatically included are ongoing campaign management (performance), CRM/automation programs (HubSpot), or an AI strategy/AI enablement. The model for operations/maintenance is clearly defined.
Concept, implementation, ongoing support. A relaunch rarely fails because of technical problems - it usually fails because of unclear responsibilities and late scope changes. That is why we clarify roles and content questions early on.
Based on requirements: roles/governance, structural complexity, operations/security, budget/speed. If a system is already in place, we optimize within it.
We create the right conditions in structure and implementation. However, rankings cannot be credibly guaranteed, as visibility also depends on competition, content quality, and ongoing upkeep.
Either we handle the implementation internally and enable your teams, or we define the scope and routine and support you with the implementation.
Planning follows a clear update logic and iterations. If updates are suspended for an extended period, risk and effort increase significantly later on.
Integrations are planned, documented, and implemented cleanly. The technical foundation is provided by the website team, while the functional logic sits with performance or HubSpot, depending on the topic.
Since we do not use standard templates, costs are based on the individual scope of features, the design ambition, and the technical integrations. Depending on your requirements, we define the right package together to keep costs predictable and efficient for you.
Next step
If you are facing a decision in the web space (relaunch, platform, shop), we prefer to start with a short, structured conversation. We discuss goals, current situation, and risks, and develop a realistic proposal for the next steps.
