Build story · In-house product

TaskShaper: one operating record for HR, payroll and projects.

Operations teams were stitching people, pay and projects together across spreadsheets and chat. We built the system we wanted to run instead.

Scope

Product strategy, UX, engineering

Surface

Web application

Status

Built and supported in-house

app.algorithmbd.com/taskshaper
TaskShaper dashboard showing open tasks, approvals, team attendance and active projects.

A working view of the operations dashboard.

The problem

The work was connected. The tools weren't.

A new hire starts in the people file. Their leave request lives in chat. Payroll is rebuilt in a spreadsheet. Project hours sit in another tab. Every handoff is a chance to lose context — or re-enter the same data.

People

Records live in spreadsheets.

Approvals

Requests get lost in chat.

Payroll

The same data is retyped.

Projects

Status lives in someone's head.

“A single change — a new hire, a leave request, a raise — touched four places.”

The pattern we kept seeing.

The approach

Design the record, then the screens.

The interface is the easy part to see. The hard part is deciding what the system treats as one fact, and what it lets drift.

01

Map the operating record.

Follow a person from hire to leave, and a project from quote to invoice. Find every handoff.

02

Design around the handoff.

Roles, permissions and audit trails are part of the workflow — not a settings page.

03

Build the core modules.

People, leave, attendance, payroll, projects and invoicing read from the same record.

04

Ship with the team.

Import data, configure approvals and keep iterating with the people who use it every day.

What we built

One login. Every operating record.

Six connected areas, designed to share the same people and project data instead of passing exports around.

Explore the product

People & roles

A single people record with documents, reporting lines and role-based access.

Feeds leave, payroll and projects

Leave & attendance

Requests, approvals and attendance in one calendar, tied to the person record.

Feeds payroll and capacity

Payroll & approvals

Pay runs built from people data, with approvals and a history you can audit.

Reads from people and leave

Projects & timesheets

Boards, ownership, time and progress in the same place as the team.

Connected to people and invoices

Invoicing & accounts

Invoices and statuses linked to the project and the people doing the work.

Connected to projects

Reports & audit

The week in one view, with a record of who changed what and when.

Built on the audit log

What changed

Fewer handoffs. A clearer week.

The point was never to add more screens. It was to remove the places where the same fact has to be entered again.

One source

People, pay and projects read from the same record.

A trail

Every request has an owner, a status and a history.

Less retyping

Changes flow into the pay run instead of being copied across.

Visible work

Progress, time and ownership sit next to the project.

A note on numbers: this is an in-house build, so there are no client metrics to quote. The test we care about is simpler: can an operations team run the week without leaving the system?

Under the hood

Built for the unglamorous parts.

The features people see are supported by permissions, history and deployment choices that keep the system usable as the team grows.

Product

PeopleLeaveAttendancePayrollApprovalsProjectsTimesheetsInvoicingReports

Engineering

Role-based accessAudit logCloud-readySelf-hosted option

Support

In-house supportData importWorkflow configurationOngoing iteration

Next build story

eCommerce — a storefront engine with many personalities.

Read the eCommerce story

See it with your workflow

Bring your messiest operations problem. We'll map it live.

A 30-minute walkthrough with a real workflow from your team — not a generic slide deck.