Absentbox

Absence emails turned into structured updates, reducing manual follow-up for teams

They built something that fits right into Outlook and actually saves our team time every single day on absence tracking.

Shipped
Workplace Productivity
Outlook Add-in
Outlook Automation

Organized desk with a laptop and office equipment

Results delivered

Shipped A cohesive product outcome delivered through one customer roadmap.

2 milestones Consolidated delivery stages defined as part of the same project.

End-to-end Connected scope from Technical Setup & Outlook Add-in Foundation through Absence Tracking & Email Fetching Engine.

Executive summary

Absentbox

What Mario Klaric set out to build, how the engagement was scoped, and the shape of the product that came out of it.

Mario Klaric partnered with Deployed to deliver Absentbox as one consolidated product engagement.

Absentbox brings absence tracking directly into Outlook, using incoming email as the starting point for structured status information. The add-in foundation and email-processing engine were developed as one workflow so routine absence messages can be captured and handled with less manual coordination.

Client: Mario Klaric
Product: Absentbox
Industry: Workplace Productivity
Project type: Outlook Add-in
Service line: Outlook Automation
Delivery stages: 2
Status: Shipped

How we approached it

Challenge & approach

Every engagement starts from a constraint. This is the problem Mario Klaric brought to us, and the route the team took through it.

The challenge

Absence information often arrives through unstructured messages, leaving teams to interpret emails and update records manually. The product needed to work naturally inside Outlook, retrieve the relevant messages reliably, and convert email content into consistent absence events without adding another disconnected tool to the user’s day.

Our approach

Deployed first established the technical setup for the Outlook add-in and the integration points required to operate within the email environment. The absence-tracking and email-fetching engine was then built on that foundation, connecting message retrieval to the product’s structured status workflow.

Delivery scope

The engagement, stage by stage

All 2 stages below belong to the same consolidated customer project. Each one builds on the stage before it rather than running as a separate piece of work.

Technical Setup & Outlook Add-in FoundationOpens the engagement and leads into Absence Tracking & Email Fetching Engine.
Absence Tracking & Email Fetching EngineBuilds on Technical Setup & Outlook Add-in Foundation to complete the engagement.

Working model

How the engagement was run

The same delivery model sits behind every customer story on this site.

One consolidated project Every stage stayed inside a single engagement instead of being split into separate workstreams, so scope, identities, and product rules were decided once.
Sequenced, not parallel Each of the 2 stages built on the output of the one before it, which kept later decisions anchored to work that was already proven.
Shipped as one product Mario Klaric received a release that resolves into a coherent outlook add-in rather than a set of disconnected features.

Outcome

What Mario Klaric has now

Absence emails turned into structured updates, reducing manual follow-up for teams.

Mario Klaric now has an Outlook-based automation foundation that moves absence processing closer to the communication channel teams already use. The shipped workflow reduces the need for repeated manual interpretation and creates a clearer base for rules, notifications, reporting, and additional absence-management capabilities.

Other products we have shipped

Different industries, the same delivery model.

Have a product outcome you want to ship?

Tell us where you are today and we will map the shortest route to a working product.

Start a conversation