01
When a connected workflow does not mean a business to own
I use the fictional 27-venue review to separate interest in integration from demand for replacement. Participants examine a ticket-engine proposal, identify which customer requests support it and consider the obligations the enterprise would accept. The exercise retains the six replacement requests while recognising that 21 venues wanted a connection to their incumbent system.
I explain why I withdrew a proposal I had supported, kept ₹38 lakh discovery expense visible and recommended an unfinished integration programme rather than declare an immediate success. The discussion is about matching a strategic commitment to the evidence behind it. It does not prescribe that every software company should avoid adjoining markets or that partnership is always preferable to ownership. Teams work with invented circumstances and no private customer terms, including a choice about which assumptions need examination before design is commissioned. The practical aim is to improve the questions asked before a plausible adjacency becomes a different business the organisation has committed to operate.