Selected product work

Blancfold Systems

Shipfire Product · Laundry operations SaaS

View project

From scattered laundry records to a product system built around the next order.

The starting point

Orders, customer details and payments were the core problem to organise. The product needed to make a busy laundry’s next action clear while staying practical for a small operation.

What needed attention

  1. Designed around the order lifecycle rather than a generic dashboard
  2. Connected customer history, garment status and payments
  3. Created role-aware workflows for owners and staff
  4. Prioritised order status and next actions over dashboard metrics

What changed

A defined v1 system connecting intake, garment status, payments and oversight, with a clear path to operator testing.

  • Operations
  • Workflow
  • Product system

ResonaOS

Shipfire Product · AI career workspace

View project

From separate career tools to one workspace with a clear purpose for each step.

The starting point

Résumés, opportunities and mentorship could feel like unrelated features. The product needed a coherent workflow and a clear distinction between AI suggestions and human guidance.

What needed attention

  1. Framed the product as a workspace instead of a collection of tools
  2. Connected AI assistance to concrete career tasks
  3. Balanced automation with verified roles and human mentorship
  4. Made AI suggestions visible for users to review and decide

What changed

A product concept and interface system that connects career tasks and makes the role of each capability easier to understand.

  • AI workflow
  • Strategy
  • Interface system

okDuo

Shipfire Product · Service booking platform

View project

From a broad platform idea to a focused path for making and managing a booking.

The starting point

The vision could expand into payments, teams and reporting before the core booking worked. The first milestone needed a tighter scope and a clear flow for both customer and provider.

What needed attention

  1. Separated public booking from provider operations
  2. Defined a lean service and availability model
  3. Excluded payments and team management from the first release
  4. Let customers book before creating an account

What changed

An MVP architecture linking provider setup, public booking and a management dashboard, with wider platform features set aside.

  • Booking
  • MVP scope
  • UX architecture

Pitchforge

Shipfire Product · Sales presentation platform

View project

From disconnected sales material to a product workflow for a clearer pitch.

The starting point

Teams can spend time polishing slides before agreeing on the argument. Pitchforge needed to make the audience, message and evidence clear before presentation work began.

What needed attention

  1. Structured the workflow around the sales narrative
  2. Separated message development from slide production
  3. Kept evidence and supporting material connected to each claim
  4. Made review and revision part of the core workflow

What changed

A focused product workflow for shaping the story, reviewing its evidence and planning a coherent presentation.

  • Narrative
  • Sales workflow
  • Presentation

Taldeck

Shipfire Product · Talent operations platform

View project

From fragmented candidate feedback to a shared workflow for hiring decisions.

The starting point

Candidate information and reviewer feedback are often scattered. The product needed to bring them together while keeping the first release focused on review and decisions.

What needed attention

  1. Organised the product around active roles and candidates
  2. Connected feedback to observable hiring evidence
  3. Created a shared view of evaluation progress
  4. Kept the first workflow focused on review and decision-making

What changed

A talent operations concept with shared criteria, candidate evidence and a record of how a hiring decision was reached.

  • Hiring
  • Evaluation
  • Team workflow

Spacebar

Shipfire Product · Team collaboration platform

View project

From scattered project conversations to decisions and actions people can find again.

The starting point

A useful decision can disappear into chat as soon as the conversation moves on. Spacebar needed to keep context available while making ownership and next actions clear.

What needed attention

  1. Made the project the primary organising space
  2. Separated durable decisions from ongoing conversation
  3. Connected tasks to the context that created them
  4. Kept navigation focused on active work

What changed

A collaboration concept with distinct places for project discussion, recorded decisions and the actions they create.

  • Collaboration
  • Project context
  • Workflow

The work has to hold up beyond the screenshot.

  • Choose the right features

  • Make the core workflow clear

  • Build working software

  • Finish the details properly

Bring the rough version.We’ll finish it properly.

Start a project