Fractional Solution Architect
Sixteen years of enterprise architecture experience, available to your team on a recurring weekly cadence. Cloud, data, and integration decisions made carefully, with the engineers who will build them.
The right moment.
Engagements are most useful when the moment is right. Below are the situations where this kind of work has produced the most value — for the client, and for the architectures that have followed.
Your engineering team is strong but lacks a dedicated architect, and decisions are accumulating faster than the organization can metabolize them.
You're between architecture hires and need a steady hand for six to twelve months.
A board or audit committee has asked for an architecture roadmap and you do not have an internal author.
You're starting a multi-year cloud or data initiative and want senior-level direction without committing to a full-time leader on day one.
Tangible deliverables.
Weekly architecture working sessions with the engineering leads and stakeholders.
Reference architectures, decision records, and target-state diagrams that the team can actually build from.
Direct participation in technical reviews — RFCs, design docs, vendor evaluations, security reviews.
Quarterly executive briefings translating technical posture into board-ready language.
On-call architectural judgment between sessions for material decisions.
Engagement structure.
Discovery
A short engagement to characterize the current state, the open decisions, and the team's posture. Two weeks, light touch.
Recurring engagement
One to two days per week on a quarterly contract. Direct collaboration with the team. Documented decisions. Quarterly executive checkpoint.
Renewal or handoff
Engagements are reviewed quarterly. If the work is finished, we close it cleanly. If it continues, we renew. If you've made the full-time hire, the transition is structured.
Where this work has lived.
Architected the strategic AWS data-platform-as-a-service originating in Marketing and adopted by roughly ten additional internal teams — a shift from always-on infrastructure to event-driven serverless and elastic compute.
Staff architect on sub-second microservices, the AWS-to-GCP migration target architecture, and a shared-sandbox CI/CD model for dozens of engineers.
Designed the company's first ground-up AWS analytics environment — VPC, security, data lake, scheduling — replacing an expensive commercial scheduler with custom Lambda + Step Functions orchestration.
Start with a conversation.
Reach out with the question on your mind. If this engagement is a fit for your moment, we'll talk about scope and structure.