HubSpot & Salesforce API-First Workflows
Overview
Rather than using the HubSpot and Salesforce front-end interfaces for CRM operations, Mark Hope has shifted to an API-first approach — interacting with both platforms programmatically via their APIs. This change dramatically increases throughput, unlocks automations that were previously impractical or impossible through the UI, and reduces the time cost of complex CRM tasks.
This approach emerged from the same broader pattern driving other tooling changes at Asymmetric: using AI-assisted scripting to eliminate low-value manual work and replace it with defined, repeatable programmatic operations.
The Core Shift
Previously, CRM tasks followed a manual UI workflow:
- Building a HubSpot automation could take 6–8 hours, and the result would frequently break or behave unexpectedly
- Salesforce changes required either deep expertise or hiring a specialist
- Debugging failures meant navigating the front-end to find what broke and why
With the API-first approach:
- Automations are defined by describing the desired outcome, then implemented programmatically
- Changes that previously required hours can be executed in a fraction of the time
- Tasks that were simply out of reach — due to complexity or UI limitations — become feasible
"Everything I'm doing now in HubSpot, I'm doing through the API, and I'm not doing anything on the front end anymore. I'm just finding that I can get a lot more done a lot faster, and also things that I could never have even done before."
— Mark Hope
Why This Works
The key insight is that knowing what you want to happen matters more than knowing how to do it manually. The API layer, combined with AI-assisted scripting, handles the implementation once the desired outcome is clearly defined. This inverts the traditional bottleneck: the constraint is now clarity of intent, not technical execution time.
This mirrors the broader productivity pattern Mark described: roughly 3× more work completed per day compared to six months prior, across all technical domains.
Practical Implications
- HubSpot automations can be built, tested, and modified programmatically — no more multi-hour UI workflows that break silently
- Salesforce fixes that would previously require hiring a specialist can be handled internally via API scripting
- The approach is extensible: as new CRM requirements emerge, they can be addressed with the same scripting toolchain rather than requiring new tooling or personnel
Related Capabilities
This API-first pattern is part of a growing internal toolbox that also includes:
- A [1] capable of bypassing anti-scraping measures
- AI-assisted SEO operations (bulk meta descriptions, alt text, keyword density) replacing manual WordPress workflows
- A document query system built for legal discovery (7,000-document corpus with state law ingestion)
Related Docs
- [2]
- [3]