Custom software development

A development shop with the business analyst built in.

Most shops expect you to arrive with a specification. We write it — then we build it.

Internal platforms, integrations and workflow systems — for the business that has outgrown its spreadsheet, and the enterprise where getting the requirements wrong is expensive.

The analyst maps the process and writes the acceptance criteria. Then the engineering is quoted from evidence instead of optimism.

Book a discovery call See what we've shipped

Free, 30 minutes. Bring a problem or bring a finished spec — both work.
Or email zied.youssfi@nextnumberglobal.com — a person replies within one business day.

Functional design documentv0.3 · signed

3.1Variance capture at dock6 AC
3.2Cycle-count scheduling rules4 AC
3.3ERP write-back & failure handling9 AC

Built from the signed spec

Inventory reconciliationLive · Dock variance

1,284counts reconciled this week

Line	Detail	Status
PO-88214 · Receiving	Variance 3 units	Resolved
PO-88219 · Receiving	Variance 41 units	Escalated
Cycle count · Aisle 12	Scheduled 06:00	Running
ERP write-back	Batch 4471	Synced

Representative view, drawn from the delivered system's documented behaviour.

What you're actually choosing between

Every option below is a reasonable way to buy software. They just fail in different places.

Hire a dev shop

They build what you asked for. Working out what you actually needed was your job — and change orders are where that gets settled.

You supply the spec

Hire a consultancy

You get a specification, then go and find someone to build from it. Whether it was buildable at that price is somebody else’s problem.

You supply the builder

Hire Elarion

One team does both. The analyst who wrote the specification leads the engineers who build from it, which is why the price holds.

Both, from one team

What we build

All six services →

Internal platforms

The system a business actually runs on — case management, dispatch, reconciliation, anything that lives in spreadsheets today.

Integrations

Making systems that were never designed to talk to each other do it reliably, including the failure cases.

Workflow & automation

Taking a process that depends on someone remembering, and making the system responsible for it instead.

AI where it earns it

Retrieval, drafting and classification with governance attached — approval state, provenance, and a human in the loop.

Two phases of analysis. Three of engineering.

The method in full →

01 — Discovery

We interview the people doing the work and map the process as it actually runs.

→ As-is process map

02 — Requirements

Every requirement gets acceptance criteria and a scope boundary. You sign it before we quote the build.

→ Signed specification

03 — Architecture

Data model, integration design, and the decisions that are expensive to change later.

→ Architecture & data model

04 — Build

Sprints against the signed scope. Tested, reviewed, deployed — with change control instead of drift.

→ Working software

05 — Handoff

As-built documentation, training, and access. You can maintain it without us.

→ A system you own

Analysis — priced as one fixed-fee phase Engineering — quoted from the signed spec

Shipped

Systems in production. Where the work was our own product rather than a client engagement, it says so — evidence that blurs the two isn't evidence.

KriftAI

Own productGoverned AI for regulated work

What we built

A governed AI platform: every model call passes through input and output validation, a deterministic compliance gate, and per-call audit logging — and nothing an AI writes reaches a customer without a human approving it.

The hard part: Making a language model safe to put in front of a compliance obligation

Specified first

Functional design document · Rules engine specification · Governance state machine · Data model · Acceptance criteria

See what shipped →

ImmiCase

Own productRegulated case management

What we built

A case management system for Canadian immigration practice, where programme rules live as data so a regulatory change is a configuration edit rather than a release.

The hard part: Rules as data — programme changes without a code deploy

Specified first

Case lifecycle model · Document requirement matrix · Data model · Audit and retention rules

See what shipped →

CrewDispatchr

Client deliveryField operations and workforce dispatch

What we built

A staffing and dispatch platform for field operations — scheduling, crew assignment and shift changes in one system instead of a phone tree.

The hard part: Real-world churn — the schedule changes all day

Specified first

Dispatch process map · Roadmap and sequencing · Build-versus-buy assessment · Vendor specification

See what shipped →

You don't have to buy the whole method

Analysis depth scales to the engagement. A two-week integration gets a scope annex; a platform gets a full specification. If you already have requirements, we'll build straight from them.

Analysis, then build

A fixed-fee analysis phase, then a build priced from it. Our recommendation when scope is unclear or contested.

Phased · fixed fee

One fixed-scope project

Analysis folded into a single price. For a well-defined ask that does not need a separate discovery phase.

Single fixed fee

Build to your requirements

You have a spec, a backlog, or your own analyst. We check it is buildable and testable, then build it.

Fixed fee or day rate

Rescue & technical audit

A build in trouble, an inherited codebase, a vendor exiting. Assessment first, options second.

Fixed-fee assessment

Embedded delivery

Engineering and analysis capacity inside your team, working to your process rather than ours.

Retainer or day rate

Fractional technical lead

A technical decision-maker part-time: roadmap, build-versus-buy, vendor specification.

Monthly retainer

Compare all six →

How we de-risk a fixed price

Read the specification this site was built from

Numbered requirements, acceptance criteria, an explicit out-of-scope list, and the assumptions the estimate rests on. It is the document that turns a build into something you can hold us to — and it is the same artifact your project would get.

Download the FDD (PDF)No email required.

Tell us what's broken. We'll tell you what it takes to fix it.

30 minutes, free, no obligation. If it isn't a fit, we'll tell you who is.

Book a discovery call Send a project brief

How we work, in three lines

Nothing gets built without an agreed written scope. The form scales to the job; its existence doesn't.

You own every document and every line of code you pay for.

Already have requirements? Bring them. We'll review rather than redo.