Recruiters were drowning in tool chaos
When I joined Workllama, recruiters were operating across a fragmented stack — email clients, SMS apps, LinkedIn InMail, WhatsApp, and VoIP tools — to reach the same candidate. There was no unified thread, no context, and no visibility. Every outreach was a cold start.
A recruiter reaching out to a candidate for the third time had no way of knowing what was said in the first two. Conversations were scattered across 4–6 tools. Response rates were low. Candidate experience was disjointed. And recruiters were spending 30–40% of their time just managing communication logistics rather than building relationships.
This wasn't a recruiter problem — it was a platform gap. Workllama had strong ATS capabilities but zero owned communication layer. The moment a recruiter wanted to reach a candidate, they left the platform entirely.
Understanding the real job to be done
Before writing a single spec, I spent three weeks in discovery — sitting with recruiters, running structured interviews, and auditing real workflows. I also worked closely with Customer Success to understand churn signals tied to communication frustration.
"We leave the platform the moment we need to talk to someone. That's where deals die."
— Enterprise recruiter, discovery interviewA unified communication layer built for recruiter speed
The Communication Hub was designed around one north star: a recruiter should be able to reach any candidate, on any channel, with full context — without ever leaving Workllama. Mobile-first by design, because 60% of recruiter outreach happened outside office hours.
Unified inbox
SMS, email, and in-app messages consolidated into a single threaded view per candidate. No more context switching or lost history.
Mobile-first design
Full communication capability on iOS and Android. Recruiters could respond to candidates during commutes, interviews, and client visits.
Personalised templates
AI-assisted message templates that pulled candidate name, role, and stage automatically — reducing manual composition time by 60%.
Engagement analytics
Open rates, response rates, and channel performance per recruiter. Gave team leads visibility into outreach effectiveness for the first time.
Chrome plugin
Browser extension enabling recruiters to initiate outreach directly from LinkedIn or job boards — capturing leads into the Hub without copy-pasting.
Integration layer
Connected to Twilio (SMS/voice), SendGrid (email), and native in-app — single API abstraction so the platform, not the recruiter, handles channel routing.
Shipping a 0→1 product across three stakeholder groups
The three hardest alignment challenges were engineering (build scope and technical debt tradeoffs), Customer Success (managing beta expectations with enterprise clients), and clients themselves (change management for a workflow shift).
Measurable impact across engagement, retention & revenue
Six months post-GA, Communication Hub was the most-used daily active feature on the platform — ahead of job posting and candidate search. It became a key differentiator in sales conversations and directly contributed to reduced churn.
Communication Hub was subsequently cited in Workllama's TIARA Talent Award nomination for Contractor Solution of the Year and featured as a key differentiator in the Ardent Partners Key Provider 2022 recognition.
On measurement: Engagement rate and adoption figures were tracked via Workllama's internal analytics platform across a 6-month post-GA window. The 70% activation figure reflects users who completed at least one outreach action via the Hub. "User satisfaction +50%" reflects an internal CSAT survey run across 3 enterprise accounts, not a platform-wide NPS — the sample size was meaningful but not exhaustive. Beta insights count (60+) includes both structured feedback sessions and async Notion comments from design partners.
Building the team infrastructure to scale beyond the product
Communication Hub wasn't just a product delivery — it became the vehicle through which I built Workllama's PM team capability. As the team grew to 3–5 PMs, I recognised that without shared processes, we'd lose consistency and speed.
What I built for the team
PM Onboarding Playbook — contents
- Product architecture & platform overview
- Customer segment map & ICP definitions
- Stakeholder directory & relationship guide
- Prioritisation principles (RICE + strategic fit)
- PRD template with worked example
- First 30 days checklist with milestones
- Common anti-patterns to avoid
Discovery-to-Delivery framework — stages
- Problem framing & hypothesis definition
- User discovery (interviews + shadowing)
- Opportunity sizing & business case
- PRD + design brief creation
- Engineering & stakeholder alignment
- Beta program design & feedback loops
- GA launch + post-launch measurement
Lessons that shaped how I lead product teams
Scope discipline is a leadership act. Cutting 40% of V1 features wasn't a failure of ambition — it was the decision that let us ship in 10 weeks and learn from real users. Junior PMs often confuse completeness with quality. The playbook I built explicitly teaches ruthless scoping.
Customer Success is a product team, not a support team. CS brought me the churn signals that made the business case undeniable. Building that partnership early — and formalising it into our beta process — became a repeatable pattern I codified in the discovery framework.
Adoption is a product problem, not a training problem. The 70% adoption rate didn't come from training decks — it came from in-app tooltips, a Chrome plugin that met recruiters where they already worked, and CS-led onboarding sessions. Distribution is part of the product.
The best way to grow junior PMs is to give them real ownership, not observation. Assigning the analytics and Chrome plugin modules to junior PMs — with coaching, not hand-holding — accelerated their growth faster than any training programme would have.
Want to discuss this in depth?
I'm happy to walk through the product decisions, the leadership approach, or the metrics in more detail.