Start with a signal. Deepen with value.
Presence, relevant demand and direct response gave smaller sellers a practical first step.
Mazzaneh · operating record
A market system, built from reality.
The historical operating record connects the original operating context, team-built MVP, product system and evidence boundaries.
One ecosystem. Multiple ways to begin.
Useful before complete. Connected by design.
For buyers, Mazzaneh made intent visible—whether explicit, local or discovery-led.
For businesses, it created a path to respond before full digitization became a requirement.
Signals become useful learning.
Connected interaction data helped turn market activity into operational understanding—without making surveillance the model.
Recommended review route
See the whole system. In the right order.
Five focused stops keep market context, product mechanics and evidence confidence separate and easy to review.
01Context
Origin
The market conditions and operating constraints that shaped the system.
Open ↗02SystemArchitecture
How intent moves through business response, interaction and learning.
Open ↗03ExperienceBusiness
A low-friction path for sellers to become present, useful and reachable.
Open ↗04RoutesSelling
The practical routes used by individuals and businesses to sell.
Open ↗05ProductsModules
Begir, Radar, Pulino, Board, Analytics and connected product surfaces.
Open ↗Complete Phase 1 directory
Active Phase 1 routes. One connected entry.
This directory exposes the active Phase 1 destinations directly from the landing page. Supporting source packages remain embedded assets—not competing public routes.
Orientation · Commerce · Core modules · Review
01Orientation
Product Hub
The product-level router and ecosystem orientation.
Open ↗02OrientationOperating Record
The historical company/MVP operating record.
Open ↗03OrientationOrigin
The constraints, market context and design causality.
Open ↗04OrientationArchitecture
The connected Phase 1 system view.
Open ↗05CommerceBusiness
Seller presence, response, participation and value architecture.
Open ↗06CommerceSelling
Individual, business and assisted selling routes.
Open ↗07CommerceMonetization
Historical and modeled revenue architecture.
Open ↗08Core moduleBegir
Explicit buyer demand and relevant seller response.
Open ↗09Core moduleRadar
Nearby and time-sensitive demand.
Open ↗10Core modulePulino
Context, eligibility, relationship and trust economics.
Open ↗11CompanionPulino Earn
Illustrative value-event and wallet companion.
Open ↗12Core moduleBoard
Product learning, questions and qualified attention.
Open ↗13Core moduleAnalytics
Signal provenance and business learning.
Open ↗14ReviewModule Index
Canonical ownership and module boundaries.
Open ↗15ReviewReview Hub
Phase-aware review, challenge and diligence routes.
Open ↗The Phase 1 boundary
Grounded claims. Clear limits.
Phase 1 describes the original Mazzaneh company and MVP operation in Iran. It remains distinct from later solo-execution work.
Team-built
The original product and operating work belongs to the company/MVP period.
Market-tested
The system met real demand, sellers and infrastructure—not a laboratory scenario.
Limited rollout
Geography, modules and versions varied; the rollout was not universal.
Evidence-controlled
Public clarity comes first. Sensitive source material stays controlled.
Architecture at a glance
From intent to intelligence.
A compact view of how Mazzaneh connected market need to business action and useful learning.
Demand appears.
Explicit, local or discovery-led.
A seller responds.
Presence, quote, content or route.
Value is exchanged.
Relationship, attention or purchase.
Signals connect.
Operational and analytics context.
Exact availability and maturity varied by product version, location and operating period.
Evidence, handled professionally
Public context. Private source review. Analytics, traffic, operating, transaction and banking records exist. Sensitive source material is shared only in a serious secondary conversation, with appropriate controls.