n.V5-3.02 | BUY, UNLESS
01| IkoCiti does not build what already exists at quality. Before anything gets built, one question comes first: is there a reliable third-party solution? If yes, we curate it. If no, we build it. We call it 3P-First, and it is the default, not the preference.
02| This is not cost-cutting dressed up as strategy. It is a statement about where we create value that nobody else can. We are infrastructure, not intervention — and infrastructure earns its keep by making other people's good work usable together, not by re-manufacturing all of it in-house.
03| The decision has four outcomes. A quality third-party solution that integrates cleanly gets curated. One that meets the standard but does not integrate gets an integration layer built for it, then gets curated. Where nothing adequate exists, we build. Where what exists sits below our standard, we build.
04| Building therefore requires justification, and the justification has to be one of four conditions. No suitable third-party option exists — some things we need were never built elsewhere because nobody else had a structural reason to build them. Available options fall below standard — the standard comes first and the build decision follows from it, never the reverse. The gap is our competitive edge — the peer training method, the marketplace mechanics, the way capability development is welded to project economics. Those are what make us different from everything else in the field, and difference cannot be outsourced. Integration costs exceed development costs — heavy customization, dependency on someone else's roadmap, maintenance that never ends; when those exceed the cost of building, building is simply cheaper.
05| The conditions are written down for a reason. Left unwritten, build-versus-buy gets decided by preference, by ego, and by the entirely human enthusiasm of engineers for a blank page. Every division feels that pull. Written conditions let it win only when it deserves to.
06| The argument for the default is arithmetic before it is philosophy. A platform that built everything itself would need an organization roughly the size of the ecosystem it would otherwise draw on. That organization is not fundable. Comprehensive capability through integration is achievable at our budget; comprehensive capability through proprietary development is not achievable at any budget we will ever have.
07| It also buys expertise we could never hire. The best curriculum designers, methodologists, evaluators and builders are scattered across hundreds of organizations. Hiring them is impossible. Integrating their best work is not. The 3P-First approach turns the dispersion of expertise from an obstacle into a supply.
08| And it buys years. Capability frameworks have been tested for decades in adjacent fields; software has been hardened by millions of commercial users; measurement methods have been beaten into shape by people who spent careers on them. Rebuilding any of that would cost us years to arrive at a quality level that already exists — and would probably arrive worse, because established solutions carry accumulated learning that a fresh build has to rediscover the hard way. A platform that takes ten years to build everything itself is a platform that shows up a decade late to work it called urgent.
09| Now the honest part. Third-party solutions rarely fit. A curriculum built for one context needs adapting to another. A commercial tool needs reworking for users with limited digital literacy. An academic method needs translating into something operational. Every integration creates work that a from-scratch build would not have created — smaller work, but real work.
10| Sometimes the compromise bites harder than that. The integrated solution is not quite what we would have designed. The dependency creates risk. The customization eats a good share of the leverage that justified integrating in the first place. We accept those costs, because the alternative consumes resources we do not have and arrives no sooner.
11| The discipline is in holding the line when friction shows up. Friction is not a signal to start building. Friction is the expected condition of integration, and how well we handle it is a fair measure of our operational maturity — considerably fairer than how often we avoid it by building our own.
