HAI VAI
HAI VAI designs coworking for two simultaneous roles: parents working and children building their own world within supported space.
01 · Direction
The site separates desk, child room, caregiver team, and pricing, using schedule and safeguarding instead of generic balance claims.
The brief is to make a membership and community platform that creates desire and helps visitors decide without assembling information from several places. HAI VAI is therefore treated as a content and conversion system, not a collection of attractive screens.
Families choose child age, work shift, and days, seeing capacity, ratio, meals, and total before a trial.
“For HAI VAI, aesthetics earn their place only when they make people, rules, activity calendar, place, and community outcomes easier to see, understand, and act on.”
- Format
- membership and community platform concept
- Audience
- Newcomers assessing culture, schedule, and fit before joining
- Primary proof
- People, rules, activity calendar, place, and community outcomes
- Primary action
- See the calendar, choose a programme, and become a member
02 · Onemember
Onemember should tell visitors what is worth remembering.
Onemember extends the hero promise into a situation a visitor can picture. For HAI VAI, the content needs to show what happens, why the detail differs, and which information matters enough to continue exploring.
In production, this module should offer a short scanning layer, deeper verification for people who need it, and a clear route forward. That structure preserves editorial pace without sacrificing search discovery or accessibility.
Principle: every artboard must add a reason to believe or a reason to act.
03 · Community
Community is not filler; it is evidence.
Community is an evidence layer for HAI VAI's positioning. Instead of adding adjectives, the artboard uses people, rules, activity calendar, place, and community outcomes to turn a visual impression into a reason visitors can remember and compare.
Every claim should carry a source, scope, and update date where relevant. That becomes essential when a concept moves towards production: trust comes from verifiable detail, not the volume of brand language.
Principle: every artboard must add a reason to believe or a reason to act.
04 · closing invitation
Place closing invitation at the right moment in the decision.
At the centre of the journey, closing invitation classifies choices and reduces cognitive load. Primary information should scan in seconds; secondary detail opens after visitors know what they care about.
Headings, image captions, and contextual links also help search engines understand the page without keyword repetition. SEO is the outcome of clear information, not a text layer added after design.
Principle: every artboard must add a reason to believe or a reason to act.
Design language
Recognise HAI VAI before the logo has to appear.
The design language follows an asymmetric editorial treatment, the concept palette, and its native image rhythm. The goal is not novelty in every section but a small set of rules strong enough to support new content.
- 01
Contrast with a job
Accent colour is reserved for attention and primary action; background, type, and imagery stay stable so HAI VAI never becomes noise.
- 02
An industry-specific rhythm
Image ratio, paragraph length, and headline placement follow how people actually explore a membership and community platform, not a universal portfolio template.
- 03
Evidence before invitation
People, rules, activity calendar, place, and community outcomes arrives before the CTA, making action a reasonable consequence of the story rather than an interruption.
Colour system
#f8f0e8
#e8c8a0
#c09868
#a06828
#406890
Colours come directly from HAI VAI's art direction. Production should validate WCAG contrast for copy, interaction states, and charts instead of assigning every colour equal weight.
Production direction
Turn the concept into a system with content, data, and clear ownership.
The visual design is an opening hypothesis. A live version must be tested with real content, real behaviour, and the technical constraints of the team that will maintain it.
- 01
Inventory content and data
Identify the source, update cadence, and approver for people, rules, activity calendar, place, and community outcomes before finalising page architecture.
- 02
Prototype the primary flow
Test “See the calendar, choose a programme, and become a member” on real devices, including missing data, failure, and interrupted-return states.
- 03
Performance and access
Serve images at display size, preserve semantic HTML, support keyboard use, and respect reduced motion so the experience does not require powerful hardware.
- 04
Measure what matters
Track calendar views, trial registrations, and returning members, exclude internal traffic, and agree event definitions before interpreting results.
Frequently asked questions
Questions to resolve before producing HAI VAI.
- Who is HAI VAI designed for?
- Newcomers assessing culture, schedule, and fit before joining. Every layout decision serves one primary action: see the calendar, choose a programme, and become a member.
- Why does this detail page differ from the other concepts?
- The asymmetric editorial treatment follows how people explore a membership and community platform, its information density, and its particular visual language.
- Could the concept become a real website?
- Yes, after replacing assumptions with real content, data, legal requirements, and the organisation's “See the calendar, choose a programme, and become a member” process.
- How should effectiveness be measured?
- A useful starting set is calendar views, trial registrations, and returning members; final targets must follow the real operating model.
Continue exploring
More concepts in the field, each with a different answer.
From concept to product
Have an idea that needs to become a real website?
ToanKhonTech can shape positioning, content architecture, conversion flow, and an interface system for your actual context—without copying a fictional concept wholesale.