Sofetch
Sofetch was a beauty-services marketplace in Armenia connecting customers, technicians, and rentable salon space.
View original storyProduct snapshot
What it was
Sofetch planned to match beauty customers, technicians, and rentable salon space in one marketplace.
Who it was for
Problem / value
Make beauty services easier to book while helping technicians and salon owners use space more efficiently.
Core workflow
A customer books a beauty service, the technician delivers it, and salon or space capacity is coordinated through the platform.
Core dependency
Both sides of the marketplace had to transact repeatedly under local payment, tax, and offline-service constraints.
Product form
Pricing model
The planned model included flat transaction fees for customer bookings and payment tiers for stylists booking spaces; revenue was never reached because the product did not launch.
Competitors or alternatives
What happened
Summary
Sofetch was an Armenia beauty-services marketplace that closed before launch.
Outcome
Sofetch did not launch, made no revenue, and spent the grant plus about $10,000 in personal funds.
Core risk
Marketplace app built before transaction and local operating constraints were proven
Shutdown reason
COVID was the main shutdown trigger, but the founder also pointed to insufficient prototype testing before custom development.
Demand signal
The source shows positive conversations with stylists, salon owners, customers, and influencers, but Sofetch did not launch or record transactions before COVID changed the market.
Distribution issue
The launch depended on Armenian beauty influencers and local service behavior, while payment processing, tax handling, cash habits, and COVID restrictions all made the transaction flow fragile.
Timeline
- idea formed after observing salon scheduling and space-utilization problems
- team hired an engineer early
- worked through legal, payment, and tax constraints
- won a $25,000 Neruzh innovation grant
- prepared launch with Armenian beauty influencers
- COVID disrupted in-person beauty services
- closed after repeated pivots failed
Before you build
Why it matters
Beauty-service marketplaces depend on local habits, payment rails, taxes, offline capacity, and both-sided commitment. Positive feedback does not prove marketplace liquidity.
Primary check
Validate real two-sided transactions, local payment constraints, and offline service resilience before funding a custom marketplace app.
Checklist
- Can you run 10 paid bookings manually?
- Can technicians and space providers repeat the workflow without founder intervention?
- Can payments and taxes work in the target market?
- Can the model survive a temporary offline-service slowdown?
- How many real bookings have happened without custom software?
- Do customers, providers, and space owners all benefit from the same transaction?
- Who handles payment, taxes, refunds, and cancellations?
- What happens if in-person demand or capacity suddenly changes?
Relevant if
- You are building a local services marketplace.
- Your product needs customers and providers to coordinate offline.
- Your market has local payment, tax, or cash-behavior constraints.
Less relevant if
- Your product is single-sided software with no offline fulfillment.
- You already have repeated paid transactions before building.
Pre-build tests
- Run concierge bookings with a small group of technicians and salon spaces.
- Collect payment before building the marketplace app.
- Document every failed booking reason before hiring developers.
Transferable lessons
- Prototype marketplace behavior manually or with no-code first.
- Validate both sides with completed transactions, not compliments.
- Test local payment and tax constraints before designing the workflow.
- Plan for external shocks when the product depends on in-person services.
If you build this today
Use no-code or concierge bookings with a few technicians and spaces first, collect real paid transactions, and only build custom software after both sides repeat the workflow.