Senior Salesforce consultant with 7+ years running complex, multi-cloud orgs. You bring the messy requirements, the half-finished integration, or the admin backlog. I scope it, build it, test it, and ship it.
Plenty of consultants will sell you a strategy presentation and disappear before anything gets built. I work the other way around. I'm the person who opens the org, builds in a sandbox, tests against your real data, and deploys on a date we agreed to.
The name is the trade. A wright is the old word for a skilled builder: shipwright, millwright, wheelwright. And the field is where real work happens, inside the org, not inside a slide deck. I'm the builder you send into the field.
One more thing worth saying plainly: I don't write code, on purpose. Everything I build uses Flow and Salesforce's native toolkit. That means your admin can open, read, and maintain every piece of it, and nothing I ship becomes technical debt your team can't touch.
A clear fit on both sides saves everyone time. Here's mine.
Win rates, pipeline, and account metrics that don't match reality because the underlying data and rollups were never built right.
Critical processes tracked in Excel because Salesforce "couldn't do it." It can. I've retired entire trackers by building the real system inside your org.
Years of flows, process builders, and one-off fixes stacked on each other until nobody knows what's safe to touch. I untangle it and leave it readable.
Requests approved over email, lost in Slack, or stuck with someone on PTO. I build multi-level approval workflows people actually follow.
A queue of field requests, flow fixes, and layout changes your one admin can't get to. I clear it on a sprint cadence.
Assignment, routing, and notifications done by hand. I automate the repetitive stuff so your team works deals instead of records.
Seven-plus years as an enterprise Salesforce administrator and builder, currently running a complex multi-cloud org for a global healthcare technology company. Before that: a utilities organization with 300+ users and a financial services firm.
Cross-system integrations. Connected the CRM to marketing and customer data platforms so records sync between systems instead of living in silos. Set up with dedicated, secured service accounts and documented end to end, all with native tools.
Record-triggered routing and assignment flows. Ownership logic that evaluates when a deal is created and re-evaluates as it moves down the funnel, with regional fallbacks when no one matches and condition-gated stage changes so nothing goes live until the right team signs off.
Account-level rollup architecture. Designed rollups for win rate, bid and project counts, and average project age, current year and rolling 12 months, across standard and global account hierarchies. Pipeline reports leadership actually trusts.
Retired a business-critical Excel tracker. Built a full project management system inside Salesforce for an analyst team: child records for deliverables, automatic timeline calculations, and an inline-editable tracker report that refreshes itself.
Account lifecycle and data governance. Designed an inactive-account and reactivation process with guided screen flows, stage-gated required fields, and clear validation messages that cleaned up data flowing to downstream billing and reporting systems.
Sprint-based feature delivery. Regular release cadence with sandbox testing, UAT, documented deployments, and plain-English release notes to the whole company after every deploy.
Ongoing monthly support. I clear your backlog, handle requests, and keep the org healthy. Your team gets a senior Salesforce resource without the senior salary.
Connecting Salesforce to your marketing, data, and business platforms with native connectors and declarative tools. Marketing Cloud Connect, Apollo, and Jira among them. Scoped, connected, tested, and documented so the next person can maintain it.
Record-triggered flows, scheduled paths, screen flows, assignment logic, routing, and notifications. Built to handle the edge cases, not just the happy path.
Multi-level approval processes for spend, requests, and exceptions. Clear routing, escalation paths, and a record of who approved what and when.
Rollup architecture, dashboards, and report frameworks your leadership can trust. Numbers that match reality and update themselves.
A full review of your automation, security, data quality, and technical debt. You get a prioritized findings report and a fix-it roadmap.
This is the difference between a flow that works in the demo and a flow that works in year three. Non-negotiable, included in every build.
Errors alert a human. When something fails, the right person gets notified with enough detail to act. Silent failures are how orgs rot.
Flow and native tools only. No custom code means nothing your team can't open, read, and maintain. What I build never becomes the technical debt nobody dares to touch.
Readable by the next admin. Elements, variables, and versions named so anyone can open the flow and follow the logic without me.
Automation you can turn off. Migrations and data loads need a way around your automation. I build the off switch in from day one.
Runs only when it should. Tight entry conditions so automation fires on the records that need it and leaves everything else alone.
The why, written down. Every build ships with a doc covering what it does, why it's built that way, and what to check when it misbehaves.
Three ways to work together. Every engagement starts with a free 30-minute call so we both know it's a fit before money changes hands.
Hourly work: $135/hour for ad hoc support and short engagements. I recommend fixed-price projects for anything bigger. You know the cost up front, and I carry the risk of my own estimates, not you.
Same process every time. You always know what stage we're in and what happens next. Scroll through it like a flow, because it is one.
You walk me through the problem. I ask the questions a builder asks: data model, users, what's been tried. No pitch.
If I'm not the right person for it, I'll say so and point you somewhere better. If I am, we move forward.
Written scope with deliverables, timeline, and a fixed price. You sign off before I touch the org.
Everything gets built and tested in a sandbox first. You get progress updates in plain English, not status-meeting theater.
Your team runs the new build against real scenarios. I fix what we find before anything ships.
Clean deployment to production, plus documentation your team can actually maintain. No mystery automations.
I stay on for a month after launch. Real usage always surfaces something, and I'd rather fix it than hand you a ticket queue.
The platform skills transfer. If your team sells B2B and runs on Salesforce, I can work in your org.
No account manager, no offshore handoff, no junior learning on your dime. You get one senior builder, start to finish.
Seven years as the in-house admin means I know what happens after the consultant leaves. I build for the team that has to maintain it.
You'll never get a status update you need a translator for. If something's behind, I tell you. If something's a bad idea, I tell you that too.
Every build comes with documentation your team can use. When I'm done, you own the system, not a dependency on me.
Scoped projects get a fixed quote and a delivery date. If my estimate was wrong, that's my problem to absorb, not yours.
The first call is free, 30 minutes, and useful even if we never work together. Tell me what's broken and I'll reply within one business day.