Monasabty Started With a Messy Conversation
Event planning in Tunisia often begins with scattered messages. Monasabty began by asking what would happen if the conversation had somewhere better to live.
The decision was spread across too many places.
Planning an event rarely begins with a clean database. It begins with a question sent to a relative: who knows a good venue, who can prepare the food, or does anyone have the number of a decorator?
Then the search moves through social media, messages and phone calls. One provider sends a voice note. Another sends a screenshot. Someone else says to visit in person. Prices arrive in different formats, availability is unclear and important details become mixed with everything else in the conversation.
The difficulty is not that people do not know how to plan events. The difficulty is that the decision is spread across too many places.
A directory would not be enough.
A directory helps someone discover a provider. It does not help them decide. It does not preserve the conversation. It does not make the difference between a vague price and a real proposal visible.
Monasabty had to sit closer to the decision itself. A client should be able to describe an event once, send that context to a provider and receive a response that can still be understood later.
The provider should not receive a blank message with no date, category or expectations. The client should not have to reconstruct every option from memory.
The quote became more important than the listing.
The listing is the entrance. The quote is where the relationship starts to become real.
A useful marketplace does not remove the human part of the exchange. It gives the human exchange a clearer shape. There is still a conversation, negotiation and uncertainty, but the important parts do not have to disappear inside a long message thread.
The vendor also needs more than visibility. A provider may manage services, packages, branches, availability, bookings and invoices. The public profile is only one part of the business behind it.
Local context is part of the architecture.
Monasabty had to respect the way people actually work in Tunisia. French may be the practical language of the interface. Arabic remains essential to the cultural context. Governorates and local geography matter. A provider in Tunis is not interchangeable with a provider in Sfax.
The success question is simple: can a Tunisian family plan a real event with less confusion than before? Can the provider understand the request without asking the client to repeat everything? Can both sides look back at the agreement and see the same story?
The original problem was a messy conversation. The product became an attempt to give that conversation memory, context and a safer next step.