Hashlogics
Case study · HR Technology · Europe

Haployee

Birthdays and work anniversaries that never slip past HR.

A platform that reminds HR ahead of every employee milestone, then sends a printed card or gift to the person's home.

Client
Haployee
Industry
HR technology / employee experience
Region
Europe
Engagement
Multi-tenant SaaS web platform · Tech lead · Google integrations · Ongoing maintenance
Overview

Haployee is a multi-tenant platform for HR and office teams across Europe. It reminds you before every birthday and work anniversary, then sends a printed card or gift to the person's home. Hashlogics served as tech lead on it, owning the Google integrations and the ongoing maintenance of the live product. The need was a small one: a milestone nobody noticed until it had passed, because the dates lived in spreadsheets and in people's heads. With Haployee you get the reminder early enough to act, and a real card lands on the doormat.

The challenge

The problem Haployee set out to solve.

01

Milestones were tracked informally, so some moments were missed outright.

02

Reminders arrived too late to order and post anything in time.

03

Sending a physical card or gift was a manual errand for each person.

04

Home addresses are the one data point HR usually doesn't hold.

05

Company anniversary dates sat in an outside public register, not in HR's own records.

06

Nothing connected an upcoming moment to something physical in the post.

What success needed to look like

  • Every upcoming moment surfaces in time to act.
  • You can review and approve a send, or trust it to go out on its own.
  • Nine moment types are handled, and birthdays are only one of them.
  • A whole team comes in through one import.
  • Employees supply their own home addresses, so HR never has to ask.
Our approach

How we delivered our part.

  1. 01

    Take the tech lead seat

    Hashlogics worked on Haployee as tech lead and delivered the work in iterative sprints.

  2. 02

    Own the Google integration surface

    The Google integrations were ours, and each one runs over authenticated API access.

  3. 03

    Fit the work to a multi-tenant product

    The Google integrations sit inside a multi-tenant product, where each organization sees only its own people and moments.

  4. 04

    Stay on after deployment

    Maintenance was part of the role: the work carried on after deployment.

The solution

Our part, and the product around it.

Hashlogics owned two parts of Haployee as tech lead: the Google integrations and the ongoing maintenance. On the integration side, that means the places where the platform reaches Google services, each one behind authenticated API access. On the maintenance side, it means the work on the product continued after it was deployed, and it runs today at app.haployee.com.

Around that work sits the product your HR team would use. You import the team once, and employees add their own home addresses. A scheduler looks ahead and sends you a reminder by email or calendar before the date. You review each send or let it go out automatically, and Haployee hands it to print-and-post for a card or to gift delivery.

One birthday, from import to doormatLive
  1. ImportHR loads the team once; employees add their own addresses
  2. Scheduler scanLooks ahead and finds the upcoming birthday
  3. ReminderAn email or calendar entry arrives before the date
  4. Review or auto-sendAn admin approves it, or the setting lets it go
  5. FulfillmentThe card is printed and posted, or the gift is delivered

Every send ends in the send history, and the choice between review and auto-send is recorded each time.

The product

What Haployee does.

Nine moment types are covered, including birthdays, work anniversaries, a new baby, a permanent contract and a house move.
Client-relationship anniversaries take recognition beyond the payroll.
A look-ahead scheduler sends reminders by email or calendar, early enough to act on.
You can review every send first, or set it to go out automatically.
Print-and-post fulfillment sends a real printed card.
Gifts are delivered to the employee's home address.
Company anniversary dates are pulled from public registry data.
Bulk import brings your whole team on in one pass.
Employees enter their own home addresses, so HR never has to collect them.
Administrators and employees hold different rights, and an employee reaches only their own record.
Each organization's data is kept apart, so no client can read another's people.
Haployee calendar for October 2026 with birthdays, work anniversaries and relation moments marked on dates
The calendar shows a month of birthdays, work anniversaries and client-relationship moments, here with the product's sample team.
Haployee card settings listing a default card per moment type with an automatic sending toggle
Card settings hold a default design for each moment type, with automatic sending switched on or off per type.
How it's built

Platform

  • Multi-tenant SaaS
  • Bulk import
  • Scheduled jobs
  • Review and approval workflow

Integrations

  • Google APIs
  • Email delivery
  • Calendar reminders
  • Public company registry data
  • Print-and-mail fulfillment
  • Gift delivery

Our role

  • Tech lead
  • Google integrations
  • Ongoing maintenance
More from the product
Haployee import employees screen with a file upload area and match fields and validation steps
Bulk import takes a .csv or .xlsx file, then moves through field matching and validation.
Haployee onboarding page with tabs for Excel or CSV, Google Sheets, Fill in yourself and NMBRS
The onboarding page lets a team arrive from Excel or CSV, from Google Sheets, by manual entry, or through an HR system.
The takeaway

What makes Haployee hard is time. A reminder that lands on the birthday is already too late, because a printed card still has to travel through the post. So every outside service the product leans on has to answer on the day the scheduler needs it. That is the case for one team owning both the Google integrations and the maintenance. If a Google connection breaks, the fix goes to the team responsible for it.

By , CEO, HashlogicsUpdated
Start

Let’s deploy working AI into your business.

We build AI agents and automation, ship them into the tools you already run, then stay on under an agreed service level. A senior engineer reads every brief, and your call gets scheduled within 24 hours.

What happens next

  1. 01

    You send a brief or book a call

    Two minutes, whichever you prefer.

  2. 02

    A senior engineer replies within 24 hours

    Not a sales rep.

  3. 03

    Honest scoping, in writing

    And if we’re not the right fit, we say so.

Abdul Basit, CEO of Hashlogics

“I started Hashlogics because too many teams ship a demo, get paid, and disappear. We build to a standard we’d run ourselves — and we stay to keep it running.”

Abdul Basit · CEO · a direct line

Not ready to talk? Take the checklist.

12 questions to ask any AI agency before you sign. They separate a demo shop from a team that ships to production.

Get the checklist

Free · no newsletter