Selected work

Systems we designed, built, and still support.

Three projects, described in enough detail to judge. Where a client's name isn't ours to publish, we've described the operation instead.

ProjectAlertAny
DomainEmergency & mass notification
StackAzure · .NET · Twilio · PostgreSQL · Docker
In production

A notification platform that had gone quiet

The problem

AlertAny lets an organization raise an alert from any phone: dial in, enter an extension and a passcode, and the system fans the message out to that extension's people by SMS and email. It had stopped working. Callers reached the system and were told no extensions were available. Separately, a second module had failed weeks earlier and nobody had noticed.

What we found

The silent failure came first. A service certificate had auto-renewed in the key vault, but the renewed public key was never pushed to the identity provider — so on the day the old key expired, authentication broke. Nothing raised a flag, because the subscription carried no credential-expiry monitoring at all.

The phone system was three faults stacked on each other. The call handler asked for available extensions without passing the number that had been dialed, so the list came back empty every single time. The stored phone number carried a typo — one extra digit. And five extensions were missing the owner record that makes them visible in the first place. Once callers could finally get through, a fourth issue surfaced: the notification step was silently skipping admin-owned extensions, because the code that resolves which account sends the message only understood the customer hierarchy.

The outcome

All four defects were fixed and shipped as a versioned container image, with previous versions retained for instant rollback. Call-in and passcode entry were verified by the customer, and the notification path was repaired in the same pass. Because the platform provides no alerting on credential expiry, we scheduled a recheck ahead of the next renewal rather than leaving it to be discovered the same way.

ProjectMaintenance management platform
DomainFacilities & equipment maintenance
StackASP.NET Core · Blazor Server · EF Core · SQL Server
In production

A system the customer can grow without calling us

The problem

A maintenance operation with equipment spread across departments and multiple sites needed a system its own staff could reorganize. Off-the-shelf CMMS products fix the navigation to the vendor's idea of how a plant is arranged. Custom builds usually hard-code the menu instead — which means every new department is a change request, a quote, and a wait.

What we built

We made the navigation data rather than code. The system opens on a page of large department tiles; each one opens into further tiles, or into a real screen, to any depth. Administrators add levels and boxes at runtime — no deployment, no database change. Staff can pin personal tiles of their own alongside the shared ones.

Underneath, a page registry keeps itself current from the application at startup and fails closed: a screen nobody has been granted access to simply doesn't exist for them. Permissions are enforced on the server, and tile visibility follows those permissions automatically, so the menu can never advertise a door the user can't open. Removing a branch soft-deletes everything beneath it, so nothing is left orphaned but still reachable.

The outcome

The navigation model proved general enough to lift out as a reusable specification, and we now start new line-of-business projects from it. Clients get a proven permission-aware navigation system on day one, and don't pay us to rebuild it each time.

ProjectAllworxVoiceToText
DomainVoicemail transcription SaaS
Stack.NET · M365 Graph · IMAP · SIP · Twilio · Entra ID
In production

A product with its own sales channel built in

The problem

An Allworx phone system can email voicemail out, but making that work means forcing SMTP relay settings through Microsoft 365 or Gmail — a job that defeats plenty of installers and generates support calls for the dealer who sold the system. And the voicemail still lands as an audio file nobody wants to stop and listen to. The opportunity wasn't one customer's problem. It was every Allworx dealer's problem.

What we built

A hosted service that takes the SMTP configuration off the table entirely: the phone system sends voicemail to us, we transcribe it, and it comes back as readable text with the original recording attached — and by SMS if that's easier. For teams that would rather keep their own mail infrastructure, it ingests from Microsoft 365 Graph or any IMAP mailbox instead, or records straight off a SIP trunk with no change to the Allworx hardware at all.

What makes it a business rather than a utility sits underneath: a distributor, reseller and tenant hierarchy where every account is scoped and self-managed, margins apply automatically down the chain, and volume discounts and distributor commissions are calculated without anyone doing arithmetic. Prospects sign themselves up with partner-referral tracking intact, and signed webhooks push events into a dealer's existing PSA or CRM.

The outcome

Live and selling at allworxvoicetotext.com — $10 a month for delivery and five extensions, with SMS, long-term storage, business texting and ad-hoc transcription as add-ons customers switch on themselves. Sign-in is email and password, a one-time magic link, or Microsoft Entra SSO with MFA; data is encrypted at rest behind a full audit log. It is the same multi-tenant, audited, role-scoped pattern we bring to client projects — running as our own product, with our own resellers on it.

The common thread

What these three have in common

We diagnose before we rebuild

On AlertAny we found four separate faults — and none of them was the one originally reported. Replacing the system would have cost far more and fixed nothing.

We build so you don't need us for routine change

Adding a department to the maintenance platform is an admin task, not a change request. We'd rather sell you the next project than bill you for a menu edit.

We design for the second customer

AllworxVoiceToText was built for every Allworx dealer, not one of them. Tenancy, margins and referral tracking were settled before the first sale — cheap at the start, ruinous to retrofit.

See more of what we've built, with demos →

Have something like this that needs building — or fixing?

We'll tell you honestly which one it is, and whether it's worth doing at all.

714-669-7709support@ivcomputer.com
621 S. B St. Unit C
Tustin, CA 92780