Lehi, Utah

Renzo Dupont

Salesforce & Software Engineer

18+ years building business systems, integrations, automation, and software platforms.

See my work Read my resume

18+

Years of experience

15+

Platforms & technologies

Engineers led

Selected Work

Systems I've owned end to end

Four platforms across fintech, marketing SaaS, and multi-tenant product — the problem each one started from, the architecture I chose, and what changed as a result.

OpenAva

Founder & Owner

2024 – Present

products in production

12+

functional modules

verticals served

A multi-tenant, white-label business platform shipping as two products: Ava CRM for operators and Agency OS for marketing agencies.

The problem

Small operators outgrow spreadsheets but cannot absorb the cost or implementation overhead of enterprise CRM. The gap is not features — it is that every vertical needs a slightly different data model, and most platforms make you fork the product to get one.

What I built

Designed a PostgreSQL-backed multi-tenant data layer with per-tenant isolation, so a single deployment serves independent customers without forking the schema per vertical
Created user-defined custom objects and fields — the same mechanism that lets one codebase serve dental practices, real-estate teams, lending offices, restaurants, and workshops
Architected a single versioned REST API (api.startupp.ai) as the only path to data; every client — web app, agency console, customer portal, third-party integration — is a consumer of that one contract
Built React + TypeScript application front ends and an Astro static marketing surface on Cloudflare Pages, so public pages ship fully-crawlable HTML with no client-side routing
Designed a BYOK model for AI features — customers supply their own model keys, which keeps inference cost off the platform and customer data out of a shared vendor account
Built twelve-plus functional modules on shared primitives (contacts, invoicing, projects, inventory, forms, email, workflows, reporting) rather than as separate applications
Localized the product to English, Spanish, and Japanese at the routing layer, not as a bolt-on translation pass

PostgreSQLREST APIReactTypeScriptNode.jsAstroCloudflareMulti-tenantWhite-labelLLM / BYOK

getopenava.com Ava CRM Agency OS

Gargle, Inc.

Senior Engineer / Business Systems Architect

2020 – Jul 2026 · Lehi, Utah

75%

technology spend reduced

20%

client retention increase

15+

platforms integrated

An 80-person dental marketing company running sales, marketing, service, and finance on a heavily customized Salesforce Enterprise Edition org.

The problem

The business technology stack had grown by accretion — redundant tools, unclear ownership, and any structural Salesforce work (org merges, migrations) outsourced at $20K+ per engagement. Leadership had no reliable read on which clients were at risk of churning.

What I built

Sole owner and architect of the Salesforce org and surrounding stack — data model, internal tools, executive reporting, cloud infrastructure, and vendor systems across 15+ integrated platforms
Ran multiple org merges and splits end-to-end with zero downtime: Apex batch jobs for staged data migration, validation triggers, and data-integrity controls — bringing in-house work previously outsourced at $20K+ per engagement
Built order-to-cash integration connecting Salesforce accounts, orders, and invoicing to ChargeOver, Stripe, and QuickBooks, so finance and revenue operations read from one system of record
Exposed Salesforce data to external customer-facing UIs through custom REST API layers rather than granting portal licenses — keeping the CRM authoritative while controlling what leaves it
Built executive BI and client-health reporting in Python against Salesforce data, surfacing retention risk to leadership before renewal conversations instead of after
Owned release engineering: GitHub-based CI/CD, a sandbox strategy spanning partial and full-copy environments, and Apex test coverage standards
Established the code-review guardrails that let junior engineers contribute safely using Claude Code and similar AI coding tools
Led a 5-person development and analytics team — sprint planning, code review, deployments, and requirements translation across Salesforce, Node.js, React, Python, and SQL Server

Salesforce (Apex, LWC, Flows, SOQL)Node.jsTypeScriptPythonREST APIsChargeOverQuickBooksStripeTwilioRingCentralSQL ServerAWSGCPn8n

DentalMarketing.net / 123 Postcards

Fractional CTO · previously Team Leader & Developer

2013 – 2019, 2021 – 2023 · Heber City, Utah

60%

call-scoring efficiency gain

40%

cost reduction

30%

productivity increase

A dental marketing SaaS whose reporting had not kept pace with the business — campaign data lived apart from CRM records, and both executives and clients were reading stale exports.

The problem

Leadership could not see campaign performance against client outcomes without manual assembly, and clients had no self-serve view at all. Call scoring — the core quality signal for the product — was a slow manual process.

What I built

Modernized reporting end to end: custom executive dashboards for internal leadership and client-facing dashboards for customers, replacing manually assembled exports
Built .NET Web APIs as the data layer between the platform and its front ends, so internal and client-facing dashboards consumed the same governed contract instead of querying production directly
Delivered dashboard front ends in React and Angular against those APIs
Built a Salesforce-integrated data platform connecting campaign data to CRM records over REST, making campaign performance and client engagement visible in one place
Redesigned the call-scoring system, cutting the manual review loop that gated the product’s core quality metric
Led a distributed engineering team across India, Nepal, and the Philippines, introducing structured scrum practices to improve release quality and cross-timezone communication

