Case study · Fractional product leadership

Repositioning a SaaS business for enterprise growth

I helped Vitay move beyond incremental feature delivery by connecting product strategy, enterprise readiness, integrations, pricing and commercial operations.

  • $850k → $1.1M

    ARR in six months

  • +6%

    Customers month on month from one integration

  • 13th → 9th

    G2 category ranking

  • Product leadership
  • Enterprise SaaS
  • Pricing
  • Integrations
  • Compliance
Company
Vitay
Product
Reference-checking software for employers, candidates and referees
Market
HRTech and applicant-tracking software
My role
Product Lead and General Manager, responsible for product strategy, delivery, revenue, growth and a team of six
Scope
Enterprise strategy, pricing, integrations, security, fraud, billing, commercial operations and market expansion
The challenge

Growth depended on more than adding features

Every completed reference relied on three parties acting in sequence. Hiring teams started the request, candidates nominated referees, and referees — the least invested party of the three — had to finish it. A delay anywhere held up the hire, and most product and commercial problems showed up at the joins.

  1. 01

    Hiring teams

    Requesting references inside an existing recruitment process, under time pressure and compliance expectations.

  2. 02

    Candidates

    Nominating referees quickly and accurately, often while managing several live applications at once.

  3. 03

    Referees

    Completing a request they did not ask for, with no product familiarity and little incentive to persist.

Connected business and product challenges
  • Unclear segment focus across SMB, enterprise and government buyers.
  • Enterprise security expectations the product could not yet evidence.
  • ATS integration needs that shaped whether the product was usable at all.
  • Pricing and billing friction slowing deals and expansion.
  • Trust and fraud risks in reference outputs.
  • Fragmented revenue systems across sales, billing and product.
  • International expansion complexity across data and compliance rules.
My diagnosis

Enterprise growth was a product-system problem

Larger customers were not asking for more features. They were asking whether the product, the commercial model and the operating model behind it could carry their hiring process.

  1. 01

    Market focus

    The roadmap tried to serve every buyer at once. Enterprise and government customers had the clearest need and the highest willingness to pay, but nothing was sequenced around them.

  2. 02

    Product readiness

    Larger customers evaluated security, data handling and audit before they evaluated features. Without that evidence, good product conversations stalled at procurement.

  3. 03

    Commercial model

    Pricing and billing were built for small self-serve accounts, so every larger agreement needed manual handling and every expansion needed a negotiation.

  4. 04

    Go-to-market credibility

    Buyers judged the product by where it sat in their existing hiring stack and by public category signals — neither of which the product was actively shaping.

What I did

Connected product leadership with commercial ownership

01

Refocused strategy around enterprise and government customers

I narrowed the roadmap onto the segments where reference checking is mandatory rather than optional, and rebuilt prioritisation around what those buyers had to see before they could sign.

  • Segment definition tied to buying process, not company size
  • Roadmap sequenced against enterprise evaluation criteria
  • Clear deprioritisation of low-value SMB requests
02

Reworked pricing and billing

Pricing was re-based on hiring volume and capability so larger customers could grow inside the model. Billing was rebuilt to handle contracts, invoicing and expansion without manual intervention.

  • Volume and capability-aligned tiers
  • Contract, invoicing and renewal handling in Chargebee
  • Expansion paths that did not require renegotiation
03

Built a product-led integration strategy

Reference checking only works where hiring already happens. I treated applicant-tracking integrations as a distribution channel, starting with Greenhouse and designing the integration to be discoverable and self-serve.

  • Greenhouse integration launched as an acquisition channel
  • Integration surface designed for self-serve setup
  • Marketplace presence and partner-led referral flow
04

Led ISO27001 delivery end to end

I owned certification as a commercial unblocker rather than a compliance exercise — scoping controls, running the programme across engineering and operations, and turning the outcome into evidence sales could use.

  • Scope, controls and audit programme owned end to end
  • Security posture built into product and engineering practice
  • Reusable security documentation for procurement
05

Improved trust in product outputs

A reference is only valuable if it is credible. I introduced verification and fraud controls so employers could rely on what the product returned, and so risk was visible rather than assumed.

  • Referee verification and identity signals
  • Fraud detection on suspicious reference patterns
  • Clear audit trail on every completed reference
06

Connected the revenue and customer systems

Product usage, CRM, billing and outbound were joined so the business worked from one view of a customer, and so reporting reflected reality instead of three partial versions of it.

  • HubSpot, Chargebee and Apollo connected end to end
  • Shared account, usage and revenue view
  • SaaS metric reporting on a single source of truth
07

Strengthened product discovery and market visibility

I put customer research back at the front of prioritisation and used the same insight to sharpen how the product was presented publicly, improving category position alongside the product itself.

  • Regular discovery with hiring teams and enterprise buyers
  • Positioning and review strategy that lifted G2 ranking
  • Competitive and category tracking feeding the roadmap
How the work connected

One system, four compounding effects

  • Clearer segment focus

    Deciding who the product was for made every later pricing, security and integration decision straightforward.

  • Stronger buyer confidence

    Certification, verification and audit evidence removed the objections that had been stalling larger deals.

  • Better workflow fit

    Integrating into the applicant-tracking systems customers already used turned adoption into a default rather than a project.

  • More scalable revenue operations

    Connected billing, CRM and reporting meant growth no longer added manual commercial overhead.

Results

A product larger customers could buy, and a business that could carry them

  • $850k → $1.1M

    ARR in six months

  • +6%

    Customer growth month on month from Greenhouse

  • 13th → 9th

    G2 category ranking

  • ISO27001

    Delivered end to end

  • 3 systems

    HubSpot, Chargebee and Apollo connected

These outcomes came from aligning product strategy, enterprise requirements and commercial operations rather than treating them as separate initiatives.

Broader leadership impact

Responsibility beyond the roadmap

  • Product strategy and delivery.
  • Revenue and growth ownership.
  • Six-person team leadership.
  • SaaS metrics.
  • Investor and shareholder reporting.
  • Long-range planning.
  • International expansion assessment.
  • Cross-functional product, finance, sales and operations leadership.
Relevant capabilities
  • Fractional product leadership
  • Enterprise SaaS strategy
  • Pricing and monetisation
  • B2B billing
  • Integrations
  • ISO27001
  • Trust and fraud controls
  • Product-led growth
  • Market expansion
  • Board reporting
  • General management

Need to make a SaaS product ready for larger customers?

I help businesses connect product direction, pricing, integrations and enterprise readiness so growth is supported by the product and the operating model behind it.