The delivery partner behind US SLED and federal primes.
FISTA Solutions works as a subcontractor and teaming partner to US prime contractors on state, local, education (SLED), and federal civilian IT work. The prime holds the vehicle and the customer relationship; FISTA delivers specified work packages such as custom applications, cloud and DevSecOps, data platforms, AI agents, and Section 508 accessibility, contracting through its Delaware entity.
- 150+
- projects delivered
- 50+
- companies served
- 99.9%
- verified uptime
- 47%
- efficiency gains
- 12+
- countries reached
Who we team with
Which US primes does FISTA team with?
Primes that already hold government IT contracts or vehicles and need delivery capacity to win and perform: mid-tier GovCon firms, regional systems integrators, the public-sector practices of consultancies, vertical primes in health IT, education technology, and smart cities, and holders of cooperative purchasing contracts. The common factor is a stretched technical team and option years to fill.
| Prime profile | Why they team with FISTA | Typical work packages |
|---|---|---|
| Mid-tier GovCon firm | Multiple active contracts, stretched delivery, pressure to compete on price without lowering quality | Application development, cloud migration, test automation, modernization |
| Regional systems integrator | Deep local agency relationships, thin engineering depth on modern stacks | Web and mobile services, data platforms, integrations |
| Consultancy public-sector practice | Large program wins that need scaled, governed delivery capacity | Workstream delivery under the prime's PMO, AI and data engineering |
| Vertical prime (health IT, edtech, smart city) | Domain expertise and a customer base; needs technical delivery per product line | Product engineering, accessibility, analytics, agent-based automation |
| Cooperative vehicle holder | A NASPO, OMNIA, Sourcewell, or state contract that buyers can order from directly | Task-order delivery capacity that lets the holder say yes to orders |
Vehicles and portals
Which vehicles and portals matter, and where does FISTA fit?
The federal and cooperative vehicles below are where SLED and federal civilian IT buying concentrates. FISTA does not need to hold them to be useful; the primes that hold them need delivery partners to perform on the orders. FISTA's role is subcontractor to the holder, named in the task order and the teaming agreement.
| Vehicle or portal | What it is | FISTA's role |
|---|---|---|
| SAM.gov | Federal entity registration and the federal opportunity portal | Subcontractor to registered primes; identifiers in the pack |
| GSA Multiple Award Schedule (IT category) | The federal schedule most agencies and many SLED buyers order from | Delivery subcontractor to MAS holders on orders |
| NASPO ValuePoint | Multi-state cooperative contracts for IT services, cloud, and security | Sub to ValuePoint vendors performing state participating addenda |
| OMNIA Partners and Sourcewell | National cooperative purchasing used by local governments and education | Sub to awarded suppliers on task orders |
| E&I Cooperative and TIPS | Higher education and Texas-based national cooperatives | Sub to awarded suppliers for campus and district IT work |
| State portals: Cal eProcure, Texas DIR, NY OGS, Florida MFMP, Virginia eVA | Statewide contracts and solicitations for the largest state IT budgets | Sub to statewide contract holders |
| DemandStar and PublicPurchase | Aggregated municipal, county, and district solicitations | Sub to local primes pursuing these solicitations |
Work packages
What work packages does FISTA take on US contracts?
The engineering that SLED and federal civilian task orders most often need and that can be specified, delivered against de-identified data, and verified: citizen-facing applications, cloud and DevSecOps, data platforms, AI agents, modernization, and accessibility. FISTA's service areas align to NAICS 541511, 541512, and 541519.
- 01
Citizen services and case management
Permitting, licensing, benefits intake, grants, and case management built on modern web stacks with audit trails and WCAG 2.1 AA conformance.
541511 - 02
Cloud migration and DevSecOps
Re-platforming to FedRAMP or StateRAMP-authorized cloud services with infrastructure as code, hardened pipelines, and observability the prime's security team owns.
541512 - 03
Data platforms and reporting
Warehouses, pipelines, and dashboards for program reporting, with lineage and reconciliation evidence for audit.
541512 - 04
AI agents and document intelligence
Claude-based agents for constituent service, document processing, and internal workflow, with permissions, evaluation, and human review designed for public scrutiny.
541511 - 05
Legacy modernization
API layers and incremental migration for aging state and county systems, sequenced so services never go dark during cutover.
541519 - 06
Accessibility remediation and testing
Section 508 and WCAG 2.1 AA remediation for existing applications and conformance testing with assistive technology, with reports for the agency.
541519
Flow-downs
What flows down, and how does FISTA handle it?
SLED and federal civilian contracts flow down accessibility, privacy, security, and offshore-access obligations. FISTA handles each one in the same way: the obligation becomes a requirement in the work-package specification, the workshare keeps restricted data with the prime, and the evidence package shows how the requirement was met.
| Obligation | What it requires | How FISTA handles it |
|---|---|---|
| FERPA | Protection of student education records in K-12 and higher education systems | Data processing agreement with the prime; de-identified student data in development; access controls and logging in production designs |
| HIPAA | Protection of health information for state health and human services systems | Business associate agreement where required; PHI stays in the prime's environment; encryption and audit logging by design |
| Section 508 and the 2024 DOJ Title II rule | WCAG 2.0 AA federally; WCAG 2.1 AA for state and local web content and apps with compliance dates from 2026 | Built to WCAG 2.1 AA; automated and assistive-technology testing; conformance report for delivered software |
| NIST CSF, SP 800-53, SP 800-171 | Security control frameworks; 800-171 where controlled unclassified information is in scope | Controls mapped in the security practices summary; CUI stays in the prime's authorized environment |
| FedRAMP and StateRAMP | Authorized cloud services for federal and participating state workloads | Build on authorized services in accounts the prime or agency owns |
| CJIS Security Policy | Restrictions on criminal justice information access and personnel | CJI stays onshore with the prime; FISTA's workshare excludes it |
| Organizational conflict of interest | Disclosure when a party helped shape a solicitation | Disclosed to the prime before teaming; no FISTA involvement in requirement writing for pursuits it supports |
| Offshore restrictions | Contract or state limits on offshore access to data or offshore performance | Workshare designed around the restriction; disclosed in the teaming agreement and the proposal |
General guidance for teaming planning, not legal advice. Which obligations apply is set by each solicitation and prime contract.
Teaming call → task order
How does a US teaming engagement start?
With a twenty-minute call on the vehicle, the agency, and the work packages. FISTA then sends the due-diligence pack under NDA, the teaming agreement fixes workshare and flow-downs, and the first task order runs specification to acceptance with an evidence package the prime can hand to the contracting officer.
- 1
Teaming call
Twenty minutes on your pursuits, the work packages you need covered, the flow-downs in play, and whether FISTA's capacity and time zone fit. No deck; a conversation between delivery people.
OutputFit decision and a named pursuit or task-order scope
- 2
Due-diligence pack under NDA
Capabilities statement, rate card by role, key personnel, security practices summary, registration and certification status, references, and FISTA's NDA and teaming templates, or yours.
OutputEverything your contracts and compliance reviewers ask for
- 3
Teaming agreement or subcontract
Scope, workshare, exclusivity per pursuit, rates, flow-down clauses, data handling, IP, key personnel, and exit terms fixed in writing before any task order starts.
OutputSigned agreement with the flow-down set reviewed line by line
- 4
Task-order delivery
Each work package runs specification to verified production: a written spec, a working system, an evidence package, and documentation you can hand to the contracting officer.
OutputAccepted deliverables and a past-performance letter
Regulatory and procurement references on this page are general guidance for planning a teaming engagement, not legal advice. Confirm obligations with your contracts and legal teams for each solicitation.
Clear answers
What primes ask before teaming.
Straightforward guidance for evaluating scope, fit, and the next step.
01Can a firm with delivery in Pakistan work on US government contracts?
As a subcontractor, yes, where the prime contract's flow-downs allow offshore performance. The contracting counterparty is FISTA Solutions Inc., a Delaware corporation. Where a contract restricts offshore access to data, FISTA's workshare keeps that data with the prime and delivers against de-identified data, and the restriction is disclosed in the teaming agreement and the proposal.
02Is FISTA registered on SAM.gov?
FISTA provides its registration identifiers and their current status in the due-diligence pack rather than publishing them, so a reviewer always sees the current position. A subcontractor does not need its own vehicle to perform on a prime's task order; the prime's registration and vehicle govern the order.
03Do you handle Section 508 and the DOJ Title II rule?
Yes. FISTA builds to WCAG 2.1 AA, which satisfies Section 508's WCAG 2.0 AA baseline and the 2024 Department of Justice ADA Title II rule for state and local government web content and mobile apps. Delivered software comes with automated and assistive-technology test evidence and a conformance report.
04What about CUI, CJIS, and security clearances?
Controlled unclassified information stays in the prime's authorized environment, criminal justice information stays onshore with the prime, and FISTA makes no clearance claims. The workshare is written so FISTA's packages never depend on that access. Department of Defense work under CMMC is not the entry point for this model.
05Which states and agencies does FISTA work in?
Any state, local, or education buyer where the prime holds the contract or vehicle, and federal civilian agencies on the prime's orders. The market pages name the largest state portals and cooperative vehicles because that is where the primes FISTA teams with hold positions, not because FISTA is limited to them.
06How quickly can a task order start?
After the teaming agreement is signed and the work package is specified. Timing depends on scope, environment access, and the seniority the package needs, and FISTA states it per task order rather than promising a generic start date. The first evidence gate is set in the specification so the prime sees progress in week one.
Six markets
Every market FISTA subcontracts in
- 01SLED and federal civilianUnited StatesOpen the market brief
- 02G-Cloud, CCS, NHS, TEDUK and EuropeOpen the market brief
- 03Digital Agency-era programsJapanOpen the market brief
- 04UAE, KSA, Qatar, Kuwait, Bahrain, OmanMENAOpen the market brief
- 05Federal supply arrangements, provincesCanadaOpen the market brief
- 06BuyICT, DTA, statesAustraliaOpen the market brief
Continue exploring
Related capabilities
Sub-first, on the record
Name the vehicle and the agency. We will propose the workshare.
Tell us which contract or cooperative vehicle you hold, the agency, and the work packages you need covered. FISTA sends the due-diligence pack and a workshare designed around your flow-downs.