WE BUILD PRODUCTS. YOU PAY FOR RESULTS.

FintechsConsumer financeSME lendingMicrofinanceLeasing and factoringBanksBuy now, pay laterAuto financeFintechsConsumer financeSME lendingMicrofinanceLeasing and factoringBanksBuy now, pay laterAuto finance

Products in production, flx360 and Connect

Release line shared by every client

Weeks

To a working environment, not quarters

RaaS

Fees tied to an agreed, measured result

Results as a Service

WE CARRY THE RISK. YOU KEEP THE RESULT.

In a project, you pay up front and hope the result arrives. Under RaaS we agree a metric and a baseline first, then build and run the product ourselves. The fee is released only as that metric moves.

Agree the result

One metric, a measured baseline and a target, signed before any build starts.

We build and run it

flx360, the implementation and the operating team are ours to deliver.

You pay as it lands

Fees are released against the metric, reported on the same dashboard you use.

Where the money goes, month by month

Your cost Measured result

Illustrative profile. Fee terms, metric and baseline are agreed per engagement.

Flagship product

flx360

The fintech suite. LMS, Ticketing and Workspace share one customer record, one workflow engine and one audit trail, and every other module runs on the same core.

Visit flx360.com

LMS, loan management

The full credit lifecycle, from application to write-off, configured against your products and your credit policy. Conventional and Islamic.

Origination and credit decisioning

Disbursement and servicing

Collections and recovery

Accounting, provisioning and IFRS 9

Origination funnel, this monthSample data

Applications1,240

Scored1,212

Approved860

Disbursed790

First instalment paid772

Ticketing, service and case operations

Every request, case and complaint in one queue, with the workflow, SLA and escalation path attached. Built for operations where a missed service window is a regulatory matter.

Omnichannel intake

SLA clocks and named escalation

Complaints with regulatory coding

Dashboards by team and branch

Service queueSample data

CS-20931Early settlement request

Within SLA

CS-20928Card dispute

Due in 2h

CS-20917Branch service complaint

Breached

CS-20912Statement request

Assigned

Workspace, the team’s side of the operation

Tasks, approvals, documents and internal requests, on the same record as LMS and Ticketing. The memo, the approval and the loan it concerns sit in one place.

Tasks and assignments

Approvals and maker-checker

Documents, memos and sign-off

Internal requests between teams

Approvals inboxSample data

Credit limit increase, SME-0412

2nd approver

Write-off memo, Q3 batch

Signed

Branch cash request, Maadi

Due today

Fee schedule, new product

In review

Most institutions start with LMS, Ticketing and Workspace. Every other module is switched on against the same record when the operation is ready for it.

LMS

Ticketing

Workspace

MIS

Collections

Project management

Reconciliation

MMS

Workflow engine

Credit

Audit and access

Accounting

Integrations

API-first platform

API sandbox

Module details

Integration layer

CONNECT

Where APIs get built, wrapped and orchestrated. Rate limits, versions and error codes are configured per endpoint, and the documentation regenerates from the live contract.

When the product you need does not exist yet, we build it.

Customer channels, agent apps, internal tools and new lending products. The same engineers, release line and standards as flx360.

Discover

Users, process and the one metric the product has to move.

Design

Flows and prototypes tested with the people who will use them.

Build

In-house engineering with working software every release.

Launch

One pilot branch first, then rollout at the pace the operation absorbs.

Run

Managed, measured and improved. Eligible for RaaS terms.

Mobile and web channelsAgent and field appsInternal toolsWorkflow and rulesAPIs on ConnectData migration

Business consultation

ADVICE WE ARE WILLING TO BE MEASURED ON.

Our consultants have run lending books and collections floors. Every recommendation names the metric it should move, so it can be tracked, and priced, as a result.

Consultation services

Strategy and operating model

Current state, cost-ranked gaps and a target model a board can act on.

Credit policy and product design

Products, pricing, limits and delegated authority, written to be configured.

Regulatory and audit readiness

Controls, segregation of duties and evidence, reviewed before the examiner does.

Programme management

We run the PMO. Weekly status, one owner per risk, one plan.

Our story

WE MOVE INSTITUTIONS FROM WHERE THEY ARE TO WHERE THEY NEED TO BE.

