ManyMangoesPerformance Audit, Solutions Update & 90-Day Growth Plan
For CEO, Kannan Kaliyur • Period covered: Past 60 days (Jul 1–Aug 29, 2025) vs. prior 60 days (May 1–Jun 30, 2025) • Prepared by: ManyMangoes (Account: Connect Tech + Talent)
Executive Summary
Read this first
In the most recent 60-day window we scaled top-of-funnel activity and raised follow-up intensity, which translated into outcomes:
Average follow-ups per person increased from 1.72 → 2.90 (+68%). That shift—from "first touch" to "consistent cadence"—is what surfaced buying intent.
Reply rates improved slightly; conversion from reply → "open to chat" dipped. That's a solvable message/CTA/playbook problem, not a market problem.
We've provided 4,009 unique mobile numbers (with 4,424 work emails) from April–August. At 7 attempts per number that's ~28k call attempts—months of work at current team capacity.
Email infrastructure, premium content engine, and AI Recruitment Services website—all ready to compound results.
Email Infrastructure Built for Scale and Safety
We purchased and began warming six CTT domains for outbound so we can responsibly add email volume without risking CTT's core domain:
Premium Content Engine Ready for a Year
52 weekly articles drafted and organized for publication: https://connect-tech-talent-articles.manymangoes.com.au/
This lets us activate "content-first" outreach and SEO while feeding LinkedIn, email, and sales enablement—every week for 12 months.
AI Recruitment Services Website—Final Demo Prepared
The new site is staged for stakeholder walkthrough and conversion tuning (copy, CTAs, forms, calendar, proof). This becomes the central "conversion membrane" that turns attention into booked meetings.
What's New Since Last Review
Solutions you can take to the Board
Why:
Google and Yahoo now enforce stricter standards for bulk senders. Staying well below a 0.3% user-reported spam complaint rate and warming new mailboxes methodically are non-negotiables if we want consistent inbox placement. Gmail explicitly states bulk senders are ineligible for mitigation while complaint rate exceeds 0.3% and only become eligible after seven consecutive days below 0.3%—so you cannot "appeal" deliverability if you're above the line. We are building on the right side of that line from day one.
What we did:
Purchased six campaign-only domains (above), stood up DNS, and began warm-up on staged mailboxes with SPF, DKIM, DMARC, PTR and TLS enforced. We're ramping with small, highly engaged cohorts and gradually increasing daily volume—trust first, volume second.
Guardrails we operate by:
Why:
Consistent, relevant publishing builds familiarity, creates reasons to follow up, and earns search visibility. It also gives SDRs/LDRs value-based pretexts for outreach and nurtures.
What we did:
Built out a full year of weekly articles, already hosted for internal review at connect-tech-talent-articles.manymangoes.com.au. Articles ladder to core themes (AI talent markets, engineering capability building, hiring velocity, cost-to-hire, time-to-productivity) and can be atomized into LinkedIn posts, SDR snippets, and newsletter highlights.
Why:
A modern growth engine needs a modern membrane—a site that loads fast, clarifies the offer, and turns interest into meetings.
What we did:
Prepared the final demo of CTT's AI Recruitment Services site with:
This site becomes the canonical link that our LinkedIn and email cadences "lean on" to convert intent.
Performance Readout: Past 60 Days vs Prior 60 Days
Headline results showing dramatic improvement across all metrics
Prior: 644
Prior: 108
Prior: 186
Prior: 0
Interpretation
This is a scale-and-discipline story. We grew the surface area (CRs), converted more of it to conversations (Accepted), then kept showing up (Follow-Ups). Those three levers together produced the result that matters—meetings.
Funnel Quality Diagnostics
Where we win, where we lose
Slight acceptance lift — targeting/positioning improved.
Modest improvement — first-touch copy & timing working better.
Down — replies skewing lower-intent or handling sequence needs refinement.
Context, Methodology & Definitions
Provide a fact-driven audit of ManyMangoes' work for Connect Tech + Talent (CTT), isolate what's working, diagnose friction, and set targets for the next 60–90 days.
Used consistently throughout this report
LinkedIn Program Trajectory
Quarter-over-quarter progress showing consistent improvement
Takeaway
Each quarter is stronger than the last — activity scale up, intensity up, outcomes up. The slope of improvement is steepest in follow-ups (where discipline is self-directed), which is why we're now seeing meetings. The next quarter's step-change will come from improving reply handling and offer clarity.
Lead Supply & Outreach Readiness
Calling + emailing capacity analysis
Delivered Apr–Aug
~1.10 emails per unique
At 7 attempts per number
Given Kritika mentioned that the team capacity is ~50 calls/day across 2–3 callers, the sustainable weekly throughput is in the 100–150 calls range (allowing for parallel responsibilities, admin, and quality notes).
Key Insight:
We've provided more than enough phone numbers for the team to stay fully utilized for months, provided we tier the list and strictly prioritize high-fit targets.
The growing email coverage per record unlocks coordinated "email first, call second" sequences (particularly useful for ISPs that reward prior engagement). It also creates surface area for content-led touches that prime calls with value.
Competition
Focused 500-word analysis; neutral tone
We've reviewed the competition's reported campaign outputs for July and August to calibrate our own plan. Our intent here is not to critique their strategy, but to draw operational implications that help CTT scale responsibly.
At volume, deliverability is earned, not assumed. When complaint rates creep up, mailbox providers tighten visibility. Gmail's current stance is explicit: bulk senders are ineligible for mitigation while user-reported spam complaints exceed 0.3%; eligibility returns only after seven consecutive days below that threshold. In practical terms, if your send program drifts above 0.3%, you cannot appeal your way back to the inbox—you have to operate your way back with better lists, better expectations, and time.
Yahoo's official sender best practices direct bulk senders to remain below 0.3% and monitor complaint rates closely. Whether guidance appears in platform FAQs or community posts, the message is uniform across the ecosystem: go slow, target carefully, design for relevance, and unsubscribe quickly. Speed that ignores fit creates invisible campaigns.
If we ever want "bigger pipes," we need fresh, dedicated infrastructure (subdomains and mailboxes distinct from the brand core), authentication configured (SPF, DKIM, DMARC), and a deliberate warm-up calendar that starts with genuinely engaged, small cohorts. That is why we (ManyMangoes) procured and began warming six CTT domains already. This approach gives us control: if one stream accumulates complaints or soft bounces, we can rest and rehab it without impacting everything else—and without touching the corporate domain.
Seen charitably, they confirm the above: when volume rises faster than reputation, complaint rates and opt-outs rise, too. That doesn't mean email "doesn't work;" it means email must be earned with relevance, segmentation, and tight unsubscribe handling. As we add email to LinkedIn and calling, our goal is to keep complaint rates ≤0.1% (working ceiling) so we stay well under the 0.3% platform threshold and preserve mitigation eligibility should we ever need it.
We deliberately built CTT's engine as LinkedIn → call/SMS → (then) email at scale. That sequencing spreads risk, gathers engagement signals before sending at scale, and ensures that when we do increase sends, they are backed by content and social proof. The competition's experience doesn't scare us off email; it validates the cautious, reputation-first approach we're already taking.
What's Driving Change
Three levers we pulled
The single biggest internal shift was raising Avg Follow-Ups per Person from 1.72 → 2.90. This correlates with 0 → 7 meetings, indicating we're surfacing buyer intent that lighter cadences missed.
CRs and Accepted nearly tripled, multiplying surface area for conversation. Scale alone isn't strategy — but in our case, it unlocked downstream activity that the team actually worked.
With reply → chat conversion down, we're leaving meetings on the table. This is now the most leverage-rich area for improvement.
How the Three New Solutions Amplify Outcomes
What changes:
We detach prospecting email from the corporate domain, earn reputation on dedicated sub-brands, and can route/rotate streams if a sender accrues complaints or soft blocks.
Why it helps now:
As LinkedIn and calling surface warmer pockets, email can follow the warmth—not cold-spray. This keeps complaint rates low and reply quality high.
What changes:
SDRs never run out of reason to write—each week has a fresh insight, chart, or case snippet to share in a DM or email.
Why it helps now:
It shifts conversations from "Can we sell you something?" to "Here's a data point we found that may help with your <hiring velocity / AI talent cost / skill mapping>."
What changes:
Every outbound channel has a clean destination—fast load, clear promise, obvious next step.
Why it helps now:
We finally have a place where the sum of our signals (LinkedIn, email, calls, articles) is converted into booked meetings with fewer hops.
Recommendations
Next 30–60–90 days
Cadence Floor
Keep ≥3 follow-ups/person; standardize a 4-touch baseline (Day 0, 2, 6, 12) and deploy a 5-touch variant (add Day 20) for Tier-A accounts.
Reply Handling
Create two micro-playbooks for replies: (1) Low-intent curiosity (acknowledge, add one crisp proof point, ask a micro-CTA: "want the 3-step outline?"). (2) High-intent operational (provide 2 calendar slots + 1-click booking only after a "yes").
CTA Clarity
Audit and simplify every "ask" — one action per message, framed as a small next step.
List Hygiene
Weekly de-dup sweeps (especially in Developers) before loading call queues; enforce field hygiene for accurate targeting.
Mobile + Email Choreography
For Tier-A, run email-then-call within 24h of an open; for Tier-B, call first then send a recap email.
A/B Test First-Touch
Test value props (e.g., cost-of-inaction %, process shortcut, peer proof) across two send-time bands (morning local, Tue–Thu).
Social Proof Tile
Add a 1-sentence client case to reply #1; test whether logos improve reply → chat lift.
Meeting Motion
On all "maybe" or "interested," trigger a 24-hour nudge (two specific time slots). If still unbooked, send a 48-hour recap (3 bullets + single time suggestion).
Seller Enablement
Short Looms (≤60s) for the top three objections; standardize snippets so every rep replies within 10 minutes during work hours.
Responsible Email Scale
If we expand outbound email, do it with fresh subdomains and dedicated mailboxes, warmed gradually, and target a complaint rate ≤0.1% to keep far below the 0.3% cap.
Tiered Dialing at Capacity
Fix weekly calling quotas by tier (e.g., 150 Tier-A, 75 Tier-B, 25 Tier-C = 250/wk if bandwidth allows; if not, constrain to 100–150/wk based on team confirmation).
Score for Recency
Prioritize recent Jul–Aug records (higher email coverage) while re-scoring the May–Jun reservoir before reuse.
Targets & Modeled Outcomes
Next 60 days projections
+5 incremental meetings without adding CRs
(if we scale email)
Why This is Working for CTT
And how we double down
LinkedIn → call/SMS → email give CTT room to grow without over-exposing the brand domain to deliverability risk.
No longer the issue — we've delivered significantly more qualified leads than the team can reasonably cycle through at full cadence. The lever now is prioritization + playbooks.
As we add capacity and sharpen playbooks, each quarter beats the last on both volume and substantive outcomes (meetings). With mid-funnel optimization, pipeline will scale faster than activity — the mark of a maturing engine.
Operating Model
Governance & instrumentation
One dashboard that tracks CRs → Accepted → Follow-Ups → Replies → Open-to-Chat → Meetings with weekly snapshots and 60-day rolling views.
Enforce clear tags: Reply (any response), Open-to-Chat (explicit willingness to talk), Interested, Meeting (scheduled time on calendar).
Pick the week's Tier-A list; assign sequences; inspect last week's conversion
Micro-retro on reply handling (listen to snippets, refine lines)
Publish a one-pager: what we tried, what moved, what we'll do next
Risks & Mitigations
Reply → chat down
Mitigate via: playbooks, faster follow-ups, smaller asks
If email scaled too fast
Mitigate via: subdomain strategy, gradual warm-up, and strict <0.3% complaint rates (aim ≤0.1%)
More leads than dials
Fix with: tiering and quota discipline, not more sourcing
Duplicates, stale entries
Fix with: weekly de-dup + recency scoring; focus on Jul–Aug coverage where emails/unique are higher
What You Should Expect Next
Clear commitments
Reply handling playbooks live; meeting-nudges templated; Tier-A cadence enforced across the board.
A/B test readout on first-touch value props and send-time bands; click-to-book ratio benchmarked.
Meetings per 60-day window at ~12 with current scale; documented learnings for the next scale step (email subdomain warm plan, if we choose to proceed).
Appendix A — Monthly Context
Sanity check
(through 29th)
Lag note: Meetings often trail engagement; several Aug follow-ups can convert in early September.
Appendix B — Lead Supply Snapshot
Apr–Aug breakdown
Delivered Apr–Aug
≈1.10 per unique
Provided ~28k total call attempts at 7 touches/number. With team capacity ~100–150 calls/week across 2–3 callers (per Kritika's guidance), the database exceeds near-term capacity by a wide margin, which is exactly where we want to be: choiceful, not scarce.
Appendix C — Responsible Email Scale
Only if/when we choose to add it
New subdomains (e.g., connect-updates.ctt.com, ctt-insights.com) and dedicated mailboxes.
SPF, DKIM, DMARC policy (monitor → quarantine → reject once stable).
Start low volume, high-engagement cohorts, ramp in 10–20% increments only after healthy opens and sub-0.1% complaints.
Enforce one-click unsubscribe and prompt processing.
Deliverability (inbox placement), read rates, complaint rates; hard guardrail: stay <0.3% to remain eligible for mitigation.
Closing to the CEO
Kannan, ManyMangoes' strategy for CTT is simple and working:
Scale the right activity (CRs, Accepts)
Persist with discipline (follow-ups)
Tighten the middle (reply handling, micro-CTAs)
Add channels the right way (six warmed domains, weekly articles, conversion-ready site).
We have provided significantly more qualified leads than the calling team can cycle through, we are improving LinkedIn quarter over quarter, and we've added the email and content foundations to turn that momentum into consistent meetings—without risking deliverability. The engine is built and compounding; now we keep the throttle steady, respect the guardrails, and let the slope of improvement do its work.