Build vs Buy: Adding Shariah-Compliant Investing Without Building Screening In-House

Every team that decides to offer halal investing faces the same fork in the road: build the Shariah screening engine in-house, or buy it as a service. It looks like a classic engineering trade-off, but Shariah screening has a twist most build-vs-buy decisions don't, it depends on scarce religious-scholarship expertise, not just code and data. This guide walks through what building screening in-house actually requires, the costs that don't show up in the initial estimate, the narrow cases where building makes sense, and why most fintechs and banks conclude that buying an AAOIFI-based API is the better path.

Table of Contents

• What building in-house actually requires
• The hidden costs of building
• What buying an API gets you
• When building might make sense
• Build vs buy, side by side
• How to buy: the Akinda API

What building in-house actually requires

On a whiteboard, Shariah screening looks simple: check a company's business, check two financial ratios, done. In practice, building it as a reliable, production-grade capability means assembling four things, each non-trivial:

• Licensed financial data. Accurate, current fundamentals, debt, cash, interest income, revenue segments, for every security across every market you cover, refreshed as companies report.
• A screening engine. Software that correctly encodes the business-activity screen, the debt and liquidity ratios, the thresholds, and the denominator logic, and applies them consistently at scale.
• A purification model. Logic to compute the impermissible portion of income that holders must cleanse.
• Scholar governance. Qualified scholars to design the methodology, rule on edge cases (mergers, partial-period reporting, borderline sectors), and stand behind the verdicts.

That last requirement is what makes Shariah screening different from a typical data build. You can hire engineers to do the first three; the fourth needs people who combine Islamic jurisprudence with financial expertise. You can see the finished shape of all four working together on Akinda's live screener and in its published methodology.

The hidden costs of building

The initial build estimate almost always understates the true cost, because the hardest parts are ongoing and human, not one-off and technical.

• Scarce, expensive governance. With fewer than 1,200 qualified Sharia board members worldwide serving 2,000+ institutions, and 42% of African Islamic banks operating without a certified compliance officer, the talent to govern a methodology is genuinely hard to recruit and retain.
• Perpetual maintenance. Compliance isn't static, a company's ratios shift every earnings season, so verdicts must be re-computed continuously. A build is a commitment to ongoing operations, not a project that ends.
• Coverage expansion. Every new market means new data sources and edge cases. Coverage that looks complete at launch erodes as your product grows.
• Compliance liability. If your engine returns a wrong verdict, that's your reputation and your users' trust on the line, with no external methodology to point to.
• Opportunity cost. Every month your engineers spend rebuilding Islamic-finance infrastructure is a month not spent on the product experience that actually differentiates you.

What buying an API gets you

Buying inverts covers every one of those costs. An AAOIFI-based API like the Akinda Halal API hands you the whole stack as a maintained service:

• The data and engine are maintained. Screening runs against current financials without you sourcing data or writing rules.
• Scholar governance, included. The methodology is overseen by Dr. Muhammad Nazir Khan, who holds an AAOIFI Shari'ah Auditing Certification, so you inherit governance instead of recruiting it.
• A published, auditable methodology. Your own compliance team and Shariah board can review the documented rules rather than reverse-engineer a black box.
• Purification and reports, out of the box. The full-report endpoint returns ratios and purification data alongside the verdict.
• Speed. You integrate a few endpoints and ship in weeks, on usage-based pricing that starts free.

The commercial picture for platforms and institutions is on the Akinda for Business page, and full request/response details are in the developer docs.

When building might make sense

Buying isn't automatically right in every case. Building in-house can be justified in a few narrow situations:

• Screening is your core product. If you're building a Shariah-screening platform itself, rather than an investing app that needs compliance, the engine is your differentiator and owning it makes sense.
• You already have the scholarship. If you employ qualified Shariah scholars with financial expertise and an established governance process, the scarcest ingredient is already in-house.
• You have a genuinely proprietary methodology. If your value proposition rests on a distinct, defensible screening approach that no provider offers, building lets you protect it.

A common middle path is hybrid: buy an API for the bulk of your screening needs and build only the narrow, proprietary logic that genuinely differentiates you. Outside these cases, though, the operational argument for buying is hard to beat, most teams don't need to own Islamic-finance infrastructure to offer a great halal product.

Build vs buy, side by side

The trade-off across the dimensions that usually decide it:

How to buy: the Akinda API

If buying is the right call, getting started takes minutes, not a procurement cycle. The Akinda Halal API is designed for self-serve evaluation:

1. Generate an API key from the dashboard and start on the free tier.
2. Call the compliance endpoint with a ticker and confirm the data fits your product.
3. Review the methodology with your Shariah board so everyone is comfortable with the rules.
4. Wire the endpoints into your app, add badges, gates, and purification, and set up quarterly re-screening.
5. Check the pricing page and move to a business plan when you go to production.

Frequently asked questions

Should I build or buy Shariah screening?

For almost all teams, buy. Building means licensing data, engineering a screening engine, modelling purification, and recruiting scarce scholars to govern the methodology, then maintaining it every quarter. Buying an API delivers the same capability through a few endpoints, with governance included, at a fraction of the time and cost. Build only if screening itself is your core product and you already have the scholarship in-house.

Why is the scholar requirement such a big deal?

Because it's the ingredient you can't simply hire engineers to replace. Credible Shariah screening needs people who combine Islamic jurisprudence with financial expertise, and they're scarce, fewer than 1,200 qualified Sharia board members serve over 2,000 institutions globally. Buying an API lets you inherit that governance rather than compete for scarce talent.

Is building ever the right choice?

Yes, in narrow cases: when Shariah screening is your core product, when you already employ qualified scholars with an established governance process, or when you have a genuinely proprietary methodology worth protecting. Many teams also go hybrid, buying the bulk of screening and building only the narrow logic that differentiates them.

What are the hidden costs of building in-house?

Mainly the ongoing and human ones: recruiting and retaining scarce scholars, maintaining verdicts as financials change every quarter, expanding coverage market by market, carrying compliance liability alone, and the opportunity cost of engineers not working on your actual product. These usually dwarf the initial build estimate.

How fast can I go live if I buy?

Weeks. Because the data, engine, and scholar governance already exist, you integrate the endpoints, design the UX around the verdicts, and set up re-screening. You can even start evaluating the same day by generating a key and calling the compliance endpoint on the free tier.

Sources

AAOIFI Shari'ah Standard No. 21: Financial Paper (Shares and Bonds) – the standard that the Akinda API's screening methodology is built around.

Akinda API screening methodology – the full three-phase screen, ratio formulas, and purification rule- is published for integrators to audit.

Akinda API Shariah advisor – the scholarly governance behind the API's halal verdicts.

Mordor Intelligence – Global Islamic Finance Market (2026) – Islamic finance market size and growth projections.

Disclaimer

This article is about a software product and is for general information only. It is not financial or religious advice. Automated Shariah screening produces data-driven signals, not a fatwa; integrators should pair it with their own Shariah governance and consult qualified scholars. API features, endpoints, coverage, and pricing change over time, so verify current details on b2b.akinda.io before building.