Independent Salesforce architecture · Est. 2017
I design the models, 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.
The chain from a quote to money in the bank, built or repaired end to end: configuration and pricing, billing schedules, payment capture across more than one gateway, revenue recognition, and the handoff into accounting — including the reconciliation nobody notices until the numbers disagree. Approval rules included, because that is usually where quoting actually stalls.
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.
Applications for the people outside your company — customers, vendors, contractors, advisors — each with their own login, their own slice of the data and their own idea of what the system is for. Built on one model rather than three, so a change to the process doesn't have to be made three times.
Moving off a legacy platform, a competing product, or the spreadsheet that quietly became one. The work is mostly reading: establishing what the old system really does, including the parts nobody documented, before deciding what deserves to be carried across at all.
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.
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
A record of where I've spent time, not a shortlist of what I'd put you on. Everything here has trade-offs — that is mostly how I came to know it — and the job is to give you what you need to decide, not to move you onto something because it happens to be familiar to me. If what you run isn't on this list, that is not a problem: picking up unfamiliar software quickly is the part of this work I'm best at.
Consulted on, short of building it end to end Clio · Confluence · Ironclad · Mindbody · NetSuite · PandaDoc · Slack
Encountered, without claiming depth Account Engagement (Pardot) · Adobe Acrobat Sign · Avalara · Blackbaud Raiser's Edge · Celigo · CRM Analytics · Data Cloud · Financial Services Cloud · Gearset · Geopointe · Jira · LinkedIn Sales Navigator · Marketing Cloud · MuleSoft · Salesforce Field Service · WealthBox · Zoho
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. One of my design documents states plainly that the build needs no custom Apex or pages at all; another recommends postponing a document-generation tool until the first phase had earned it. That costs me the most billable part of a project, 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 custom scheduling service — its own API, authorisation layer and notification workers — talking both ways to a Salesforce org built to match: orders into sessions into shifts, practitioner availability, time entries and post-session scoring. Bookings arriving from five instances of a third-party scheduling product land in the same model as everything else.
Configure-price-quote through billing schedules into revenue contracts and recognition, with an approval matrix in front of it and more than one payment gateway behind it. Cloud-marketplace orders land in the same pipeline as direct sales rather than in a spreadsheet beside it.
A marketplace where photographers, processing staff and agents each sign in to the same system and see a different one. Orders fan out into work orders and line items, move through an upload-and-review pipeline, and come back as a finished product — with payment capture and order history in the place the work actually happens.
Matters, claims, damages, negotiations, time and expense entries and billing, modelled from scratch. The design work was mostly forensic: reading three competing practice management products to establish what the firm actually relied on, before deciding what deserved to be rebuilt at all.
A sync between Salesforce and a portfolio accounting platform — households, financial accounts, holdings and balance history — with custom pages for the parts the standard integration wouldn't do, and a migration that merged the old records into the new model instead of leaving the firm running both.
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. The other half of the job is the opposite: drawing the object model before anything is built, so the org has a shape worth inheriting in the first place. Either way I spend as much time reading and drawing 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