Same work. Your colors.
Practical engineering for GTM & operations
I help teams clean up their data, automate manual work, and build AI tools they can actually use.
Hi, I’m Brandon. I work where business problems meet engineering.
What I can help with
Start with the part of the job that takes too much time, depends on too many handoffs, or never quite works.
CRM migrations, system integrations, and the cleanup that makes them trustworthy. I turn inconsistent records and business rules into a process people can follow.
Less spreadsheet archaeology.
Clearer answers.
Routing, research, reporting, and the glue between tools. I build automations and internal tools around the way your team actually operates.
Fewer manual handoffs.
A process you can understand.
A focused assistant, a research workflow, a better way to score accounts. I connect AI to useful data, test its behavior, and keep people in control of the decisions.
A specific job.
A result you can check.
Selected work
Different systems. Different teams.
The same job: understand the problem,
then build something that holds up.
Data engineering / CRM migrations
I built Python migration pipelines that mapped unfamiliar CRM data into a repeatable process, then helped build and lead the team using them.
The problem. Every source CRM came with its own structure and interpretation of the same business information. Manual cleanup made each migration a new project.
My contribution. I worked with clients to understand their data, built mappings and transformation scripts, and automated migration and validation steps with Python and Salesforce tooling.
What changed. Multi-week data projects became work that could run in hours, with reusable tooling and a team able to carry the process forward.
Applied AI / GTM systems
I reworked an unreliable scoring workflow by separating the criteria, grounding the research, and checking results against known examples before expanding coverage.
The problem. An answer can look convincing while being a poor fit for the business. Account scoring needed clearer definitions and a way to check the model’s judgment.
My contribution. I combined firmographic information with LLM-assisted research, worked through the scoring criteria, and tested representative accounts before running the wider dataset.
The useful part. The workflow made the criteria and validation process explicit, so the team had something concrete to inspect and refine.
Internal tools / Workflow automation
I built internal AI tools for company news, deal health, and next-best actions, including a Slack-based research assistant that brought useful account context into the team’s workflow.
The problem. Useful context was spread across tools, documents, and research. Asking people to visit another destination added another step.
My contribution. I built a Slack-based news and research workflow, connected relevant account information, and supported the people learning to use the tools.
The approach. Put a bounded capability in the place the team already works, and keep access to information tied to the person using it.
How we’d work together
We walk through the real workflow, the people involved, and where things get stuck.
We agree on a bounded problem, what success looks like, and what the build needs to work with.
I build against real examples, test the important paths, and make the tradeoffs visible.
Working software, clear documentation, and a team that understands what it has.
The person behind the build
My background runs from IT infrastructure and data migrations to trading systems and GTM engineering. I’m comfortable getting into the technical detail and explaining it to the people who need the result.
That same curiosity follows me outside client work. A few things on my own workbench:
League analytics with a clear trail back to the source data.
Local prototypeA deck-building tool where changes get a preview before they get applied.
Local alphaA macOS dictation tool that keeps the speaker in control of the final text.
Personal desktop toolLet’s make something useful.
Tell me what your team is trying to do, what tools you’re working with, and where the process breaks down. We can figure out a useful place to start.
brandon@freeck.com