north9 was founded by people who had already run lending books, collections floors and core migrations from the inside. That is the whole difference: we have sat on your side of the table, under your regulator, against your quarter-end.

Every person here has run a lending book, a collections floor or a core migration before doing it for a client. That depth turns a diagnosis into a working pilot, and a working pilot into an operating model your own team keeps running long after we leave.

Read our story

We state what shipped, and what it changed.

The operating model is written down, not assumed.

We name the team, and keep it named.

We finish.

Next step

BOOK A DEMO.

A short working session with the team that would run your programme. Bring the metric you most need to move.

Book a demo

Explore flx360

Digital products

TWO PRODUCTS. ONE RELEASE LINE.

flx360 is the fintech suite that runs the operation. Connect runs the integrations underneath. Both are configured to your institution, and both can be taken on Results as a Service terms.

flx360

The fintech suite · flx360.com

flx360 carries the whole operation: the credit lifecycle in LMS, the service and case lifecycle in Ticketing, the internal work of the team in Workspace, and the supporting modules around all three.

One customer record, one workflow engine, one audit trail. A collections officer and a complaints handler see the same history, so nobody has to reconcile two systems by hand.

At a glance

Core modulesLMS, Ticketing, Workspace

DeploymentCloud or on-prem

LanguagesArabic and English

ProductsConventional and Islamic

Websiteflx360.com

LMS — loan management

The full credit lifecycle, from application to write-off, configured against your products and your credit policy.

flx360 LMS loan detail with balance summary

Origination

Applications, document capture, scorecard hooks, branch and digital channels.

Credit decisioning

Policy rules, limits, exceptions, four-eyes approval, delegated authority matrix.

Disbursement

Schedules, fees, interest and profit methods, payment instruction to the switch.

Servicing

Repayments, early settlement, rescheduling, top-ups, holidays and waivers.

Collections

Queues, promises to pay, field visits, call outcomes, legal escalation.

Accounting

Ledger posting, provisioning, IFRS 9 staging, write-off and recovery treatment.

Reporting

Regulator packs, portfolio cuts, ageing, vintage and roll-rate analysis.

Access and audit

Roles, segregation of duties, maker-checker, complete and immutable trail.

Ticketing — service and case operations

Every request, case and task in one queue, with the workflow, SLA and escalation path attached. Built for operations where a missed service window is a regulatory matter, not a support ticket.

flx360 ticket with task timeline and actions

Omnichannel intake

Branch, call centre, mobile app, email, messaging and self-service portal.

Case management

One customer record shared with LMS: accounts, products and prior cases.

Workflow engine

Visual process design, conditional routing, no code required on the common path.

SLA and escalation

Clocks per case type, breach thresholds, and a named person told on breach.

Field and branch ops

Assignment, routing, mobile capture, signature and evidence attachment.

Complaints and compliance

Regulatory categories, root cause coding, response windows, audit export.

Automation

Rules, triggers, scheduled actions and robotic steps for repetitive work.

Dashboards

Volume, ageing, first-contact resolution and breach rate, by team and branch.

Workspace — internal operations

The team’s side of the operation. Tasks, approvals, documents and internal requests run on the same record as LMS and Ticketing, so the memo, the approval and the loan it concerns sit together.

Tasks and assignments

Work routed to a person or a team, with due dates and the record it concerns attached.

Approvals

Maker-checker and multi-level approval on any request, with delegated authority applied.

Documents and memos

Credit memos, policies and board papers drafted, reviewed and signed in one place.

Internal requests

Requests between branches, finance, risk and operations, tracked like cases.

Announcements

Policy changes and circulars pushed to the roles they affect, with read receipts.

Team dashboards

Workload, ageing and turnaround by team, branch and approver.

Also inside flx360

LMS, Ticketing and Workspace are the three modules most engagements start with. The rest of the operation runs on the same record, the same workflow engine and the same audit trail.

MIS

Reporting and dashboards, customized per institution and per role.

Collections

Queues, strategies, promises to pay and field assignment, shared with LMS.

Project management

Milestones, tasks and delivery tracking for the rollout itself.

Reconciliation

Automated matching across the ledger, the switch and the bank statement.

MMS

Merchant and agent network management: onboarding, limits and settlement.

Workflow engine

Visual process design and conditional routing, shared across every module.

Credit

