Clear navigation, distinctive design and a website that explains your business.
What we build with you
Visitors need to understand your offer and their next useful step. We connect visual identity with understandable information, clear journeys and mobile interactions that work when time is limited.
- Information architecture
- Wireframes and visual system
- Responsive page layouts
- Forms and conversion paths
Design starts with the decision a visitor needs to make. We organize content, develop page hierarchies and define reusable components. Typography, spacing, images and interactions form a connected system. Prototypes make journeys testable early. Mobile layouts have their own priorities instead of simply shrinking the desktop presentation.
How the project takes shape
User journeys
Map audiences, information and contact paths.
Design system
Agree typography, imagery and components.
Responsive delivery
Review pages, forms and device widths together.
20 / QUESTIONS & ANSWERS
Decide with clarity.
What makes effective web design?
Clear information, recognisable actions and readable design. Motion supports orientation without obscuring content.
Will the site work on mobile?
We review navigation, forms, images and touch targets on small screens. The mobile content order is assessed separately.
Can I edit content myself?
Editable pages and components are created in the agreed CMS. Roles reserve technical settings for authorised people.
Can we use Elementor?
Yes. Elementor handles presentation while business logic and protected client data belong in independent modules.
How do animations stay fast?
We limit active effects, load media when needed and respect reduced motion. Testing on actual devices is essential.
Are existing URLs preserved?
Existing addresses are inventoried and retained where possible. Changed URLs receive specific redirects.
How is accessibility considered?
We review semantics, keyboard access, focus, contrast and form labels. A formal conformance audit is a separate scope.
Can the website be multilingual?
Language versions get separate URLs and matching links. Text and media labels need editorial care in each language.
How does the project start?
We clarify the audience, existing systems, responsible people and intended outcome, then agree the scope.
What determines the price?
Scope, integrations, content, licences and support are considered separately. You receive an individual offer before delivery starts.
When is the schedule agreed?
After discovery and prioritisation we agree milestones. Approvals, access and external dependencies influence dates.
Who supplies content and access?
We agree which text, images and data you provide. Access should use roles, invitations or limited tokens wherever possible.
Can existing systems keep running?
Yes, subject to a technical review. We plan changes, backups and rollback paths to keep the transition controlled.
How are changes agreed?
Questions are collected in the project. Extensions get a defined scope and approval before additional implementation.
How is acceptance handled?
We agree concrete test cases and responsible people. Open issues are documented and release follows the agreed approval.
Is a handover session included?
Handover can include training, documentation and defined access rights. The scope and format are specified in the offer.
What happens after launch?
Support, updates and response times are agreed separately, making internal and KG-NET responsibilities clear.
How is personal data handled?
We limit access and review data flows, retention and processor arrangements. Legal approval remains with the controller and their advisers.
Can you work across borders?
We work with businesses in Austria, Germany, Switzerland and Serbia. Language, responsibilities and actual market needs are agreed together.
How are outcomes assessed?
We agree verifiable goals and identify the data source. Without connected measurement there are no invented metrics or guaranteed outcomes.