CRM · lead pipeline · reminders · booking system · 2017
Just Coaching CRM — lead pipeline automation from my early 42 days.
Early full-stack work while starting 42: CRM feature implementation for a coaching business, including lead pipeline automation, reminder flows, booking-system improvements, and the practical glue that kept follow-up from falling through the cracks.
A pipeline that
remembers the next move.
The shape
2017
Early 42 period
CRM
Business operating system
Lead pipeline
Automation focus
Bookings
Feature implementation
Public proof
A real business with visible demand signals.
Market position
Leader du coaching sportif
The current public site positions Just Coaching as a leader in coaching sportif, with home, outdoor, and video coaching offers.
Review footprint
4.9 rating signals
The site surfaces 4.9 review scores with 1,193 and 149 review counts in its public proof section.
Media references
National press logos
The public site lists references including L'Equipe, Forbes France, L'Express, Doctissimo, Femme Actuelle, Le Parisien, France TV Info, Femina, and Magicmaman.
Operational surface
Client portal
The navigation links to a dedicated client.justcoaching.fr portal, which makes the CRM and booking context visible from the public surface.
Public references are taken from the current Just Coaching site and linked surfaces. They establish the business context; the case study describes the CRM feature work I contributed in 2017.
The problem
A coaching business with public demand signals lives or dies on follow-up. Just Coaching presents itself as a coaching sportif leader, points prospects toward a discovery session, and maintains a client portal. Leads arrive through conversations, forms, referrals, and calls; then the real work starts: qualify them, remind the team, book the right slot, and keep the relationship moving without losing context.
The operational problem was not a single missing screen. It was the everyday friction around the pipeline: who needs a reminder, what status a lead is in, whether a booking has been handled, and which manual steps can be turned into dependable product behavior.
This was early in my engineering path, around the time I started 42. The useful part was learning that software is often less about impressive architecture and more about removing repeated operational drag from a real business.
What I did
Four practical CRM improvements.
Lead pipeline automation
Implemented CRM behavior around lead stages so prospects could move through the pipeline with clearer state, fewer manual checks, and less reliance on memory. The goal was simple: make the next action obvious.
Reminder flows
Built reminder logic for follow-ups and operational tasks around the sales/coaching process. For a service business, the value is not just storing the lead — it is making sure the next conversation actually happens.
Booking-system features
Worked on booking-system improvements that connected the CRM workflow to scheduled sessions. The booking layer had to support the business process rather than sit apart from it.
Production feature implementation
Shipped practical product improvements inside an existing CRM context: small features, bug fixes, and workflow details that made the tool more useful day to day.
What transferred
Early CRM lessons that still show up in my automation work.
- The best CRM work is workflow work. Data entry alone does not create leverage; state, reminders, and next actions do.
- Automation should support the operator, not hide the business from them. The system needs to make the next step clear and auditable.
- Booking flows are part of the revenue process. If booking sits outside the pipeline, follow-up gets fragmented.
- This shaped how I later approached AI automation: start with the real operating rhythm, then automate the repeated decisions and handoffs.
Scope
- Full-stack CRM feature work
- Lead pipeline automation
- Reminder and follow-up flows
- Booking-system feature implementation
- Service-business operations
- Live business: https://justcoaching.fr
FAQ
Common questions.
What was Just Coaching CRM?+
It was a CRM project for a coaching business, focused on the operational workflow around leads, reminders, and bookings rather than a public consumer product.
What did you build on the CRM?+
I worked on lead pipeline automation, reminder flows, booking-system features, and general CRM feature implementation that made day-to-day follow-up easier to manage.
When did this work happen?+
This was early in 2017, around the period when I started 42. It belongs at the beginning of my professional engineering timeline.
Why include this case study now?+
It shows the early version of work I still do today: understanding a business process, finding the repeated handoffs, and turning them into reliable software behavior.
Free download · 6 pages · PDF
10 AI workflows worth building first.
Practical workflows for support, sales, ops, content, and on-chain intelligence. Includes the stack choices, rough costs, and failure modes worth checking before shipping.
No spam. Unsubscribe whenever.
Keep reading