01Capabilities
What we build, and what we will not bid
Written for evaluators. Every claim here is one we can substantiate on request, and the limits are stated as plainly as the capabilities.
Core competencies
Native iOS and iPadOS application development
- Swift, SwiftUI, UIKit, Objective-C interop on legacy codebases
- Citizen-facing, field-worker, and internal agency applications
- Offline-first and intermittent-connectivity designs for field use
- MDM-aware deployment, managed app configuration, per-app VPN
- VoiceOver, Dynamic Type, and contrast conformance built in from the first commit
macOS application development and fleet automation
- Native Mac applications and command-line tooling
- Security-baseline automation against the NIST macOS Security Compliance Project
- DISA STIG and CIS benchmark tailoring, evidence generation, and drift detection
- Notarization, code signing, and managed distribution
Section 508 and WCAG 2.1 AA conformance
- Assessment against the DHS Section 508 Compliance Test Process for iOS Mobile Applications
- Remediation of existing applications, with before/after evidence
- Accessibility Conformance Report (VPAT) preparation
- Automated conformance checks wired into CI so regressions never reach a review
Sustainment, modernization, and O&M
- Taking over applications from a departing vendor, including undocumented ones
- Dependency, OS-version, and deprecation currency — the work that prevents outages
- Incremental modernization of aging Objective-C and legacy Swift codebases
- Documented runbooks and transition-out packages, so the next vendor is never held hostage
How we deliver
Small teams fail in predictable ways. These are the practices that prevent each one.
Working software on a schedule you can verify
Short increments with demonstrable output. You should never have to take our word for progress between milestones.
Accessibility evidence with every build
Conformance checks run in CI. The artifact a reviewer asks for at the end already exists from week one.
Documentation and source delivered continuously
Code and documentation land in your repository throughout, not at closeout. Transition-out material is written as we go.
Data rights marked during development
Pre-existing components and contract-funded work are tracked and legended separately, so what you receive is unambiguous.
Fixed price where scope is knowable
You get cost certainty; we get the upside of working efficiently. Milestone-billed, never one payment at the end.
Named engineers, start to finish
The people in the proposal are the people on the contract. There is no bench and no substitution.
Codes, vehicles, and compliance posture
Classification
- Primary NAICS — 541511 Custom Computer Programming Services
- Secondary NAICS — 541512, 541519, 541715
- PSC — DA01, DA10, DB01 (confirmed at registration)
- Business size — Small Business
- Entity type — Arizona limited liability company
- Place of performance — Phoenix, Arizona; CONUS remote
Compliance posture, stated honestly
- SAM.gov — registration in process; UEI and CAGE published here on issue
- Section 508 / WCAG 2.1 AA — core practice, evidence provided with deliverables
- CMMC — not currently assessed. We do not bid work involving DoD CUI.
- Clearances — none held. We do not bid classified work.
- Accounting — commercial. Suited to firm-fixed-price and commercial-item T&M; not a DCAA-adequate system, so we do not bid cost-reimbursement contracts.
- Insurance — general liability, professional liability, and cyber; certificates on request
Why we publish the limits. A vendor who says yes to everything costs you a failed award and a re-solicitation. If your requirement involves CUI, a clearance, or cost-type accounting, we are the wrong firm and we would rather tell you now — and point you at someone who fits.