Back to selected work
PRODUCT CASE STUDY / CLYNTO AI

From scattered account signals to a clear next action.

Clynto was an AI-powered Customer Success platform for lean B2B SaaS teams. I worked across customer discovery, segment selection, product definition and the build from an early concept to beta.

CLYNTO / AGENTS & WORKFLOWSPRODUCT CAPTURE
Clynto Agents and Workflows product interface
Actual product interface01 / 02
ROLECo-Founder & Director
TEAM5–7 engineers
SCOPEDiscovery to beta
BETA CONTEXTFour users at Docsumo
THE PROJECT IN BRIEF

A product problem, a focused first customer and a workflow to prove.

THE CHALLENGE

Customer context was spread across systems. Lean teams still had to connect the signals, decide what mattered and make sure someone followed through.

THE PRODUCT DIRECTION

Bring account context together, surface explainable signals and route a useful next action to a clear owner.

MY CONTRIBUTION

Customer conversations, segment and GTM thinking, MVP prioritisation, product requirements, engineering collaboration and beta learning.

100+customer conversations
50+B2B companies
10–12problem areas grouped
2–3MVP bets prioritised

These figures describe discovery activity and product scope. They are not adoption, revenue or customer outcome metrics.

THE DECISION TRAIL

Five decisions that shaped
the product.

Follow the story from the original workflow problem through customer selection, product choices, execution and beta learning. Each chapter is self-contained, so you can go straight to the part you want to explore.

CHAPTER 01

Understand the work
before designing the product.

The first task was to understand how Customer Success teams actually managed their accounts, where context lived and where follow-through became difficult.

01 / THE PROBLEM

The data existed. The hard part was turning it into timely action.

As a B2B SaaS company grows, customer context spreads across CRM, product analytics, billing and support. Someone still has to connect those signals, decide which accounts need attention and make sure the follow-up happens.

For a lean team managing dozens or hundreds of accounts, this work can become inconsistent. A drop in usage, a change in champion activity or a renewal date may be visible somewhere, but the signal is useful only when it is understood in context and reaches an owner in time.

The opportunity was not simply to add another dashboard. It was to shorten the distance between a meaningful signal and a clear, owned next action.

01Scattered context

CRM, usage, billing and support live in separate tools.

02Late visibility

Account changes surface during reviews or after a customer goes quiet.

03Manual triage

CSMs decide what matters, what is urgent and who should act.

04Follow-up slips

Actions lose momentum across inboxes, spreadsheets and task tools.

This problem framing synthesises the workflows explored during the build and Clynto's documented product focus. It is not a verbatim customer quote.

02 / CUSTOMER DISCOVERY

Look for repeated jobs, not a longer feature wish-list.

100+customer conversations
50+B2B companies
10–12problem areas grouped
2–3MVP bets prioritised

I used conversations to compare workflows across companies, then grouped recurring needs into a smaller set of opportunities. The important distinction was between a one-off request and a job that appeared repeatedly across the segment we wanted to serve.

The discovery lens focused on the user's weekly routine, data sources, breakdown points, current alternatives and buying context.

01 / WORKFLOWWalk me through the week.

How are accounts reviewed? What happens before a renewal? What changes when usage drops?

02 / DATAWhere does the context live?

Which CRM, billing, support and product tools are used? What is copied into spreadsheets?

03 / BREAKDOWNWhere does the process fail?

Which accounts get missed? What triggers late escalation? Who owns the follow-up?

04 / ALTERNATIVESWhat do you use instead?

Software, spreadsheets, exports, inboxes, consultants or manual review. Why do they remain?

05 / BUYING CONTEXTWho feels it and can act?

Who owns retention, who uses the workflow and what would make a new tool worth adopting?

INSIGHT 01Customer context is split

People switch between systems to understand the state of an account.

INSIGHT 02Health is hard to trust

Teams rely on judgement or static signals without a clear explanation.

INSIGHT 03Coverage does not scale

High-touch accounts receive attention while the long tail gets reviewed less often.

INSIGHT 04Signals do not own themselves

Even when a problem is visible, follow-up needs an owner, a next step and a deadline.

The problem areas are a synthesis of recurring themes, not percentages or verbatim interview themes. No interview transcripts or individual quotes are recreated here.

WHAT THIS CHANGED

We framed the opportunity around a complete job: understand which account needs attention, why it matters and what should happen next.

THANK YOU FOR READING

Good products start
with good questions.

I’d be glad to talk about product discovery, AI workflows or the decisions behind this build.

Get in touch Connect on LinkedIn ↗