Neha & Vikram

Back to Stories

"Sixteen vendors. A four-day programme. Two families with very different ideas about how things should go. Nodus was the one thing everyone could actually agree on."

— Neha

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: a haldi on Thursday, a mehndi on Friday, the wedding ceremony on Saturday, a reception for 280 guests on Sunday. A total spend of £58,000 managed across almost ten months of planning. And two families — Neha's from London, Vikram's from a Gujarati community rooted across west London and the Midlands — with very clear and occasionally competing ideas about how a Hindu wedding should be done.

"It's not a complaint," she is 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 with the same disposition she brings to complex work projects: a plan, a system, clear ownership of each decision. What she found was that the tools available to her — spreadsheets, shared Google Docs, a multi-group WhatsApp setup she designed carefully and which the families used chaotically — were not adequate to the coordination problem she actually had.

The specific difficulty was not 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."

By month four of planning, Neha's spreadsheet had 140 rows. She was spending three to four hours a week maintaining it. The spreadsheet was accurate. Nobody else was reading it.

A colleague whose family had used Nodus for an event the previous year suggested it in October. Neha joined the platform, mapped every existing vendor into it, and spent two weekends getting it set up properly. Her assessment at the end of that process: "It was the right tool for the actual problem."

Where it made the most difference

The decor coordination was where the platform earned its place most clearly. Neha had commissioned a decorator for the full four-day programme — mandap, mehndi stage, reception centrepieces, haldi setup. Over the course of planning, the scope changed nine times. Some changes were additions requested by Vikram's family. Some were budget adjustments Neha initiated. Some were the decorator's own suggestions as their vision for the event developed.

Every version of the quote, every change request, every confirmation was logged in Nodus. When Vikram's mother asked — as she did, at one point — why the total decorator cost had increased from the original quote, Neha could show her the full change log: which changes had been requested by whom, when each was approved, 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, most with deposit-balance payment structures, across a ten-month planning period. Neha's count, at the peak of the planning, was that she had 23 payment events to track: some deposits already paid before the platform was set up, every remaining balance, and the final settlements with vendors who invoiced after the wedding.

The dashboard in Nodus showed upcoming payment dates against vendor records. Reminders were logged. Neha moved the instalment payments through the platform — where they were tracked against the corresponding contract — rather than making separate bank transfers with no link to what the payment was for.

"The number of times I would have made a payment and then immediately been uncertain 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 haldi was exactly what Neha had imagined it would be: small, warm, chaotic in the right way. The mehndi the following evening was larger and went until late. The wedding on Saturday was the day Neha still describes first when anyone asks her about the wedding. "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 handled it 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 ten months. Instead, I managed the process for the first month and the platform managed it for the rest. The difference was that when the weekend arrived, I wasn't exhausted."

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