Kavita & Devesh

Back to Stories

"Our families are spread across three cities. Nodus meant everyone could see what had been confirmed and what was outstanding. No more repeat phone calls at 11pm."

— Kavita

Kavita and Devesh did not set out to have a complicated wedding. A Hindu ceremony in Leicester, the city where Kavita grew up. Three ceremonies across two days — a mehndi on the Friday evening, the wedding itself on Saturday, a small family lunch on Sunday. Nine vendors in total. They had planned, by most standards, a manageable event.

The complication was geography. Kavita's immediate family is in Leicester. Devesh's parents are in Manchester. His sister, who was coordinating much of the logistics on his side, lives in London. Three cities, three sets of people with questions, three sets of people making calls to vendors to check on bookings that had or hadn't been confirmed. By February — six months before the wedding — Kavita estimates the caterer had received the same enquiry about the menu from four different people in the two families.

The problem with family coordination

The specific difficulty was visibility. Everyone involved in planning the wedding — Kavita and Devesh, both sets of parents, Devesh's sister, Kavita's aunt who had offered to handle the florist — was working with different information. Nobody had a complete picture of what was confirmed, what was pending, and what had been paid. The WhatsApp group that was supposed to solve this had, by April, become a 3,000-message thread that nobody except Kavita was reading in full.

"The 11pm calls were the thing that wore me down," Kavita told us. "Devesh's mum would ring to ask whether the caterer had confirmed the vegetarian menu option. I would have confirmed it two weeks earlier. But there was no way for her to see that without asking me. So she asked. Every time someone asked, it felt like the whole process had to go through me."

Devesh found Nodus through a recommendation from a colleague whose sister had used it for a wedding the previous spring. They joined the platform in March, four months before the wedding. Within a fortnight, every vendor enquiry, confirmation, and payment was tracked in one place that both families could access.

What changed

The immediate effect was not dramatic. Vendors were already confirmed, deposits were already paid. Nodus did not change any of that. What it changed was the information layer on top of it. When Devesh's mother wanted to know whether the mehndi artist had confirmed the Friday evening slot, she could check. When Devesh's sister wanted to see what the payment schedule looked like for the remaining vendor balances, it was there. The calls to Kavita did not stop immediately — it took a few weeks for both families to build the habit of checking the platform first — but they reduced significantly within the first month.

Two months before the wedding, the caterer proposed a change to the vegetarian menu following a supplier availability issue. The change was logged in Nodus, flagged to both families, and discussed and approved without anyone needing to relay the information between cities. "Under the old system, that would have been a confusing week of phone calls," Devesh said. "It was a 20-minute conversation in the platform."

The week before

By the week before the wedding, Kavita had three things left to confirm: the timing of the dhol player's arrival for the baraat, a final headcount update to the caterer, and collection of a final payment to the florist. Everything else was done, confirmed, and visible in the platform. She showed us the dashboard from that week: nine vendors, nine confirmed statuses, every payment either completed or scheduled.

"I kept waiting for something to go wrong," she said. "Because that had been my experience of planning — something always went sideways at the last minute. And there were small things, small adjustments. But they were manageable because we actually knew where things stood. I wasn't guessing whether we'd confirmed something or just discussed it."

The wedding was, by their telling, exactly what they had planned. The mehndi was full, the ceremony went on time, the Sunday lunch was relaxed. Devesh's mother — the one who had been calling at 11pm — gave a speech at the reception in which she specifically mentioned how smoothly the planning had gone.

What they would tell other couples

When we asked Kavita and Devesh what advice they would give to couples in a similar situation — multi-city families, complex coordination — their answer was direct: sort the information problem before anything else.

"The vendors were fine," Kavita said. "We were lucky — we had good vendors. But even with good vendors, the coordination was the hard part. Every question that had to go through one person, every message that got lost, every time someone had to ask me what had already been confirmed — that was the friction. Get that right and the rest is manageable."

Kavita and Devesh's story is shared with their permission. Some details have been reviewed by both at their request before publication. Financial figures reflect platform records.