How a small team turned a one-week deadline into a breakthrough for NRI banking — without anyone outside the room ever knowing how close it came to not happening

When one of India’s leading private banks needed to digitize a document-signing journey for overseas customers, the ask itself wasn’t unusual. The timeline was.

3 Days

FROM REQUIREMENT TO LIVE, SECURE, CLOUD-BASED SIGNING

4 TEAMS

ENGINEERING, PRODUCT, IMPLEMENTATION, AND A THIRD-PARTY PARTNER — ALIGNED IN REAL TIME

0 DISRUPTIONS

TO THE CUSTOMER EXPERIENCE, DESPITE EVERYTHING HAPPENING BEHIND IT

A Requirement That Didn’t Fit the Clock

The brief was deceptively simple on paper: make it possible for customers living outside India to sign and complete a regulated banking process — securely, digitally, without ever stepping into a branch. Underneath that one sentence sat a maze. A new certificate-based signing infrastructure to integrate. Identity verification that had to work for people thousands of miles away, across time zones and document formats. Compliance and security standards that couldn’t bend, no matter how tight the clock got.

And the clock was very tight. What would ordinarily be a multi-week integration had to be understood, built, tested, and shipped in a matter of days.

When the Map Runs Out

There was no existing playbook for this exact combination of partner infrastructure, customer geography, and deadline. The team had to learn the certificate workflow while building against it — figuring out the rules of the road at the same speed they were laying it.

That’s the point where most timelines quietly slip. Instead, engineering, product, implementation, and the partner team collapsed into one working unit — no queues, no waiting for the “next sprint.” A blocker discovered by one team in the morning was being solved by another before the day was out.

“When you don’t have time to be careful in the usual way, you have to get comfortable moving fast and course-correcting in public. That’s not recklessness — that’s what fearless thinking actually looks like under pressure.”

— Engineering Rep, Melento

“I kept coming back to one question every time we hit a wall: what does the customer on the other end of this actually need to feel — simple, safe, done. Everything else was just a detail we had to solve to protect that feeling.”

— Product Manager, Melento

“Nobody waited to be told what to do. The moment someone spotted a gap, they picked it up — even if it wasn’t technically their piece. That’s the only way a one-week deadline survives.”

— Implementation Rep, Melento

What Shipped, and What Didn’t Show

The result went live as Cloud DSC on the Melento platform — a secure, cloud-based digital signing capability now available to enterprises serving customers across geographies. From the outside, it looks like a clean product launch. From the inside, it was a week of people quietly refusing to let a hard deadline become a customer’s problem.

“Our clients don’t remember the architecture diagrams. They remember whether we showed up when it mattered. That’s the real transformation we sell — not just the platform, but the people behind it who treat a client’s deadline like their own.”

— Krupesh Bhat, CEO, Melento

No press release captured the week it took to get there. No customer ever saw the late nights or the real-time trade-offs. They just experienced something that worked, simply, the first time.

That’s the quieter definition of transformation at Melento: not the certificate, not the integration, not the platform. The people who decided a one-week deadline was a problem to be solved together — not an excuse to fall short.