Revenue teams routinely treat tool selection as the solution to an operating problem. Melanie Stiekman's career suggests a more demanding standard: strategy, infrastructure, process, and adoption determine whether the technology creates value.
Her path into RevOps began almost accidentally. An executive-assistant role expanded into office management, HR, contracts, an acquisition, and support for the company's first sale. That first sale exposed the absence of a sales process, operations process, and invoicing process. Building them became the work that defined her career.
Customer service teaches composure
Early jobs at Subway and the Staples copy center taught Melanie that customers sometimes bring the rest of their day into the interaction.
She learned to stay calm, understand what the business could actually provide, and communicate an alternative without escalating the situation.
Internal operations requires the same skill. A stakeholder may arrive frustrated with the CRM when the real problem is unclear ownership or an inconvenient policy. The operator has to hear the concern without allowing emotion to define the diagnosis.
Scrappy roles create business context
After college, Melanie moved to Southern California and eventually interviewed for an executive-assistant job at an early-stage company. The role expanded quickly.
Because the company was small, contracts, people operations, insurance, and business processes crossed her desk. She learned how the organization worked by helping it survive day to day.
That breadth created the context later needed to build revenue operations. She understood that a sales process cannot be separated from invoicing, customer delivery, or the people responsible for each handoff.
One sale can reveal the missing system
The company's first sale exposed that there was no complete process behind the win. The team had to determine how to move from commitment to contract, invoice, and delivery.
Melanie found that she enjoyed establishing the process and enabling other people to use it. That combination is central to RevOps.
A workflow is not finished when it is documented or configured. It is finished when the people involved can perform it and the organization can see whether it worked.
Maintenance mode can conceal stalled growth
Melanie stayed with the same organization through acquisitions by AOL and Verizon, accumulating more than a decade of experience. Eventually, the work moved into maintenance mode and stopped providing enough challenge.
Leaving that stability led to new roles, a COVID-era layoff, a difficult six-month search, consulting, another transition, and eventually BTC Inc.
The experience taught her not to rely on one company as the entire professional network. Operating skill matters, but relationships and a visible body of judgment help the market understand where that skill belongs next.
Tool choice follows the operating model
At BTC Inc., Melanie chose HubSpot in part because she was the administrator and needed something practical to configure. That did not make her a partisan for the platform.
Her principle is tool agnosticism. Start with the strategy, process, infrastructure, and users. Then choose technology that fits those requirements.
This order prevents teams from reproducing a weak process inside a newer interface.
Adoption is a designed outcome
If the team does not use the tool, the tool does not matter. Adoption requires more than a launch announcement.
Operators should involve users during discovery, explain the purpose of the change, reduce unnecessary steps, train through real workflows, support managers, and monitor behavior after launch.
Enablement is not decoration around the implementation. It is part of the implementation.
The practical lesson for RevOps teams
Before buying or replacing revenue technology:
- Define the operating problem and desired behavior.
- Map the process and ownership across functions.
- Confirm the data required for the workflow.
- Choose a tool the team can realistically administer.
- Design enablement and manager reinforcement before launch.
- Measure adoption and business outcomes after launch.
- Fix the process when the technology is exposing a deeper problem.
The best platform cannot rescue an incoherent operating model. A clear process, supported by adoption, can create value even before every tool is perfect.
About the guest
Melanie Stiekman is Director of Revenue Operations at BTC Inc. Her career spans office management, business operations, sales operations, enablement, consulting, and RevOps leadership across multiple company stages and acquisitions.
