BRIA vs manual due diligence

Compliance and credit teams often patch together Kenyan counterparty checks — registry lookup, a court search, a news trawl, a memo in Word. BRIA automates that assembly with the same cited output every time. Use this page when you need to justify budget to a manager, procurement panel, or finance lead.

For internal champions: forward this link or print the comparison table below. Numbers are directional — your loaded analyst cost and screening volume will differ. We confirm pricing on pilot or quote.

See output first: Sample report  ·  Live demo  ·  Use cases
Manual due diligence BRIA
Time Typically 1–3+ days per counterparty when you cover courts, gazette, procurement, regulators, news, and director ties — longer if queues back up or names are ambiguous.
  • Each source has its own portal or search flow
  • Re-screening means starting over
  • Batch onboarding becomes a project plan
Seconds to under a minute from typed name to scored JSON; PDF typically ready in the same request window under pilot conditions.
  • One call checks the source families in your plan
  • Same latency whether it's the first or fiftieth name of the day
  • Built for weekly onboarding volume, not ad hoc heroics
Cost Hidden and variable. Loaded analyst time (often 8–16+ hours at internal day rates), registry fees, occasional external research — plus opportunity cost when deals wait on a memo.
  • Hard to forecast per entity at scale
  • Quality drops when teams rush
  • Outsourced DD adds margin on top
Predictable per entity. One-time screening from KES 5,000 (~$40) per company; monthly API plans from KES 15,000 for low-volume teams — see pricing for tiers.
  • Volume economics improve with API plans
  • No surprise “research day” invoices
  • Pilot lets you benchmark cost against your current process
Citation trail Fragile audit trail. Screenshots, bookmarks, pasted excerpts, and narrative memos — format varies by analyst; links break; six months later it's unclear what was checked or when.
  • Hard to prove negative search (“we found nothing”)
  • Regulators and auditors ask for primary sources anyway
  • Duplicate spellings may be missed or double-counted
Source-first by design. Every flag links to the underlying court judgment, gazette notice, register entry, or article. Reports include scored date, coverage metadata, match confidence, and scoring model version.
  • PDF attaches cleanly to KYC / credit files
  • JSON for systems that need structured audit fields
  • Spot-check any flag against the cited record — see Our process
Batch API Manual queues. Spreadsheets of names, assigned analysts, status columns, chase threads — no standard schema, no SLA, fragile when staff leave or volume spikes.
  • Hard to wire into onboarding or core banking
  • Periodic review = another manual cycle
  • Peak volume forces hire-or-defer trade-offs
REST API from day one of a plan. GET /v1/risk/{name} with your API key; same response shape every call — score, flags, citations, freshness. Integrate once; screen on trigger or schedule.
  • Batch merchant, borrower, or supplier lists programmatically
  • Rate limits and key rotation documented in Security
  • Full integration guide in API docs
Consistency Output quality depends on who ran the search and how much time they had. Two analysts can reach different conclusions on the same company. Same checklist and scoring model on every query. Version stamped on each report so you know when methodology changed.
Coverage Easy to skip a source under time pressure — especially gazette, procurement, and director-network checks that aren't part of a registry lookup. Defined source families (courts, gazette, procurement, regulators, media, plus onboarded licensed feeds). See Sources for what we watch today.

Simple volume math (illustrative)

Replace the placeholders with your team's loaded day rate and average hours per file.

20 entities / month, manual

At ~12 analyst hours each × your internal day rate, manual DD often exceeds KES 200k–400k/month in people cost alone — before peaks, rework, or external reports.

20 entities / month, BRIA Pro

API plan from KES 50,000/month (tier confirmed at pilot) with predictable per-lookup economics — same cited output whether it's entity 1 or 20.

When manual still makes sense

BRIA is screening intelligence, not a replacement for every judgment call. Manual work still belongs where context exceeds public records:

  • One-off, high-stakes deals where partners want bespoke field interviews
  • Material findings that need legal interpretation before you act
  • Jurisdictions or entity types outside current Kenyan coverage

Most teams use BRIA for the repeatable baseline — litigation, debarment, media, licences, director ties — then escalate exceptions to humans. That split is usually where budget conversations click.