Coveo for Sitecore out of the box provides a rich suite of Sitecore renderings that can achieve most business search objectives. The configuration options enable users to achieve sophisticated search interfaces extremely fast. There are many quick wins available in Coveo for Sitecore but some that are less quick, and can be necessarily complex. Depending on budget it can be important to consider these before committing to a design that may involve the harder yards.
*The first 15 minutes of this presentation will demonstrate the out of the box renderings and an example page consuming data from a complex demo site with large volumes of content. Showing how you could achieve a decent search experience in 15 minutes solely in content if willing to constrain requirements and design to fit in with out of the box features.
*The second 15 minutes will show how Sitecore Content Search concepts have been applied in Coveo for Sitecore. Moving on to a more complex summary on how to build custom versions of existing Coveo JS components, using data attributes to make the configurable in Sitecore. Then touching on the extreme complexity behind building custom Coveo JS components using Underscore JS, as well as how to integrate these components into Sitecore renderings. Throughout this section, used as a comparison against the out of the box renderings, I will explain how development effort can increase exponentially.
*The third 15 minutes will focus on the admin interfaces used to configure Coveo for Sitecore. In the process it will become evident how if expecting limited developer effort to cover the implementation then there are many complexities aside from the basic integration of the search interfaces that someone else may need to own. I'll also cover analytics and reporting in this section.

The overall point of this presentation is to outline options for using Coveo for Sitecore and present an impartial opinion on certain realities which mean it's important developers influence the design. Or else that designers and business stakeholders have an understanding of what effort will be involved when forming their requirements. If the cost of Coveo as a product is a large proportion of the project's budget assigned to the search feature, thus expecting minimal development effort, then the design and requirements should account for this else it may be unrealistic to achieve within budget. Developer's experience with Coveo may also need consideration as beyond the out of the box renderings there is a learning curve involved in implementation. Conversely, if the search feature is the most important part of the website and budget constraints permit significant development time from an experienced team then there is an extremely rich toolkit which can be customised to meet any design.

I will be creating a blog series, supported by videos, that I'll release shortly before SUGCON. The aim of which will be to give further information from an impartial perspective to anyone interested in using Coveo for Sitecore. This should provide next steps for attendees interested in exploring further.