Adam Valine

I have spent my entire professional life inside one specific corner of software: the workflow, automation, and integration systems that large institutions run on. Nine years at Franklin Templeton building Aprimo Marketing Operations workflows and the integration plumbing around them (Boomi, Aprimo Connect, custom), plus the Xerox / FileMaker / XMPie automation stack that fed production. Six-plus years and counting at Wells Fargo as the discovery and design lead for Marketing systems, the SME on integrations — APIs, file formats, delivery, triggering — and the person who turned a manual monthly cycle-time report into an automated Tableau suite.

The qubic* family is that same craft, applied independently and on my own terms. qubicflow is a workflow engine — the thing I have spent fifteen years configuring inside someone else's product, rebuilt as a graph-based platform with human and agent review steps. qubichelm is workflow scheduling — cron-driven, audited Claude runs against a projects / tasks hierarchy, which is what an automation suite for AI agents should look like if you take the operations side seriously. qubicrelay is the integration plumbing, an API-to-API platform with a CEL-like transform DSL, scheduling, and a dead-letter queue — because every shop I've worked in had a homegrown version of this held together with vendor lock-in and prayer.

The rest of the family extends the same instincts. sendafield is a multi-tenant field-service SaaS with Vault-encrypted PII per tenant, because that's how you run multi-tenant data if you've ever sat through a third-party risk review. qubictether is a self-hostable license server with Ed25519-signed runtime tokens and a ten-state heartbeat policy engine, for software that needs to keep working when the network doesn't. qubicgrade is a Next.js gradebook with a CSV bridge between two real-world teacher platforms and fuzzy name matching — the small-scale version of every integration project I've ever shipped.

What the corporate work taught me, more than any specific platform, is what makes these systems good and what makes them frustrating to live with. Vendor workflow engines flexible enough to model your real process but opaque enough that nobody can debug them at 11pm. Integration tools that handle the happy path beautifully and lose your data the first time a partner changes a field name. Reporting layers that are technically correct and operationally useless. The qubic* versions are written by someone who had to support the alternatives — TypeScript and Node, Postgres with Prisma or Drizzle, self-hosted on single boxes via idempotent bash and systemd and nginx, no Docker. I build for the operator who has to read the logs at 2am, because that operator is usually me.

The reason I'm still doing this after twenty-five years is simpler than the framing suggests: software is the closest thing to magic I've found. Almost anything you can picture clearly, you can actually make. Off-keyboard the same instinct points at physical things — woodwork, leather, any hand craft. When I need a hard reset, a long hike out to a real view does it. Different medium, same impulse: make or earn something you can hold or stand on, and then live with what you ended up with.

Background, briefly: Forward Observer in the US Army (2000–2003) before college, B.S. Finance from Sacramento State, MBA from Boise State in 2025, plus PMP and a working set of certifications in AI and cybersecurity. I live in the Boise area. If any of this overlaps with something you're working on, hello@qubicfold.com — or find me on LinkedIn.