Case studies

Each one starts with a business need

The need, what we built, and what changed. Sorted by the kind of problem, not the technology.

Operations and payments

Removing manual work from daily operations

01 · FindFill

Automated HHS-OIG exclusion screening

The need

Staff checked every clinician by hand on the HHS site, a compliance requirement for per-diem placement.

What we built

An integration that pulls the full exclusion list internally and screens new and existing clinicians on a recurring schedule.

The outcome

A manual compliance task became an automated, repeatable check.

ComplianceScheduled jobsIntegration
02 · FindFill

Instant clinician payouts

The need

Clinicians were paid through manual bank transfers after each shift.

What we built

A Branch API integration that pays out on shift approval, plus custom Bubble.io plugins for Stripe subscriptions and clinician payments.

The outcome

Same-day payment straight to clinician wallets or bank accounts.

Branch APIStripeBubble.io
03 · FindFill

Self-serve background checks

The need

Background check orders waited on manual activation by staff.

What we built

A Simply Verified integration where clinicians order and pay for their own checks.

The outcome

No activation bottleneck, and faster profile approval.

Simply VerifiedPayments
04 · FindFill

Secure webhook pipelines

The need

Payment, compliance and credentialing systems all push events into the platform.

What we built

Webhook pipelines with HMAC signature validation and OAuth 2.0 client-credentials integrations.

The outcome

Every third-party endpoint is verified before it touches business data.

HMACOAuth 2.0Webhooks

Data and integrations

Keeping systems in sync

05 · FindFill

Geolocation verification service

4 msresponse time
The need

Clinicians’ physical addresses had to be verified and shifts geofenced without slowing the platform down.

What we built

A proprietary .NET serverless service on Azure Functions for geolocation identification, address verification and geofencing.

The outcome

Higher throughput, with responses down to 4 ms.

.NETAzure FunctionsGeofencing
06 · Nurse First Travel Agency

Travel nursing job board

2,000+live postings, refreshed every 5 minutes
The need

The agency needed a public job board that stays in sync with its job feed.

What we built

A WordPress job board with custom PHP plugins, ingesting postings through the Jobrobotix API.

The outcome

2,000+ live postings refreshed every 5 minutes.

WordPressPHPJobrobotix API
07 · Nurse First Travel Agency

Symplr VMS integration

The need

Agency systems and facility-side workforce management did not talk to each other.

What we built

A bidirectional integration with Symplr’s contingent talent management VMS.

The outcome

Data now flows both ways between the agency and its facilities.

Symplr VMSBidirectional sync
08 · Nurse First Travel Agency

Azure data infrastructure

The need

Production staffing workflows needed reliable event processing and data pipelines.

What we built

Azure Data Factory for orchestration, .NET Azure Functions for event-driven processing and Storage Accounts for persistence. I supervised deployments and service health.

The outcome

Monitored uptime across environments for the agency’s production systems.

Data FactoryAzure FunctionsStorage

Field and industrial

Getting data out of the field

09 · IoTech LLC

Industrial wireless transmitter

7 yearsbattery runtime
The need

Field measurements had to reach the platform wirelessly, without mains power, from inside an explosion-proof enclosure.

What we built

A battery-powered Zigbee wireless transmitter, with custom antenna assemblies that integrate with an Ex d enclosure while keeping its flameproof barrier intact.

The outcome

Wireless field data on a battery runtime of 7 years.

ZigbeeBattery poweredEx dRF
10 · IoTech LLC

Zigbee gateway

The need

Remote oil and gas field operations needed reliable long-range telemetry and real-time data.

What we built

Hardware for a custom Zigbee gateway: schematics and multi-layer PCB layouts optimised for signal integrity and power efficiency in harsh industrial environments.

The outcome

Reliable long-range telemetry and real-time data ingestion across remote oil and gas field operations.

ZigbeeMulti-layer PCBGateway
11 · IoTech LLC

Industrial instrumentation prototypes

4–20 mARS-485 and Modbus interfacing
The need

New field instruments had to interface with existing industrial signals and protocols.

What we built

Prototypes covering sensor integration and signal conditioning, 4–20 mA, RS-485 and Modbus interfacing, component selection and BOM development.

The outcome

Functional prototypes, validated through bring-up and bench testing with firmware and manufacturing partners.

4–20 mARS-485ModbusBOM
12 · IoTech LLC

Node.js IIoT gateway

The need

Traditional C-based embedded systems were slow to change for non-critical applications.

What we built

IoTech’s first IIoT gateway on Node.js and Angular, including a Modbus port to the Node.js runtime.

The outcome

The proof of concept was adopted internally as a standard approach.

Node.jsAngularModbusMQTT
13 · IoTech LLC

Intellija SCADA frontend MVP

The need

IoTech’s SCADA platform needed its first operator interface.

What we built

An Angular and TypeScript frontend on a customised PrimeNG library, an ISA 18.2 alarm UI on ag-grid, Gridstack dashboards with Chart.js and Highcharts charts, and Protobuf decoders for live MQTT data.

The outcome

An MVP that consumes live MQTT data in the browser.

TypeScriptAngularPrimeNGMQTTProtobufISA 18.2

Have a need that isn’t on this list yet?

Most of these started as a single sentence from a client. Send me yours.

Tell me about it