What the practice does.
Three lanes, one engagement model: you work directly with a senior engineer from the first call to the last deploy. No account layer, no handoffs, no bench.
Salesforce front ends & integration
Lightning Web Components, Experience Cloud portals and B2B Commerce storefronts, built by someone who writes front-end code for a living. The work spans public-sector portals, partner and customer sites and storefronts, and the MuleSoft and API integrations behind them.
A lot of it is code health: components that grew without standards, tests that stopped meaning anything, accessibility nobody checked. That gets fixed in reviewable slices, with the reasoning written down.
Good fit when
- Your Experience Cloud site or storefront needs senior front-end hands
- Your LWC codebase has outgrown its first design
- A portal has to meet WCAG and work in more than one language
- Salesforce has to exchange data reliably with other systems
AI agents & MCP integrations
Agents that work against the systems a business already runs, not demos. I built a contract-analysis agent, with an MCP server and every output checked against its source documents, that was productized and used across a consulting practice, and an agentic prototype on Health Cloud, Agentforce and Data Cloud that became a standing sales tool.
Salesforce now hosts MCP servers and Agentforce has its own MCP client, so the same patterns connect Salesforce data to the AI tools your team uses, and back. The engineering is the same either way: decide what the agent may touch, verify what it returns, and make the result something people trust.
Good fit when
- You want an agent working with your real data, safely
- An internal system or Salesforce needs an MCP server in front of it
- An AI pilot works in the demo but nobody trusts it yet
- You're weighing Agentforce against tools your team already uses
Product engineering
Full-stack web products in React, Next.js and TypeScript on Node.js, and Vue when that's what the codebase uses. Past work includes salon booking for a national beauty retailer, an advisor app for an investment bank's wealth-management business, and an insurance plan comparison tool. C# and Python where the project calls for them.
This lane covers greenfield builds, feature work inside existing codebases, and the unglamorous-but-critical stuff: performance, accessibility, and tests that hold up.
Good fit when
- You need a product built, not a team assembled
- An existing codebase needs senior hands, fast
- Your front end has outgrown its foundations
- You want architecture decisions you can defend later
Simple by design.
Most engagements move from first note to first commit inside two weeks.
A short call to understand the project, the constraints, and whether it's a fit — both ways.
A brief written scope: what gets done, how it's priced, and what you'll see week to week.
Weekly cadence, working software over status decks, and direct access in your channels.
Documentation and transfer are part of the scope, not an add-on. The work is yours to run.
Same three offers, however you hire.
Every lane above is sold as a Review, a Sprint or a Retainer, whether you hire Foundry Tabor directly or through an agency. Each one ends in writing your team keeps.
1–2 weeks, fixed fee. A written assessment of an org or codebase: what's at risk, what it costs to fix, and in what order. Often the first step before a Sprint.
2–6 weeks, fixed scope. A defined build, rescue or integration, shipped with a handover document and a decision log.
Monthly, committed hours. Ongoing senior capacity in your tools, with a written summary of the month's work.
Senior capacity under your name.
Agencies bring me in as white-label senior capacity: in your Slack and your Jira, on your process, under your brand. Your client relationships stay yours, and I don't solicit your clients.
I also write. Estimates, SOW sections, solution designs and client-facing documentation come from the person who'll build the thing, so what you sell and what gets built match.
What agencies get
- Overflow capacity without a new hire
- Salesforce depth: LWC, Experience Cloud, B2B Commerce, MuleSoft
- Pre-sales help: discovery, estimates, SOW review
- Written handover, so your team can run what I build
- Partner rates that leave room for your margin
Not sure which lane fits?
Describe the project in a paragraph and I'll tell you honestly — including if it's not a fit.