Founding Formalwear Cohort

  • Home
  • / Founding Formalwear Cohort

Five qualified shops • application required

Help prove the formalwear rental workflow before we scale it.

The founding cohort is a guided pilot for formalwear shops willing to test one representative rental, name what does not work, and decide whether a broader rollout is justified. Tuxedo and formalwear rental remain the core; bridal-rental shops with the same garment lifecycle are a deliberate adjacent fit.

About 3 minutes to apply. No payment and no customer data required.

14 guided daysA bounded validation period
1 rental proofParty through return
2 checkpointsOnboarding and founder review

Pilot structure

A learning contract, not a logo collection.

Selection is based on workflow fit and our ability to support the proof responsibly. It is not first come, first served, and an application is not automatic enrollment.

  1. Step 1

    Define the proof

    Agree on the one representative party, garment, payment, pickup, and return scenario the shop needs to trust.

  2. Step 2

    Prepare safely

    Use a safe sample catalog or a separately reviewed, redacted source sample to understand setup and migration gaps.

  3. Step 3

    Run the workflow

    Complete one guided onboarding appointment and run the representative rental through its expected states.

  4. Step 4

    Review the result

    Record blockers, confirm whether the shop returns in a separate session, and decide the next step from evidence.

Good pilot fit

  • You actively manage tuxedo, suit, mixed formalwear, or bridal-garment rentals.
  • A wedding, prom, or group order is central to the workflow you need to prove.
  • An owner or workflow decision-maker can attend the guided session.
  • You can describe the workflow without sending customer data through this form.
What this does not promise

The cohort does not promise a universal importer, an emergency cutover, custom development for one shop, free migration, or specific commercial terms. Any migration and pricing scope is agreed separately after qualification and readiness review.

Cohort application

Tell us about one rental workflow.

Do not include customer names, contact details, measurements, order records, or other sensitive information in this form.

About 3 minutes • no payment • no customer export required

The actual product proof

Run one rental from wedding party to returned garments.

These are the screens and results an invited shop records in its secure workspace. Public checkmarks are intentionally disabled: cohort progress, owners, evidence, blockers, and timestamps are stored against the approved shop—not in this browser.

Proof boundary

Use demo or redacted customers and safe inventory. Never paste card data, passwords, production credentials, or unredacted customer records into an evidence note.

Open invited shop workspace

Requires the verified email on an invited application.

1

Set up one test wedding party

Choose the exact rental the shop will run and create it with safe data.

Create the party and enter all three dates

POS → Create Party Reservation

Shop operator

Do this

Create “Sample Wedding Party” and enter its event date, pickup date, and return date.

Done when

The Party Reservation opens with a reservation code and the correct event, pickup, and return dates.

Name the shop operator running the test

Cohort review

Shop manager

Do this

Choose one staff member to run the rental and make the final continue, change, or stop decision.

Done when

That person and the date of the final review are written in the application’s Next action.

Use two demo members and safe inventory

Party Reservation + POS

Shop operator

Do this

Use demo or redacted customer records and sample inventory. Do not enter real card numbers or production credentials.

Done when

The entire test can run without exposing a real customer’s private or payment information.

Agree on the exact start and finish

Cohort onboarding call

Shop operator + SleekSync

Do this

Confirm that the test starts at party creation, ends after return, and includes one size or availability problem.

Done when

Both people can repeat the same route, exception, and final review date before the test starts.

2

Complete two party members

Prove the roster stays understandable when measurements or sizing change.

Complete two member profiles, then change one size

Party Event Workspace → Party Roster

Shop operator

Do this

Add a primary contact and one additional member, assign their roles, and complete profile and measurement details. Then change one member’s size.

Done when

Both members appear in the Party Roster and its Profile and Sizing states show the correct next action after the change.

Assign each member’s rental items

POS → Packages or Products

Shop operator

Do this

Add a package or rental items for each member, choose sizes, and handle one unavailable item as Order Required or transfer-needed.

Done when

Each member has linked ticket items, and the unavailable item has a visible order or transfer action instead of looking available.

3

Create the ticket and record payment

Make sure the rental details and money agree before anything leaves the shop.

Create the ticket with a partial payment

POS → Create Ticket

Shop operator

Do this

Review the party items, create the ticket, and record a deposit or partial payment so a balance remains due.

Done when

The ticket is linked to the party and its total, amount paid, balance due, and Partially Paid status all agree.

4

Prepare and hand off the pickup

Prove another staff member can prepare the correct garments and finish pickup.

Scan the order, collect the balance, and complete pickup

Prepare Orders → Party Event Workspace

Pickup staff

Do this

Select the ticket, scan or confirm every item, resolve the Order Required or transfer item, collect the remaining balance, and complete pickup.

Done when

The ticket is Prepared or Checked Out, payment is Paid, and each member’s Pickup state matches what actually left the store.

5

Process the return and make the decision

Close the inventory and money loop, then see if the shop can understand it later without help.

Process the return and one real exception

Rental Return

Return staff

Do this

Choose the representative case: a full return or a partial return. Mark the returned garments, then record one damaged, late, or missing-item issue and its fee, refund, or no-refund decision.

Done when

A full case shows Returned; a partial or missing-item case shows Partially Returned. Returned inventory is Available, the exception stays visible, and the net refund or charge matches the decision.

Come back later and explain the party without help

Party Event Workspace + Rental Return

Shop operator

Do this

Close the test. In a later session, reopen the party and ticket without the founder driving the screen.

Done when

The shop operator can identify the open member action, payment state, pickup state, and return result, then chooses continue, change, or stop.

SleekSync records this only after the shop returns in a separate signed-in browser session; it cannot be checked manually.

The final continue, change, or stop decision requires all ten database-backed proofs plus a written rationale. The founder control room keeps the audit history without a separate spreadsheet.