.NET / SQL / Enterprise Engineering
Technical Capture and Solution Evidence Support for Government Primes
Report summary
LongTermCapabilities should enter this market with a fixed-price, per-bid Technical Capture and Solution Evidence service , sold to government contractors from their bid-and-proposal budgets rather than directly to agencies. The first commercial objective should be a paid architecture-readiness revi
Key topics
- .NET / SQL / Enterprise Engineering
- .NET
- SQL
- Enterprise Engineering
- AI
- Runtime
- Research Archive
- Strategy
- Audit
Research provenance
For citation, use the report title and canonical URL. Archival presence does not establish authorship or promote report statements into portfolio evidence.
Source availability: 46 citation markers in the source export have no recoverable source links. Those markers are omitted from this reader; any supplied bibliography and ordinary links remain. Check the original sources before relying on the cited claims.
This page renders the archived Markdown as safe, formatted HTML. It is background research and does not become a portfolio claim without evidence review.
Full report
On this page
Executive judgment
LongTermCapabilities should enter this market with a fixed-price, per-bid Technical Capture and Solution Evidence service, sold to government contractors from their bid-and-proposal budgets rather than directly to agencies. The first commercial objective should be a paid architecture-readiness review or solution-evidence sprint attached to a named pursuit. A monthly capture-architecture retainer becomes credible only after a contractor has used the service successfully on at least two pursuits, while a preferred-partner or subcontract agreement should follow demonstrated working compatibility rather than precede it.
The strongest near-term market is among small and mid-sized digital-services contractors that have recently added or expanded access to government-wide acquisition contracts, indefinite-delivery vehicles, or agency-specific digital-services vehicles. GSA’s 8(a) STARS III remains available for new orders through July 1, 2029; OASIS+ is operational and supports rolling awards; Alliant 3 received notice to proceed on March 10, 2026; and several Polaris pools are now able to receive task orders. NASA announced SEWP VI awards in June 2026, with ordering expected to begin November 1, 2026. These developments create a recurring need to translate broad corporate capabilities into task-order-specific architectures, work plans, staffing rationales, acceptance criteria, and presentation evidence. They do not, by themselves, prove that any awardee is pursuing a particular order or needs outside help.
The most attractive initial partner targets are TCG, Coforma, RIVA Solutions, Bixal, Makpar, Fearless, Sparksoft, CivicActions, eSimplicity, and Brillient. Their public signals show relevant vehicle access, recent contract or vehicle activity, and service portfolios aligned with AI, cloud, data, cybersecurity, modernization, and software engineering. The analyst thesis is not that these firms lack technical architecture expertise. Rather, their reviewed public materials emphasize delivery capabilities, contract vehicles, and customer outcomes; the existence, capacity, and availability of a dedicated bid-architecture function remain unknown.
LongTermCapabilities should take no immediate action on firms where a bounded engagement cannot be connected to a named vehicle, active capture calendar, warm introduction, or funded bid-and-proposal work order. In particular, large contractors with extensive visible solution organizations, firms undergoing ownership integration, and contractors unable to identify an accountable capture executive should remain watch-list candidates.
Evidence, inference, unknowns, and decision boundaries
| Classification | Meaning in this report | Treatment |
|---|---|---|
| Verified public fact | A fact found in an official company source, official contract-vehicle page, SAM notice, USAspending record, procurement portal, or government regulation. | Cited and dated wherever the source provides a date. “Current page checked July 31, 2026” is used when an official page has no publication date. |
| Analyst inference | A bounded commercial or technical hypothesis derived from public facts, such as likely capture congestion after a new vehicle award. | Explicitly labeled as inference and never treated as buying intent, weakness, distress, or proof of deficient capabilities. |
| Unknown | Information not established by public evidence, including the contractor’s bid calendar, internal architecture capacity, bid-and-proposal budget, incumbent relationships, subcontract onboarding time, and willingness to use an external architect. | Must be resolved through a human discovery conversation or procurement diligence. |
| Required human decision | A LongTermCapabilities choice involving positioning, price floors, conflicts, delivery capacity, exclusivity, intellectual property, or sector concentration. | Must be decided before contracting or before expanding beyond a paid pilot. |
An existing contract award is evidence that a contractor operates in a relevant market; it is not open work. A place on an indefinite-delivery vehicle indicates eligibility to compete for qualifying task orders; it is not evidence that a task order is currently available or that the contractor intends to bid. A SAM sources-sought notice, request for information, draft solicitation, or broad agency announcement is a market signal whose current status must be rechecked in SAM immediately before any commercial approach.
Recent examples of relevant public market signals include the Defense Counterintelligence and Security Agency’s Mission Partner Program broad agency announcement covering digital skills, artificial intelligence, cybersecurity, and IT governance; a January 28, 2026 SUNet modernization notice; a March 9, 2026 Summit Data Platform notice; and a June 8, 2026 ITRP support notice. These demonstrate recurring government demand for the kinds of architectures and evidence LongTermCapabilities can help primes articulate, but their presence in this report does not mean that they remain open on July 31, 2026.
Federal organizational-conflict rules are especially important. FAR Subpart 9.5 directs contracting officials to identify, evaluate, avoid, neutralize, or mitigate significant potential organizational conflicts, particularly in management-support, consulting, and professional-services work. LongTermCapabilities therefore needs an opportunity-level conflict screen before receiving nonpublic requirements, competitor information, procurement-sensitive material, or incumbent artifacts.
Service and commercial architecture
The recommended offer is a Technical Capture and Solution Evidence package, not generic proposal writing. Its purpose is to make the prime’s proposed technical approach internally coherent, traceable to the solicitation, operationally credible, and easier for evaluators and oral-presentation panels to assess.
Bounded package structure
| Package | Scope and concrete deliverables | Fixed-price hypothesis | Estimated delivery effort and internal cost | Conservative gross margin |
|---|---|---|---|---|
| Architecture Readiness Review | Review one draft or final solicitation; requirement-to-response gap map; preliminary solution context diagram; top technical risks and dependencies; architecture evidence checklist; one executive readout. Maximum 150 pages of source material and two review meetings. | $8,500–$12,000, with a working midpoint of $10,000. | Approximately 32 hours. At an assumed fully loaded internal delivery cost of $165 an hour: $5,280 base cost or $6,336 with a 20% overrun. | Approximately 47% base and 37% with 20% overrun at the midpoint price. |
| Solution Evidence Sprint | Full requirement-to-solution traceability matrix; logical, deployment, integration, data, security, and operations architecture views as applicable; work breakdown and delivery sequence; risk and dependency register; evaluation and acceptance criteria; staffing-role rationale; transition outline; two facilitated reviews. | $22,000–$32,000, midpoint $27,000. | Approximately 90 hours. Cost: $14,850 base or $17,820 with 20% overrun. | Approximately 45% base and 34% with overrun. |
| Full Technical Capture Package | Everything in the sprint, plus alternative analysis, detailed transition and handoff plan, technical-management integration, oral-presentation storyline and rehearsal, evaluator-question bank, and independent red-team review. Maximum two architecture alternatives, two oral rehearsals, and two revision rounds. | $45,000–$65,000, midpoint $55,000. | Approximately 190 hours. Cost: $31,350 base or $37,620 with overrun. | Approximately 43% base and 32% with overrun. |
| Capture Architecture Bench | Up to 80 hours a month across a capped number of pursuits; reusable reference architecture maintenance; early solution shaping; reviews of task-order responses; architecture office hours; one oral rehearsal a month. Three-month initial term. | $22,000–$32,000 a month, midpoint $27,000. | Approximately 80 hours. Cost: $13,200 base or $15,840 with overrun. | Approximately 51% base and 41% with overrun. |
The $165 internal-cost assumption is not a verified LongTermCapabilities cost and must be replaced with actual principal compensation, benefits, nonbillable time, tools, insurance, and subcontractor costs. The price bands should be tested against official GSA labor-pricing data rather than presented as a universal government-contracting market rate. GSA’s Contract-Awarded Labor Category tool provides awarded hourly-price information, while OASIS+ pricing is generally negotiated at the order level.
FAR recognizes bid-and-proposal costs as costs incurred in preparing, submitting, and supporting bids and proposals. That makes a funded bid-and-proposal purchase order, consulting agreement, or subcontract a more credible commercial route than speculative work conditioned solely on contract award.
Best commercial model
The recommended progression is:
| Commercial stage | Recommended model | Rationale |
|---|---|---|
| First engagement | Fixed price for one named pursuit | Gives both parties a bounded test, measurable deliverables, and controlled conflict scope. |
| Repeated task-order activity | Monthly retainer with explicit hour and pursuit caps | Appropriate when the prime has recurring orders across STARS III, OASIS+, Polaris, Alliant 3, SPRUCE, SEWP VI, or a similar family. |
| Mature relationship | Preferred-partner agreement or indefinite-delivery subcontract with fixed call-off packages | Reduces onboarding friction while preserving a separate funded authorization for each pursuit. |
| Unqualified or very early lead | Paid readiness workshop only | Prevents LongTermCapabilities from producing a complete solution before the prime has qualified and funded the pursuit. |
| Contingent-fee-only proposal | Decline | Creates uncompensated delivery risk and can produce inappropriate incentives or compliance complications. |
Useful point in the capture cycle
The service has its highest value when engaged during qualified capture, roughly 45 to 120 days before a final solicitation, when architecture decisions can still affect teaming, staffing, demonstrations, transition assumptions, and pricing. It remains useful after a final solicitation when at least 12 to 15 business days remain and the prime has a stable compliance matrix, proposal owner, and authorized solution lead. With seven to fourteen business days remaining, LongTermCapabilities should sell only a tightly bounded readiness review or red-team intervention. With fewer than seven business days, it should decline unless the task is limited to reviewing an already-developed architecture.
Oral-presentation preparation is a legitimate part of the product because FAR allows oral presentations to substitute for or augment written proposal information and permits them at various points in the source-selection process. Federal oral-presentation guidance also contemplates work plans, staffing, transition approaches, and sample-task responses—the same elements that benefit from coherent technical architecture.
Reuse across task-order families
One technical architecture should not be copied unchanged across multiple bids. LongTermCapabilities can reuse non-customer-specific assets such as:
| Reusable asset | Must be recreated or substantially tailored |
|---|---|
| Architecture-view templates and notation | Requirement-to-solution traceability |
| Standard cloud, DevSecOps, data-platform, AI-governance, observability, and zero-trust patterns | Agency security boundaries, authorization assumptions, data classifications, and inherited controls |
| Generic work-breakdown structures | Solicitation-specific sequencing, milestones, dependencies, and acceptance criteria |
| Risk taxonomy and quality gates | Customer, incumbent, transition, staffing, and integration risks |
| Staffing archetypes | Labor-category mapping, clearance assumptions, location, availability, and named-key-person constraints |
| Oral-presentation frameworks | Evaluator-specific storyline, proof points, sample tasks, and likely questions |
The reusable asset should be treated as LongTermCapabilities’ pre-existing intellectual property. The prime should receive a license to use paid, bid-specific deliverables for the named opportunity and resulting contract, while LongTermCapabilities retains generalized patterns, templates, and methods.
Protection against unpaid speculative work
LongTermCapabilities should require an NDA and conflict screen before reviewing nonpublic material, followed by a funded purchase order, subcontract, or consulting statement of work before producing a bid-specific architecture. A free introductory meeting may explain the method and show redacted artifact fragments, but should not include a complete compliance map, customer-specific architecture, staffing model, or solution narrative.
Every order should specify input deadlines, page and document limits, one accountable prime-side solution owner, no more than two revision cycles, a stop-work right for delayed or materially changed inputs, and a change-order mechanism when the solicitation is amended. Payment terms should be 50% on authorization and 50% on delivery for an initial engagement, or net terms only after the partner has demonstrated reliable procurement administration. The minimum acceptable economics should be set so that a 20% delivery overrun still yields at least a 30% gross margin.
Partnerable procurement families
The following are procurement families or channels, not assertions of currently open work. Every task order, solicitation, pool eligibility rule, and due date must be verified at the time of pursuit.
| Procurement family | Verified status and date | Why it is partnerable | Appropriate LongTermCapabilities role | Open-work caution |
|---|---|---|---|---|
| 8(a) STARS III | GSA states that the vehicle is active, with new orders permitted through July 1, 2029 and performance potentially continuing through July 1, 2034. GSA reported more than 1,100 contract holders and billions of dollars in task-order activity. | Large population of small-business primes and recurring IT task orders creates a broad partner pool. | Task-order architecture sprint, independent red team, reusable cloud/data/DevSecOps patterns, and oral preparation. | Vehicle membership is not an open task order; an eligible prime and named order are still required. |
| OASIS+ Small Business and Unrestricted | OASIS+ has issued awards and notices to proceed, supports multiple professional-services domains, and includes continuing on-ramping and official 2026 program resources. | Technical and Engineering, Research and Development, and Management and Advisory domains can involve complex delivery architectures and cross-functional work plans. | Architecture/evidence layer inside a larger management, engineering, or research response. | OASIS+ is not primarily an IT commodity vehicle; the service must support a qualifying domain and order scope. |
| Alliant 3 | GSA issued notice to proceed on March 10, 2026, making the vehicle available for orders. GSA also publishes vehicle and labor-pricing resources. | New ordering activity can force awardees to operationalize broad proposals into task-order-specific solutions. | Early task-order solution shaping, cross-domain architecture, risk and acceptance evidence, oral support. | Access difficulty will be higher because many awardees have mature solution organizations. |
| Polaris | GSA authorized task-order activity in the HUBZone and service-disabled-veteran-owned pools beginning December 2, 2025 and the women-owned pool beginning March 9, 2026; additional pool activity continued in 2026. | Small-business pool structure creates direct relevance to mid-sized and specialist primes. | Fixed-price solution-evidence sprint or preferred technical-capture subcontract. | Pool membership, socioeconomic eligibility, and order status must be checked for every target. |
| NASA SEWP VI | NASA announced awards on June 22, 2026. The planned ordering period begins November 1, 2026 and extends through October 31, 2036, subject to transition and program implementation. | Awardees are preparing partner ecosystems, solution catalogs, architectures, and response operations before ordering begins. | Pre-order reference architectures, partner-solution integration, evidence templates, and task-order readiness. | This is a transition and preparation opportunity as of July 31, 2026—not evidence of an already-issued SEWP VI order. |
| VA SPRUCE | The Department of Veterans Affairs describes SPRUCE as a vehicle connecting the VA with service-disabled-veteran-owned small businesses for high-quality digital products and services. | Digital product, platform, modernization, data, and reliability work is closely aligned with LongTermCapabilities’ practice. | Product-platform architecture, modernization sequencing, nonfunctional requirements, transition, and acceptance criteria. | Participation and task-order access are limited to eligible contractors and their permitted teams. |
| Army ITES-3S | The Army’s ITES-3S vehicle runs through September 24, 2027 and covers cybersecurity, enterprise design and integration, network operations, business-process reengineering, and related services. | Remaining ordering runway and broad enterprise scope can support technical-capture engagements with existing prime holders. | Architecture red team, enterprise integration model, migration sequencing, and operational acceptance plan. | Shorter remaining ordering horizon makes this a targeted, near-term pursuit rather than a long-term platform investment. |
| Missile Defense Agency SHIELD | SHIELD is a large, multi-award defense vehicle with awards announced beginning in late 2025; public awardee announcements describe a ten-year, $151 billion ceiling. | Large and technically complex task orders can require integrated systems, software, cybersecurity, analytics, and engineering narratives. | Independent architecture challenge, risk/dependency analysis, WBS integration, and oral red team. | Classified requirements, export controls, organizational conflicts, facility clearances, and incumbent knowledge may sharply restrict participation. |
| CIO-SP3 Small Business | Official contractor pages show ordering and performance periods approaching their end in late October 2026. | There may be late-stage task orders, extensions, or transition work among existing holders. | Review-only, transition, or recompete support. | Do not invest in a long-term vehicle-specific offering; use only for a named near-term pursuit. |
| Chicago Department of Procurement Services bid families | Chicago’s Department of Procurement Services is the city contracting authority and publishes contracts accepting bids through its regularly updated Bid Opportunity List. | Local IT, data, cybersecurity, cloud, application, and professional-services bids can be reached through established municipal primes, certified firms, and technology partners. | Technical volume architecture, implementation sequencing, subcontractor integration, oral/interview support, and acceptance framework. | The recurring portal is an active channel, but no specific Chicago IT opportunity should be represented as open without checking the current list and solicitation documents. |
The highest-value family combination for the first year is STARS III, OASIS+, Polaris, SPRUCE, and pre-order SEWP VI readiness. Alliant 3 and SHIELD offer greater potential contract value but generally involve harder access, stronger incumbent solution organizations, and higher compliance or conflict burdens. CIO-SP3 should receive only opportunistic attention because of its limited remaining runway.
Potential prime and subcontract partners
The following ranking combines fit, public-evidence quality, probable speed to a paid pilot, likely bid scale, potential for repeated work, delivery risk, and access difficulty. It is not a win probability. “Architecture complement” means a possible externally supplied capture function; it does not mean the contractor lacks internal technical expertise.
The package abbreviations are Review for the $8,500–$12,000 Architecture Readiness Review, Sprint for the $22,000–$32,000 Solution Evidence Sprint, Full for the $45,000–$65,000 Full Technical Capture Package, and Bench for the $22,000–$32,000 monthly retainer.
| Rank and organization | Verified public signal and evidenced operating change | Analyst inference, likely problem, and buyer titles | Smallest credible paid engagement and economics | Route, cycle, validation, unknowns, and no-go |
|---|---|---|---|---|
| TCG | TCG’s official contract portfolio includes OASIS+ Unrestricted, CIO-SP3, FCC ADSS, SHIELD, and other vehicles. The company announced a NASA SEWP VI award on June 30, 2026. | Inference: A new SEWP VI position alongside multiple existing vehicles may create demand for reusable solution patterns and surge support across task-order responses. Likely buyers: Chief Growth Officer, Vice President of Capture, Chief Technology Officer or Vice President of Solutions, SEWP Program Manager, Proposal Director. | Review, 32 hours, midpoint $10,000, assumed cost $5,280, 37%–47% margin depending on overrun. Deliver a SEWP VI task-order readiness map, architecture evidence checklist, one representative solution view, and reuse plan. | Direct B&P-funded subcontract; probable cycle three to eight weeks. Validate through one targeted partner-development conversation about SEWP VI readiness and one paid review. Unknown: internal SEWP solution bench and partner onboarding. Decision: prioritize only with a named solution family. No-go: request for an unfunded catalog or complete sample response. |
| Coforma | Coforma’s official contracting page lists VA SPRUCE, OASIS+, NASA SEWP VI, GSA MAS IT, and an OPM BPA, and identifies the company as an 8(a) and service-disabled-veteran-owned small business. Page checked July 31, 2026. | Inference: Its combination of digital-service delivery and multiple vehicles makes independent bid architecture or overflow capacity plausible, particularly when several pursuits overlap. Buyers: Head or Vice President of Growth, Capture Director, Technical Strategy lead, Proposal Director, vehicle program managers. | Sprint, approximately 90 hours at a $27,000 midpoint, $14,850 base cost, 34%–45% margin. Include traceability, application/data/cloud architecture, WBS, risks, acceptance criteria, staffing rationale, and transition. | Direct partner or referral-led subcontract; likely cycle two to six weeks for a named pursuit. Validate by offering a paid SPRUCE or OASIS+ architecture sprint against one real solicitation. Unknown: internal capacity and pursuit timing. No-go: no accountable solution owner or expectation that LongTermCapabilities writes the entire proposal. |
| RIVA Solutions | RIVA states that it has 16 prime contract vehicles and lists OASIS+ Unrestricted among them. It announced a NASA SEWP VI award on July 8, 2026, with the vehicle expected to extend through 2036. | Inference: Vehicle expansion increases the operational burden of maintaining current solution evidence and preparing task-order-specific architectures. Buyers: Chief Growth Officer, Vice President of Business Development, Vice President of Solutions, SEWP Program Manager, Contracts Director. | Review first; upgrade to Bench only after a paid pilot. Review deliverables should focus on a representative task-order family, evidence gaps, integration boundaries, and reusable artifacts. | Direct or subcontract route; three to eight weeks plus vendor onboarding. Validate with a SEWP VI pre-order architecture review. Unknown: whether RIVA already has a centralized solutions office. No-go: broad exclusivity across the entire SEWP program or unpaid partner-solution integration. |
| Bixal | Bixal announced an OASIS+ Small Business award on December 19, 2024, contract 47QRCA25DSC85, and also publicly identifies 8(a) STARS III access. | Inference: Its digital-transformation work can benefit from a rigorous bridge between user-centered delivery, platform architecture, evaluation evidence, and task-order execution plans. Buyers: Chief Growth Officer, Capture Director, Chief Technology Officer, Digital Transformation Practice Lead, Proposal Director. | Sprint, 70–100 hours, $22,000–$32,000. Produce the full evidence package with special attention to product/platform architecture, measurable outcomes, transition, and nonfunctional requirements. | Direct paid subcontract or referral through an existing proposal partner; two to six weeks. Validation target: one OASIS+ or STARS III pursuit. Unknown: current capture volume and internal architecture bandwidth. No-go: no access to evaluation factors or requirement baseline. |
| Makpar | Makpar’s official pages list STARS III, GSA MAS, and agency experience across IRS, Labor, Interior, Agriculture, and USCIS, alongside cloud, data, automation, and AI-ready architecture capabilities. Page checked July 31, 2026. | Inference: Because Makpar already presents architecture capability, the most credible offer is independent red-team evidence and surge support, not replacement solution design. Buyers: Chief Growth Officer, Capture Vice President, Chief Technology Officer, Quality or Delivery Executive, Proposal Director. | Review, emphasizing independent challenge, requirement coverage, evaluator evidence, dependencies, and acceptance criteria. 24–36 hours, midpoint $10,000. | Direct B&P purchase order; two to five weeks. Validate with an independent architecture red team on a named task order. Unknown: willingness to use an external reviewer. No-go: positioning that implies Makpar lacks architecture competence or pricing below the review floor. |
| Fearless | Fearless publicly announced work under Maryland’s ADEPT program on September 16, 2025, a House IT staff-augmentation award on January 28, 2025, and an OASIS+ teaming relationship with Coforma in November 2024. | Inference: Movement across federal, state, and legislative markets may create a need to normalize architecture evidence and transition plans across different procurement formats. Buyers: Growth Executive, Capture Director, Chief Technology Officer, Director of Government Solutions, Proposal Lead. | Sprint for a named state or federal pursuit. Emphasize traceability, delivery increments, platform boundaries, operational reliability, staffing rationale, and acceptance tests. | Direct or referral route; two to six weeks. Test one jointly selected ADEPT, OASIS+, or federal digital-services pursuit. Unknown: pursuit calendar and architecture staffing. No-go: staff-augmentation-only work with no bounded technical volume or deliverable. |
| Sparksoft | Sparksoft’s official contract pages list OASIS+, STARS III, CMS SPARC, CIO-SP3, Polaris, and SeaPort-NxG. | Inference: A large set of vehicles can generate recurring task-order capture needs and justify a reusable evidence library. Buyers: Chief Growth Officer, Vice President of Capture, Chief Technology Officer, GWAC Program Director, Proposal Director. | Sprint first, with a path to Bench after two pursuits. Initial deliverables should include one family-level reference architecture and one fully tailored task-order evidence set. | Direct preferred-partner route; four to ten weeks because of vehicle breadth and onboarding. Unknown: centralization of capture and current bid volume. No-go: retainer before a successful fixed-price pilot or unlimited concurrent pursuits. |
| CivicActions | CivicActions’ official contracting page identifies it as a small business with prime contracting access and extensive public-sector open-source, Drupal, US Web Design System, and data-platform experience. Page checked July 31, 2026. | Inference: Open-source and user-centered delivery narratives may benefit from more formal requirement traceability, cloud/security boundaries, operations models, and evaluator-ready acceptance evidence. Buyers: Growth Lead, Capture Manager, Chief Technology Officer, Federal Practice Director, Proposal Lead. | Review or a narrowly scoped Sprint. The review should add architecture discipline without displacing the company’s product and open-source strengths. | Direct small-business partner or referral route; two to five weeks. Validate on one federal or municipal digital-platform pursuit. Unknown: appetite for external capture support. No-go: commodity staff augmentation or a request limited to writing prose without architecture authority. |
| eSimplicity | eSimplicity’s official OASIS+ materials identify Technical and Engineering and Management and Advisory access. On July 20, 2026, the company announced a roughly $40 million CMS QDAS II award involving data, analytics, and DevSecOps. | Inference: Recent award execution plus OASIS+ pursuit activity may create temporary capacity conflicts between delivery architecture and new capture. Buyers: Chief Growth Officer, Capture Vice President, Chief Technology Officer, Data or DevSecOps Practice Lead, Proposal Director. | Review as an independent red team, 24–36 hours. Deliver requirement gaps, architecture consistency findings, acceptance-test gaps, and a prioritized correction list. | Direct or referral-led; two to six weeks. Validate by asking whether delivery leaders are being pulled into OASIS+ capture. Unknown: internal separation of delivery and solutioning. No-go: assumption that the recent award implies distress or lack of capacity. |
| Brillient | Brillient publicly identifies OASIS and digital-transformation capabilities and announced participation in the Missile Defense Agency’s SHIELD vehicle. | Inference: SHIELD task orders may require stronger integration among technical architecture, systems engineering, analytics, cybersecurity, staffing, and risk evidence. Buyers: Chief Growth Officer, Defense Capture Vice President, Chief Technology Officer, SHIELD Program Manager, Proposal Director. | Sprint, with a likely $27,000 midpoint. Include systems context, integration dependencies, technical WBS, acceptance criteria, staffing rationale, and oral-question preparation. | Direct subcontract or referral from a defense capture consultancy; four to ten weeks. Unknown: clearance and controlled-information requirements. No-go: classified or export-controlled access that LongTermCapabilities cannot lawfully support, or unresolved OCI. |
| Oddball | Oddball’s official contracting page lists VA SPRUCE and CEDAR, CMS ACME, SEC, HHS, Air Force, OPM, and other federal contracting channels. | Inference: A broad digital-services portfolio may occasionally need external surge capacity or independent architecture review, especially across simultaneous health and civilian pursuits. Buyers: Growth Executive, Capture Director, Chief Technology Officer, Solutions Director, Proposal Director. | Review, focused on evaluator traceability, platform boundaries, reliability and security evidence, transition, and staffing consistency. | Direct paid pilot; two to six weeks. Unknown: internal technical-capture depth. No-go: generic outreach without a named pursuit or positioning as a replacement for the company’s delivery leadership. |
| Agile Six | Agile Six’s official capabilities page describes full-spectrum digital modernization, including product, engineering, cloud, data, and related government delivery. USAspending records show prior VA prime-contract activity. | Inference: The best fit is independent review or temporary capture architecture, not broad delivery consulting. Buyers: Growth or Partnerships Executive, Capture Lead, Chief Technology Officer, Engineering Executive, Proposal Lead. | Review, with a modernization traceability map, architecture gap assessment, nonfunctional-requirements check, and acceptance evidence. | Direct or referral route; two to five weeks. Unknown: current eligible vehicles and bid cadence. No-go: no current procurement route, no named pursuit, or engagement economics below the review floor. |
| Highlight Technologies | Highlight announced an Air Force EWAAC award on May 21, 2025. The ten-year vehicle has a stated $46 billion ceiling and includes open architecture, analytics, engineering, and related capabilities. | Inference: EWAAC task orders can require technically integrated solution and evidence packages even where the contractor has internal engineering strength. Buyers: Chief Growth Officer, Air Force Capture Vice President, Chief Technology Officer, EWAAC Program Manager, Proposal Director. | Sprint or independent Review, depending on task-order maturity. Focus on open-system boundaries, integration, delivery sequencing, risk, and acceptance. | Direct subcontract; four to ten weeks. Unknown: task-order pipeline and internal EWAAC solution bench. No-go: controlled or classified scope beyond capability, or a request to work for competing teams on the same order. |
| Gunnison Consulting Group | Gunnison’s current vehicle page lists its government contracting access. The company announced a House digital-services IDIQ running through 2028 and a $26.6 million State Department cybersecurity award in November 2024. | Inference: Parallel digital and cybersecurity pursuits could benefit from a common architecture-evidence method and independent technical red team. Buyers: Chief Growth Officer, Capture Director, Chief Technology Officer, Cybersecurity Practice Lead, Proposal Director. | Sprint for a named pursuit; deliver traceability, cloud/security architecture, operating model, risk register, acceptance criteria, and transition. | Direct or referral route; three to eight weeks. Unknown: whether current pursuits are solution-based or primarily staffing. No-go: labor-only requirement with no bounded solution architecture. |
| NetImpact Strategies | NetImpact’s official vehicle portfolio includes OASIS+, MAS, SeaPort-NxG, a USPTO BPA, FDIC ordering arrangements, and CIO-SP3. Its FDIC materials describe ServiceNow and enterprise-platform work. | Inference: Enterprise-platform and workflow bids may need independent evidence connecting platform configuration, integration, data, security, operations, and acceptance. Buyers: Chief Growth Officer, Capture Vice President, Chief Technology Officer, Platform Practice Lead, Proposal Director. | Review, with an option to expand into a Sprint. Initial deliverables: requirement coverage, platform/integration architecture review, transition risks, and acceptance-test gaps. | Direct partner route; four to eight weeks. Unknown: internal platform-solution staffing. No-go: expectation of proprietary platform implementation work without appropriate specialists. |
| Kentro | Kentro’s official site reflects the rebrand from IT Concepts and lists Polaris SDVOSB, OASIS+, GSA MAS, HCaTS, and STARS III among its vehicles. Page checked July 31, 2026. | Inference: Rebranding and a broad vehicle portfolio may create a period in which corporate capabilities need to be translated consistently into new task-order solution evidence. This is not evidence of operational weakness. Buyers: Chief Growth Officer, Capture Vice President, Chief Technology Officer, Vehicle Program Managers, Proposal Director. | Sprint, with a family-level reference architecture and one bid-specific tailoring. | Direct subcontract; four to ten weeks. Unknown: effect of rebrand on capture processes and current workload. No-go: treating rebrand as distress, or proposing brand work rather than technical capture. |
| Technica | Technica’s official contract page lists OASIS+ Unrestricted and multiple federal vehicles and explicitly states that it participates in teams as a subcontractor. | Inference: Its visible openness to teaming creates a credible partner route, though its own technical depth means independent review is more plausible than primary architecture creation. Buyers: Growth Executive, Capture Vice President, Chief Technology Officer, Partner Alliance Lead, Proposal Director. | Review, especially for cross-company integration, cybersecurity, operations, and risk evidence. | Partner or reciprocal subcontract route; four to eight weeks. Unknown: willingness to purchase external capture architecture. No-go: reciprocal arrangement that requires unpaid work or conflicting commitments. |
| NewWave | NewWave’s official pages describe federal contract vehicles and capabilities in data, analytics, cloud, AI, and digital modernization. Page checked July 31, 2026. | Inference: Data and AI bids may benefit from stronger model-governance, data-lineage, deployment, monitoring, and acceptance evidence. Buyers: Chief Growth Officer, Capture Director, Chief Technology Officer, Data and AI Practice Lead, Proposal Director. | Review, with a data/AI architecture and evidence checklist; expand to Sprint only for a named pursuit. | Direct paid pilot; two to six weeks. Unknown: current active vehicles and AI-bid calendar. No-go: using historic vehicle information as proof of present access or making unsupported AI performance claims. |
| Dev Technology Group | Dev Technology’s official site describes mission-critical IT work for homeland security, law enforcement, and defense customers. Page checked July 31, 2026. | Inference: Mission-critical bids may need independent reliability, integration, transition, and acceptance review, but public evidence of a current partnerable vehicle or named pursuit is limited. Buyers: Growth Executive, Capture Director, Chief Technology Officer, Mission Solutions Director. | Review only after a named pursuit is identified. | Referral-led route is preferable; three to eight weeks. Unknown: current bid pipeline and subcontract onboarding. Human decision: keep as watch-list until a concrete route emerges. No-go: cold pursuit without vehicle and opportunity confirmation. |
| Excella | Excella’s official contracting page lists CIO-SP3, GSA MAS, a FERC BPA, and other channels. Its USCIS DID(it) award announced in March 2022 had a five-year period and a potential value of $116.6 million. | Inference: The likely fit is an independent modernization red team or recompete architecture review, not routine delivery architecture. Buyers: Growth Executive, Capture Director, Chief Technology Officer, Federal Practice Lead, Proposal Director. | Review, particularly for recompete differentiation, transition, modernization sequencing, and measurable acceptance. | Direct or referral route; three to eight weeks. Unknown: current recompete plans and internal capture capacity. No-go: reliance on the historic award without evidence of a current pursuit. |
| Dynamo Technologies | Dynamo’s official site describes federal technology and mission support. GSA records show an active MAS contract with options extending well into the next decade, and USAspending shows federal prime-contract activity. | Inference: Long-term vehicle access can support recurring capture, but Dynamo’s present small-business status, internal architecture depth, and near-term pipeline need confirmation. Buyers: Chief Growth Officer, Capture Vice President, Chief Technology Officer, Contracts Director. | Review attached to a named MAS or agency pursuit. | Direct or referral route; four to eight weeks. Unknown: socioeconomic and vehicle positioning relevant to the target order. No-go: pursuit dependent on an outdated size-status assumption. |
| Sev1Tech | Sev1Tech’s official portfolio lists OASIS+, SeaPort-NxG, ASTRO, and other government-wide channels, and the company maintains an Alliant 3 vehicle page. | Inference: Alliant 3 and other broad vehicles provide recurring potential, but the company likely has substantial internal solution depth. Buyers: Chief Growth Officer, Capture Vice President, Chief Technology Officer, Alliant Program Manager, Proposal Director. | Independent Review only, unless a specific overflow need is disclosed. | Referral or subcontract route; six to twelve weeks. Unknown: internal solution capacity. No-go: generic offer without senior sponsorship or a named task order. |
| MetroStar | MetroStar updated its official contract-vehicle portfolio on July 14, 2026; it includes CDAO artificial-intelligence channels, ITES-3S, DIA SITE III, SHIELD, OASIS+, and other major vehicles. Its OASIS+ contract runs from 2024 into 2034. | Inference: There is substantial recurring bid volume, but visible technical depth and scale make LongTermCapabilities an overflow or independent-red-team supplier rather than a core solution architect. Buyers: Chief Growth Officer, Senior Capture Executive, Chief Technology Officer, Vehicle Portfolio Executive. | Review only, preferably through a trusted referral. | Referral or specialist subcontract; six to sixteen weeks. Unknown: external-specialist procurement policy. No-go: cold outreach, no named surge, or pursuit requiring broad exclusivity. |
| REI Systems | REI’s official vehicle portfolio includes Alliant 2, CIO-SP3, STARS III, OASIS+, and SeaPort-NxG. The company announced a SHIELD award on December 16, 2025. | Inference: REI’s scale and visible solution capability lower the likelihood of needing primary architecture, but independent red-team or cross-team integration support may still be useful. Buyers: Chief Growth Officer, Capture Vice President, Chief Technology Officer, SHIELD or OASIS+ Program Manager. | Review, scoped to one high-complexity pursuit. | Referral or subcontract; six to twelve weeks. Unknown: approved consultant pool and conflict rules. No-go: no internal executive sponsor or request for extensive free prequalification work. |
| Easy Dynamics | Easy Dynamics announced a Treasury TTB identity, credential, access-management, and cloud task in November 2024 and a $50 million USDA recompete award in June 2025. The company’s official materials place it in the 100–199 employee range in 2026. | Inference: Cybersecurity and identity bids may benefit from independent acceptance, dependency, transition, and operations evidence, but the firm’s specialist depth means the offer must be additive. Buyers: Chief Growth Officer, Capture Director, Chief Technology Officer, Identity or Cloud Practice Lead. | Review, focused on architecture consistency and evidence rather than primary ICAM design. | Direct or referral route; four to eight weeks. Unknown: current capture load. No-go: representing recent awards as proof of strain or attempting to displace domain specialists. |
| ShorePoint | ShorePoint’s official material identifies GSA MAS and Highly Adaptive Cybersecurity Services access. In January 2025 the company reported substantial prime awards and workforce growth. | Inference: Cyber task orders may create a need for independent technical-volume review, but strong specialist positioning reduces fit for general architecture creation. Buyers: Chief Growth Officer, Capture Executive, Chief Technology Officer, Cyber Solutions Vice President. | Review, emphasizing zero-trust boundaries, operations, transition, dependencies, and acceptance. | Referral route; four to ten weeks. Unknown: internal solution bench and current vehicle pipeline. No-go: inferred distress from growth, or unsupported claims about vulnerability or security posture. |
| Alpha Omega | Alpha Omega’s official portfolio includes GSA cloud channels, OASIS+, DIA SITE III, SeaPort-NxG, and other federal vehicles. The company has also announced acquisitions and continued expansion through 2025 and 2026. | Inference: Acquisition and portfolio expansion may generate occasional integration or surge needs, but visible scale and architecture capability lower the baseline fit. Buyers: Chief Growth Officer, Integration Executive, Capture Vice President, Chief Technology Officer. | Review only after referral or disclosure of a specific surge. | Referral/subcontract route; six to sixteen weeks. Unknown: preferred-vendor and post-acquisition operating model. No-go: treating acquisition as distress or offering an undifferentiated architecture service. |
| BryceTech | BryceTech publicly announced access to the Space Force’s Hemisphere vehicle, described as a ten-year vehicle with a $2.5 billion ceiling. | Inference: Space and defense task orders may require cross-disciplinary architecture and evidence, but domain, clearance, and access requirements increase delivery risk. Buyers: Chief Growth Officer, Space Capture Vice President, Chief Technology Officer, Hemisphere Program Manager. | Review limited to unclassified, releasable material and a named order. | Referral or subcontract; eight to sixteen weeks. Unknown: clearances, controlled information, and internal solution depth. No-go: classified scope, export restrictions, or no cleared prime-side solution owner. |
| Steampunk | USAspending records and company announcements show Department of Homeland Security contract activity, including a 2024 award. | Inference: DHS modernization work is relevant, but the reviewed public evidence is insufficient to identify a current, bounded partner route or architecture-capacity gap. Buyers, if a route emerges: Chief Growth Officer, DHS Capture Executive, Chief Technology Officer. | Review only with a named opportunity and referral. | Referral-led, likely six to twelve weeks. Unknown: present vehicle access, capture priorities, and external-consultant policy. Required decision: no proactive investment beyond light monitoring. No-go: outreach based only on a historic award. |
| Raft | Raft announced selection for the Space Force Kronos program on July 14, 2026. On July 28, 2026, it announced an agreement to be acquired by Leonardo DRS. | Inference: Ownership transition could alter procurement authority, partner policy, and capture ownership. It must not be treated as distress or immediate buying intent. | No immediate offer. After integration ownership is clear, a paid Review could be considered for an unclassified named pursuit. | Referral only; likely more than three months. Unknown: transaction close, operating autonomy, vendor onboarding, and solution ownership. Required decision: pause. No-go: approaching the company on the premise that acquisition creates a capability gap. |
Candidates requiring no immediate action
The firms ranked below the top twenty should not receive cold, generic business-development activity. MetroStar, REI Systems, Sev1Tech, Easy Dynamics, ShorePoint, Alpha Omega, BryceTech, Steampunk, and Raft should be approached only through a credible referral, a named pursuit, or a disclosed surge requirement. Dev Technology and Dynamo should remain conditional until current vehicle and pursuit access are verified.
This “no immediate action” recommendation is commercial discipline, not a negative assessment of those organizations.
Ranked opportunity portfolio
Scores below are analyst judgments on a five-point scale. For delivery risk, five means relatively lower risk. For access, five means comparatively easier access. They are prioritization aids, not probabilities or forecasts of a contract award.
| Rank | Partner opportunity | Fit | Public evidence | Speed to revenue | Contract value | Recurring potential | Low delivery risk | Access | Recommended action |
|---|---|---|---|---|---|---|---|---|---|
| 1 | TCG: SEWP VI and multi-vehicle solution readiness | 5 | 5 | 4 | 5 | 5 | 4 | 3 | Seek a paid SEWP VI readiness review, then propose a capped bench arrangement. |
| 2 | Coforma: SPRUCE, OASIS+, and SEWP VI digital-services capture | 5 | 5 | 4 | 4 | 5 | 4 | 4 | Lead with one named digital-services sprint. |
| 3 | RIVA Solutions: SEWP VI partner and task-order architecture | 5 | 5 | 4 | 5 | 5 | 4 | 3 | Offer a fixed pre-order architecture review with strict IP boundaries. |
| 4 | Bixal: OASIS+ and STARS III solution evidence | 5 | 5 | 4 | 4 | 4 | 4 | 4 | Pursue a paid sprint through growth or capture leadership. |
| 5 | Makpar: independent architecture red team | 5 | 4 | 4 | 4 | 4 | 4 | 4 | Position as independent assurance, not replacement architecture. |
| 6 | Fearless: cross-market digital-services evidence | 5 | 4 | 4 | 4 | 4 | 4 | 4 | Test one federal or Maryland pursuit. |
| 7 | Sparksoft: recurring multi-vehicle task-order support | 5 | 5 | 3 | 5 | 5 | 4 | 2 | Seek a senior-sponsored pilot; avoid broad retainer before proof. |
| 8 | CivicActions: formal architecture evidence for open-source delivery | 5 | 4 | 4 | 3 | 4 | 4 | 4 | Offer a compact review on one digital-platform bid. |
| 9 | eSimplicity: delivery/capture overflow and independent review | 4 | 5 | 4 | 5 | 4 | 3 | 3 | Validate whether recent delivery commitments are drawing on solution staff. |
| 10 | Brillient: SHIELD and complex systems evidence | 4 | 4 | 3 | 5 | 4 | 3 | 3 | Pursue only unclassified work with a completed conflict screen. |
| 11 | Highlight Technologies: EWAAC task-order evidence | 4 | 5 | 3 | 5 | 5 | 3 | 2 | Seek referral access to the EWAAC capture organization. |
| 12 | NetImpact Strategies: enterprise-platform task-order review | 4 | 5 | 3 | 5 | 5 | 3 | 2 | Offer independent platform/integration evidence review. |
The best balance of speed and fit is likely to come from one small digital-services contractor and one recently expanded vehicle holder, rather than pursuing only the largest potential contracts. A $10,000 readiness review that can be authorized in three weeks is strategically more useful for market validation than a theoretically larger SHIELD or Alliant opportunity requiring months of onboarding, clearances, and internal approvals.
The recurring-revenue thesis should be considered validated only when a partner has all of the following: at least three qualified technical pursuits per quarter, a capture executive who can authorize work, a repeatable need for architecture artifacts, and willingness to reserve a funded monthly capacity block. Without those conditions, per-bid fixed pricing remains superior.
Market validation, relationship development, and required decisions
Relationship-development plan for the next thirty days
| Period | Activities | Required output | Stop condition |
|---|---|---|---|
| Days one through three | Finalize a two-page service brief, package pricing, redacted sample traceability matrix, redacted architecture views, sample risk register, NDA, short-form subcontract statement of work, conflict questionnaire, and intellectual-property schedule. Establish a one-page qualification rubric covering named opportunity, due date, contract vehicle, prime role, capture owner, budget authority, source-material availability, and conflict status. | Sales-ready package with no customer-confidential content and no free customer-specific solution. | Do not initiate discussions until the minimum price, loaded cost, contracting entity, insurance, and conflict policy have been decided. |
| Days four through ten | Select twelve hand-researched organizations: the top ten candidates plus two referral-accessible alternatives. Use public corporate business-development channels, official partner portals where available, and warm professional referrals. Contact titles rather than compiling personal information. Lead with a specific vehicle or solution family and a paid review, not a generic capability pitch. | Twelve individually prepared approaches and at least four substantive conversations scheduled. | Stop outreach to any organization where no relevant vehicle, named family, or credible referral can be established. |
| Days eleven through seventeen | Conduct structured discovery covering pursuit cadence, current solution process, architecture bottlenecks, oral-presentation frequency, approval authority, subcontract onboarding, and conflict boundaries. Ask for no nonpublic solicitation material until an NDA and conflict screen are complete. | Six completed discovery interviews, two qualified paid-review proposals, and a written record of recurring objections. | No free architecture workshops. End conversations where the contractor will discuss only contingent compensation or seeks a complete technical concept before authorization. |
| Days eighteen through twenty-three | Deliver up to two paid Architecture Readiness Reviews. Track actual hours by artifact, input delays, revision volume, decision-maker attendance, and whether the prime incorporated the findings into its technical approach. | Two completed paid pilots or, if only one is sold, one completed pilot plus a documented reason the second did not convert. | Invoke change control when source material exceeds limits, the solicitation changes materially, or more than two review cycles are requested. |
| Days twenty-four through thirty | Conduct post-engagement reviews, quantify which deliverables were used, and offer either a Solution Evidence Sprint for the next pursuit or a three-month capped bench arrangement. Decide which procurement families and partner types merit continued investment. | One follow-on paid engagement or retainer proposal, a revised price model based on actual hours, and a go/no-go decision for the market. | Do not continue broad market development after twelve qualified conversations if no organization will fund even the smallest bounded review. |
The experiment should measure commercial behavior, not subjective enthusiasm. Relevant measures are the number of qualified conversations, proportion that disclose a named capture calendar, time from first substantive conversation to funded authorization, average review effort, revision burden, effective gross margin, and proportion requesting another paid engagement. A request for a proposal, verbal interest, vehicle award, recent contract win, or invitation to an unpaid teaming call is not revenue validation.
Required human decisions before launch
| Decision | Recommended starting position |
|---|---|
| Target concentration | Concentrate the first cycle on civilian digital services, health, data, cloud, and modernization. Accept defense work only when unclassified, bounded, and conflict-compatible. |
| Minimum price | Do not sell the standard review below $8,500 without reducing scope. Do not accept work projected to fall below a 30% gross margin under a 20% overrun. |
| Delivery capacity | Cap the initial experiment at two simultaneous reviews or one sprint. Do not sell the monthly bench until capacity has been demonstrated. |
| Exclusivity | Limit exclusivity to the named solicitation or task order and a defined period. Reject agency-wide, vehicle-wide, or technology-wide exclusivity unless separately compensated. |
| Conflict ownership | Assign one principal to maintain the opportunity conflict register and approve every new engagement. Seek government-contracts counsel for ambiguous OCI situations. |
| Intellectual property | Retain pre-existing templates, reference architectures, methods, and generalized improvements. License paid bid-specific artifacts to the partner for the named pursuit and resulting performance. |
| Payment terms | For new partners, require 50% at authorization and 50% on delivery, or an irrevocably funded purchase order with acceptable terms. |
| Subcontract route | Prefer a direct B&P-funded consulting subcontract. Use referral relationships to obtain access, but do not let a referral intermediary control technical scope or create undisclosed conflicts. |
| Municipal positioning | Use Chicago’s recurring procurement portal for opportunity discovery and local partner mapping, but do not claim municipal specialization until LongTermCapabilities has completed at least one municipal bid engagement. |
| Evidence standard | Describe architecture depth as unknown unless directly established. Never infer distress, urgency, vulnerability, or deficient personnel from hiring, incidents, financing, awards, acquisitions, or restructuring. |
Portfolio-level no-go rules
LongTermCapabilities should decline or stop an opportunity when there is no named or reasonably bounded procurement; no prime-side capture owner; no access to the solicitation’s requirements and evaluation criteria; fewer than seven business days remain and the requested scope exceeds review; work is contingent solely on award; a funded purchase order or subcontract cannot be issued; organizational conflicts remain unresolved; the requested work depends on classified, export-controlled, personally sensitive, or procurement-sensitive material that LongTermCapabilities is not authorized to handle; or the prime expects production code, penetration testing, security certification, cost-volume development, legal compliance opinions, or staffing commitments outside the agreed technical-capture scope.
It should also decline when the customer wants a polished architecture diagram without granting authority to resolve contradictory assumptions, when the technical approach is already frozen and the engagement would merely provide decorative artifacts, or when conservative delivery economics fall below the established margin floor. Under those conditions, recommending no action is commercially stronger than converting an unbounded proposal-support request into underpaid consulting.