KRAFTHUB / FLOW REVIEW / 07 NOVEMBER 2026

Customer request
journey 2.

A lean path from a customer’s idea to a designer’s pattern and a knitter’s finished garment. The original preview is preserved.

Create a request as the customer, then switch workspace to continue the same project. All actions are local preview scenarios; payments and messages are simulated.

The complete journey.

01 / Customer

  1. Choose a pattern or describe an idea.
  2. Set size, fit, budget, timing and delivery area.
  3. If design work is needed: approve the designer’s proposal, pay the separate design fee, review the result.
  4. Publish a free making request.
  5. Review the crafter’s quote; accept or reopen.
  6. Review the complete price, enter delivery details and pay.
  7. Follow making and delivery; inspect, accept and release payment, or report a problem.

02 / Crafter

  1. Check the brief, design permissions and delivery area.
  2. Reserve the request and prepare a making quote.
  3. Wait for customer approval.
  4. Confirm size, timing and exact materials with a retailer quote.
  5. Receive assignment after successful full payment.
  6. Confirm yarn, pattern access and measurements; make and share updates.
  7. Dispatch with tracking; await customer acceptance and payout confirmation.

03 / Designer

  1. Review a new brief or a requested adaptation; accept or decline.
  2. Propose scope, fee, time and permitted use.
  3. Start after approval and separate design payment.
  4. Deliver the pattern/specification and yarn plan.
  5. Complete the included revision if requested.
  6. Customer approval unlocks the making request.
  7. Keep designer credit and the approved specification with the commission.

What needed to change.

Original frictionImplemented in version 2
Generic entry, fixed patternTwo honest starting points: choose the recorded pattern or describe an idea. The catalogue states its preview limit.
Pattern price could look like the garment price“Pattern licence only” is explicit. Design, making, customer fee, yarn and both deliveries are itemised before payment. Paid design is never charged twice.
“Choose a crafter” obscured the reservation modelOne eligible crafter at a time prepares a quote. The customer can accept, decline or reopen. A reservation does not assign the job.
Too much detail too earlyThree short request steps. Town and postcode first; street address and email at checkout. Technical details and conversation open on demand.
Customer and crafter fixtures were disconnectedThe same saved project moves through all three workspaces. The approved brief, quote, materials, conversation and status remain attached.
Designer contribution was missingExisting paid patterns come first. Adaptations require designer approval; original work has a paid proposal and approval step. No AI-generated pattern is offered.
Making flow ended too earlyPreparation, progress updates, dispatch, receipt, explicit customer acceptance and confirmed payout are included. Reporting a problem pauses the project.

Keep the craft visible.

ES Allianz, the manual’s shared controls and cards, thin rules, generous spacing, pill actions, the black/white customer identity and lime crafter accent are retained. The supplied knit photography stays. No new decorative design system is introduced.

Describe → explore existing patterns → ask the designer about an adaptation or commission a new design → approve → have it made.

Designers keep authorship and credit. The proposed service includes one revision and access for one commissioned garment; commercial terms still need agreement with participating designers.

Before the live service.

Connect real accounts and permissions, catalogue search, participating designers, versioned pattern files, retailer availability, payments, private delivery details, notifications and support resolution.

Confirm the proposed 24-hour quote reservation, design payment and refund terms, designer payout arrangements, licence scope and the existing customer/crafter fee model. The preview uses one recorded pattern and clearly labelled example prices.

The preview checks failed payments, required approvals and payout order. It does not provide live payments, legal agreements, actual stock or backend access control.