The honest answer to “Moment or build in-house?” is that the team cannot decide until it compares both options against the same evidence. A vendor name, a funding announcement and an internal engineering estimate do not establish which route will cost less, ship sooner or carry less risk.
IT News Africa reports that pan-African fintech Moment has closed a $22 million Series A led by AlphaCode Venture Partners, with participation from existing and new investors. That financing is relevant evidence about the company’s backing. It does not answer the product decision facing a payments team.
The hallway question exposes a familiar gap. The team may know the vendor exists. It may also believe an internal build offers more control. Without documented requirements, verified capabilities and comparable cost estimates, both positions remain assumptions.
Start with the payment problem, not the company name
“Moment or build in-house?” compresses several decisions into one sentence.
What payment methods and markets must the product support? Which settlement, reconciliation, reporting and refund workflows matter? What uptime, latency and support commitments are required? Which regulatory, security and data-handling obligations apply?
Until those questions have written answers, a vendor comparison rewards confidence rather than fit. The person who has seen the strongest demo may favor buying. The engineer who can picture the architecture may favor building. Neither view tells the team how the system will perform against the actual workload.
A useful requirements document can be short. It should identify the flows that must work on launch day, the failures the team must recover from and the evidence required before approval. It should also separate firm requirements from preferences. A feature that sounds useful in a sales call should not receive the same weight as a payment method required in the first launch market.
Compare two complete costs
Vendor pricing is only one part of buying. Engineering salaries are only one part of building.
A credible buy estimate should include integration work, contract minimums, transaction charges, implementation support, internal compliance review, monitoring and the cost of switching later. The team should verify each figure through documentation, a written proposal or a scoped technical assessment.
A credible build estimate should include design, development, testing, certification where applicable, operational coverage, incident response and ongoing maintenance. It also needs an opportunity-cost line: what planned work will move when engineers spend months building payments infrastructure?
Time estimates deserve the same treatment. “The integration should take two weeks” and “we can build it in a quarter” are starting hypotheses. Ask what each estimate includes, which dependencies sit outside the team and what could delay production use.
The result will rarely be one perfectly comparable number. It can still reveal where the uncertainty sits. A narrow cost range supported by evidence is more useful than a precise total built from guesses.
Test the claims that could reverse the decision
Every evaluation has a few claims that matter more than the rest. Find them before the team spends weeks collecting low-value detail.
If the case for Moment depends on support for a specific market, payment rail or settlement process, verify that capability directly. If the case for building depends on an existing internal component, confirm its production readiness and ownership. If either route depends on a launch date, map the approvals and testing that must happen before customers can use it.
A proof of concept should target those decision-changing claims. It should exercise a representative transaction, a failure path, a refund or reversal, reconciliation output and the operational information available when something breaks. A polished happy-path demo proves little about Friday-night recovery.
This is the same discipline behind The Workflow Was Wrong, Not Broken: examine the real operating conditions before choosing a remedy. Product decisions often look technical on the surface while the decisive constraint sits in ownership, support or process.
Give Friday’s question an evidence owner
The next step is a decision record, not another hallway opinion.
Write the two options at the top. Beneath them, list the requirements, evidence source, confidence level, unresolved risk and person responsible for closing each gap. Keep reported facts separate from analysis. Mark vendor statements as vendor statements until they are verified. Mark internal estimates with their assumptions.
The Series A belongs in that record as current company context, attributed to IT News Africa. It may affect questions about financing, planned expansion or counterparty review. It should not be treated as proof of product coverage, implementation speed, reliability or fit.
Set a date for the decision and define what evidence must exist by then. On Friday afternoon, the payments PM should be able to open one page and show why the team chose to buy, build or postpone. The useful outcome is a decision another operator can audit six months later, after the launch plan changes and the hallway conversation has been forgotten.
Sources
IT News Africa, reporting on Moment’s $22 million Series A. No direct source URL was supplied.
Comments
No comments yet.