Post a job, compare proposals, on your own site

What Upwork is, and who it suits

Upwork is a hosted marketplace built around the job post. A client describes the work, freelancers send proposals, and the client picks one. Its pages describe other routes too: browsing freelancer profiles, inviting people to apply, hiring an agency, buying from a catalogue of fixed-scope projects and signing a direct contract. It also has an enterprise side.

It suits businesses that want flexible freelance talent and are happy to run a hiring process. Freelancers use it to find work without owning a site or a pipeline. Upwork sits in the middle, running the contracts, the payments and the support.

Its own client pages say it is free to create an account and post a job, and that the client pays once a contract starts. That is the shape most people mean when they say Upwork-style.

The request and proposal model, and what it needs

The pattern has four parts: a brief, a pool of people who can answer it, a way to compare answers and a way to pay in stages. The hard part is not the software. It is having enough good freelancers so that a buyer who posts a brief gets answers worth reading.

This matters more than any feature list. A request marketplace with no vendors is an empty job board, and buyers do not come back to one. Plan your seller side first, then switch the buyers on. Approach a small group of people you already trust, give them a reason to answer early briefs well, and seed a few real requests yourself so the board looks alive on day one.

Early on, you may also want to lead with ready-made services and let requests grow beside them, since the same site runs both.

The software side is well covered in the free plugin. The request marketplace use case walks through the setup in detail, and the two marketplace modes post explains why you can lead with requests and still sell ready-made services.

How a brief becomes an order

Every step below is in the free plugin unless noted.

1. The buyer posts a request. The form takes a title, description, category, a fixed budget or a range, a delivery timeline, skills and attachments. Posting costs nothing. A request stays open for 30 days by default, and you can change that.
2. Approved vendors see it. They browse open requests, filter by category, search and sort by budget or date. Any approved vendor can answer; there is no category or level gate.
3. A vendor sends a proposal. It needs a cover letter, a price and a delivery time, with optional attachments and a link to an existing service. The vendor also picks a fixed price or a milestone plan.
4. The buyer compares. Proposals show their contract shape side by side, with ratings and the vendor profile.
5. The buyer accepts one. An order is created, the other proposals are declined and the request is marked hired.
6. The order runs. Requirements, delivery, revisions, completion and review follow the standard workflow, the same one a ready-made service uses.

One limit is worth knowing. Buyers cannot message a vendor directly through a request before accepting. Vendors can put questions in the proposal, and the buyer judges from the proposal and the profile.

Milestones, and how the money moves

The commission on a request marketplace is usually taken from the accepted proposal value, not from a catalogue price. You set the global rate and can override it for a vendor you want to reward or recruit. It is taken from the vendor’s earnings when the work completes, and from milestone phases at payment time, so the money reaches the vendor’s wallet before delivery of that phase.

A milestone plan splits a project into named phases, each with a title, description, amount and days. The buyer sees the whole plan before accepting. On acceptance the order starts immediately with the phases laid out, and the buyer pays phase one from the order page.

Phases pay in lock-step. Phase two only opens once phase one is approved. When every phase is approved, the project completes and the buyer is asked for a review. That protects buyers from paying for work not yet seen. It also means money is not held for future phases in advance. If you want funds locked up front, this is not that model.

Milestones, tips and paid extensions work on the built-in checkout and on WooCommerce, and not on other checkout rails. Pro adds the WooCommerce checkout, Stripe Connect and PayPal Payouts. The free plugin takes Stripe, PayPal and offline payment, and pays vendors by a manual withdrawal flow with a CSV of what is owed.

What is free and what is Pro

For a request marketplace the split is simple. These are all in the free plugin:

• Posting buyer requests, with budget, deadline, skills and attachments.
• Vendor proposals, with a cover letter, price, timeline and attachments.
• Fixed and milestone contracts, and the lock-step phase payments.
• The full order workflow after acceptance, with reviews and disputes.
• The commission system and manual withdrawals.

These need Pro:

• WooCommerce as the checkout, and Razorpay as a gateway.
• Stripe Connect and PayPal Payouts, which pay vendors without a manual step.
• Tiered commission rules by category, volume or seller level.
• Vendor subscription plans, if you want to charge vendors to sell.
• Tipping, analytics with export, white label and cloud storage for deliveries.

Free also caps a few listing limits that matter to ready-made services more than to proposals: three add-ons, four gallery images, five FAQs and five buyer requirements per service.

What WP Sell Services does not do here

We checked for the parts of the Upwork pattern that we could not find, so you hear them first.

• There are no hourly contracts and no time tracking.
• Buyers cannot invite a specific vendor to a request.
• Buyers cannot chat with a vendor on a request before accepting.
• There is no talent pool of its own. You recruit every vendor.
• Recurring or subscription billing for a service is not available: the code is switched off, so do not buy Pro for it.
• There is no importer from Upwork.

None of these is hidden, and a few of them decide the question. If your buyers hire by the hour or want to chat with three freelancers before choosing, you will miss them.

