Case Study

Case Study

How We Combined Operations Consulting and Automation at Ops Kings

· Updated

· Updated

We joined Client Ascension separately and met in London before developing an offer together. Tony worked on operations problems; Ryan worked on automation. Clients could need both, which gave us a practical reason to combine the services.

By the interview, we reported $95,000 in revenue for the previous month. Growing the team and transferring client relationships were important parts of that stage. The figure was monthly business revenue, not profit or personal income.

The partnership joined two different starting points

Tony described coming from operations work and initially helping people for free, then gaining referrals. Ryan described having automation experience but no developed offer or customer base when he entered the community.

After connecting through Slack and meeting in London, we discussed a joint offer. Tony could identify an operational problem that required a technical solution, while Ryan could connect automation work to how the business actually ran.

Content showed both clients and prospective teammates the work

Ryan said Twitter supplied most leads during roughly the first year. He used content to explain the work, test offers and learn from the response rather than assume the original idea was already right.

Content also brought people into the team. A business analyst saw a video of a client lunch we held around the Tampa event, reached out and later became a key team member. That was a different benefit from counting audience size alone.

Client Ascension related reading: Luke’s automation-offer account describes changing the service structure and adding fulfillment support.

We made client proof something to track

Tony described tracking video testimonial interviews and comparing them with the number of clients onboarded. We wanted to capture what the work had done and share that evidence with the market.

We estimated almost thirty video interviews over a year. Those were client stories we could share alongside the work we were doing.

Hiring mattered when people could own the relationship

Business analysts, client-success staff and developers began handling client relationships rather than leaving the founders in every interaction. That let us take on more work while spending more time improving the service itself.

Ryan described having to figure out how to add value after delegating development. Training people and improving the systems around them became part of that role, rather than treating a developer hire as the end of his involvement.

Client Ascension related reading: George’s leadership-team account describes promoting leaders and assigning departmental metrics.

Client Ascension was also a customer

During the interview, Andre described Client Ascension as a customer of Ops Kings. He gave the example of automating student assignment to customer-success staff based on capacity and availability.

That was a commercial relationship alongside our participation in the program. The interview therefore included both our experience as students and the host’s experience buying our service.

Adapted by Client Ascension with AI assistance from Ryan and Tony's interview. The first-person narrative follows the source speaker’s account. Watch the original video