Your first suppliers need a person, not a form.

The sign-up count is lying to you, a little

Launch week goes well. The landing page works, the outreach works, and the number of suppliers who've created an account keeps going up. Someone puts it on a slide.

Then a buyer searches for something specific and gets three results. Two of them have no availability. One has a price that the supplier, it turns out, changed in their own system last month.

It isn't that the suppliers aren't interested. Most of them got as far as the form and then hit something: a tax document they didn't have to hand, a photo requirement, a question about how payouts work that nobody answered. So now your team is emailing them one at a time, which is exactly the manual coordination the marketplace was supposed to remove.

As we put it on our marketplaces page, a marketplace can look self-service while its team quietly coordinates every important transaction. Onboarding is usually where that starts. The good news is that it's also where it's easiest to see.

Walk one supplier from yes to first payout

Pick a real supplier, ideally one who signed up and then went quiet. Walk their path with them, or at least alongside their account, from the first invitation to the first time money lands in their bank. At each step, write down two things: what the supplier needed to know or do, and what your team had to check.

For most marketplaces the path looks something like this:

1. Invitation and account. They hear about you and sign up. Easy part.
2. Verification. You need to know who they are. Identity, business details, maybe licenses or insurance, depending on what you sell.
3. Payout details. Bank account, tax forms, and whatever your payment provider requires. This is where a lot of people stop, because it's the first step that asks them to go find something.
4. First listing. Description, photos, price, options. The supplier knows their offer far better than your form does.
5. Availability. How a buyer knows they can actually book or buy. Often this lives in the supplier's own calendar or stock system.
6. First order. A buyer commits. The supplier has to notice, accept, and deliver.
7. First payout. Money arrives, and it matches what they expected.

You'll probably find the path is longer than anyone drew it, and that your team is doing invisible work at several steps. That's fine. Now you can see it.

Find where they stall

Once you've walked a few suppliers, the sticking points tend to repeat. The common ones:

Payouts. Suppliers want to know when they'll be paid, what you take, and what happens with refunds before they hand over bank details. If that answer is buried in terms of service, they'll wait to ask a person.

The listing. The form asks for fields. The supplier wants to explain what makes them different. Listings stay half-finished because the form doesn't make room for the thing that would sell it.

Availability. If availability lives somewhere else, every listing goes stale the moment the supplier gets busy. A buyer finding something "available" that isn't is one of the fastest ways to lose both sides.

The first order. New suppliers are nervous about it. Will they see it in time? What if they need to decline? Who do they call?

This is where the kind of thing being listed matters. On Spin:Market, the marketplace connected DJs with businesses looking for bespoke playlists, so the thing on offer was a person's taste and craft, not a box on a shelf. A form can't capture that alone. The more your supply looks like that, the more onboarding is a conversation.

Do the early onboarding by hand, on purpose

For your first suppliers, give each one a person. Not as a stopgap you're embarrassed about, but as research.

Have someone on your team get on a call, walk through the setup together, and fix whatever gets in the way. The important part is what happens after the call: write down what you did. Which question did they ask? Which field confused them? Which document did they not have? Where did you have to change something in the admin by hand?

After a dozen or so of those notes, patterns show up. The question everyone asks belongs on the screen where they ask it. The field that confuses people needs a better label or an example. The admin change you keep making by hand is a feature. Suppliers who needed the same help can be grouped, and that group gets a better path.

This is how the onboarding product gets designed: from what real suppliers needed, not from a guess about what they'll tolerate.

Set an end point for the hand-holding, too. Decide in advance that once a step has gone smoothly for a run of suppliers without anyone stepping in, it comes off the call script and lives in the product. Otherwise the concierge quietly becomes permanent, and you've built a marketplace that needs another person every time a new batch of suppliers arrives.

Decide what "bookable" means before anything goes live

The last piece is a definition. A listing can be in your database without being something a buyer should see. Write down, in plain terms, what has to be true before a listing goes live. For example:

• The supplier is verified and can be paid.
• The listing has the details a buyer needs to choose, reviewed at least once by your team for early suppliers.
• Availability is connected or confirmed recently enough to trust.
• The supplier knows how they'll hear about an order and what to do if they can't fulfill it.

Anything short of that is a draft. Drafts are useful because they tell you who's close. They just shouldn't show up in search.

That one rule protects buyers from dead ends and gives your team a clear list each morning: these suppliers are one step away, here's the step.

Start with one supplier type

If you're building a marketplace or trying to fix one that grew faster than its onboarding, pick one kind of supplier and one kind of transaction, and follow both sides through it. The gaps between what the supplier expected and what the buyer expected usually tell us what to build first.

It's also the first thing we'd do on a marketplace engagement. When onboarding involves verification and payouts across several systems, it overlaps with business process automation too. Either way, bring us a supplier who went quiet, and we'll walk their path with you.