Every ERP dollar inspected before it reaches Cobra

Stratholt™ checks every line of your ERP cost, flags what's wrong, drafts the requests your team needs and writes the files Cobra imports, on your own servers.

Stratholt™ checks every line of your SAP, Oracle or Costpoint cost export, ties it to the ERP to the cent, flags what needs fixing, and writes the actuals, status and ETC files your Cobra administrator imports. Labor ETC stays in hours; everything else is in dollars. It runs on your own servers.

Stratholt™ is in its pilot phase and taking a few early-access programs. Ask about early access

Month-end tie-out FY2026-P09

ERP cost read$45,068,920
Set aside, with a reason−$586,687
Cobra actuals file$44,482,232
Difference$0.00

Caught before Cobra lines

Older system's history300
Not yet placed30
Not program cost14
Duplicates14
Late postings held10

Actual cost by element to Cobra

Labor$32.29M
Material$7.28M
ODC$2.59M
Subcontract$1.21M
Travel$0.70M
Interdiv.$0.42M

Actual cost to date $44.5M

Jan to Sep, 87 work packages, 19,402 ERP cost lines. Overhead surcharge lines are left out at import; Cobra burdens them.

Made-up demo program, month-end FY2026-P09: four vehicles, 87 work packages, run through the real software.

How a month-end runs

Five steps, in the order Stratholt™ runs them. Your team sees the same tracker.

  1. 1LOAD
    Your exports

    ERP extract, Cobra structure, parts list, schedule.

  2. 2CHECK
    More than 100 checks

    Rules on charge numbers, periods, hours, duplicates and parts.

  3. 3REQUEST
    Requests for finance

    Your master parts list shows where material belongs; Stratholt™ drafts the JEV (journal entry) requests.

  4. 4TIE OUT
    To the cent

    Every dollar placed or set aside; the total matches the ERP.

The main check categories
  • Charge numbers. Cost on a charge number closed in the ERP, or on a work package closed in Cobra.
  • Periods. Cost posted into a closed month; late postings held for a decision.
  • Duplicates. The same posting twice in the extract.
  • Labor. Labor cost with no hours; leave or holiday pay charged to the program.
  • Material and parts. A part charged to a different work package than the master list; parts not in the list; material left over on a completed part.
  • Placement. Cost that can't be placed on a work package or element of cost; unallowable cost.
  • Estimates. EAC below cost to date; ETC left on finished work; to-complete efficiency far from CPI.
  • Schedule. The data date; activities dated on the wrong side of it; percent complete that disagrees with the dates.

The screens your team uses

Real Stratholt™ screens, redrawn on the made-up demo program. Pick one to look closer.

Fig. 1 · The softwareFrom the real software · made-up demo data
Exceptions queueEverything the checks could not map or that broke a rule this month. Decide once; fixes are remembered.

Where every dollar goes

Every cost line Stratholt™ reads ends up in one of two places: on a work package in the Cobra file, or set aside with its reason. Overhead surcharge lines, which Cobra burdens itself, are left out at import and listed.

Fig. 2 · Cost flow, ERP to CobraMade-up demo program · set-aside band drawn wider than scale

Made-up demo program, month-end FY2026-P09. The set-aside band is drawn thicker than its true size so it can be seen.

  1. ERP export19,402 cost lines read from the export$45,068,920
  2. Set aside with a reason10 late postings, 14 duplicates, 14 not program cost, 30 not yet placed, 300 lines of an older system's history, 5 held at a cutover−$586,687
  3. Cobra actuals file87 work packages, by cost element$44,482,232
  4. Difference$0.00

Also written: the status file for P6 or Microsoft Project, the ETC files for Cobra and the JEV requests for finance.

Your team imports the files

Your team imports the files once the checks are clear.

When the checks are clear, Stratholt™ marks the actuals file, the ETC files and the schedule status file ready, and keeps a fingerprint of each so the same file is never loaded twice. Labor ETC stays in hours; Cobra prices the labor.

Hand-off checklistFY2026-P09
  • ✓ERP extract loaded, 19,402 cost linesDONE
  • ✓More than 100 checks runDONE
  • ✓Parts-list differences listed for financeDONE
  • ✓Tied to the ERP, $0.00 differenceDONE
  • ✓Schedule data date checkedDONE
  • Files handed to your Cobra administratorNOT YET
Fig. 3 · Cobra feedFrom the real software · made-up demo data
Cobra feed · FY2026-P09The files your team imports into Cobra this month, and the status file for the schedule. Stratholt™ changes nothing in Cobra.
Goes toFileCoversStatus
Cobra · actual costcobra_actuals.csv$44,482,232 · 87 work packagesReady
Cobra · forecastETC files, forecast workbookETC: labor in hours, everything else in dollarsReady
Schedule · statusP6 or Project import filePercent complete, data date checkedReady
AccountingJEV request listParts booked elsewhere than the master listFor finance to post

Runs inside your network

Stratholt™ installs on your server, behind your sign-in. It makes no connections to us or the internet, only to systems you set up, and we never need to see your data.

Your server

Windows Server or Linux with Docker, with an offline installer.

Your sign-in

Your single sign-on, or local accounts with an authenticator app.

Export control

An ITAR program opens only to accounts marked as US persons.

For your ISSO

A NIST SP 800-171 responsibility matrix and a hardening guide.

Read the security details

Early access for one of your programs

Stratholt™ is in its pilot phase. We're taking a small number of programs to run it on before general release.

What you get

Stratholt™ on one program, run alongside the way you close today, set up with you.

A direct line

You talk to the people building it. Your month-end shapes what comes next.

What we ask

Your feedback, and your report layouts or a scrubbed sample made on your own machine. Never your program data.

No commitment to ask

Tell us your ERP and your program, and we'll say whether it's a fit.

Ask about early access

Why I built Stratholt™

As an EVMS consultant, I've seen almost every program's month-end start the same way: the ERP export lands, and analysts spend days finding mischarges, duplicate postings and parts booked to the wrong work package before anything can go into Cobra.

Corrections, status and the ETC are meant to happen early in the close. In practice they slip, so variance analysis gets rushed and reports go out late. Most teams hold it together with spreadsheets that only one or two people understand.

Stratholt™ runs those checks every month, the same way, before cost reaches Cobra, so your analysts spend their time on analysis instead of hunting for errors. It's time we get back to understanding the data rather than micromanaging it.

Cameron Smith · Founder

Thirty-minute demo on sample data

We run a full month-end on a made-up program in your ERP's format, from load to release. No real data needed.

In orbit: the demo program's 87 work packages. Orange ones have a parts-list difference.