iBi Nexus

Company / How we work

An engineering company that turns useful ideas into working systems.

We build software, connect systems and use AI where it helps. Our engineers bring these skills together to solve practical problems for the people doing the work.

Understand + designBuild + connectValidate + deploy + evolve

Delivered client work

A public-sector system in operation.

iBi Nexus designed and deployed the Washington State Department of Commerce Solicitation Management System to support solicitations and requests for proposals and other information.

Explore the Commerce project →

A project of our own

See how we built this website with AI.

We built this website with AI assistance and hands-on engineering. Our team shaped the design, reviewed the code and tested the interactive examples before deploying it to production.

See how this website was built →

Our role / Make the parts work together

The screen, process and records need to agree.

A screen can show one thing while the process or record says another. We design them together so people have consistent information and know what to do next.

Illustrative context
Automation ↔ Software

Agree who handles the next step and show that person in the application.

Responsible person + visible request status. Specialized physical-system work is not required in this office example.
01
Automation

How work reaches the person who handles the next step.

Shared decision
02
Software

What a person sees and what the application does.

Shared decision
03
Cloud / integration

How applications exchange information.

Contributes
04
Data

What the information means and who owns it.

Contributes
05
Engineering systems

How equipment and operating conditions shape the software.

When needed

Conceptual example / Office service request

Who handles the next step, and does the screen show that person?

At an unclear boundary

The process names a next step, but the screen does not name the responsible person.

Responsible person + visible request status
Bring the responsibilities together

Agree who handles the next step and show that person in the application.

Our working approach

A conversation becomes something people can use.

We understand the need, design the system, build and test it, deploy it and improve it through use. Each stage produces something the next team can work with.

  1. 1. DiscoverContext sketch

    Agree on the handoff that needs to change.

  2. 2. ArchitectResponsibilities and interfaces

    Agree what each part does and who is responsible.

  3. 3. EngineerPrototype and connected behavior

    Try the design and check how it works.

  4. 4. DeployDeployment and support handover

    Know who will run and support the system.

  5. 5. EvolveFeedback into the next design

    Decide what should change after use.

Discover → Context sketch. Agree on the handoff that needs to change.

Conceptual project sketch / Context sketch
RequesterService coordinator
Where does the document question go?Unclear next step → agree who handles it
Inbox / documentService record

People + current tools + one question to resolve

01

Discover

We learn how people do the work, where problems occur and which systems are involved. Together, we define a specific problem to solve.

Agree on the handoff that needs to change.

Your team explains the work. Our engineers turn that understanding into clear designs, working software and practical next steps.

The approach reaches real work

Designed, deployed and operating.

iBi Nexus designed and deployed the Washington State Department of Commerce Solicitation Management System portal. It is operational for solicitation and RFP/RFX-related workflows.

See the confirmed Commerce work →

Institutional work includes an ERPO-related project and other smaller projects at the University of Washington. Specialized maritime and offshore descriptions reflect engineering-team experience.

Choose technology to fit the task

The right tools for each part of the system.

People and work

Application experience + workflow

Web applications make the next action understandable. Automation and intelligent assistance support defined tasks and review points.

Information across boundaries

Interfaces + owned data

Application programming interfaces (APIs), cloud systems and data connect the experience to its existing environment.

The operating environment

Configuration + operational context

Microsoft technologies and Azure services are used where appropriate. Specialized systems bring equipment, interfaces and operating constraints into the conversation when needed.

Start with the work

Tell us what your next useful system should do.

Tell us what people need to do, the information they use and the applications already in place. We can identify a focused prototype or development project that fits.