Ten hours of senior Salesforce architecture per week.
A delivery team handles the rest.
I'm the architect, PR reviewer, and escalation point. Cloud Nimbus brings the delivery team — developers and AI agents that ship the implementation. You get senior judgment without buying an FTE, and a team that actually moves without standing meetings.
For Salesforce-using companies that need senior architecture + faster delivery, but don't want to hire another full-time architect or babysit another agency.
The Model
I orchestrate. The team executes.
Most senior Salesforce hires fall into one of two failure modes. Either the architect ends up writing implementation code and never has time to think strategically, or the team ships features that quietly break the architecture because nobody senior is auditing the patterns going in.
This engagement avoids both. My ten hours per week buy you architectural decisions, PR audits, and escalation debugging. The Cloud Nimbus delivery team — developers and AI agents running through Cumulus CI, GitHub-flow, and AI-augmented PR review — handles the actual implementation. The two halves compose into outcomes faster than either one alone.
You pay for outcomes. Not hours. Not status meetings. Not vendor markup on developers you'll never meet.
What my 10 hours per week buys you
Architecture, audit, escalation. The leverage activities. Not ticket-pushing.
Architecture decisions
Domain modeling, integration design, sync strategy, security review, governance. The choices that compound for years.
Pull-request audits before deploy
Every PR going to production gets reviewed against the architecture. Bad patterns get caught before they harden into the codebase.
Production-blocking escalation
If something the team shipped is breaking ongoing business, I debug it. Urgent + important + actively blocking — that's the on-call surface.
AI-agent orchestration
Your team gets Claude Code workflows, Cumulus CI pipelines, and PR-review agents I've already proven on Delivery Hub. Velocity multipliers, not toys.
Standards + repo hygiene
GitHub-flow, metadata API, scratch-org workflows, PMD scanner, Apex test discipline. The boring infrastructure that keeps releases safe.
Hiring + vendor calibration
Interview your candidates. Audit your existing Salesforce vendors. Tell you whether you're paying market rate for the work you're getting.
What I don't do
Honesty about scope is part of the offer. These are the activities the delivery team owns, or that fall outside the engagement entirely.
Writing the implementation code
I architect, audit, and unblock. The team writes the Apex, builds the LWCs, ships the integrations. That's their craft, not mine on this engagement.
Standing meetings + status calls
No daily standups. No weekly status updates. We sync when there's an architectural decision to make or a PR queue to clear.
Debugging features the team is releasing
If your team ships a feature and it breaks in QA — that's their feature, their fix. I'm not the safety net for net-new development your team owns.
Project management or delivery dates
I don't run sprints, write tickets, or commit to deadlines on behalf of the implementation team. That's the team lead's role.
Why this works
I built a Salesforce platform solo. The velocity is real.
Delivery Hub is a free open-source Salesforce platform I built end-to-end: 225 Apex classes, 68 LWCs, 16 custom objects, 7 workflow types covering 93 stages, document engine, native e-signature, cross-org sync, AI integration, MCP server. Solo. In the last twelve months. The same workflows + AI agents that built it will be working on your codebase.
12 mo
Solo build
100+
Features shipped
89%+
Test coverage
$0
License cost
Pick the level of help you need
Three engagement shapes. Architect-only is the proof-of-concept tier. Most clients move to Architect + Delivery Team within 60 days.
Architect on Retainer
10 hours per week of my time. Architecture decisions, PR audits, production-blocking escalation. You bring the team.
- 10 hours/week senior architecture time
- Unlimited PR review queue
- Production-blocking escalation (urgent + business-impacting only)
- Cumulus CI + GitHub-flow setup
- AI-agent workflow templates
- Monthly architecture review meeting
10 hours don't roll over. Hard cap. Designed for orgs that already have a Salesforce team and need senior oversight, not headcount.
Start with thisArchitect + Delivery Team
Everything in Architect on Retainer, plus a Cloud Nimbus delivery team that ships the implementation. Devs + AI agents, scoped to your roadmap.
- Everything in Architect on Retainer
- Dedicated dev capacity (30–60 hrs/week typical)
- AI agent runs included in scope
- Sprint output reports — outcomes, not hour ledgers
- Direct line to the team lead
- First-month onboarding included
Team capacity scales by month. Pricing depends on scope — typical engagements run $28K–$45K/month. Custom quotes for larger throughput.
Scope a delivery teamGreenfield Build
Net-new Salesforce app, integration, or platform. Discovery → architecture → delivery → handoff. Fixed-scope or T&M.
- Discovery + architecture deliverable
- Full delivery team (devs + AI agents)
- Handoff to your internal team or ongoing retainer
- Cumulus CI + GitHub-flow from day one
- Open-source-first: nothing proprietary that locks you in
- Done-when-you-say-done, not done-when-the-statement-of-work-ends
For new platforms, integrations, or major migrations. Typical engagements 6–16 weeks. Quote on call.
Scope a buildAll engagements are month-to-month. No annual contracts. Cancel with 30 days notice. Cloud Nimbus retains your repo and metadata ownership end-state — no proprietary lock-in.
Common questions
Why only 10 hours per week of your time?
Because architecture is a leverage game, not a labor game. Ten focused hours of senior thinking — domain modeling, PR review, escalation debugging — moves a team further than forty hours of feature work. The math works for both sides: I keep my throughput across multiple clients; you get senior judgment without buying a full FTE.
What does "production-blocking escalation" actually mean?
Something is broken in your live production org and it's actively blocking ongoing business — sales reps can't close deals, invoicing is stuck, customers are seeing errors. That's escalation. A QA bug on a feature your team is about to ship is not escalation — that's the team's job.
What if I don't have a team yet?
Start with the Architect + Delivery Team tier. Cloud Nimbus brings the developers and AI-augmented workflows; you get architecture and delivery as one package. Once you've decided you want a permanent in-house team, I help you hire them and the engagement transitions to architect-only.
Are you on-call?
I'm reachable for production-blocking issues during US business hours. Outside that, I respond next business day. If you need 24/7 coverage, the delivery team carries it via shared on-call rotation.
What stack do you actually work in?
Salesforce-native: Apex, LWC, custom REST endpoints, platform events, managed packages, Experience Cloud, Cumulus CI, Salesforce DX. Integrations via REST, webhooks, OAuth — Stripe, QuickBooks, Plaid, Flinks, Anthropic, OpenAI, anything API-driven. GitHub-flow, scratch orgs, PMD, automated test gates. No Copado, no Gearset, no change sets — those are slower than what I run.
What's Delivery Hub and why does it matter to me?
It's a free open-source Salesforce platform I built solo over the last year — 225 Apex classes, 68 LWCs, 7 workflow types, 93 stages, document engine, e-signature, sync, AI integration. It's the portfolio piece that proves the velocity. You don't have to install it to hire me — but if your team is shipping work tracking or wants Jira-killer-on-Salesforce, it's free and ready.
Can I try a smaller engagement first?
Yes. The Architect on Retainer tier is the proof-of-concept. Run a month, decide if the leverage is real, scale up to a delivery team if it is.
Get senior Salesforce architecture without the FTE.
30 minutes is enough to figure out whether this is a fit. If it is, we'll scope a starting tier on the call. If it isn't, you'll leave with a clearer read on what your Salesforce org actually needs.