Software that fits the way your business actually works.
You already have a system of record. What you are missing is the software for the moments it goes quiet — exceptions, approvals, settlement, and the close. We ship products you operate and, for selected teams, builds that leave a system behind.
Where businesses usually start.
Most engagements begin with a workaround that became policy. If one of these sounds familiar, the work is probably concrete enough to write down.
- A spreadsheet is doing a system's job
Night shift, finance, or a producer keeps a private workbook because it is faster than the official tool. The record lives in one person's head and one person's file.
- Money moves through a vendor you cannot explain
Settlement, payouts, or contractor payments run through a hosted processor. When a payment goes quiet, nobody on your side can say what is owed, confirmed, or in flight.
- Approvals happen in inboxes
Scope changes, holds, and sign-offs are decided in email threads. Finance translates them into line items after the fact.
- Systems that do not talk to each other
The TMS, ERP, CRM, and messaging tools each hold half the story. Integrations are one-off scripts that only one engineer understands.
What the catalog gives a business.
Three products, each with a job and a commercial path. They are software you deploy and operate — not platforms we quietly run for you.
- Own your payment infrastructure
Self-hosted stablecoin gateway: payment intents, payment links, and invoices through a versioned API, with an operator dashboard for tracking, confirmation, and settlement. Keys, database, and RPC providers stay yours.
- Run the night shift properly
Exception queues with owners, states, and reopen reasons. Approval paths written as they exist on the floor, a morning digest for finance, and adapters into the TMS, ERP, and messaging tools you already run.
- Bill from approved work
A workspace per engagement, change orders as first-class objects, role-based entitlements for client, producer, and finance, and invoices that can only be emitted from an approved state.
How the software fits around what you have.
None of the products asks you to rip anything out. They sit between the systems that already work and the people who have to cover the gaps.
- 01
Your system of record stays
The TMS, ERP, CRM, or accounting tool remains the book of record. Northframe and Meridian read from and write to it through adapters and exports.
- 02
The gap gets an owner
Exceptions, approvals, and payments each get a state, an owner, and a written reason they can be reopened — so the answer is not in someone's head.
- 03
Decisions are written down
Roles mirror the ones that exist in the business: dispatcher, night lead, producer, finance closer. Policy lives in the product, not a wiki page.
- 04
Finance closes from the same record
The morning digest, the accounting export, and the settlement file come from the object the team already used — not a parallel spreadsheet.
Products behind this path.
StablePay
Self-hosted stablecoin payment infrastructure.
From $4,800 one-time license
Northframe
The operations layer for teams who still run the night shift.
From $890 per month
Meridian
Client workspaces and living billing for project-shaped firms.
From $190 per month
Proof from named engagements.
- LogisticsHalcyon Freight
A regional freight operator replaced four shared workbooks with an exception-first operations layer their night shift could actually use.
Workbook usage after 30 days: RetiredMorning close time: 41 min → 12 min - Energy servicesHelios Grid
A field-services company needed to pay contractors in stablecoin on jobs that close in hours — and keep an audit trail the existing ERP could accept.
Median contractor settlement: 14 days → 11 hoursERP exceptions after ingest: < 0.4% - Creative servicesAperture Collective
A forty-person studio needed client workspaces, entitlements, and invoices that matched how productions actually run — not how SaaS billing assumes they run.
Invoice cycle time: −38%Unbilled approved extras: Near zero
Who this is for, and what it is not.
Who it is for
- Mid-market operators with a system of record and a spreadsheet beside it
- Finance and treasury teams who want a record they can reconcile themselves
- Firms that sell projects, not seats, and invoice from inboxes
- Teams with someone named who will operate the result
Not this
- Not a replacement for your TMS, ERP, or CRM
- Not a hosted processor, custodian, or bank
- Not staffed operations-as-a-service
- Not a marketing site or a digital transformation programme
Two ways in, one honest next step.
Say whether you mean a product or a build. Vague briefs wait; specific ones get a written answer.
- 01
Use a product
Start with the catalog. Read the status, the job, and what the product is not. Licensing and pricing live with each product.
A licence, a deploy, and a handover note.
- 02
Frame the problem
If the catalog is not the fit, write the use case, the constraints, and who will operate the result. We reply when the fit is real.
A written problem, operator, and non-goals.
- 03
Ship the smallest complete cut
Interfaces, data, and deployment are designed together. The first cut goes into the environment that matters, not a demo.
A production release and a handover.
From the journal.
Is this internal tool worth building? A worksheet for operations leaders
Before you commission software, put a number on the workaround. A five-step way to decide whether to build, buy, or leave the spreadsheet alone.
By Emily Sinclair, Omar Farouk
Reconciling stablecoin payments: a treasury operator's guide
Three records, one truth. How to tell what is owed, what is confirmed, and what is still in flight — without opening three tools.
By Layla Haddad, Daniel Whitfield
Handover runbooks: writing for the 2am case
A runbook is not documentation of the happy path. It is a letter to the person who is alone, tired, and looking at something odd.
By Daniel Whitfield, Emily Sinclair
Questions worth asking.
Do we have to replace our existing systems?
No. The products are designed to sit between the systems you already operate. Northframe adapts into your TMS, ERP, and messaging tools; Meridian exports into your accounting tool.
Do you run the software for us?
No. You deploy and operate what you buy — keys, data, and on-call stay with you. We hand over with written runbooks.
How long does a first release take?
The median first release is six weeks: a focused cut in a real environment, then a second cut shaped by use.
Can you build something that is not in the catalog?
For selected teams, yes — internal tools, operational software, and integrations, when the scope can be written down and someone will operate the result.
Write down the workaround.
Tell us what the team still keeps in a spreadsheet, who runs it, and what cannot change. We will say whether it is a product, a build, or a no.