Plano, Texas · Senior Business Analyst · Salesforce · AWS · AI
Senior Business Analyst at HotelKey, working at the scope of a solution architect. Five-plus years across hospitality SaaS, automotive, and financial services, sitting where enterprise clients, product, and engineering meet: running discovery, designing the Salesforce, AWS, and API integrations that follow, testing them to certification, and increasingly wiring GenAI into the delivery itself.
I'm a Senior Business Analyst at HotelKey, where I sit between enterprise hotel brands and the engineers who build for them. I run discovery, write the specs, design the Salesforce and API integrations that follow, and stay on the hook until they're certified and running in production. Seven Salesforce certifications, an AWS one, and a habit of writing the SQL that checks whether the system did what we said it would. Before this: financial forecasting at CG Infinity and a Salesforce re-architecture for Daimler AG at Infosys.
Definitions get agreed in writing before build, so UAT tests the logic we signed, not opinions.
A passing API call isn't a passing integration. I query the tables to confirm the data arrived correctly.
Flows and configuration before code. Solutions the next admin can read survive the one after that.
If the outcome can't be measured, the work isn't finished. The strip above is the receipt.
Building Trowel for Salesforce, an AI agent that audits a Salesforce org · studying for Salesforce AI Specialist · shipping one project a week through September.
Tools Salesforce (Sales & Service Cloud, Apex, LWC, Flows, Einstein) · Postman · Swagger/OpenAPI · SQL · AWS Kinesis, Glue, Athena, DynamoDB · Jira · Confluence · Agile/Scrum
Tools Python · SQL · Snowflake · Power BI (DAX, Power Query) · Power Automate · Alteryx · Excel · LLM summarization
Tools Salesforce (Apex, LWC, Flows, Process Builder) · GitHub Actions · Bitbucket · Jenkins · Tableau · Jira · Confluence · Agile/Scrum
Tools Video analysis · Database management · QA reporting
Nine-plus brands on a single org: brand as a data dimension, declarative-first automation, Einstein where it changed a decision.
+20% conversion · 70%+ FCR→ 02 · APIs & integrationSpec-as-contract, Postman collections, written pass/fail certification, SQL audits, and SLA tracking across 10+ mission-critical APIs.
30% fewer API support tickets→ 03 · AWS & dataKinesis, Glue, and Athena for live booking visibility, plus validating a DynamoDB DAX rollout against the SLAs brands actually enforce.
Validated · signed off→An AI agent that reads a Salesforce org's metadata and produces the Well-Architected assessment consultancies bill five figures for. It's the answer I'm working out to a question I keep hitting at work: what does agentic AI look like inside a governed enterprise platform?
Give it a city, a starting point, and a time budget; it returns a routed day plan through real places, using real street-network travel times, that gets you back where you started before the time runs out. Picking a day out is not a sorting problem: every attraction has a location, a visit duration, an opening window, and a value to a particular person, and choosing the best subset and the best order is the Orienteering Problem, which is NP-hard.
It is also a deliberate rebuild of my own 2018 university project of the same name. That version specified three itinerary modes, route optimization, ratings, and opening-hours awareness, and shipped a two-column SQL lookup over four rows of placeholder data. This repository is the honest version of that specification, and it tracks the gap on purpose.
An AI agent that reads a Salesforce org's metadata and produces the kind of Well-Architected assessment consultancies bill five figures for: dead automation, conflicting triggers, permission sprawl, and a prioritized remediation roadmap. The design principle is that findings are detected deterministically by dependency-graph queries, and the language model explains and prioritizes them but never discovers them, because a hallucinated finding would destroy the product's whole premise.
Currently early and paused while the travel planner takes priority. The scaffold, retrieval pipeline, and a deliberately seeded test org are in place; the parser, dependency graph, and eval suite are not yet written. Listed here because the architecture argument is worth reading, not because it is finished.
Static analysis for Salesforce Flow metadata: five rules that catch missing fault paths, hardcoded record IDs, recursion risk, dead automation, and two Flows fighting over the same field. Exits non-zero so it can gate a pull request.
View repository ↗ APIs · integration testingPartner certification for reservation APIs as one command: a mock CRS with deliberately planted defects, an OpenAPI contract, a Postman collection run by Newman, and an audit-ready pass/fail sign-off document generated from the results.
View repository ↗ Observability · SLA managementIntegration SLA monitoring as a system instead of a spreadsheet: scheduled probes into SQLite, rolling uptime and p95 latency against contractual thresholds, breach alerts with a cooldown, and a dashboard that shows which integration is failing and by how much.
View repository ↗Apex, Lightning Web Components, Flows, Einstein AI, Data Cloud. Well-Architected by habit: declarative first, code where it earns its place, CI/CD around all of it.
Kinesis, Glue, Athena, DynamoDB, S3, Lambda, API Gateway. Reservation data pipelines and near-real-time booking visibility; validating API performance and SLAs on DynamoDB-backed services.
Postman collections, certification cycles, SLA monitoring, payload auditing with SQL. I treat an integration as untested until the client's data has landed and been queried.
Claude, Einstein, prompt engineering, hybrid retrieval, LLM-as-judge evals. The interesting part isn't the model; it's the eval gate that makes it safe to ship.
Discovery, user stories, acceptance criteria, data mapping, UAT, partner certification, backlog prioritization, Agile/Scrum, Jira & Confluence. Client-facing by default; every requirement traceable to a test and a metric.
SQL, Snowflake, dbt, Power BI, Tableau, Python, Alteryx. Pipelines with quality checks, dashboards leadership actually opens.
Verify: Salesforce Trailblazer profile · AWS on Credly
I read everything that comes in. Fastest replies go to specific questions: a role, a project, an org that needs an honest look.