Bluemark · Haptic Logistics SaaS · B2B operations · concept-stage build

We designed a B2B logistics SaaS from idea to dev-ready.

Outcome From an idea + user stories to a development-ready platform. Strategic partner for one of the largest US logistics companies, research-first, 2–3 sessions a week with PM, sent straight to development.
Bluemark / Haptic. B2B logistics SaaS for branded shipping at scale

Imagine the operational backbone of a logistics company, digitized into one B2B SaaS.

Bluemark / Haptic is a B2B logistics SaaS built for one of the largest integrated logistics companies in the USA, branded shipping at scale, from build-a-campaign through configure-a-kit, route through warehouses, approve, and ship. They came to us with an idea and user stories, nothing else built. We embedded as the strategic partner the team didn’t have in-house. The design was sent straight to development.

01Concept-stage build. Idea + user stories, no in-house design partner. The team trusted us to do strategy work upstream of design, not just produce screens.
02Strategic partner, not a vendor. 2–3 working sessions a week with the client’s Product Manager, working sessions, not handoffs over email.
03End-to-end platform. Dashboard, Project flow (formerly Campaigns), Audience, Inventory, Kit Builder, 3-step Approval, Billing, every module designed and sent to dev.
Start Concept An idea + user stories, nothing else built. Strategy work upstream of any screen.
Cadence 2–3 / week Working sessions with the PM. Strategic partner role, not screen vendor over email.
Scope End-to-end Every flow on the platform. Dashboard, Projects, Audience, Inventory, Kit Builder, Approval, Billing.
Outcome Sent to dev Client satisfied. Design went straight to development; Haptic is being built today.
The story

One of the largest US logistics companies handed us an idea and trusted us with the strategy.

Bluemark / Haptic is a B2B logistics SaaS built for one of the largest integrated logistics companies in the USA: branded shipping at scale, build a campaign, pick recipients, configure a kit, route through warehouses, approve, ship. The starting point was an idea and user stories, nothing else built. The client trusted Denovers as the strategic partner they didn't have in-house. We started with strategy, not screens: deep study of goals and user needs, mapped in Miro, before any UI got drawn.

Bluemark's Design Manager and the client's Product Manager ran two to three working sessions every week, working sessions, not handoffs over email. Across that rhythm we shipped the operational spine: Dashboard reflecting every module, plus Campaign, Audience, Inventory, Kit Builder, Approval, and Billing all sharing a single mental model. User testing rewrote the core noun: Campaigns became Projects, onboarding got four clean moves (Create, Invite, Tour, Complete profile), and a three-step approval gated artwork to PDF preview to physical sample before manufacturing. The client was satisfied. Design went straight to development.

ClientBluemark / Haptic · major US logistics co.
RegionUS · integrated logistics
Duration2 to 3 working sessions / week with PM
StatusSent to development · in build
Chapter 01

Strategy from concept. Research came before screens.

The team came with an idea and user stories, nothing built. The work began with a strategy phase: deeply studying the goals and user needs of every stakeholder, building a shared map in Miro, meeting with the PM two to three times a week. The first weeks looked nothing like “design”, they looked like research notes, user stories, and system maps. That’s what made the design phase fast.

strategy.haptic.io/research/user-flows
Haptic research artifact 1, user flow mapping during the strategy phase, mapping every user story to a screen and a state
Research · 01 User flows · mapping each user story to a screen and a state Strategy phase
strategy.haptic.io/research/wireframes
Haptic research artifact 2, early wireframes from the Miro brainstorming phase, before high-fidelity design began
Research · 02 Early wireframes · pre-fidelity, post-research Miro brainstorms
strategy.haptic.io/research/system-map
Haptic research artifact 3, system map showing how Dashboard, Campaign, Audience, Inventory, Cart, Approval and Billing fit together as one platform
Research · 03 System map · modules + dependencies + the all-in-one thesis Strategy → design
Chapter 02

The platform takes shape. Dashboard, Campaign, Audience, Inventory.

