Productized service first. Tech-enabled platform second. Pure SaaS third. In that order, not skipped.
The diagnostic that came out of Book 1, applied to NorthAI, gave a score of 45 out of 100 and a posture verdict of Overcorrection. Overcorrection is the third of three named failure modes for services firms trying to productize. It means attempting an overnight pivot from services to pure software. Three products positioned as enterprise SaaS, no FedRAMP, no ATO, no commercial credit-card-swipe entry path. Buyers love the product, cannot procure it. That is exactly the gap that came up on the call: “we’ve settled on the right pricing, but I don’t know that we’ve settled on a good easy entry path.”
The fix is not a different price. The fix is a different rung of the productization spectrum. Four levels: Level 1 is pure services, Level 2 is productized service (fixed scope, fixed price, IP-leveraged delivery), Level 3 is a tech-enabled platform with light services wrap, Level 4 is pure SaaS with self-serve and full credit-card acquisition. You skipped Levels 2 and 3 and landed on Level 4 positioning, which is why the entry path collapsed. Going back to Level 2 deliberately, building the recurring-revenue base there, and then earning the right to climb is the move.
Of NorthStar, Tech Vector, and Defense BD, our recommendation is to package Tech Vector first. Four reasons. First, the deliverable is the most tangible: a quarterly “universe pack” on a named technology area (say, directed energy weapons through 2030), produced on your machines with your data, delivered as a structured PDF plus a live point-of-contact arrangement for follow-up questions. The buyer gets the answer, not the tool. What came up on the call was: “they don’t have time to do this. They just want the answers, like give me the answers.”
Second, the engineering bar is the lowest of the three. Tech Vector already does guided-query construction at speed. The productized version is the same machinery with a controlled output template and a defined scope per engagement. NorthStar is more dependent on conversational interaction, which is harder to bound. Defense BD is more dependent on integration depth with the buyer’s internal planning systems, which is harder to ship in 30 days. Tech Vector ships in 30 days.
Third, the buyer set is already warm. Office of Directed Energy is the documented fan. The DIB policy office and the tech-transfer shops at OSD components fit the same profile. The “crickets” pattern that came up on the call dissolves when there is a CLIN they can put against a line item they already have authority to spend, instead of a SaaS subscription that requires a FedRAMP authorization they cannot fast-track.
Fourth, Tech Vector has the cleanest Phase III topic-alignment back to AF20C-TCSO1. The verbatim Phase I scope from USASpending: “discover a new method for identifying commercialization partners for government-funded research output using multiple, connected big data sets (patents, grants, financial) powered by artificial intelligence.” That is what Tech Vector does. The derives-from connection is textually direct. Of the three products, Tech Vector has the shortest derivation chain back to the predicate award. That means the CO action memo for a Phase III sole-source CLIN is easier to write, faster for a contracting officer to accept, and harder for a competitor to replicate. NorthStar and Defense BD extend the scope. Tech Vector derives from it. That distinction matters when a CO is deciding whether to sign.
Weeks 3-6 of the engagement: the productization roadmap. All three product lines mapped onto Level 2 SKU candidates, sequencing recommendation locked, scope and price ranges for the first SKU. Weeks 5-8: the FedRAMP path memo. The Watch page covers this in detail. The conclusion is that 20x LI-SaaS via the post-authorization sponsor model is now a parallel track to Level 2 revenue, not a prerequisite.
Weeks 6-12: first Level 2 SKU shipped to one to two named customers on existing CHN paper. Running in parallel, weeks 7-10, is the Phase III action-memo drafting workstream. This workstream produces three things: a derive-extend-complete mapping for each product against the Phase I scope of FA8649-21-P-0756, a CO action-memo template adapted to CHN's Phase I lineage under AF20C-TCSO1, and CO relationship-building briefs for the program office contacts already in the network. The action-memo workstream runs inside the same engagement. It does not add calendar time. It runs alongside the SKU ship.
Week 12 end-state: first contract booked. The frame matters. This is not a Level 2 productized-service SOW under an existing contracting vehicle in the conventional sense. This is a Phase III sole-source CLIN under CHN paper, backed by 15 U.S.C. 638(r)(4)(B), with a CO action memo on file. The raise-diligence anchor that starts climbing at week 12 is anchored to a federal sole-source award, not a services agreement that looks like any other T&M line. That distinction moves the multiple.