Aelio is the flex-work platform built by Aethon — a staffing company two decades deep into mission-critical sectors: healthcare, childcare, education, government. A 2023 rebrand and a 2024 founder buyback brought in a new, tech-oriented management team with a sharp ambition: become a tech-led marketplace where supply and demand actually meet. But growth had stopped meeting the ambition — stagnant through the private-equity years and the post-Covid market, while the model itself had to shift from temp staffing to freelance.
Aelio ran a Marketing-led Sales motion, and it had reached its natural limit — growth stalled despite the rebrand, the ambition, the new team. Working harder against the same motion wouldn't break through. The diagnosis went deeper than tactics. Aelio had entered the freelance market fast — on a white-label platform built for another sector, stitched to legacy systems and fragmented tooling. The result: a leaking funnel, with the bottleneck on the supply side. Stat callouts: 49 screens to activate / only 6% reached active worker status / retention falling away.
Changing a motion isn't something you announce — it's a system you architect. And in a Product-led Sales motion, the order is non-negotiable: activation and retention first. You fix the product-led funnel before you pour acquisition into it. So we designed the system around the supply-side bottleneck. Strategy at the center: one scalable growth engine connecting acquisition, activation and matching. HubSpot as the operating layer — a single source of truth beneath a proactive matching engine. The commercial team rebuilt around one shared funnel, not silos. We ran it as a pressure-cooker engagement — a transformation like this can't wait, and a moving train has to be rebuilt while it runs.
We activated the system in three builds — each one closing a gap that capped growth. Build 01 — Close the leaky bucket: We redesigned onboarding to cut time-to-value, redefined the retention funnel, and implemented HubSpot as the foundation. When regulation pushed freelance onboarding off the priority list, the system flexed — focus moved to retention and the existing database. Build 02 — Build the matching engine: Supply and demand weren't meeting regionally — one city's shift drew 40 sign-ups, another drew none, and no one could see why. We built dashboards that exposed the mismatch, a HubSpot engine for proactive job-matching, and a commercial team organized around one shared funnel. Build 03 — Scale the matching engine: To scale, the engine had to run inside the whole organization. We integrated HubSpot with every Aethon system for automation at scale, ran contact-flow experiments across email, app and manual, and set up growth meetings that shifted the team from running tactics to compounding them.
With the system live, 2025 became a record year.















