We do the engineering and the adoption work as one engagement. Custom software, systems integration, and the organizational readiness that decides whether a modernization actually holds.
For public agencies, universities, and prime contractors. Systems engineering · integration · adoption.
A system gets delivered on spec. It passes acceptance. And then it sits underused, because the people expected to operate it were never part of the change.
Operators revert to familiar workarounds. Managers don't reinforce the new process. Internal teams stay dependent on the vendor long after the contract was supposed to end.
The integrator leaves at go-live. A training vendor gets procured months later, once the underuse shows up in the numbers. Two contracts, two accountabilities, and a gap between them where the value leaks out.
Nissus closes that gap with one team. The people designing the system are the people preparing the organization to use it.
A system nobody uses is a system nobody bought.
We map how the work is actually done today, not how the process document says it is. Who touches what, where the workarounds live, which decisions are already informal. A technical requirements exercise and a change readiness assessment at the same time, because they are the same conversation.
Custom software, systems integration, API and data layers, cloud architecture — built against the constraints that are real in public-sector environments. Legacy systems that cannot be turned off, security and access requirements, procurement cycles that outlast staff.
Operator readiness, custom curriculum, and the leadership work that makes managers advocates rather than obstacles. We name what's in it for each group, because adoption is a communication problem before it is a training problem.
Transfer capability, not dependency. Documentation the next team can read, internal capability rather than dependency on us, and a clear measure of whether the thing is actually being used.
Most contracts are written to end at the first of these three. We build toward the third.
It passes acceptance and runs in production. This is where most technical scopes stop.
Operators work in the new system rather than around it, and the old workarounds go quiet.
Staff can operate, extend, and maintain the system without the vendor. Nissus is built around this outcome.
We focus where our team has direct delivery experience. Concentrated capability outperforms broad claims — particularly in government work.
Builds the technology, then leaves at go-live.
Arrives afterward, without having built the thing.
Custom application development, systems integration, API design, data infrastructure, and cloud architecture. Backend depth in Java and Spring, full-stack delivery in Angular and React, enterprise database work in Oracle and SQL Server. Our team has more than two decades of experience delivering production systems across government contracting, banking, healthcare, telecom, and high-volume retail — including secure information-sharing platforms delivered under U.S. government contract.
Change management, operator readiness, and leadership development for the teams inheriting new systems. Stakeholder mapping, adoption planning, and custom curriculum design — grounded in adult development research rather than generic management training. Delivered by the same team that built the technology, scaling through a curated network of senior associate trainers.
The difference: both are delivered against the same system, the same requirements, and the same operational outcomes.
Our team has more than two decades of experience delivering production systems for government, financial services, and Fortune 500 enterprise clients. Selected engagements.
Agencies needed to exchange sensitive information and coordinate emergency communications across organizational boundaries, under evolving operational requirements.
A production system supporting secure information exchange in a multi-agency government environment.
Loan origination and onboarding workflows required secure processing and regulatory validation while remaining workable for the business teams operating them daily.
Released into production in a regulated banking environment, with business stakeholders involved from requirements through release.
Document management and publishing workflows spanned business owners in one country and development teams in another, with requirements repeatedly lost in translation between them.
Workflows delivered and handed over with the documentation and shared understanding needed to operate them after the engagement ended.
Business-critical merchandising, inventory, and order systems needed continuous modernization without interrupting operations that cannot be paused.
Sustained ownership of business-critical systems as lead developer, including data integrity through peak operating cycles.
Detailed case studies available on request. Client references furnished for qualified opportunities.
Selected production-system experience from prior roles and engagements of Nissus personnel.
Engagements delivered by Nissus personnel in prior roles as employees or contracting engineers. Nissus has not held a contract with these organizations, and no endorsement or affiliation is implied. Named here because the systems and the standards they were built to are relevant to the work we do now.
Nissus is deliberately small. There is no business development layer between you and the people delivering. Both partners are on the engagement, and the firm scales through a curated network of senior associates rather than a broad bench with thin specialization.
Leads applied AI, analysis, and adoption. Builds AI-powered applications and analytical tools end to end — document processing and AI-assisted drafting, workflow and approval systems, audit trails, and role-based access. Designs the data schemas, KPI frameworks, and reporting infrastructure organizations run on, including the measurement architecture a twenty-company portfolio reports against. Two decades across organizational analysis, data and measurement design, and capital strategy. Guest faculty at the California Institute of Integral Studies. Trained in the Social Finance Programme at Saïd Business School, University of Oxford.
Leads systems and software delivery. Two decades building and supporting production enterprise applications, including U.S. government contract work on secure information-sharing systems at NC4 and financial systems for USAA. Prior delivery at Accenture, Cisco, Sony, AT&T, and HP across banking, healthcare, telecom, and high-volume retail. Currently lead developer on business-critical merchandising, inventory, and order systems in a Linux and Oracle environment, with ownership spanning architecture, integration, release management, and production support.
Brothers. Which means the handoff between the technical work and the organizational work isn't a process we invented — there's nobody to hand off to.
For primes, that means engineering capacity plus the operational readiness work that determines whether the delivered system actually gets used.
Whether the delivered system gets used is what agencies remember and what CPARS records. We support primes on both sides of that: production engineering capacity, and the adoption work that most technical subcontractors don't offer and most training vendors can't deliver in a technical context.
| UEI | SKWZL71W9YG5 |
|---|---|
| CAGE | 07D99 |
| UBI | 604762945 |
| Designations | Small Disadvantaged Business · Minority-Owned Business |
| In progress | SBA 8(a) Business Development — pursuing |
| Registered | SAM.gov · WEBS (Washington State) · UW supplier system |
| Personnel | U.S. citizens |
| Primary NAICS | 541512 Computer Systems Design Services |
| Secondary NAICS | 611430 Professional & Management Development Training |
| Location | Bellevue, Washington |
Whether you're a contracting officer, prime contractor BD lead, or program manager — we respond directly and quickly. We respond within one business day.
info@nissuscapital.com