From first enquiry to a client who actually stays
Client Lifecycle and Growth System
Outcome
A repeatable path from first enquiry to a client who stays, with what they say feeding back into what gets built.
90%customer retention contributed to
Product work that stops at launch is half a job. This is the other half. The process that takes someone from first email to a client who stays, and the loop that carries what they tell us back into what we build.
- Company
- Inceo Group
- Product
- Client lifecycle process, CRM and prospecting model
- Role
- Business Development Associate
- Timeline
- October 2025 to September 2026
- Status
- In use
90%
customer retention contributed to
35
prospects identified
6
conversions supported
€20m
opportunity surfaced
Team and ownership
Said plainly, because it is what makes the rest believable.
I owned
- The client journey from first enquiry through to ongoing contact
- CRM structure, records and follow up workflows
- The marine finance prospecting model
I supported
- Proposals and client facing materials
- Retention across the existing client base
- Introducer and referral relationships
I did not own
- Commercial terms and pricing
- Credit and lending decisions
- The underlying finance products
The problem
Client communication, tracking and follow up were all happening, just not consistently. What a client experienced depended on who picked it up and how busy that week happened to be.
Follow up was the specific weak point. Enquiries got a good answer and then went quiet, because nothing in the process said whose job it was to get in touch when there was no obvious reason to.
We were also throwing away good information. People told us what they needed and it never reached anyone making product decisions.
What made it hard
- This is a relationship business. Introducers and referrals matter more than volume, so a process built around sending more emails would have broken the thing that actually worked.
- Decisions take months. That long quiet gap is exactly where an inconsistent process loses people.
- Small team, no operations person. Whatever I built had to be maintainable by people whose real job was something else.
My job
- Run the client cycle end to end. First enquiry, working out what they need, proposals, regular updates, follow up.
- Keep the CRM accurate enough that the pipeline showed reality rather than optimism.
- Build a prospecting model for marine finance, a segment the business wanted to test.
- Carry what clients said in commercial conversations back into product discussions.
- I did not own pricing, credit decisions or the finance products themselves.
What I found out
- Mapping the real journey showed the gap was not at the pitch. It was the quiet weeks afterwards, where nothing was scheduled so nothing happened.
- Staying in touch predicted retention better than deal size did. Clients who heard from us on a predictable rhythm stayed, whatever their position was worth.
- In marine finance, referrals and introducers converted far better than going in cold, so I built the model around relationships instead of lists.
What I decided
- 01
One record per relationship, kept honest
A CRM that flatters you is worse than no CRM. Keeping it accurate, including marking things dead when they were dead, turned it into a planning tool instead of a report.
- 02
Schedule the check in that has no reason
The updates that kept relationships alive were the ones with no commercial purpose at all. Making those a scheduled part of the process, rather than a good intention, is what moved retention.
- 03
Build prospecting on introducers, not volume
For marine finance I built the model around referral routes, because that is what the evidence pointed at. It produced 35 real prospects instead of a much longer list of colder ones.
- 04
Send commercial feedback to product
What clients asked for in sales conversations went to the same place as discovery findings. Sales objections and product requirements are usually the same information arriving through a different door.
The thinking, not the screenshots.
These are the structures the work produced. That is the part that carries over to the next product.
Artifact · Lifecycle design
One path, from enquiry to a relationship that holds
The gap was never the pitch. It was the quiet weeks afterwards, where nothing was scheduled and nothing happened.
- 01
Enquiry
First contact goes on one record, with a name against it and a next step
- 02
Needs discovery
Understand what they are dealing with before proposing anything
- 03
Proposal
A response shaped by what we learned, not a standard pack
- 04
Ongoing communication
Scheduled updates, including the ones with no commercial reason at all
What clients said in commercial conversations went back into the same place as discovery findings. Sales objections and product requirements are usually the same information arriving through different doors.
Artifact · Commercial evidence
What the process produced
90%
customer retention
contributed to
35
prospects identified
marine finance
6
conversions
supported
€20m
opportunity surfaced
via introducers
What changed
- Helped hold retention at 90 percent through a consistent update and follow up rhythm.
- Found 35 prospects in marine finance and supported six conversions.
- Surfaced a 20 million euro opportunity through referrals and introducers.
- Gave product discussions a live source of commercial evidence instead of second hand stories.
Product outcome
A repeatable path from first enquiry to a client who stays, with what they say feeding back into what gets built.
What I learned
Owning both ends of the relationship changed how I think about product. When you are the person explaining a decision to the client who has to live with it, adoption stops being someone else's problem. It also made me sceptical of feature requests made in sales meetings. People ask for what they can picture, and what they can picture is usually a slightly better version of what they already have.
What I would do better
The process leaned on me far too much. I documented the workflows but never built a way to check the rhythm was still happening once I was not the one doing it. I would now pick a few simple health measures, like time to first reply, how recently we contacted someone, and how much of the pipeline has a scheduled next step, so the system reports on itself. I would also write down the route from commercial feedback into product, because relying on me being in both rooms is not a process. It is luck.