Category: People

  • From Complexity to Clarity: The Operational Mind Behind Onik

    How Co-Founder Jeremy Francis built a career on fixing what actually matters—and brought that mindset to web performance.

    Most organizations don’t have a performance problem.

    They have a clarity problem.

    Too many tools.
    Too many metrics.
    Too many competing priorities.

    And no clear answer to a simple question:

    What actually needs to be fixed?

    This is where Jeremy Francis operates best.

    Built in Complexity

    Jeremy didn’t start in tech.

    He started in global retail—an environment where operations are constant, pressure is real, and inefficiencies show up fast. It’s where he developed the instinct that would define his career:

    Focus on what matters. Ignore the rest.

    When he moved into tech at Rebel.com, that instinct sharpened. Over more than a decade, Jeremy worked across nearly every operational function—logistics, project management, HR, financial systems, and cost efficiency—ultimately becoming COO.

    But more importantly, he became the person teams relied on when things weren’t working.

    Not to diagnose everything.

    To fix the right things.

    Making Performance Visible

    At Assent, Jeremy led Revenue Operations across Customer Success and Professional Services—two areas where performance is often felt, but not clearly measured.

    He built systems that changed that.

    By developing and visualizing KPIs around customer health, churn, and retention (NRR/GRR), Jeremy helped teams see what was actually happening beneath the surface. Executives got clarity. Teams got direction. Decisions got sharper.

    He also restructured CRM systems and standardized the customer journey—turning fragmented processes into something measurable, repeatable, and improvable.

    Because in Jeremy’s world, if you can’t see it clearly, you can’t fix it properly.

    Operational Discipline at Scale

    Earlier, at Heroic, Jeremy focused on building the operational backbone of the business.

    He developed financial forecasting models and reporting frameworks.
    Improved data hygiene across the organization.
    Built new datasets around customer behavior, product usage, and subscriptions.

    At the same time, he supported HR systems and internal policies—ensuring the team itself could operate at a high level.

    It’s not flashy work.

    But it’s the difference between organizations that react—and those that operate with control.

    Bringing That Mindset to Performance

    At ONIK, Jeremy applies that same discipline to a space that is often anything but disciplined: web performance.

    Most teams are overwhelmed by it.

    They run audits.
    They see scores.
    They get lists of issues.

    And then they stall—because they don’t know what actually matters.

    Jeremy changes that.

    He cuts through the noise.
    Identifies the highest-impact issues.
    And focuses teams on fixing what will actually move the needle.

    Not everything.

    Just the things that matter most.

    The Operator’s Perspective

    Jeremy doesn’t think about performance as a technical checklist.

    He sees it as an operational problem:

    • What’s causing the most friction?
    • What’s having the biggest impact?
    • What can be fixed quickly and effectively?

    Because performance doesn’t improve through awareness.

    It improves through focused action.

    The Bottom Line

    Most teams don’t need more data.

    They need better decisions.

    And better decisions come from clarity—about what matters, what doesn’t, and where to focus.

    That’s what Jeremy brings to ONIK.

    Not more complexity.

    Just a clear path to fixing what’s actually slowing you down.

    Wanna chat with Jeremy? Connect with him on LinkedIn.

  • From Infrastructure to Insight: The Experience Behind Onik

    From Infrastructure to Insight: The Experience Behind Onik

    How Founder Rob Villeneuve’s experience at scale shaped Onik’s view on web performance.

    Rob Villeneuve didn’t start Onik because he wanted to build another tool.
    He built it because he kept seeing the same problem play out across businesses of every size: websites that looked fine, tested well, and still quietly failed the business.

    He had seen this pattern before — at scale.

    As CEO of Rebel.com for a decade, Rob led an organization responsible for millions of domain names and directly hosting thousands of websites. At that level, performance issues stop being edge cases. You see recurring misconfigurations. Infrastructure shortcuts. Silent degradations that compound over time. The same preventable mistakes repeated across agencies, developers, and growing companies.

    You also see the cost.

    Rob is the current Chair, and has served for many years, on the Board of Directors of Canadian Internet Registration Authority (CIRA), steward of Canada’s national .CA domain and world-class DNS infrastructure. That experience reinforced something fundamental: digital reliability isn’t cosmetic. It’s foundational. When infrastructure falters, trust and credibility follow.

    After years operating inside large-scale hosting and DNS environments, one gap became clear: businesses invest heavily in growth, brand, and acquisition — while relying on digital systems they don’t continuously observe. Or they rely on advisors, agencies or developers that lack specific expertise to identify and address performance issues.

    Onik was built to close that gap.

    Rob’s work focuses on giving leadership teams visibility into how their websites actually behave in real-world conditions — not just how they perform in tests. Because performance issues rarely announce themselves. They surface slowly, in softer conversions, rising acquisition costs, and eroding trust that’s hard to diagnose.

    His belief is direct: If no one is actively watching how your website performs in the real world, the business is absorbing risk silently — whether it realizes it or not. 

    Connect with Rob. Everyone who knows him, likes him. It’s a bit annoying really.