Architecture as Margin
Platform architecture is a margin decision. Every build-vs-buy choice, every abstraction layer, every shared foundation either compounds leverage or compounds cost. I lead engineering where technical decisions are economic investments.
This means asking not just “can we build it?" but also “what does this unlock?” and “what does it cost to maintain?” The result is platforms that scale economically, so each new customer, feature, or team adds leverage rather than incurring linear costs.
What this looks like
Build-vs-buy rigor: Vendor evaluations grounded in financial modeling and proof-of-concept validation, not surface impressions or vendor demos.
Multi-tenancy as economic strategy: Shared infrastructure that serves hundreds of deployments from a single codebase, replacing per-client builds with configuration-driven variation.
Debt reduction as velocity investment: Platform work that lowers the cost of every future sprint—the foundation that makes everything else move faster.
Architecture as organizational enablement: API contracts and service boundaries designed so teams ship faster because of constraints, not despite them.
How I’ve done it
Turning 37 codebases into one platform
In a consulting engagement, I inherited a fragmented portfolio: 37 separately maintained codebases across iOS and Android, each a slightly different version of the same product. Every change affected all of them. SDK updates, policy changes, and build system upgrades cascaded across dozens of codebases.
I designed and led the migration to a multi-tenant platform architecture, consolidating sprawl into shared codebases that powered over 200 white-labeled applications through configuration instead of code forking. The economics changed overnight: what had been linear cost became leverage, as more clients required only incremental configuration, not additional infrastructure.
This required:
Configuration-driven behavior: Features, theming, content, and environment controlled by tenant config files rather than code branches
Standardized build systems: CI/CD pipelines that eliminated per-client build drift
Automated release management: App Store and Google Play publishing workflows that removed the manual bottleneck requiring engineering time for every release, policy change, and SDK update
85% automated test coverage: The safety net that made shared-codebase changes safe at scale
The new platform cut client onboarding from weeks to days and ensured that every platform improvement benefited all 200+ deployments simultaneously.
Making build-vs-buy a discipline, not a debate
At Dayforce, I led vendor evaluations for fraud detection, feature flagging, and engineering analytics—decisions that would shape platform capabilities for years. Rather than defaulting to build or chasing vendor demos, I established a structured assessment framework:
Financial modeling: Total cost of ownership for vendor solutions vs. internal build costs, including opportunity cost of engineering time
Proof-of-concept validation: Engineering teams tested vendor solutions against real workloads before commitment
Alignment reviews: Product, finance, and engineering leadership evaluated strategic fit and long-term maintainability
The result was a hybrid approach: we bought where vendor maturity exceeded what we could build within our timeline, and built where our domain complexity made off-the-shelf solutions a liability. The tools mattered less than the discipline—giving the organization a repeatable way to make high-stakes technical investments with confidence.
Autonomous velocity inside enterprise governance
Leading mobile engineering at iSeatz within an enterprise travel and loyalty ecosystem, I faced a structural problem: our delivery velocity was throttled by enterprise approval cycles. Monthly governance reviews were non-negotiable, but they were killing our ability to iterate.
I redesigned the release architecture around integration contracts—YAML-based specifications defining API boundaries, security models, and operational permissions between mobile clients and platform services. This allowed our teams to ship on biweekly cycles while Amex maintained its monthly governance cadence. We decoupled without diverging.
The result: mobile capabilities delivered inside a $9B+ loyalty platform, with expanded trust and scope from Amex leadership. The constraints didn’t change—our architecture did.
