Satvic Movement

Satvic Movement

From a Wix page and Zoom links to an app users actually use

From a Wix page and Zoom links to an app users actually use

From a Wix page and Zoom links to an app users actually use

How we helped Satvic Movement validate their MVP before code, then ship an app that crossed 50,000+ users in the App Store.

How we helped Satvic Movement validate their MVP before code, then ship an app that crossed 50,000+ users in the App Store.

How we helped Satvic Movement validate their MVP before code, then ship an app that crossed 50,000+ users in the App Store.

Industry

Industry

HealthTech
Mobile app

Growth stage

Growth stage

Bootstrapped

Bootstrapped

Services

Services

UX Audit
Strategy & Discovery
User Testing
Product Design

Satvic Movement was running daily live workshops for 15,000 to 20,000 participants on a free Wix page with shared Zoom links, manually updated FAQs, and zero way to track who showed up. With plans to expand outside India, that workflow had a hard ceiling.

Satvic Movement was running daily live workshops for 15,000 to 20,000 participants on a free Wix page with shared Zoom links, manually updated FAQs, and zero way to track who showed up. With plans to expand outside India, that workflow had a hard ceiling.

Satvic Movement was running daily live workshops for 15,000 to 20,000 participants on a free Wix page with shared Zoom links, manually updated FAQs, and zero way to track who showed up. With plans to expand outside India, that workflow had a hard ceiling.

3 weeks

3 weeks

3 weeks

Time to prototype

Time to prototype

Time to prototype

5 users

5 users

5 users

Tested before any code

Tested before any code

Tested before any code

50K+

50K+

50K+

App store downloads

App store downloads

App store downloads

the situation

A workshop community held together by manual work and shared links

Satvic Movement is an online holistic health education platform founded by Subah and Harshvardhan. Their workshops run for 21 days at a stretch, with 15,000 to 20,000 participants joining live every day. The community is real, the demand is real, and the founders had spent years building it, mostly through their own social presence.

Satvic Movement is an online holistic health education platform founded by Subah and Harshvardhan. Their workshops run for 21 days at a stretch, with 15,000 to 20,000 participants joining live every day. The community is real, the demand is real, and the founders had spent years building it, mostly through their own social presence.

The setup behind the scenes was a different story. Workshop access lived on a free Wix page. The team manually updated FAQs and resources every day, for 21 days, for every cohort. Zoom links were shared, then re-shared, then shared again with people who hadn't paid. There was no way to track who completed what, no replay option for participants who missed a session, and no foundation that would scale to time zones outside India.

The setup behind the scenes was a different story. Workshop access lived on a free Wix page. The team manually updated FAQs and resources every day, for 21 days, for every cohort. Zoom links were shared, then re-shared, then shared again with people who hadn't paid. There was no way to track who completed what, no replay option for participants who missed a session, and no foundation that would scale to time zones outside India.

The decision was clear: build an app that gave participants a real product instead of a cobbled-together delivery system. The harder question was what that app actually needed to do, and what could wait. Three weeks isn't a long time to figure that out.

The decision was clear: build an app that gave participants a real product instead of a cobbled-together delivery system. The harder question was what that app actually needed to do, and what could wait. Three weeks isn't a long time to figure that out.

A Wix page doing the work of a product

No login, no access control, no progress tracking. Workshop links got shared with people who hadn't paid. The platform couldn't tell the team who was there.

21 days of manual updates per cohort

FAQs, resources, daily content. All updated by hand, every day, every workshop. Time the founders could have spent on growth went to logistics instead.

No replay, no flexibility, no global path

Live sessions only. Anyone in a different time zone couldn't really participate. The demand was there. The delivery model couldn't reach it.

A product to scope, not a problem to fix

No analytics, no in-app behaviour, no funnel data. Every assumption about what to build had to be tested with real workshop attendees, not pulled from product instinct.

the situation

the situation

Powerful features that nobody could find

Powerful features that nobody could find

Powerful features that nobody could find

Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.

Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.

Bliro is an on-device AI meeting assistant that integrates with all meeting tools without relying on bots. It's highly customizable, users can create different AI notes for various meetings and automatically send them to Salesforce, HubSpot, Slack, and more.

The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.

The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.

The product grew organically over time. Features were added in an 80/20 fashion, which left many powerful capabilities hidden in the platform. Users didn't know they existed or couldn't figure out how to use them.

In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.

In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.

In some cases, users couldn't even find their way around the platform after being personally onboarded. The design itself didn't look professional, and there was no unified design language across web, mobile, and desktop.

Product didn't match the team's ambition

A Wix page doing the work of a product

A Wix page doing the work of a product

Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.

No login, no access control, no progress tracking. Workshop links got shared with people who hadn't paid. The platform couldn't tell the team who was there.

No login, no access control, no progress tracking. Workshop links got shared with people who hadn't paid. The platform couldn't tell the team who was there.

Product didn't match the team's ambition

21 days of manual updates per cohort

21 days of manual updates per cohort

Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.

FAQs, resources, daily content. All updated by hand, every day, every workshop. Time the founders could have spent on growth went to logistics instead.

FAQs, resources, daily content. All updated by hand, every day, every workshop. Time the founders could have spent on growth went to logistics instead.

Product didn't match the team's ambition

No replay, no flexibility, no global path

No replay, no flexibility, no global path

Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.

Live sessions only. Anyone in a different time zone couldn't really participate. The demand was there. The delivery model couldn't reach it.