With the strategy locked, four core modules emerged as the operational spine. Dashboard for at-a-glance status, Campaign for planning a branded shipping push, Audience for managing recipients, Inventory for product catalog and warehouse stock. The Dashboard reflects every other module, so a logistics manager sees activity, alerts, segments, and approval status without clicking into each one.

app.haptic.io/dashboard
Haptic Dashboard, operational view of campaigns, inventory health, and shipping activity
Dashboard Operational view · reflects every module · status without clicking in The single surface
app.haptic.io/campaigns
Haptic Campaign, original design for planning a branded shipping campaign, before user testing simplified the flow
Campaign Original campaign builder · planning a branded shipping push Pre-iteration
app.haptic.io/audience
Haptic Audience, recipient management with segmented lists, addresses, and sender attribution
Audience Recipient management · segments · addresses · sender attribution Who’s receiving what
app.haptic.io/inventory
Haptic Inventory, product catalog and warehouse stock, primary view
app.haptic.io/inventory/detail
Haptic Inventory, detail view showing product information, stock levels, and warehouse routing
Inventory Catalog + warehouse + product detail · the same surface, two depths Feeds the kit builder
Chapter 03

User testing rewrote the flow. Campaigns became Projects.

Users told us the original Campaign flow was harder than it needed to be for first-time users. We brought the team back to the whiteboard. Campaigns became Projects. Onboarding got four clean moves. Create project, Invite team, Take tour, Complete profile, and three project goals (Onboarding, Retention, Marketing) replaced the loose campaign types. Renaming a core noun mid-build is expensive, but the test sessions paid for it the first day after the change.

strategy.haptic.io/flows/projects-v2
Haptic new flow, the Projects workflow mind map showing the redesigned end-to-end path: create project, invite team, take tour, complete profile, then choose a project goal
The new flow Projects mind map · create → invite → tour → profile → goal Post user-testing
app.haptic.io/projects/new
Haptic Create Project, the simplified project creation step, the first move of the new four-step onboarding
Create project Step 01 of four · the new onboarding the test sessions earned Simplified
Chapter 04

From kit to ship. Configure, bill, approve, manufacture.

The Kit Builder is where digital becomes physical, products, quantity, color, packaging, shipping, warehouse, and transit configured in one continuous flow. Billing is seamless and transparent with line items per project. Approval is a deliberate three-gate sequence: artwork upload → PDF preview → physical sample. A kit is a physical object shipping to real customers; the three gates catch errors at the cheapest possible moment, before manufacturing.

app.haptic.io/cart/build-kit
Haptic Kit Builder, assemble a branded shipping kit by configuring products, quantity, color, packaging, shipping, warehouse, and transit options
Kit Builder Products · qty · color · packaging · warehouse · transit One continuous flow
app.haptic.io/billing
Haptic Billing, seamless and transparent invoicing for the kit, with line items broken out per project
Billing Seamless + transparent · no surprise totals · line items per project Trust as a feature
app.haptic.io/approval
Haptic Approval, three-step approval flow: artwork upload, PDF preview, physical sample, each gating manufacturing to catch errors before kits ship
Approval Artwork upload → PDF preview → physical sample Errors caught early
Outcome · client satisfied · sent to development

From an idea to shipped to dev.

The client received the entire product, every flow, every module, every detail, end-to-end. The client was satisfied; the design went straight to development. Today, Haptic is being built. Our role was the strategic partner the team didn’t have in-house, from idea through research and user testing to handoff.

Book a free sprint
Pilot week · on us

Concept-stage founder with a complex domain to digitize? Start with the same free week we ran for Haptic.

Five working days, a senior product designer + strategist sitting next to your PM. If it doesn’t click, keep every file we ship.

  • Capped at 4 sprints / month
  • No card · NDA on request
Next case study → Case 07 · Finwize · 2023

From idea to investor-ready MVP, accelerator-accepted.

A fintech SaaS that turns Excel chaos into a visual planning tool. Repeat client (Lity); MVP shipped in weeks, accelerator-incubated.

Accelerator Incubated · in beta
Weeks MVP to demo
Fintech · SaaS · MVP Read →