Sebastian joined the team to tackle something I knew I needed to pay attention to but never would: revenue operations. For a mathematician, I have a horrible time with numbers. I’d always viewed sales methodology and forecasting as a bit of hocus-pocus, which was exactly why I needed to find ways to instrument the work better and make the commercial reality more visible.
He was the least romantic of the three, which is part of why he mattered so much. Shelley could get a rep a meeting. Sandy could spot a churn risk and help us turn it around. Sebastian dealt with the systems work that determines whether a revenue team actually functions well. It is easier to ignore that work because it rarely announces itself all at once. It just quietly taxes the team until everyone is compensating for broken process with memory and habit.
I brought him on to handle the systems work that keeps a GTM org from gradually drifting into dysfunction. Some of it was straightforward data work. Some of it was structural. Some of it was about making hidden commercial reality more visible. All of it had the same effect: it moved important but under-owned work out of the realm of “somebody should really get to that” and into the realm of actual ownership.
A lot of RevOps pain is not dramatic. It is cumulative. A field gets stale. A workflow gets weird. An account picture becomes incomplete. A useful view of the business exists in fragments but never gets assembled into something the team can manage from. People compensate for the system gaps with memory and habit until they can’t anymore. Sebastian reduced that tax.
One of the most valuable things he did was help turn scattered commercial information into something more operationally visible. Projecting organic growth for potential upsell is a good example. The raw information existed, but it was not yet arranged into a view that made management easier. Once that got built into the system properly, the team had a clearer picture of where value was actually accumulating and where opportunity might exist. That is not flashy work. It is foundational work.
Sebastian also surfaced a less glamorous truth about agentic systems: once an agent owns part of a business process, you inherit all the maintenance burden that comes with it. Access has to be provisioned. Integrations have to hold. Shared context has to stay coherent. The toolchain breaks in annoying ways. The work does not stop being operational just because AI is involved.
In some ways, Sebastian was the cleanest illustration of what separated the agentic team from prompt experimentation. A prompt can help clean up a spreadsheet. A persistent agent with operational ownership can become part of the machinery that keeps a revenue organization functioning. That is a different category of thing, and it creates a different category of responsibility.
Sebastian mattered because he made the systems side of the business more visible, more maintained, and less dependent on humans remembering to get to it after they finished everything that felt more urgent. If Shelley proved an agent could help own the front of pipeline work, and Sandy proved an agent could help own customer awareness, Sebastian proved that agents could also take on the quiet infrastructure work that keeps the whole GTM machine from wobbling.
That is why the team felt real.
On the name
Sebastian is named after Sebastian the crab from The Little Mermaid, keeping with the shell and claw theme running through all three agents and the OpenClaw platform they live on. The fit is good: Sebastian works in the systems that keep everything else running—CRM hygiene, data quality, revenue visibility. Mostly invisible, rarely celebrated, essential to the machine. Just like the original.