FDE Times: When customers say “we could build this ourselves,” ask who wants to own it long term
A 5 November FDE Times guide reframes the common build-vs-buy pushback FDEs hear in week one: acknowledge the customer’s prototype, then shift to ownership—ops, model-change maintenance, on-call and data egress—so differentiating workflow stays with the client team and shared infrastructure rides the platform.
FDE Times published a 5 November guide on handling “our team could build this ourselves.” The article argues the objection is usually about pride, lock-in fear and who will run the system after the FDE leaves, not a feature shoot-out. Starting with a sincere yes to the prototype, then asking which parts the team wants to own six months later, beats defending the product line by line.
Drawing on Gong, MIT Sloan and a16z framing cited in the piece, it separates first-build cost from lifetime run-and-maintain cost, and recommends a four-column ownership map: component, who builds, who operates after handover, and risk if it fails. Differentiating logic (for example ticket classification and routing) stays with the customer; connectors, evals and access control can sit on the platform so the engagement does not become endless custom consulting.
For FDEs, the practical edge is turning a defensive meeting into a named client owner and a clear split of work—useful on the project and as a concrete STAR story in interviews.
Source: fdetimes.net