A developer can build around some of them with the REST API and hooks, and that is custom work.

What it costs you to run, compared with Upwork

On Upwork the cost sits with the platform: its fees and its terms. Check the vendor’s site for current figures, because they change. On your own site the cost sits in running a website: hosting, a domain, updates, gateway fees, and the time you spend on support, moderation and payouts.

You also need people to run it. Someone has to approve vendors, watch briefs that get no proposals, answer disputes and handle refunds. At a small scale that is you. At a large scale it is a hire. A quiet request that gets no proposals is a sign you have too few vendors in that category, and the fix is recruiting, not settings.

Pro is a paid yearly licence; see the pricing page. The core is free and covers the whole request flow.

Trust, vetting and disputes

In a request marketplace, trust is built at the moment of choosing. A buyer who reads five proposals needs to tell the careful one from the copied one. The cover letter helps, but the profile, the ratings and the linked service do most of the work.

Upwork gives buyers reviews, portfolios and a platform that carries the contract. A new site has to build that trust from nothing, and in a request marketplace the risk is quality: vendors who paste a template reply into every brief.

The product gives you levers for that:

• A vendor approval step, so only people you accept can propose.
• Reviews and star ratings on completed orders, with seller replies and moderation.
• Seller levels earned from real order history.
• A public vendor profile with a portfolio, response time and level.
• A dispute process with evidence from both sides and admin mediation.

Quality control is also a policy. Remove vendors whose proposals are copy-paste, and say in your terms that you will. What you must do yourself is write the terms, vet vendors well, and act on disputes in good time. See milestone payments for a freelance marketplace for the money mechanics.

Data and ownership

Every buyer and vendor is a WordPress user on your site. Briefs, proposals, orders, messages and the earnings ledger sit in your database and are reachable by REST API and WP-CLI. Standard WordPress privacy tools export and erase a member’s marketplace data, and erasure is refused while an order is in flight or a payout is mid-transfer.

Briefs and proposals also carry value over time. You can see which categories get requests but few answers, which vendors win, and where buyers drop out. On a hosted marketplace the platform holds that history. That is fine until you want to leave, change the rules or study your own numbers.

Moving over from Upwork

There is no importer, and we will not pretend otherwise. Moving over is a rebuild. Vendors recreate their profile and services through the wizard. A developer can script bulk creation against the REST API or WP-CLI, which is custom work. Reviews, job history and ratings stay on Upwork.

Check Upwork’s terms before asking anyone to take clients off the platform, because the vendor governs that, not us.

A staging and launch checklist

1. Install WP Sell Services on a staging site and run the setup wizard.
2. Set your commission, currency, withdrawal minimum and clearance period.
3. Create a few vendors and approve them.
4. Post a request, send two proposals, accept one and walk the order to review.
5. Repeat with a milestone plan and pay each phase.
6. Open and resolve a dispute, then approve a withdrawal.
7. Write your terms and refund policy.
8. Recruit your first vendors before you invite any buyers.

The rest of the stack on the same site

WP Sell Services is one of several separate, optional plugins from the same team. They run on one WordPress site and one login. You install, host and update each one yourself.

The connections we can state sit in the marketplace. Checkout is the built-in one, or WooCommerce with Pro; EDD and FluentCart adapters ship in Pro as beta and are not offered by default. Gateways are Stripe, PayPal and offline payment, plus Razorpay in Pro. Payouts can run through Stripe Connect or PayPal Payouts in Pro. Delivery files can live on Amazon S3, Google Cloud Storage or DigitalOcean Spaces in Pro. See integrations.

The sister products run on the same site, and we claim no integration with the marketplace:

• BuddyNext for community.
• Jetonomy for forum and Q&A.
• Learnomy for courses.
• Listora for a directory.
• WP Career Board for a job board.
• Eventonomy for events.
• WB Gamification for points and badges.

The themes BuddyX Pro and Reign come from the team too. A hosted marketplace is one bill and takes a cut. These plugins are separate things you run, so you keep the margin and carry the upkeep.

Other alternatives worth a look

• Fiverr wins for ready-made, fixed-price services with a large built-in audience.
• Freelancer.com wins for high bidding volume and design contests.
• Sharetribe wins when you want a hosted marketplace builder with its own negotiation and offer flows and no server to look after.
• Dokan is a WordPress multi-vendor plugin we compare separately.
• WCFM Marketplace is a second WordPress option with its own page.
• WC Vendors is a third, compared on its own page.

Who should stay with Upwork

The honest test is supply. If you cannot name where your first fifty good vendors come from, the software will not fix that.

Stay if you are a buyer who needs a specialist quickly and has no interest in running anything. Stay if you are a freelancer whose clients find you there. Stay if you need hourly contracts, a very large talent pool or an enterprise contract with a vendor that carries the risk.

Start your own marketplace if you have a niche, a way to attract both sides and the patience to curate. See features, free versus Pro and compare.