Independent Salesforce architecture · Est. 2017
I build the integrations, untangle the automation, and write the documentation that lets your team understand its own system again. One senior engineer, working directly with you — no account managers, no offshore hand-off, no discovery deck.
“Excellence from understanding why, not just knowing how.”
Services
Most engagements start as one of these and grow into another. All of them are scoped against a written Statement of Work before any code is written.
Connecting Salesforce to the systems that actually run the business — billing platforms, operator APIs, payment providers, internal services. Built with real error handling, so failures surface loudly instead of disappearing into a debug log.
Find out what your org actually does. Every flow, trigger, validation rule and assignment rule traced, tested against live behaviour, and written up in language your admins and your auditors can both use.
The chain from a quote to money in the bank, built or repaired end to end: CPQ, billing, payment capture, tax, and the handoff into accounting — including the reconciliation nobody notices until the numbers disagree.
Ongoing senior capacity for teams that need an architect occasionally but can't justify one full-time. Deployment discipline included: targeted, test-gated releases, and a production org that is never a guess.
Working depth
Not a list of everything I've encountered. These are the products I've built on, broken and repaired — where I can tell you the limitation that isn't in the documentation, and what it costs you three years later.
Worked with, without claiming expertise Account Engagement (Pardot) · Adobe Acrobat Sign · Avalara · Celigo · CRM Analytics · Data Cloud · Gearset · Geopointe · Jira · LinkedIn Sales Navigator · Marketing Cloud · MuleSoft
Approach
These are the commitments that tend to matter most to the people who hire me, so they're worth putting in writing before we ever speak.
Architech is one person by design. The person who scopes your project is the person who writes the code and the person who answers the phone when something breaks. Nothing is translated through an account manager or passed to a delivery team you've never met.
Every engagement ends with written documentation of what was built and why. Consultants who leave behind undocumented systems create the exact problem I usually get hired to fix — so I refuse to be the next one.
Targeted, test-gated deployments only — specific components with their specific tests, never a whole directory pushed and hoped over. You always see the exact change before it reaches production.
Sometimes the honest answer is that a feature isn't worth what it costs to maintain, or that a licence you already own solves it. Saying so costs me billable hours and buys the kind of trust that keeps clients for years.
Selected work
Client names are withheld under the confidentiality terms of my standard agreement. Described by problem and shape instead — which is the part worth reading anyway.
Flow-invocable Apex connecting Salesforce to an operator billing platform across seven regional endpoints. Every batch is validated completely before a single callout fires, so a bad row fails the batch instead of leaving half the records sent.
A mature org where nobody remaining knew what the automation did. Traced every flow and rule against live behaviour, eliminated well over a hundred false positives from the initial scan, and delivered a twenty-three chapter guide the team still works from.
Revenue-share calculation and multi-currency reconciliation built on top of a managed accounting package, including the currency-conversion corrections that made the USD figures reconcile for the first time.
A customer-facing booking and scheduling application on Experience Cloud, packaged for repeatable deployment across multiple client orgs rather than rebuilt each time.
About
I've spent my career inside other people's Salesforce orgs — usually the ones that have been running long enough to accumulate history. Layers of automation added by people who have since left. Managed packages nobody fully understands. Integrations that work right up until the day they quietly stop.
The work I'm best at is making those systems legible again, and then extending them without adding to the pile. That means I spend as much time reading and documenting as writing new code, and I think that ratio is the reason the systems I build tend to outlast my involvement in them.
Architech has operated since 2017. I work with a small number of clients at a time, directly and under a standard master services agreement, which is the arrangement that produces the best work for everyone involved.
Get in touch
The readiness review is free, needs no sign-up, and runs entirely in your browser — I never see your answers unless you choose to send them. Do that first if you want a better conversation than a blank email allows. Otherwise, plain email is always welcome.
info@architechbc.com