All Work

Achareh / Independent UX Exploration

The next need
starts here.

What if the next thing someone needed felt like another reason to remember the same marketplace?

Growth Design / AI-assisted Prototyping

Independent UX concept. Not affiliated with Achareh. All bookings are simulated.

Try the Interactive Prototype

The starting point

Four needs, one marketplace.

I used Achareh for four unrelated needs: AC servicing, sofa cleaning, washing machine repair, and a car mechanic.

AC servicing
Keeping the air conditioning working.
Sofa cleaning
Refreshing the furniture.
Washing machine repair
Getting an appliance working again.
Car mechanic
Finding help with the car.

That personal experience inspired a retention hypothesis: the next reason to return may come from a different category. This is a starting observation, not user research or evidence of a wider behavior pattern.

The strategic question

The low-frequency
retention paradox.

A successful repair may remove the reason to return for months. Low repeat use in the same category could reflect a solved problem rather than a failed experience.

The hypothesis here is different: could someone who arrived for a repair remember the marketplace when they later need an unrelated service?

This is a product framing, not evidence that Achareh has a measured retention problem. Internal cohorts and customer research would be needed to establish that.

Three proposed interventions

A wider frame.
A clearer path. A quiet reminder.

Home: Service breadth awareness

Introduce varied everyday needs on the homepage, while preserving a familiar service catalog. Test whether people can name more categories without making the first task harder.

Search: Problem-first discovery

Offer problem-first examples beside search. Test whether users can reach the appropriate service confidently, including when no matching service is available.

Post-order: Recall for future needs

Preserve the order summary and primary actions, then add a gentle reminder of other categories. Test future recall, rather than pushing an immediate second purchase.

Interactive experience

Compare the starting point
with the proposal.

Compare Home, Search, and the post-order moment across the two versions. Look for how each helps you connect a new need to another service category.

Baseline

The comparison starting point, before the three proposed interventions. It is a concept reference, not a verified copy of the current Achareh product.

Proposed

The concept with service breadth on Home, problem-first Search, and a post-order reminder for future needs. These are hypotheses to test, not validated improvements.

Open the prototype as a full-screen page. On mobile, use this link to explore without nested scrolling.

Independent UX concept. Not affiliated with Achareh. All bookings are simulated.

Proposed validation strategy

Measure the next category,
not just the next tap.

180-day Cross-Category Repeat Rate.

Future validation metric — not a measured outcome.

The proportion of eligible customers who complete a service in a different category within 180 days of their index completed service.

The denominator includes all eligible customers with a full 180-day observation window, including those who never return. Use a consistent category mapping and exclude test accounts and cancelled services.

First: test comprehension and usability.

Ask participants to find help for the four scenarios, including an unfamiliar category. Observe matching accuracy, hesitation, recovery from no results, and completion of the simulated flow.

Then: test recall without prompting.

Compare baseline and proposed experiences with representative users. After a delay, introduce a different need and ask where they would start. Avoid naming Achareh in the task prompt.

Finally: evaluate in a real product.

With the platform’s participation, run a randomized rollout with a full observation window. Compare cross-category repeat rate, accounting for acquisition channel, seasonality, and exposure. Guard against reduced first-order completion, unwanted messaging, or lower satisfaction.

A simulated prototype cannot establish long-term behavior. No participant study, live experiment, or conversion improvement is claimed here.

Key strategic takeaway

The next need may be different.
The starting point can stay familiar.

For low-frequency services, retention does not have to mean repeating the same task. It can mean being remembered when the next, different need appears.

My contribution: retention framing, the three proposed interventions, and AI-assisted prototyping.

Explore independent UX studies