Live sessions only. Anyone in a different time zone couldn't really participate. The demand was there. The delivery model couldn't reach it.

Product didn't match the team's ambition

A product to scope, not a problem to fix

A product to scope, not a problem
to fix

Bliro had just raised a €2.8m seed round and needed a product that reflected the quality of the technology behind it.

No analytics, no in-app behaviour, no funnel data. Every assumption about what to build had to be tested with real workshop attendees, not pulled from product instinct.

No analytics, no in-app behaviour, no funnel data. Every assumption about what to build had to be tested with real workshop attendees, not pulled from product instinct.

"We had a free Wix page with link access for the workshop and we wanted to move to a password-protected login. We also had to manually change the FAQs and resources each day for 21 days. That was a lot of manual work"

"We had a free Wix page with link access for the workshop and we wanted to move to a password-protected login. We also had to manually change the FAQs and resources each day for 21 days. That was a lot of manual work"

"We had a free Wix page with link access for the workshop and we wanted to move to a password-protected login. We also had to manually change the FAQs and resources each day for 21 days. That was a lot of manual work"

Harshvardhan Saraf

Harshvardhan Saraf

Co-founder

Co-founder

the results

the results

Validated before code.
Adopted after launch.

Validated before code.
Adopted after launch.

Validated before code. Adopted after launch.

When the framework runs at the pre-launch stage, the work is done well before the launch metrics ever exist. Satvic walked into development with five user tests in the bank, a validated MVP, and a design system ready for build. After launch, users moved over.

When the framework runs at the pre-launch stage, the work is done well before the launch metrics ever exist. Satvic walked into development with five user tests in the bank, a validated MVP, and a design system ready for build. After launch, users moved over.

When the framework runs at the pre-launch stage, the work is done well before the launch metrics ever exist. Satvic walked into development with five user tests in the bank, a validated MVP, and a design system ready for build. After launch, users moved over.

3 weeks

3 weeks

3 weeks

Time to prototype

Time to prototype

Time to prototype

Validated MVP

Validated MVP

Validated MVP

Dev-ready assets

Dev-ready assets

Dev-ready assets

“Within two to three weeks we had a ready-to-develop prototype. Would've taken 45 to 60 days otherwise. It saved us a lot of time and made the experience enjoyable too.”

“Within two to three weeks we had a ready-to-develop prototype. Would've taken 45 to 60 days otherwise. It saved us a lot of time and made the experience enjoyable too.”

“Within two to three weeks we had a ready-to-develop prototype. Would've taken 45 to 60 days otherwise. It saved us a lot of time and made the experience enjoyable too.”

Harshvardhan Saraf

Harshvardhan Saraf

Co-founder

Co-founder

how we got there

how we got there

Three phases. Three weeks.
An MVP validated by 5, adopted by 50,000.

Three phases. Three weeks.
An MVP validated by 5, adopted by 50,000.

Three phases. Three weeks. An MVP validated by 5, adopted by 50,000.

diagnose

diagnose

diagnose

What does this community actually
need from a product?

What does this community actually
need from a product?

What does this community actually need from a product?

Workshops with the founders to map out the real product building blocks: target customers, competitors, vision, key metrics, the assumptions baked into the original idea. Mapped the workshop participant flow end-to-end and used that to define what an MVP would and wouldn't include.

Workshops with the founders to map out the real product building blocks: target customers, competitors, vision, key metrics, the assumptions baked into the original idea. Mapped the workshop participant flow end-to-end and used that to define what an MVP would and wouldn't include.

Workshops with the founders to map out the real product building blocks: target customers, competitors, vision, key metrics, the assumptions baked into the original idea. Mapped the workshop participant flow end-to-end and used that to define what an MVP would and wouldn't include.

define

define

define

What's the smallest version of this
that's worth testing?

What's the smallest version of this
that's worth testing?

What's the smallest version of this that's worth testing?

Using the Sprint method, we aligned the team on goals and constraints, sketched concepts, and built a prototype. Tested it with real customers, surfacing three specific behaviours the original platform didn't account for, including how customers update submissions and request multiple offers.

Using the Sprint method, we aligned the team on goals and constraints, sketched concepts, and built a prototype. Tested it with real customers, surfacing three specific behaviours the original platform didn't account for, including how customers update submissions and request multiple offers.

Using the Sprint method, we aligned the team on goals and constraints, sketched concepts, and built a prototype. Tested it with real customers, surfacing three specific behaviours the original platform didn't account for, including how customers update submissions and request multiple offers.

refine

refine

refine

What do engineers need to ship
without ambiguity?

What do engineers need to ship
without ambiguity?

What do engineers need to ship without ambiguity?

Took the validated direction into production design and a complete design system. Delivered every flow, every state, and every component the engineering team needed to rebuild the platform, and the foundation ProfiCircle would scale across new markets.

Took the validated direction into production design and a complete design system. Delivered every flow, every state, and every component the engineering team needed to rebuild the platform, and the foundation ProfiCircle would scale across new markets.

Took the validated direction into production design and a complete design system. Delivered every flow, every state, and every component the engineering team needed to rebuild the platform, and the foundation ProfiCircle would scale across new markets.

where we start

where we start

Let's find out where users get stuck, and what to fix first.

Let's find out where users get stuck,

and what to fix first.

Let's find out where users get stuck,

and what to fix first.

We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.

We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.

We'll look at how users experience your product, identify the biggest friction points, and outline what to fix first.