Neha & Vikram

Illustrative story

16 Vendors managed · £58,000 Total managed · 132 days Planning window

When Neha describes planning her wedding, she starts with the logistics, because the logistics were, by any reasonable measure, formidable. Sixteen vendors. Four days of events in and around Manchester, from 24 to 27 September 2026: a pithi (the Gujarati haldi) on Thursday, a mehndi and garba night on Friday, the wedding ceremony on Saturday, and a reception for 280 guests on Sunday. A total spend of £58,000, managed across just over four months of planning. And two families, Neha's from Manchester and Vikram's from the Gujarati community in Preston, with very clear and occasionally competing ideas about how a Hindu wedding should be done.

"It's not a complaint," she's careful to say. "Both families were involved because they cared. The involvement was an expression of love. But involvement without coordination is chaos. And we had a lot of both."

The coordination problem at scale

Neha works in project management. She approached the wedding the way she approaches complex work: a plan, a system, clear ownership of each decision. What she found was that the tools she had (spreadsheets, shared Google Docs, a multi-group WhatsApp setup she designed carefully and the families used chaotically) weren't up to the coordination problem she actually had.

The hard part wasn't managing the vendors. It was managing the information about the vendors across two families who were both genuinely involved. "My mother-in-law and my mother both wanted to be across everything," Neha said. "Which was wonderful. But they were both getting information from different places, at different times, and arriving at conversations with me with different understandings of what had been decided."

Three weeks in, before a single vendor was booked, Neha's spreadsheet had 140 rows. She was spending three to four hours a week keeping it up to date. The spreadsheet was accurate. Nobody else was reading it.

A colleague suggested Nodus in early June. Neha joined, added every vendor on her shortlist, and spent two weekends setting it up properly. Her verdict at the end of it: "It was the right tool for the actual problem."

Where it made the most difference

Decor was where the platform earned its place most clearly. Neha had booked a decorator for the full four-day programme: mandap, mehndi stage, reception centrepieces, pithi setup. Over the course of planning, the scope changed nine times. Some changes were additions Vikram's family asked for. Some were budget cuts Neha made. Some were the decorator's own suggestions as their ideas for the event developed.

Every version of the quote, every change request and every confirmation was logged in Nodus. When Vikram's mother asked, at one point, why the decorator's total had gone up from the original quote, Neha could show her the full change log: who had asked for each change, when it was approved, and what each addition cost. The conversation was over in ten minutes.

"Without that record, that conversation would have been impossible," Neha said. "Not difficult. Impossible. Because nobody remembered the same sequence of events in the same way. The platform remembered it for us."

Payment management across sixteen vendors

Sixteen vendors, each on the same structure: a deposit to confirm, then the balance before the wedding. At the peak of planning, Neha counted 32 payments to track, sixteen deposits and sixteen balances, every one due before the pithi on the Thursday.

The Nodus dashboard showed upcoming payment dates against each vendor. Reminders were logged. Neha paid each deposit and balance through the platform, directly to the vendor through Stripe, where each payment was tracked against its booking, instead of making separate bank transfers with no link to what they were for.

"The number of times I would have made a payment and then immediately been unsure whether I'd already made it: that's a specific anxiety of managing this many vendors," she told us. "The platform just showed me what had been paid and what was outstanding. It sounds simple. When you're tracking sixteen vendors it's not simple."

The four days

The pithi was exactly what Neha had imagined: small, warm, chaotic in the right way. The mehndi and garba the following evening was bigger and went on late, with Vikram's relatives from Preston leading the garba. The wedding on Saturday is the day Neha still describes first when anyone asks. "The pheras were beautiful. Vikram cried. I tried not to and failed. The pandit was exactly as experienced as his references had suggested."

The reception on Sunday (280 guests, a full dinner, dancing, speeches) finished close to midnight. Every vendor delivered.

Vikram's account of the weekend is shorter. "Nothing went wrong that we had to manage. There were small things. The lighting at the venue took longer to set up than planned, so cocktail hour was a bit compressed. But the vendors sorted it out between themselves. We didn't have to solve anything on the day."

Neha's final word on the platform: "I would have been fine without it. I'm an organised person. But I would have been managing the process for four months. Instead, I managed it for the first few weeks and the platform managed it for the rest. The difference was that when the weekend arrived, I wasn't exhausted."