AVERANE / OUR PROCESS
Every detail.
Every decision.
Moving you
forward.
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 STAGES FROM POSSIBILITY TO PRESENCE01 / 05BUILT WITH INTENTIONYour nextchapter.PURPOSE → CRAFT → CONFIDENCE01Strategy02Design03Development04Review05Launch
A clear direction.
Start with the people, the purpose, and the paths through your website.
Move through the process 01 — 05EXPLORE THIS STAGE →FIVE STAGES. ONE CONNECTED EXPERIENCE.Your input. Our craft. A shared direction.AVERANE / OUR PROCESS
Thoughtful at every stage.
Connected from the start.
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
Give every page a reason to exist.
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.
Before we move forwardThe structure and scope make sense to the people responsible for approving and maintaining the website.
Your audienceDiscoverUnderstandActPurpose connects every page.
AudienceStructureScopeStart with real visitor needs.
Identify who is arriving, what they need to understand, and what a useful next step looks like.
Audience groups, priority tasks, and success measures.
Include this stage in my discussion notesWhat we work towardDiscovery notes, audience priorities, sitemap, content inventory, integration requirements, and an agreed scope as applicable.
Where your input mattersBring your business goals, current website, brand materials, audience insight, constraints, and decision-makers.
How the stages connectThe agreed scope and content structure inform the design direction.
THE WORK BEHIND THE WORK
The blueprint behind the beautiful.
Start with the business
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.
Understand what already exists
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.
Define what good looks like
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
A process that thinks.
Not just a checklist.
Good projects encounter new information. Explore how we make a change understandable before it becomes a surprise.
A new integrationA change in contentA new deadlineBefore adding a new connection, understand the handoff.
01Clarify
What information needs to move, between which systems, and who will use the result?
02Consider
Review access, provider capabilities, data requirements, and failure behavior.
03Agree
Agree on scope, ownership, validation, and any effect on the delivery plan.
Content is part of the design, not a finishing layer.
01Clarify
Which pages and audiences does the new material affect?
02Consider
Review hierarchy, layouts, related links, content ownership, and mobile behavior.
03Agree
Confirm the revised content and review the affected pages before approval.
A useful plan makes the tradeoffs visible.
01Clarify
What must be ready by that date, and what makes the date important?
02Consider
Review dependencies, content readiness, approvals, and essential launch journeys.
03Agree
Agree on a realistic release scope and explicitly plan any later phase.
02 / Visual design
Make the brand feel considered.
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.
Before we move forwardThe approved direction explains how the experience should look, behave, and adapt across agreed screen sizes.
DESIGN SYSTEM / CONCEPTDistinctive.Consistent.
Considered.
Aa / Space / Rhythm
DirectionComponentsPrototypeEstablish a coherent visual direction.
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.
Include this stage in my discussion notesWhat we work towardAgreed visual direction, representative page designs, reusable patterns, and interaction guidance within scope.
Where your input mattersProvide approved brand assets, realistic content, useful references, and consolidated feedback from your decision-makers.
How the stages connectApproved 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
Design the moments between the screens.
Real content. Real constraints.
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.
A system with room for character
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.
Feedback that moves the work forward
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
Carry the intention into the build.
The platform should fit the work your website needs to do. We consider WordPress, Drupal, Shopify, Webflow, and relevant alternatives against your content, commerce, integrations, and team workflow.
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.
Before we move forwardThe agreed functionality works in the review environment and is ready for structured pre-launch checks.
<experience>
Designed with intent.Built to work.
</experience>
StructureBehaviorEditingPlatformBuildReviewChoose around the requirements.
Discuss editing needs, integrations, commerce, ownership, maintenance, and platform constraints.
A platform decision with practical tradeoffs and dependencies.
Include this stage in my discussion notesWhat we work towardA reviewable website, agreed CMS structures, implemented integrations, and documented build decisions.
Where your input mattersSupply approved content, access through agreed secure channels, integration contacts, and timely review of working features.
How the stages connectApproved 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
Care on both sides of the screen.
An editing experience your team can use
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.
Connected journeys, not isolated features
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.
Performance as a design decision
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
Beautiful is the beginning.
Ready goes deeper.
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.
0 / 5Choose the review areas you want to discuss.
Responsive layoutsLong headings, page stacking, image crops, and touch interactions across agreed screen sizes.Keyboard & feedbackNavigation, visible focus, relevant controls, form labels, and error or success feedback.Content & discoveryHeading structure, page titles, metadata, relevant links, and indexing or redirect requirements.Connected journeysForms, notifications, checkout where applicable, third-party handoffs, and useful failure behavior.Ownership & releaseAccess, publishing responsibilities, agreed recovery considerations, and post-release checks.04 / Pre-launch review
Look beyond the polished surface.
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.
Before we move forwardThe responsible people approve launch and understand the release, verification, and recovery arrangements.
01 Visitor journeys02 Technical foundations03 Release readinessTest. Learn. Refine. Verify.
ExperienceSearch & systemsReadinessFollow the important journeys.
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.
Include this stage in my discussion notesWhat we work towardAgreed QA checks, reviewed launch settings, issue resolution, and a coordinated deployment plan.
Where your input mattersComplete acceptance review, confirm final content and third-party settings, and identify the people available during launch.
How the stages connectApproved 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
The details deserve a second look.
Across screens and ways of navigating
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.
Protect the transition
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.
A shared release decision
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
Cross the finish line. Keep looking forward.
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.
Before we move forwardThe site is live, ownership is understood, and your team knows how to maintain content and request assistance.
LIVEIS A BEGINNING.
Release · Ownership · Evolution
ReleaseHandoverEvolveVerify the live experience.
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.
Include this stage in my discussion notesWhat we work towardLive verification, agreed handover materials, training, and a defined route for ongoing support.
Where your input mattersNominate website owners, participate in handover, and share feedback from the people using and maintaining the experience.
How the stages connectLive feedback helps shape future improvements, with new requirements scoped explicitly.
THE WORK BEHIND THE WORK
A handover with somewhere to go next.
Verify the public experience
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.
Make ownership understandable
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.
Improve with context
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
You bring the ambition.
We bring the questions worth asking.
Business context
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.
Considered delivery
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.
Clear decisions
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
Your priorities.
A clearer starting point.
Select stages above to build discussion notes. Your selected scenario is included. Nothing is submitted or saved by this tool.
Your process discussion notesCOPY MY NOTESCLEAR EXPECTATIONS FROM THE BEGINNING
Questions about the process.
How long does the process take?
Timing depends on scope, content readiness, integrations, review cycles, and dependencies. We establish milestones during planning and discuss changes when assumptions shift.
Will we be involved throughout?
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.
Do you only build on WordPress?
No. We choose an appropriate platform around your requirements, considering options such as WordPress, Drupal, Shopify, and Webflow. The decision includes editing, integrations, ownership, and long-term care.
Can you work with an existing website?
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.
Who provides the content?
Content responsibilities are defined in scope. We plan structure and requirements together; writing, photography, migration, and specialist review are agreed explicitly.
What if requirements change?
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.
Do you guarantee search rankings or business results?
No. We can build sound technical and content foundations within scope, but rankings and business outcomes depend on factors beyond website development.
What happens after launch?
We agree on handover, access, documentation, and ongoing responsibilities. Hosting, maintenance, support, and future improvements are scoped around your needs.
Additional process scenarios
02 / 05
A distinct character.
Turn that direction into a visual system, using real content and considered interactions.
03 / 05
Intention, made real.
Connect the approved experience to the platform and the people who will manage it.
04 / 05
Details, put to the test.
Review the important journeys, responsive behavior, and agreed launch requirements.
05 / 05
Ready for what’s next.
Coordinate the release, handover, and the next chapter of care.
Connect the information.
Organize services, evidence, practical details, and conversion paths. Account for existing URLs and content that needs to move.
Sitemap, page purposes, content relationships, and migration considerations.
Make the work explicit.
Agree on requirements, responsibilities, integrations, assumptions, and approval points before delivery begins.
An agreed scope, dependencies, content ownership, and project milestones.
Content is part of the design, not a finishing layer.
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.
A useful plan makes the tradeoffs visible.
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.
Design a system, not isolated screens.
Define reusable patterns while allowing important pages to have meaningful differences. Consider long titles, missing imagery, and varied content.
Reusable components, hierarchy, spacing, and content rules.
Explore the experience before the build.
Review navigation and important interactions. Consider mobile layouts, keyboard operation, feedback, and error states early.
Key prototypes, responsive behavior, and reviewed design decisions.
Build for the people on both sides.
Implement the visitor experience and the editing workflow. Use appropriate content models and keep repeated patterns consistent.
Working templates, components, content fields, and agreed connections.
Review real behavior with real content.
Check representative pages, controls, validation, empty states, and editing tasks. Keep sensitive production information out of development.
Reviewable implementation, issue tracking, and decisions documented.
Check what visitors cannot see.
Review indexability settings, metadata, redirects, sitemap needs, approved analytics, integrations, and applicable security configuration.
Technical launch checks and confirmed external dependencies.
Agree on the release conditions.
Confirm approval, deployment responsibilities, content readiness, backup/recovery arrangements, and a way to handle issues.
A launch checklist, named owners, and a release decision.
Give ownership a practical shape.
Explain agreed editing tasks, access roles, provider responsibilities, and how to request help.
Training, documentation, ownership, and support contacts within scope.
Prioritize what comes next.
Review useful feedback and available measurement. Discuss maintenance and improvements according to the agreed support arrangement.
A considered backlog and clearly scoped ongoing work.