“I would take the deal, but only after the team maps exactly how the integration couples to the fragile surface so we know the cost of the next change. At Rebel Girls we once rushed a paywall onto a content feed we had not decoupled, and the months after launch were harder than the launch itself.”
“I would take the deal but wall it off. I built our CRM Prepaid integration through the fragile legacy OSS/BSS layer by isolating the new path behind a thin adapter, so the customer gets their six-week launch while the rest of the system stays refactorable.”
“I watched a $50 million ecommerce launch crater because architecture bowed to a deadline, and I have never forgotten the 10 orders it produced. If the fastest path hardens the fragile part of your codebase, I would negotiate scope or staging with the prospect now, because the six-week win can cost you every future release.”
“I would ship the integration behind a narrow adapter and schedule the refactor for right after close, because at TikTok we once let a big search customer’s six-week deadline force logic deep into the ranking path; the temporary branch lived for two years and slowed every later launch.”