Policy rules, limits, exceptions and delegated authority, usable by any module.

Audit and access management

Roles, segregation of duties, maker-checker, a complete and immutable trail.

Accounting

Ledger posting, provisioning, IFRS 9 staging, write-off and recovery treatment.

Integrations and integrated actions

Triggered actions and data exchange with Connect, run from inside the workflow.

API-first platform

Every module reachable as an API first, on the same contract as everyone else.

API sandbox

A working sandbox to test integrations and new modules before they touch production.

CONNECT

The API integration and orchestration layer

Connect is where APIs get built, wrapped and orchestrated. Expose any flx360 module as a REST endpoint, wrap an existing interface behind a clean contract, and chain multiple calls into one integration, without writing custom code for the common path.

Rate limits, versioning and the HTTP status code returned on failure are all configured per endpoint. Documentation regenerates itself from the live contract, so the reference a developer reads is never behind the API itself.

Connect integration builder showing a demo flow

API builder

Expose any module as a REST endpoint with no custom code.

Wrapping and orchestration

Wrap an existing interface behind a clean contract, or chain several calls into one.

Rate limiting

Per endpoint and per consumer, configured, not hardcoded.

Custom error handling

Map any failure to the HTTP status code your consumers expect.

Versioned contracts

Old and new versions run side by side until every consumer has moved.

Live documentation

Reference docs regenerate from the contract, every time it changes.

Sandbox

A working environment to test an integration before it touches production.

Call logging and replay

Every request logged, inspectable, and replayable on demand.

SEE IT ON YOUR OWN DATA.

We can configure a working sandbox against one of your own products, well before any commercial conversation.

Book a demo

Two ways to engage.

Fixed scope

A defined deliverable, a plan and milestone payments. Right when the outcome is clear and you want to own it.

Scope, plan and price agreed up front

Milestone-based payments

Handover to your team, or managed run

Results as a Service

We agree the metric and the baseline, then build and run the product ourselves. The fee is released as the metric moves.

One metric, a measured baseline and a target

Build, implementation and run included

Fee released against the reported result

Expertise built to move from one generation of the team to the next.

Every senior person here has run a lending book, a collections floor or a core migration from inside an institution before doing it for one. That is not a hiring line. It is how the delivery team gets built, engagement by engagement.

Every engagement feeds a shared library: configuration patterns, workflow templates, integration playbooks, and the edge cases that only surface once a platform is live. A new consultant or engineer does not start from zero. They start from what the last engagement already solved.

That is what lets the expertise move from one generation of the team to the next without resetting, and what lets a client's own team pick up the operating model and keep running it long after we leave.

Documented, not tribal.Every configuration decision and workaround goes into the pattern library, not one person's head.

Reused, not rebuilt.The next engagement starts from what the last one already solved.

Handed forward.Onboarding pairs a newer team member with a senior one until the pattern is theirs to carry.

WE BUILD PRODUCTS. YOU PAY FOR RESULTS.

WE CARRY THE RISK. YOU KEEP THE RESULT.

LMS, loan management

Ticketing, service and case operations

Workspace, the team’s side of the operation

When the product you need does not exist yet, we build it.

ADVICE WE ARE WILLING TO BE MEASURED ON.

WE MOVE INSTITUTIONS FROM WHERE THEY ARE TO WHERE THEY NEED TO BE.

BOOK A DEMO.

TWO PRODUCTS. ONE RELEASE LINE.

LMS — loan management

Ticketing — service and case operations

Workspace — internal operations

SEE IT ON YOUR OWN DATA.

CONSULTATION, PRODUCT DEVELOPMENT AND RESULTS YOU CAN MEASURE.

Two ways to engage.

WHAT WE SHIPPED, AND WHAT CHANGED.

TALK TO US ABOUT A SIMILAR ROLLOUT.

{{ caseStudy.title }}

SEE IT ON YOUR OWN DATA.

THE EXPERTISE IS THE ASSET. IT OUTLASTS ANY SINGLE PROJECT.

Expertise built to move from one generation of the team to the next.

SMALL TEAM. REAL SYSTEMS. NO SPECTATORS.

Four conversations, no take-home marathon.

NOTHING FITS? WRITE ANYWAY.

{{ job.title }}

TELL US WHAT NEEDS TO BE REAL, AND BY WHEN.