Summary of business requirementsDiscuss needsDiscuss the frameworkFramework for business needs
Use the page outline, materials, and measurements to begin discussing business needs.
Example of planning materials
Examples of materials you can prepare to clarify the context of the project.
Summary of business requirementsDiscuss needsDiscuss the framework
Have material to discuss together?
Tell us about ideas or materials you want to develop into digital work.
Discuss needs
From framework to scope
About the Oura framework
An outline helps you explain your website's goals, customers, offerings, and content needs. The final design is adjusted through research and project discussions.
From framework to real work
Start with concrete needs: customer information, service structure, evidence, and key actions. The framework is used as discussion material and is developed according to the business context.
How to discuss needs
Select the need you want to discuss. Complete the available business materials, determine any unclear information, then review priorities with the Oura team.
Questions about Oura services
The Oura Works catalog offers page structures to help you discuss your website needs. Start with a relevant example, then adapt it to your customers, services, and operations.
Review the page's purpose, information buyers are looking for, navigation, CTAs, and integration needs. Layout choices need to support visitor tasks as well as how your team organizes content.
Catalogs help with planning conversations, but lead time and business outcomes depend on scope, material readiness, and the review process. Layout examples are not evidence of performance improvements.
Customizations can be discussed according to brand identity, user needs, and project scope. The choice of template, CMS, or special development is determined after the needs and management of the website are reviewed.
The example becomes material for discussing page structure. Colors, typography, components, and copy are adjusted to available brand guidelines and reviewed before implementation.
Forms, payments, CRM, or database needs are examined based on functionality, access, API, provider costs, and maintenance responsibilities. Integrations are only included if listed in the agreed scope.
Select an example that helps explain your needs, then contact Oura via the contact page. Prepare the business objectives, users, available materials, and functions you want to cover.
The team reviews this information to develop priorities, work results, access needs, and review stages. Additional needs are noted so they can be assessed together.
The proposal describes the scope, estimated schedule, service and third-party costs, and assumptions that need to be confirmed. The time for preparing the offer is agreed based on the completeness of the information and the complexity of the needs.
Launch estimates are determined once the number of pages, material readiness, functionality, integration, and approval process are known. There is no duration that applies to the entire website.
Work may include information architecture, copy, design, development, and review as agreed in the proposal. Performance is assessed on relevant pages under defined conditions; tool scores do not guarantee business results.
Schedules, dependencies, review responsibilities, and handover criteria are recorded in the project agreement. Specific SLAs only apply if targets and service limits have been agreed upon.