Our strengths are in website implementation. In a typical website development creative web designers (user interface developers) design and produce sitemaps, key screen shots, key wireframes, branding, look, feel and user journeys. Some high level UML may be produced. The website owner approves these elements and the project progresses to the implementation stages.
Creative agencies have different strengths. An agency may be less strong in website implementation Website implementation is a software engineering discipline.
WhyWaitForever can handle a complete website development project or can work with a company's existing creative agency and handle website implementation. Knowledge of website implementation possibilities at the design stage means future developments such as extending content management and extending personalisation can be handled at far less cost.
In addition to website developments, here are some other website related projects we have undertaken.
Search visibility analyses a website to understand which content elements are visible to the search engine software used by search websites. A WhyWaitForever expert reviews the information and produces an assessment and a set of recommendations on how the implementation of website could be improved.
By improving search visibility the quality of information obtained through web analytics and from email marketing is improved.
Better information increases web visitors and results in increased web sales. more
Search visibility software is run against a number of competitor websites to extract information about products and prices. This information is formatted into a report. Extracts of the information can be formatted as emails and sent to interested parties.
Advantages of automated intelligence gathering include the ability to trawl through many websites, collating only pertinent information and delivering to the time constrained individuals who can make most benefit of the information.
Email marketing is straightforward. Individuals register to receive information about products and services. A company periodically sends out mailings to those that are registered. The email has to be tagged in such a way that every web page visited and every web sale made as a result of the email is accounted for.
It is important to track all sources of visitors. If the interests of particular types of visitors are known more web sales can be made.
Understanding why web sales are made is very useful for improving website personalisation and extended scenario processing. Business rules are devised whereby content specific to the interests of the visitor is presented to the visitor in a way best suited to achieving sales.
One challenge is that companies with many products typically use webservers that automatically generate URLs which are not memorable or meaningful. Unique session identifiers can be difficult to map to particular customers .
Tracking can be difficult. WhyWaitForever has expertise in marking up emails, configuring logging settings and running web analytics to provide accurate quality marketing information. more
Web analytics is the analysis of web activity. In common with all software auditing it is necessary to know who did what to what where and when.
The standard tools provide a basic level of analysis. WhyWaitForever extends these tools to provide more detailed information for more web aware marketing department.
WhyWaitForever can run web analytics and will provide a series of observations and recommendations based on the results. A company would provide access to the logs or would provide a copy of the logs on a set of CDs. The analysis in the form of reports would be returned.
Here are a good starter set of reports for the WhyWaitForever website for each of the last few years.
Website owners should take great care of their raw web logs. They are a valuable company asset.
WhyWaitForever has written a web application to support content management. It uses the OpenCms content management system as a base. Customised forms are used to create, amend or delete content. There is support for workflow and users with different security rights can be set up.
Typically WhyWaitForever uses the content management system to create document fragments. These are automatically processed to create other derived document fragments. For example when a news item is created, summary information is created. This summary is automatically extracted to create document fragments used in menu and index pages.
WhyWaitForever has written a web application to support web accounts and web customers. It is fast in that it uses individual XML documents to hold customer information. It is secure in that each XML document can be individually encrypted differently than any other. It is easy to incorporate with existing front and back office applications which usually use a secure relational database to hold information.
WhyWaitForever has written a web application to support store processing, catalogues, products, orders and purchases. It provides support for accessing third party payment card processing websites.
It is fast in that it uses individual XML documents to hold customer information. It is secure in that each XML document can be individually encrypted differently than any other. It is easy to incorporate with existing front and back office applications which usually use a secure relational database to hold information.
WhyWaitForever has written a web application to support hotel processing. This includes hotel search, room availability search, room selection, room booking and room cancellation. It provides support for accessing third party payment card processing websites or for capturing payment card information for the hotel reservation process. It is fast in that the application holds availability information in cache which means a hotel reservation search can support cross hotel searches including both price constrained searches and time constrained searches. A business customer would typically be time constrained. A leisure customer would typically have some flexibility as to when the booking can be made and is more price sensitive.
It is fast for registered customers in that it uses individual XML documents to hold preferences, reference information, previous room availability searches, previous room selections, bookings and cancellations. Holding preferences and references allows "quick book" and "repeat book" to only require the date to be input for the confirmed booking to be made. Preferences includes elements such as room type e.g. suite or double or single. Reference information includes elements such as loyalty card identifiers.
It is secure in that each XML document can be individually encrypted differently than any other. It is easy to incorporate with existing front and back office applications which usually use a secure relational database to hold information. A monitor task can be run to routinely exchange information between the hotel reservation application and the web application. A customer can cancel a web booking directly through the hotel call centre and within a few minutes the status of the booking is changed online.
The web application can connect directly to the hotel reservation such as the OPERA Enterprise Solution from Micros Fidelio. It can connect to the major global travel industry aggregators, distributors and switches such as Pegasus or WizCom. It can connect to specialist travel industry application suppliers such as Chauntry.
As the information is held in XML document format it is straight forward to exchange information with affiliates, partners and others using message exchange protocols such as SOAP, XML dialects such as the Open Travel Alliance and Really Simple Syndication or RDF Site Summary (RSS) feeds.
By building a "parallel" web booking application the "master" hotel reservation is better protected from the peaks of Internet traffic. If direct Internet access to the hotel reservation system is allowed volumes could overwhelm the hotel reservation system. A typical hotel reservation system connected to the Internet has a response time of seconds for a general availability request. The WhyWaitForever application has a response time of milliseconds.