AI Workflow, Dashboard & Portal Delivery for Civilian Federal and Native-Serving Primes
We sub-perform discrete software for federal primes — the bounded portal, dashboard, AI-document-review, or intake module your task order needs — shipped inside your prime contract, your invoice, and your compliance posture. We work under 8(a) STARS III, GSA MAS IT, OASIS+, NITAAC CIO-SP, and civilian-agency task orders. Civilian and unclassified.
Targeting civilian task orders at IHS, BIA / BIE, DOI, GSA, and HHS.
We don’t compete for your agency relationship. We sub-perform under your contract and hand the program back to you.
Teaming inquiries answered within two business days. Capture and proposal work available now · sub-PO issuance available on award.
Status — can you sub-PO us today?
Registration status up front, so you don't waste time. UEI is active (QDL3BAL1NLY3); CAGE Code 212P3 is assigned; SAM.gov registration is active. We can support teaming conversations and proposal capture now — a sub-PO can be issued on award.
NAICS: 541511, 541512, 541519, 541715, 518210 — custom programming, systems design, other computer-related, R&D, and computing infrastructure. The full registration table, NAICS detail, insurance posture, set-aside eligibility, NIST 800-171 / FedRAMP detail, and the certifications we deliberately do not pursue all live on one page — see Certifications & Compliance Posture → · Security & Data Handling →
Federal Capability Statement → · Team@OlenArc.com · Book a 25-min call · Utqiaġvik, AK (HQ) · Scottsdale, AZ
Vehicles we're sub-ready under
We sub-perform under our prime's existing vehicle, on our prime's invoice. We do not hold our own GWAC seats — that's the point. We don't compete for your agency relationship. We fit cleanly inside FAR 52.219-14 subcontracting limitations on services contracts.
- GSA OASIS+ (Unrestricted / SB / 8(a) pools) · 8(a) STARS III · GSA MAS IT (SIN 54151S) · NITAAC CIO-SP3 SB / CIO-SP4 · GSA Polaris (SB / HUBZone / WOSB) · Agency IDIQs at IHS / BIA / BIE / DOI.
We do not claim to hold OASIS+, STARS III, CIO-SP, or MAS IT as a prime. We sub under primes who do. If your vehicle isn’t listed here, ask — we can usually sub under it. For the full reference — set-aside pool and the module shapes we sub under each — see Contract Vehicles & Sub-Readiness →
Why pick us — when 100 small subs are on your bench list
The first sub-PO is the hardest. You carry the CPARS risk; we don’t have history with you yet. This page is the short answer to why us, not them — compared to the other shapes you could put on your task order.
What primes ask us first — and our specific answer
The six real questions that surface in the first capture call. Short, direct answers; no hand-waving on the things your contracts team will actually check.
No— we sub-perform under primes — we don’t compete for your agency relationship, and don’t hold a federal prime vehicle. Your task order is safe; there’s no path on our side to recompete you next cycle.
Senior teamwith a vetted specialist network across engineering, AI, UX, and operations. Founders on every engagement. Specialist subcontractors brought in by name when scope requires — backup ownership is structural, not improvised.
Productionacross all 8 North Slope Iñupiat villages for the Arctic Slope Community Foundation — applicant portal, admin/review dashboard, AI navigator chatbot, impact reporting layer. Multi-year operating agreement, not a pilot.
Fixed shapeper module with an explicit decline list in writing. Weekly scope check on each demo. New asks go to a change-order conversation, not a silent overrun.
Weekly demosprevent the end-of-engagement surprise. Your PM sees real software every week. If something’s sliding, you know in week 2, not at the finish.
Civilian / unclassified only— we don’t pursue DoD or cleared work, which keeps the engagement clear of DFARS surprises. NIST SP 800-171 self-assessment in flight; FedRAMP-Moderate inherited via AWS GovCloud or Azure Gov when the task order requires it. See compliance posture.
From first call to first sub-PO — a five-step de-risking path
Designed so each step costs you something small and produces something your capture team can show. The first deal is the hardest; this is how we make it cheap to start.
What we sign for — and what we decline
Named up front so your contracts team can rule us in or out before the first call.
What we sign for
- Discrete software modules — portal, intake, AI doc review, dashboard, integration glue.
- Fixed-scope sprints — fast increments from one week, with named acceptance criteria.
- Civilian / unclassified work — HIPAA-aware and CUI-aware where required.
- Sub-PO under your existing vehicle — OASIS+, STARS III, MAS IT, CIO-SP, Polaris.
- Commercial project experience — deployed, named, references under mutual NDA.
- Civilian agencies — IHS, BIA, HHS, GSA, DOI, state HHS, Tribal programs.
What we decline
- Strategy decks & advisory hours. Not our shape.
- Standalone staff augmentation. Bodies-on-keyboards is not what we sell.
- Cleared / DoD / ITAR / classified scopes. Civilian only.
- Fabricated past performance. No CPARS-rated federal PP claims.
- Work a community we serve hasn’t consented to. Tribal & Native-serving: non-negotiable.
- Competing for your agency relationship. The prime stays the prime.
How we handle access, security, and sensitive data
Primes are accountable to the agency for risk posture. Here’s ours at a glance — without overclaiming certifications we don’t hold.
| Item | Posture | Status |
|---|---|---|
| NIST SP 800-171 | Self-assessment against the 110 controls; SPRS-ready summary on request | In progress |
| FedRAMP-Moderate | Via inheritance — AWS GovCloud or Azure Government deployments when the engagement requires it | Posture-ready · not pursued as a CSP |
| Clearance posture | Civilian / unclassified lane. No DFARS-7012, no CMMC L2 work today. | By design |
| Personnel staffing | Matched to each task order’s compliance requirements — Public Trust eligibility or US-person staffing on request | Per engagement |
| CUI handling | Role-based access, separation of public / internal / sensitive data, audit-ready permission model on forms, dashboards, documents, reports | Built-in by default |
| HIPAA-aware development | For healthcare-adjacent scopes — practices defined before implementation, not claimed as HIPAA compliance | Per engagement |
| Third-party pen testing | Scopable add-on when the task order or prime requires independent assessment | On request |
Data sovereignty-aware design
Client data stays under client ownership and control. We align with existing Tribal, agency, or funder data policies, and can work with preferred hosting partners when required. For ANC and Tribally-owned primes this means we slot into your data governance rather than imposing our own. We do not claim sovereign-AI guarantees or legal data-sovereignty consulting.
We do not claim FedRAMP authorization, CMMC certification, automatic HIPAA compliance, or any certification we have not received. Compliance scope is defined at the start of each engagement.
Federal subcontracting assets
Capture briefs, compliance posture, vehicle reference, FAQ, and the first-30-days playbook — everything a prime BD lead, capture team, or contracts officer might want in one place. Take what you need.
Federal Capability Statement
Two-page corporate capability statement — NAICS, code, point of contact, compliance posture, deployed work. Drop into your capture binder.
Compliance & security posture
SAM/UEI/CAGE timing, NIST SP 800-171 self-assessment plan, FedRAMP inheritance posture, NAICS coverage. Updated as items complete.
Federal teaming FAQ
Ten questions primes actually ask — FAR 52.219-14 50% math, NIST 800-171, GWAC vs sub, NAICS, sub-PO readiness, CUI / FedRAMP, DFARS / CMMC.
Contract vehicles reference
Vehicles our sub partners typically hold — OASIS+, 8(a) STARS III, GSA MAS IT (54151S), CIO-SP3/4, Polaris, agency IDIQs. We don’t hold prime; we sub.
First 30 days as your sub
Prime-PM onboarding playbook — what we file, who shows up, how the kickoff and first SOW review actually run. For capture team reads.
Considering a sub engagement?
Tell us the agency, the vehicle, and the module gap. We respond within two business days with a fit / no-fit read. More questions? Federal teaming FAQ →