Skip to content

Case Study

hapily Uses Claude to Cut Engineering Triage Time by 80%

Case Study Badge-Sep-28-2026-05-02-14-9858-PM
Group 148 copy

80
%

Less engineering triage time

$180
K

Direct annual cash savings

40
%

Fewer internal bug submissions

AI OPERATIONS & ENABLEMENT:

   Scaling a Lean Team's Output With Claude Workflows and Agents

hapily logo 1

The Client

 

hapily builds software for teams in the HubSpot ecosystem, and its small team supports customers, builds product features, and creates marketing assets. The team works across a GitHub codebase, Slack, HubSpot CMS, and Figma design systems that cover brand, product, and mobile standards. With limited room to add headcount, hapily engaged Aptitude 8 to deploy Claude so the team spends less time routing questions to engineers and moving designs through manual web production.

The Problem

  • Product and customer teams relied on engineers to explain features and confirm supported requests
  • Engineering spent time triaging support requests and bug reports instead of building product
  • Turning design standards into prototypes and HubSpot pages was a manual process
  • Risks and opportunities in customer conversations were hard to act on within team workflows
  • Limited_Control

    Limited Control

  • Limited_Control

    Limited Control

  • Limited_Control

    Limited Control

Group 145-1

The Solution

Phase 1: Design Systems & HubSpot Pages

  • Brought hapily's brand, product, and mobile design systems into Claude Design as reusable standards
  • Structured page briefs that supply business context, messaging, and visual direction for every new page
  • Built a custom Claude Code skill that converts approved designs into HubSpot CMS pages for review
  • Enabled product teams to build working feature prototypes that serve as clearer engineering specifications

Phase 2: Lenny the Codebase Agent

  • Connected Lenny to hapily's GitHub codebase, covering production code and pull requests awaiting review
  • Deployed Lenny in Slack so staff can ask how product features work without pulling in engineering
  • Configured Lenny to draft bug fixes and small features as pull requests for engineer review
  • Gave nontechnical teammates a path to investigate requests without routing every question to the CTO

Phase 3: Customer Intelligence

  • Built a workflow that reviews call recordings, email interactions, and CRM context across customer accounts
  • Flags customer concerns and routes potential risks and expansion signals to the right account owners
  • Weighs each account's lifecycle stage, including onboarding, adoption, and renewal, when assessing signals
  • Surfaces signals inside the team's existing workflow so account owners can act without separate reporting

Phase 4: Social Content

  • Deployed an agent that mines relevant internal conversations for ideas and subject matter expertise
  • Drafts potential social posts from those conversations and routes them to marketing for review
  • Gives the marketing team a repeatable source of content ideas grounded in internal team expertise
  • Keeps human review in place, with marketing editing every drafted post before anything is published
Claude skills and Monday.com MCP integration automating OrangeDot proposals, scoping, and CRM

The Outcome

  • Cut engineering time spent triaging routine questions, support, and customer success requests by 80%
  • Reduced internal bug submissions from teammates to engineering by 40% after Lenny was deployed
  • Lowered annual design spend by over $130,000 after adopting the Claude design-system workflow
  • Reduced customer ticket volume from 380 to 272, a 28% decline in support demand
  • Reduced onboarding team cost by approximately 30% across hapily's customer onboarding function

Business Impact

  • Lets a lean team get more work done without adding headcount
  • Gives nontechnical teammates direct access to product knowledge without routing through engineering
  • Keeps engineering focused on building and improving the product rather than triage
  • Surfaces account risks and expansion signals inside the team's existing daily workflow
28%
Ticket Volume
Customer tickets fell from 380 to 272, easing support load on the team.
30%
Onboarding

Onboarding team cost dropped approximately 30% following the Claude workflow rollout.

3
Design Systems

Brand, product, and mobile standards now drive every page and prototype in Claude Design. 

4
AI Workflows

Claude workflows deployed across product, engineering, customer success, and marketing teams. 

The Tools

New Tech Stack

Group 149

What the client is saying...

CONNOR JEFFERS | HAPILY

“We have to get more work done without adding headcount, and Claude is how our team does it.”


 

 

 

 

 

 

BRP_NYCX24-45 1 (1)
hapily logo 1 copy
Connor Jeffers
CEO, hapily

HOW WE SET YOU UP FOR SUCCESS

Next Steps

Aptitude 8 delivered the hapily engagement in four phases, from design and page production to engineering support, customer intelligence, and social content. Human review stays built into every workflow, with engineers approving agent code before release, the team reviewing pages before publishing, and marketing editing each drafted post. Because every workflow runs inside tools the team already uses, hapily can scale its operational output as it grows without adding headcount.





About Aptitude 8

Implement. Integrate. Optimize.

Aptitude 8 is a technical consulting firm that helps companies make their business process, and the tools they use to deliver it, a competitive advantage. In today's business environment, the experience your customers have when buying from you is just as important as what you're selling. We build it better.

HAVE A SIMILAR PROJECT YOU NEED HELP WITH?

Contact Us!