Reliable to the core
We're self-funded and privately held.
Customer revenue funds Najaxa. We intend to remain privately held, with the people who run the company still close to the work.
Founded in 2018. Still run from the work.
Najaxa began as a services company. Staffing firms needed help with the systems they already had, and they needed someone who would stay with the problem. That practice became Najaxa Middle Office and the Najaxa Data Team.
Jamie leads the company and sets the direction of Middle Office. Nate runs the data practice and operations. Jason leads the engineering team that builds Middle Office. The team around them designs, builds, implements, and supports the work. We take the implementations that team can deliver well.
Read where we came from, and email Jamie or Nate from the about page.
One team follows the account.
The people who learn your rules are the people who configure them, sit with your team while you accept the setup, and answer later. Some customers keep us closely engaged. Others call when a client rule, a file, or a question shows up.
- 01
Discovery
We map every application you use, what was bolted on, and what people still do by hand. The proposal says what is ready, what needs configuration, and what has to be built. Client rules, approval paths, imports, exports, testing, and cutover are on that plan before the work is scheduled.
- 02
Configuration
Pay and bill, conversion, overtime, invoice grouping, purchase orders, imports, and the payroll file go into Middle Office. The people from discovery put those rules in, so a later question still has a person who remembers why the rule is there.
- 03
User acceptance testing
Our engineers work directly with your team. Your team learns the system by using it, and they accept the way it has been configured. Adjustments happen in that room so the expectations and the system match before the first payroll.
- 04
Go-live
The first payroll and the first invoices tie out with the people who configured them. A held line, or a file the provider needs reshaped, goes back to that person.
- 05
The year after
A new client rule, a new file, or a pay and bill question comes back to people who already know the configuration. When that question is one every staffing firm has, it becomes part of Middle Office. A question that belongs to your firm stays in your configuration.
You can see how a number was produced.
Pay, bill, and margin for a worker and period are on the screen before the invoice goes out. When a result needs an explanation, the path back to the timesheet, the export batch, and the invoice is the same path the calculation used.
-
A change leaves a trail. A manual edit can carry the old value, the new value, the reason, the person, and the time.
-
A credit stays with its invoice. The credit and the rebill remain connected to the invoice they replace, so the history of that bill is still there.
-
Engineering starts from the record. Application traces, metrics, logs, and regression tests give the team a concrete place to begin.
-
Your data can leave. Use the API, configured files and webhooks, or NMO Sync to SQL, Fabric, or Snowflake.
You know where to find me.
If you want to ask about ownership, how we implement, or a pay or bill question, email me or call the office. A person answers the phone and brings in the person who knows the account.
Request a demo of Middle Office and bring one timesheet. We will walk through pay, the invoice, and the margin.
jamie@najaxasoftware.com (701) 997-1040
Jamie EvensonFounder & CEO