.NET / C#Web APIReactAngularSalesforceNode.jsAWSREST APIs

Credilit S.A.

Fractional CTO

2014 – 2025 · Montevideo, Uruguay

$20K+

saved annually

11 yrs

engagement length

40+ yr

legacy business modernized

A credit administrator more than 40 years old, running loan origination on manual process and phone calls while its CRM data sat in Salesforce.

The problem

Clients and partner brokers had no way to submit or track loan requests themselves. Every request round-tripped through staff, and the operational record lived separately from the Salesforce data that the business actually ran on.

What I built

Led the technology transformation end to end — from a manual, phone-driven origination process to client- and partner-facing self-service
Built ASP.NET (MVC) portals connected directly to the company’s Salesforce environment, so clients and partners could submit and manage loan requests against live CRM records rather than a synced copy
Kept Salesforce as the system of record and treated the portal as a controlled view onto it — avoiding the dual-source drift that usually follows bolting a web app onto a CRM
Automated accounting workflows and delivered integrated marketing dashboards for leadership
Hosted on Azure, with Salesforce CRM workflow and admin/dev work carried alongside the application build

ASP.NET MVCC# / .NETSalesforceAzureSQL ServerREST APIs

Approach

How I build

Positions I've arrived at from 18 years of owning production systems — and would defend in a design review.

One system of record, always

Most business-systems failures are not code failures — they are two systems that both think they are authoritative. I keep the CRM (or the database) as the single source of truth and expose everything else through a controlled API layer, even when a direct sync would ship faster.

Migrations are engineering, not data entry

Org merges, splits, and platform migrations get treated as staged, reversible, tested work — batch jobs, validation triggers, integrity controls, and a rollback story — not a weekend of Data Loader runs. That is what makes zero-downtime cutovers repeatable instead of lucky.

Integration is a contract problem

Connecting fifteen platforms is easy; keeping them connected through five years of vendor API changes is the actual job. I design integrations around explicit contracts and failure behavior, so a partner outage degrades one workflow instead of corrupting the pipeline.

Reporting should change a decision

A dashboard that nobody acts on is cost, not value. I build reporting backwards from the decision it should inform — which is why the client-health work at Gargle surfaced churn risk before renewal conversations rather than after them.

Leverage juniors, do not gatekeep them

Leading a small team means the constraint is review capacity, not typing speed. I put guardrails in place — CI/CD, sandbox strategy, test coverage standards, review checklists — so less-experienced engineers, including ones using AI coding tools, can ship to production safely.

Cut spend by removing systems, not features

The 75% reduction at Gargle came from consolidating redundant tools and reallocating licenses, not from degrading what the business could do. Knowing what a stack actually needs is the prerequisite to knowing what it can lose.

Stack

What I go deep on, and what I've shipped with

I own this

Primary responsibility in production, at depth, over years.

Salesforce Platform

ApexLightning Web ComponentsFlowsSOQL / SOSLREST IntegrationsSales & Service CloudData MigrationSandbox & Release StrategySecurity & Sharing

Business Systems & Integration

System-of-record architectureOrder-to-cashChargeOverQuickBooksStripeTwilioRingCentralExecutive BIOrg merges & splits

Engineering

Node.jsTypeScriptC# / .NETPythonReactREST API designPostgreSQLSQL Server

I've shipped with this

Used in delivered production work — productive, not my deepest specialty.

Cloud & Infrastructure

AWSAzureGCPCloudflare (Workers, D1, R2, KV)DockerGitHub Actions

Front End & Data

Next.jsAngularAstroMongoDBMySQL

AI & Automation

LLM workflowsn8nZapierClaude CodeHarvard CS109x (ML/AI with Python)

About

About my experience

I have about 18 years of experience building and supporting the business systems that companies rely on, with most of that time focused on Salesforce. I've worked as both an administrator and a developer — setting up CRM workflows, connecting different systems together, building custom tools and reports, and automating manual work. Over the years I've worked with a range of technologies, including Apex, Node.js, TypeScript, Python, C#/.NET, React, SQL databases, and the major cloud platforms. I've also led and mentored small engineering teams, handling planning, code reviews, and day-to-day delivery. I do my best work where business systems, hands-on development, and working with a team come together.

References

“

Renzo has a great mix of technical talent and people skills that make him an invaluable asset to any organization. He does a fantastic job melding together the technical and automation pieces to improve the company overall.

Jacob

Former CTO, Gargle

“

Renzo brings a ton of technical talent to any engineering environment. He is highly effective in his communication skills and ensuring everyone he is working with is on the same page.

Skyler

Senior Frontend Engineer, Payscale

“

Renzo is an exceptionally thoughtful engineer. He approaches system design with clarity and intention, always considering scalability, security, and long-term maintainability. His solutions shine with structure, reliability, and a vision for the future.

Oscar Vissani

CEO/CFO, Credilit S.A.