Tell the story with care.
Good storytelling helps people understand the work without reducing people to a campaign asset. Plan how stories and imagery are approved, who can grant permission, and how content is reviewed as circumstances change.
AVERANE / NONPROFIT
Make the purpose clear.
Make participation possible.
Your website brings together people with very different reasons to care. We connect the story, the programs, and the practical next steps—so visitors can understand your work and find their place in it.
EXPLORE THE HUMAN SIDEConnect the mission with credible context, then make the giving journey understandable.
ONE MISSION. DIFFERENT REASONS TO VISIT.
A first-time visitor needs a clear explanation of the organization, its work, and the people or places it serves. Mission statements gain meaning when the surrounding content makes them tangible.
→︎02A person looking for a program may need eligibility, availability, location, or contact details quickly. Practical information should not be hidden behind a fundraising message.
→︎03Donating, volunteering, and partnering are different commitments. Explain each route, set expectations, and make it clear when the next step happens in another system.
→︎NONPROFIT / PURPOSE INTO EXPERIENCE
Your website connects people with the work you do. Some arrive looking for support. Others want to give, volunteer, or understand your mission. Averane helps shape those different needs into a clear, considered digital experience.
Explore the decisions behind the design, then build a starting brief around your organization’s priorities.
Explore all industriesTRY THE EXPERIENCE FROM THEIR SIDE
Move through a visitor’s journey. See how the information changes from a first question to a useful next step.
Make the mission tangible with clear context and approved stories.
01 / MISSION & STORY
Your mission deserves more than a prominent statement. We connect purpose, programs, and the people behind the organization into a clear story—one that helps visitors understand the work before asking them to act.
We consider the questions a first-time visitor brings, the information a returning supporter needs, and the content your team can maintain. Stories and evidence should be approved, relevant, and presented with care.
EXPLORE THE EXPERIENCE / MISSION & STORY
Explain whom you serve, what you do, and why it matters in language your audience can understand.
Purpose → audience → message
Original planning concept. No information is submitted and no client results are implied.
Good storytelling helps people understand the work without reducing people to a campaign asset. Plan how stories and imagery are approved, who can grant permission, and how content is reviewed as circumstances change.
Reports, updates, and outcomes should be accurate, appropriately contextualized, and maintained by a clear owner. The website should make useful evidence easier to find without overstating what it demonstrates.
DETAILS WE WORK THROUGH TOGETHER
Lead with what the organization does, who it serves, and why that work matters. Connect broad purpose to specific programs rather than asking the visitor to decode internal terminology.
Define how stories and images are selected, approved, and maintained. Consider consent, context, and whether material should be updated or removed when circumstances change.
Present approved reports, leadership information, partners, and useful outcomes with context. Distinguish documented results from ambitions and avoid unsupported claims.
02 / PROGRAM DISCOVERY
People looking for a program should not need to understand your organizational chart. We plan navigation and program content around their needs, with useful explanations of services, requirements, and next steps.
A useful program page explains what is offered, whom it serves, and how to proceed. Content ownership matters too: information about availability, eligibility, or contact routes needs a reliable review process.
EXPLORE THE EXPERIENCE / PROGRAM DISCOVERY
Discuss the ways your audiences look for support and organize the information around those tasks.
Audience needs → categories → program pages
Original planning concept. No information is submitted and no client results are implied.
Clarify who the program serves, what it offers, any eligibility requirements, and how to make contact. Use language the audience recognizes, with useful alternatives when online information does not answer the question.
Program availability, contact details, and locations can change. Reusable content structures and review responsibilities help prevent different pages from giving conflicting information.
DETAILS WE WORK THROUGH TOGETHER
Use audience needs, recognizable topics, and practical filters where useful. The right structure depends on the scale of the program list and how people describe their needs.
Explain eligibility, cost if applicable, location, accessibility information, and any prerequisites. Identify who answers questions that cannot be resolved on the page.
Clarify whether the next step is an enquiry, referral, registration, or an external system. Explain what happens after contact and how your team handles incoming interest.
03 / GIVING JOURNEYS
A donation journey connects the story on your website with the tools and processes behind it. We help plan a clear handoff, appropriate information, and useful feedback around the donation platform your organization chooses.
We discuss one-time and recurring giving requirements, campaign information, provider capabilities, and the team’s workflow. Payment processing, receipts, and donor records depend on the selected systems and agreed integrations.
EXPLORE THE EXPERIENCE / GIVING JOURNEYS
No payment is collected in this illustration.
Present approved campaign information and the available giving routes. Any statements about how funds are used should come from your organization.
Campaign context → options → giving route
Original planning concept. No information is submitted and no client results are implied.
Consider the handoff to the donation provider, available giving options, confirmation, receipts, and where supporters can ask questions. An attractive donation button is only one part of that experience.
Donation platforms, CRM tools, email services, and payment providers have their own settings and owners. Confirm what information is collected and where it goes before assuming the integrations are connected.
DETAILS WE WORK THROUGH TOGETHER
Explain the purpose of the giving journey and distinguish available options, such as one-time or recurring support, only where the organization and provider support them.
Consider branding continuity, mobile behavior, error feedback, confirmations, and receipt responsibility. Validate the agreed journey with the relevant provider rather than assuming the website button completes it.
Map which organization and service handle supporter information. Discuss access, consent, privacy requirements, and reporting needs with the responsible people before implementation.
04 / VOLUNTEERS & PARTNERS
Volunteers and partners need more than an invitation. They need to understand the opportunity, what is expected, and how the organization will respond. We plan participation paths that serve both the visitor and the team receiving the inquiry.
The right workflow may involve opportunity listings, event information, expressions of interest, or an existing volunteer-management system. We define the requirements before choosing the form or tool.
EXPLORE THE EXPERIENCE / VOLUNTEERS & PARTNERS
Organize approved opportunities around the information people need to decide whether to participate.
Role → location or format → availability
Original planning concept. No information is submitted and no client results are implied.
Describe the role, time commitment, location, requirements, and application process where relevant. Visitors should understand what expressing interest means and whether a placement is confirmed or subject to review.
Think through form fields, routing, notifications, and follow-up ownership. Collect information appropriate to the initial step and use an agreed process for sensitive documents or checks.
DETAILS WE WORK THROUGH TOGETHER
Useful opportunity pages explain the work, location, time expectations, and relevant requirements. Differentiate an expression of interest from an accepted placement.
Identify who receives an application or enquiry, what they need to respond, and how the next step is communicated. Avoid collecting sensitive material prematurely.
Corporate partners, community groups, and individual volunteers may need different information and contact routes. Give each a meaningful starting point without fragmenting the mission.
05 / CONTENT & STEWARDSHIP
Programs evolve, campaigns change, and new stories become available. We shape the editing experience around the people maintaining the website, with reusable content structures and a practical approach to review.
Content roles, publishing responsibilities, and platform choices should reflect your team’s capacity. We discuss WordPress, WordPress VIP, WooCommerce, Shopify, Drupal, Webflow, Astro, and Next.js in context rather than choosing a platform from the industry label alone.
EXPLORE THE EXPERIENCE / CONTENT & STEWARDSHIP
Identify the content types your team updates regularly and the fields or layouts that help keep them consistent.
Content types → reusable structure → editing
Original planning concept. No information is submitted and no client results are implied.
Build around the updates your team makes repeatedly: programs, stories, events, contacts, and resources. Useful fields and reusable patterns can make those tasks clearer while preserving the intended design.
Discuss permissions, approval responsibilities, content dates, and handover. A maintainable website includes an understandable publishing process, not just an editable page.
DETAILS WE WORK THROUGH TOGETHER
Programs, locations, stories, events, and resources may benefit from structured fields and relationships. Agree which content types and workflows are practical for the team.
Define drafting, review, publishing, and archiving responsibilities. Consider how a change to a shared contact or program detail should reach every relevant page.
Plan training around actual editing tasks and document the agreed ownership of accounts and services. Ongoing maintenance and support should have a clear scope.
06 / ACCESS & TRUST
Your audiences may arrive with different devices, abilities, languages, and levels of familiarity. We bring those needs into the planning conversation alongside information handling and the systems that support the experience.
Readable layouts, keyboard behavior, meaningful labels, and understandable feedback are part of a considered experience. Specific accessibility, privacy, security, or reporting requirements must be defined and agreed for the project.
EXPLORE THE EXPERIENCE / ACCESS & TRUST
Plan clear headings, meaningful controls, visible focus, and relevant device checks. Agree on the testing approach and any formal requirements.
Audience needs → interaction design → agreed checks
Original planning concept. No information is submitted and no client results are implied.
Readable content, keyboard interaction, focus visibility, clear form labels, and responsive layouts belong in the design conversation. Specific accessibility requirements and specialist testing should be agreed for the project.
Identify sensitive workflows and decide which systems should handle them. Privacy, consent, security responsibilities, and third-party tools need review in the context of the information actually collected.
DETAILS WE WORK THROUGH TOGETHER
Consider headings, meaningful links, keyboard navigation, focus, forms, contrast, and content clarity. Establish the required review scope, including specialist assessment where applicable.
Review important journeys on smaller screens, including donation handoffs and longer program information. Media, fonts, and third-party tools all influence the practical experience.
Inventory donation, email, CRM, registration, and other tools. Clarify integration capabilities, access, error handling, and provider responsibilities before committing to a solution.
A CONNECTED APPROACH
Give service users, supporters, volunteers, and partners relevant paths rather than asking one page to do everything.
Connect content, tools, and publishing responsibilities to the people who will use and maintain the website.
Discuss hosting responsibilities, maintenance, handover, and future improvements so the organization knows what comes next.
QUESTIONS WORTH ASKING
We can discuss a review of the current website, content, platform, and priorities to determine whether targeted improvements or a broader redesign would be useful.
We review the tools, provider capabilities, access, and intended workflow before confirming the integration approach and scope.
We plan content structures and editing responsibilities around your team and the chosen platform. Training and documentation are discussed as part of the build.
Content structure and ownership are part of the planning conversation. Writing, migration, and ongoing editorial work should be defined in the project scope.
No. We work on clarity, usability, and the agreed experience. Fundraising outcomes depend on many factors beyond the website.
We discuss audience needs, relevant requirements, and the agreed testing approach before the build. Any formal standard or review needs to be included in the scope.
BRING YOUR MISSION INTO THE CONVERSATION
Your choices are collected here. Add context about your organization and copy the brief for a conversation with Averane.
Nothing is submitted or stored. Copy your brief before leaving this page.
DISCUSS YOUR WEBSITEYOUR PURPOSE. A CONSIDERED DIGITAL EXPERIENCE.
Tell us about your organization, the people you serve, and what your website needs to make possible.
BOOK A CONSULTATION