Clients Case studies
What it looks like when we plug in.
These aren’t project bullets. Each one is a partnership where we became the engineering team — the people on the inside, building, fixing, and shipping alongside our clients.
01 Case study
Niitoiyis Family Support Society
Replacing a fragmented stack with one quiet, owned system.
The challenge
Family-services intake and donor records lived in five places — two SaaS subscriptions the team couldn’t sustain long-term, a shared spreadsheet, paper consent forms, and a Mailchimp list that was three exports out of date. Caseworkers were re-keying the same family three times before they could offer a service. Renewal season was approaching with a price hike on one of the SaaS tools.
What we built
A single owned platform on top of WordPress with a custom intake module, role-scoped case records, donor management, and a printable consent flow that families fill out on a tablet at the front desk. The system mirrors how their staff actually works — not how a generic CRM thinks they should. Go-live is scheduled for June 2026.
The outcome
The team retired both SaaS subscriptions before renewal. Front-desk intake dropped from a 12-minute paper exercise to a four-minute conversation. And the families show up on day one already knowing they’re in good hands.
02 Case study
Electronic Recycling Association
Lifting an orphaned codebase off a single laptop.
The challenge
ERA’s intake-to-redistribution tracking software was custom-built years ago by a developer who’s no longer reachable. The application ran on one aging server in the warehouse, the source repo was on a hard drive nobody had a backup of, and adding a single field meant calling someone who couldn’t pick up. Volume was growing; the system couldn’t.
What we built
We recovered the codebase, rebuilt the gaps, and ported the whole thing onto AWS — RDS for the database, Elastic Beanstalk for the application, S3 for asset storage, automated nightly backups. Then we layered in barcode-driven intake and a clean refurb-to-distribution dashboard so the warehouse team can see device status without asking IT.
The outcome
The single point of failure is gone. Intake throughput is up because nobody’s waiting on the warehouse server to wake up. And ERA owns the source code, the keys, and the documentation.
03 Case study
Redline Energy Services
From paper tickets in glove boxes to a tool crews actually use.
The challenge
Daily job tickets were paper. Equipment tracking was a rotating Excel sheet that nobody wanted to own. Crews were dispatched by phone call. Tickets came back to the office a week late, sometimes coffee-stained, sometimes lost — which meant invoicing was always a week behind reality.
What we built
An offline-first field-ops app for Android tablets that lives in the trucks. Crews log job tickets, equipment hours, and incident reports in the field; the app syncs the moment it sees cell coverage. We added a lightweight AI-assisted dispatch layer that suggests crew assignments based on location, certifications, and equipment availability — the dispatcher still decides, but the obvious assignments are pre-staged.
The outcome
Tickets are in the system before the crew gets back to the yard. Invoicing went weekly. The dispatcher stopped staying late on Fridays.
04 Case study
Cascade Fulfillment Group
Owning the integration layer so the operations team doesn’t have to.
The challenge
Shopify, QuickBooks, a WMS, and three carrier APIs — none of them really talked to each other. The ops team was reconciling order, inventory, and shipping data by hand every morning, and any time a Shopify update broke a webhook, the whole stack went silent. Nobody owned the integration layer because nobody had been hired to.
What we built
We took ownership of the full integration surface and built a reconciliation dashboard that flags mismatches between what Shopify says shipped, what the WMS says left the dock, and what the carrier says was scanned. Everything routes through a single typed event bus we maintain — when a vendor breaks something, the alert hits us, not them.
The outcome
Hours of manual reconciliation gone. Inventory accuracy that holds up to a Monday-morning audit. And the ops team has visibility into carrier costs they never had before.
05 Case study
Bright Futures Society
A grant intake portal that respects the people on both sides of the form.
The challenge
Grant applications arrived as PDFs, emails, and the occasional handwritten letter. Reviewing them meant a small team reading every document end-to-end, summarizing by hand, and trying to compare apples to apples across very different communities. Good applications were getting lost in the volume.
What we built
A community-facing intake portal with a respectful, plain-language form, plus a back-office review tool with an AI-assisted summarization layer that turns a 14-page application into a one-page brief — surfaced alongside the original, never replacing it. Reviewers see structured highlights, flagged risks, and a clean comparison view across submissions in the same cohort.
The outcome
Reviewers spend their time on judgment, not on reading the same eligibility sentence sixty times. Applicants get faster decisions. And the team can run a cohort review in a single afternoon that used to take a week.
06 Case study
CanvassIQ
A donor platform built for how Canadian fundraising actually works.
The challenge
Canadian fundraising agencies were stitching together American-built donor tools that didn’t speak PAD, didn’t integrate cleanly with Flinks for bank verification, and treated Stripe Connect like an afterthought. Onboarding a new donor took days of back-and-forth and a non-trivial percentage of recurring gifts failed silently.
What we built
A platform engineered around the Canadian payment stack from day one — Stripe Connect for sub-merchant onboarding, native PAD support, Flinks for instant bank verification, and a donor lifetime-value model that flags at-risk recurring donors before they churn. Hosted on AWS with autoscaling so a successful campaign night doesn’t take the platform down.
The outcome
New donors onboard in minutes instead of days. Failed transactions get caught and re-attempted intelligently. And agencies have a Canadian-first platform they can finally recommend without an asterisk.
What’s next
Wondering what your story could look like?
Let’s find out. A short conversation is usually enough to tell whether we’re a fit — and what the first month would look like if we are.