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
Caught before Cobra lines
Actual cost by element to Cobra
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.
- 1LOADYour exports
ERP extract, Cobra structure, parts list, schedule.
- 2CHECKMore than 100 checks
Rules on charge numbers, periods, hours, duplicates and parts.
- 3REQUESTRequests for finance
Your master parts list shows where material belongs; Stratholt™ drafts the JEV (journal entry) requests.
- 4TIE OUTTo the cent
Every dollar placed or set aside; the total matches the ERP.
- 5HAND OFFTo your Cobra team
Actuals, status and ETC files, ready to import. Labor ETC in hours, everything else in dollars.
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.
$64,724 charged by the ERP to a different work package
$6,893 that cannot be placed until assigned
parts in the master
5,020 from file
This period $121,477
This period $101,596
Non-labor ETC $156,096
Labor ETC 94 h, labor EAC 1,530 h (Cobra prices labor)
Labor VAC −140 h
Data date (the date the schedule was statused to): 2026-09-30 · expected 2026-09-30 Matches
2 activities with dates on the wrong side of the data date · 1 whose percent complete does not match its dates · 1 work package in progress with no cost
In Cobra, export the actual cost class with Integration › Assignment Export, once with hours and once with dollars. Upload both here; every work package, resource and period is compared with what Stratholt™ counts.
Spending $1.15 for every $1.00 of work done
▲ 0.01 from FY2026-P08
Spent $5,732,570 more than the work done is worth
▼ $115,229 from FY2026-P08
Budget 327,856 h · 10% more hours than budgeted
Hours only · Cobra prices labor
Budget $17,782,075 · $2,161,095 under (12.2%)
BAC as last loaded
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.
Made-up demo program, month-end FY2026-P09. The set-aside band is drawn thicker than its true size so it can be seen.
- ERP export19,402 cost lines read from the export$45,068,920
- 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
- Cobra actuals file87 work packages, by cost element$44,482,232
- 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.
- ✓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
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.
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.
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.