AVERANE / OUR PROCESS
Great work is intentional.
So is the way we get there.
From the first conversation to the live experience, we bring strategy, design, and development into one connected process. You see the thinking, understand the decisions, and help shape what comes next.
EXPLORE THE FIVE STAGESStart with the people, the purpose, and the paths through your website.
AVERANE / OUR PROCESS
A website is a sequence of decisions that need to work together. We bring strategy, design, development, and delivery into one considered process—with clear responsibilities, useful review points, and attention to the details that shape everyday use.
Explore the five stages below. Each interactive view shows a different decision, the work behind it, and what we aim to clarify before moving forward. Specific deliverables and review cycles are agreed in your project scope.
01 / Strategy & sitemap
Before we design a screen, we work to understand the business behind it. Your audience, goals, content, and operational needs shape the structure—not the other way around.
We examine the existing experience, identify important visitor tasks, and map the routes that support them. A sitemap becomes a shared plan for what belongs, how it connects, and what needs to be created.
The structure and scope make sense to the people responsible for approving and maintaining the website.
Identify who is arriving, what they need to understand, and what a useful next step looks like.
Audience groups, priority tasks, and success measures.
Discovery notes, audience priorities, sitemap, content inventory, integration requirements, and an agreed scope as applicable.
Bring your business goals, current website, brand materials, audience insight, constraints, and decision-makers.
The agreed scope and content structure inform the design direction.
THE WORK BEHIND THE WORK
We connect commercial goals with useful visitor actions: finding the right service, evaluating a product, making an enquiry, or completing a task. Those priorities guide the structure rather than becoming a list added after design.
Content, URLs, forms, integrations, and editing workflows all carry context. We identify what to retain, retire, improve, or move, and discuss the practical implications before a rebuild begins.
We agree on requirements and review criteria alongside assumptions, dependencies, and responsibilities. A shared definition of the work makes feedback more specific and changes easier to assess.
STEP INSIDE THE DECISION
Good projects encounter new information. Explore how we make a change understandable before it becomes a surprise.
What information needs to move, between which systems, and who will use the result?
Review access, provider capabilities, data requirements, and failure behavior.
Agree on scope, ownership, validation, and any effect on the delivery plan.
Which pages and audiences does the new material affect?
Review hierarchy, layouts, related links, content ownership, and mobile behavior.
Confirm the revised content and review the affected pages before approval.
What must be ready by that date, and what makes the date important?
Review dependencies, content readiness, approvals, and essential launch journeys.
Agree on a realistic release scope and explicitly plan any later phase.
02 / Visual design
A distinctive website needs more than a strong first screen. We shape typography, hierarchy, imagery, spacing, and interaction into a system that feels like your business at every point.
We explore layouts with representative content and use tools such as Figma to make the direction tangible. Key page types and device behaviors help reveal the details that a single desktop mockup cannot.
The approved direction explains how the experience should look, behave, and adapt across agreed screen sizes.
Discuss how the website should feel and why. Ground creative decisions in the audience, message, and brand.
Typography, color, image direction, and representative page concepts.
Agreed visual direction, representative page designs, reusable patterns, and interaction guidance within scope.
Provide approved brand assets, realistic content, useful references, and consolidated feedback from your decision-makers.
Approved decisions from the previous stage guide the work. New findings are discussed, documented, and reflected in affected plans before moving forward.
THE WORK BEHIND THE WORK
We explore representative content rather than relying entirely on perfect placeholders. Long headings, varied images, empty states, and practical calls to action help reveal where a layout needs to be more resilient.
Typography, spacing, color, components, and motion create continuity. Important pages can still have their own emphasis. Consistency should make the experience recognizable without making every screen identical.
We ask what a design helps someone understand or do, and compare feedback with the agreed direction. Consolidated comments and clear approvals help resolve conflicting preferences before development.
The reveal is a moment.
The care is continuous.
03 / Website development
The platform should fit the work your website needs to do. We consider WordPress, WordPress VIP, WooCommerce, Shopify, Drupal, Webflow, Astro, and Next.js against your content, commerce, integrations, and team workflows.
We translate the approved design into reusable components and practical editing tools. Navigation, forms, content relationships, and integrations are reviewed as connected journeys—not just individual features.
The agreed functionality works in the review environment and is ready for structured pre-launch checks.
Discuss editing needs, integrations, commerce, ownership, maintenance, and platform constraints.
A platform decision with practical tradeoffs and dependencies.
A reviewable website, agreed CMS structures, implemented integrations, and documented build decisions.
Supply approved content, access through agreed secure channels, integration contacts, and timely review of working features.
Approved decisions from the previous stage guide the work. New findings are discussed, documented, and reflected in affected plans before moving forward.
THE WORK BEHIND THE WORK
We plan reusable content and page patterns around the people maintaining the website. Appropriate permissions, clear fields, and practical guidance help protect the design as content changes.
A form includes its labels, validation, confirmation, destination, and failure behavior. An integration includes provider ownership and access. We examine the complete agreed journey rather than stopping at the visible interface.
Image treatment, fonts, scripts, media, and third-party tools affect the experience. We discuss those tradeoffs and review relevant performance conditions instead of assuming a single score tells the whole story.
MOVE BEYOND THE SCREENSHOT
A finished-looking page is not the same as a reviewed experience. Explore the areas we discuss when defining a project’s quality checks.
This is a planning exercise—not a test of your website or a certification. Review coverage is agreed for each project.
Choose the review areas you want to discuss.
04 / Pre-launch review
A launch review follows the paths people will actually take. We bring content, usability, technical checks, and operational readiness together before the website goes live.
The test plan reflects the agreed scope. We consider desktop, tablet, and mobile behavior; keyboard use; forms and handoffs; search fundamentals; performance; and who owns the site after release.
The responsible people approve launch and understand the release, verification, and recovery arrangements.
Review navigation, responsive layouts, form messages, key actions, and relevant accessibility behavior. Record issues and repeat affected checks after fixes.
A practical test record and resolution of agreed launch blockers.
Agreed QA checks, reviewed launch settings, issue resolution, and a coordinated deployment plan.
Complete acceptance review, confirm final content and third-party settings, and identify the people available during launch.
Approved decisions from the previous stage guide the work. New findings are discussed, documented, and reflected in affected plans before moving forward.
THE WORK BEHIND THE WORK
We review agreed breakpoints and important interactions, including content wrapping, keyboard navigation, focus visibility, and form feedback. Accessibility requirements and any specialist assessment are defined in scope.
For a replacement website, we consider URL changes, redirects, content migration, indexing settings, and relevant measurement. Account access and provider dependencies are confirmed as part of release planning.
Findings are recorded and prioritized. The team understands unresolved items, responsibilities, and the release plan before proceeding. Testing reduces uncertainty; it does not justify claiming that every possible issue has been eliminated.
05 / Launch & ongoing care
Going live is a transition into everyday use. We coordinate the agreed release, verify the live experience, and help your team understand the website they now own.
We discuss practical handover, access, documentation, and support responsibilities. Future improvements should respond to real needs and evidence, with scope and priorities made clear.
The site is live, ownership is understood, and your team knows how to maintain content and request assistance.
Review critical pages, forms, redirects, integrations, and relevant tracking after deployment. Confirm the intended destination and behavior.
Post-launch verification and a clear route for reporting issues.
Live verification, agreed handover materials, training, and a defined route for ongoing support.
Nominate website owners, participate in handover, and share feedback from the people using and maintaining the experience.
Live feedback helps shape future improvements, with new requirements scoped explicitly.
THE WORK BEHIND THE WORK
The live environment can differ from a preview. We check agreed critical journeys after release, including relevant forms, links, redirects, and integrations, and communicate the outcome.
We clarify domain, platform, hosting, and connected-service responsibilities. The agreed handover explains who can change content, where documentation lives, and how to request help.
Visitor feedback, team experience, and available analytics inform the next conversation. We distinguish routine support from new work and agree priorities, scope, and review criteria before further development.
A COLLABORATION WITH CLARITY
Your knowledge of the audience, offer, operations, and constraints shapes the work. Approved content and timely, consolidated feedback help decisions reflect the people the website serves.
We translate requirements into a connected experience, explain relevant tradeoffs, and make review points understandable. New findings and changes should be discussed before expectations drift.
Named decision-makers, agreed milestones, and a documented scope give the project a practical structure. We clarify what is approved, what remains open, and what needs attention next.
TURN EXPLORATION INTO A USEFUL CONVERSATION
Select stages above to build discussion notes. Your selected scenario is included. Nothing is submitted or saved by this tool.
CLEAR EXPECTATIONS FROM THE BEGINNING
Timing depends on scope, content readiness, integrations, review cycles, and dependencies. We establish milestones during planning and discuss changes when assumptions shift.
Yes. Your insight and approvals help shape the work. We identify review points and ask for consolidated feedback so decisions are clear and the project can move forward.
No. We consider WordPress, WordPress VIP, WooCommerce, Shopify, Drupal, Webflow, Astro, and Next.js around your requirements. The decision includes editing, integrations, ownership, and long-term care.
Yes. We can review what is working and what needs to change. The outcome may be focused improvements, a migration, or a broader redesign rather than an automatic rebuild.
Content responsibilities are defined in scope. We plan structure and requirements together; writing, photography, migration, and specialist review are agreed explicitly.
We discuss the change, its dependencies, and the impact on scope, timing, and cost before proceeding. Clear decisions protect both the intended experience and the delivery plan.
No. We can build sound technical and content foundations within scope, but rankings and business outcomes depend on factors beyond website development.
We agree on handover, access, documentation, and ongoing responsibilities. Hosting, maintenance, support, and future improvements are scoped around your needs.
