Upwork Project Catalog or a job post for an automation?

The short answer

A Project Catalog listing is a package the freelancer has already scoped: a price, a delivery time and a list of what is included. A job post is a scope you write, which freelancers then quote on.

Buy from the catalog when a listing matches your automation closely: one workflow, your tools, a result you can test in one go. Write a job post when your job has its own rules, connects several systems, or needs an acceptance test the listing does not mention. In both cases, the scope that ends up in the contract should be yours.

How Project Catalog works

From Upwork’s help center, checked October 2026:

• The catalog lists ready-to-launch projects; Upwork’s help page says more than 290,000.
• Each listing shows pricing, terms, scope and timing. Freelancers can offer paid add-ons.
• Many listings have tiers, and you can compare them side by side before choosing.
• You pay up front with “Confirm and Fund”, plus the one-time contract initiation fee, which the help center gives as $0.99 to $14.99 depending on the contract and your account.
• You have 48 hours to submit your requirements. If you do not, the project is cancelled automatically and refunded.
• After delivery you have 14 days to review. If you do nothing, the funds are released automatically.
• You do not need to post a job or sort through proposals.

That last point is the appeal. It is also the catch: the package was written before the freelancer knew anything about your job.

How a job post differs

A job post starts from your description. Upwork asks for a title, skills, the size of the project, the experience level you want, a budget (hourly or fixed) and a description, and you can add up to five screening questions. Freelancers apply with proposals, you interview a few and agree a contract.

It takes longer: writing the post, waiting for proposals, reading them. In exchange, every quote is for your scope, including your rules, your systems and how you will test it. The signals in how to pick an automation freelancer apply once replies arrive.

	Project Catalog	Job post
Who writes the scope	The freelancer, in advance	You
Speed to start	Quick: choose a tier and fund it	Slower: post, collect proposals, interview
Price	Fixed per tier, plus add-ons	Quoted for your job, fixed or hourly
Fits	A common, well-defined job	A job with its own rules, systems or tests
Risk	The package leaves out something your job needs	A vague post gets vague proposals

Four questions to decide

Three “yes” answers and a one-off: the catalog is a good route. Otherwise, write a job post using the workflow automation brief as the description.

A worked example

Say you run a small agency and want new enquiries from your website form copied into your CRM, with the right account manager emailed each time. Enquiries that mention an existing client should go to that client’s manager, not the general inbox.

In the catalog you find a listing called something like “Connect your form to your CRM” with three tiers. The basic tier covers one trigger and one destination. The middle tier adds email notifications. Neither mentions routing rules, what happens when the CRM refuses a record, or a handover document.

Run it through the four questions:

1. Trigger, tools and output match. Yes.
2. Failure and handover are not mentioned. No.
3. You can test it within the review window with real enquiries. Yes.
4. You will want a second workflow later, for invoices. Maybe.

That is a near match. The sensible route is to message the freelancer before buying, ask whether the routing rule and the failure alert fit in the middle tier or an add-on, and buy only once the answer is in writing. If the reply is “that is a custom project”, you have your answer too: write a job post with the same description and let several freelancers quote it.

Making a package fit your job

Packages rarely fit exactly, and that is normal. Even on a package-first marketplace, every order I have placed on Fiverr went through a custom offer rather than a package bought as listed. On a catalog project the same idea applies. Before you fund it, message the freelancer and get the gaps agreed in writing:

Before I buy the [tier name] tier, can you confirm this covers my job?

1. Goal: [one measurable sentence].
2. Trigger and tools: [what starts it], connecting [tool A] to [tool B]. All accounts are mine; you get access I can remove.
3. If a step fails: I get an alert within the hour, and nothing is lost.
4. At handover: the workflow export and a one-page run-book.
5. I will test: three runs fired by the real trigger, one forced failure and one duplicate test, within the review period.

If any of this is outside the tier, which add-on or tier covers it?

Two points about timing. The 48-hour requirements deadline starts once you fund the project, so have your brief ready before you buy, not after. And the 14-day review is your window to run the test above; put the dates in your calendar on the day of delivery.

The reason for the failure and test lines is practical. In my own scheduled jobs, a computer that went to sleep made publishing slots run hours late or not at all, and an expired token left a publishing job starting on schedule for two days while nothing went out. Neither shows up in a demo. The acceptance checklist for unattended automations explains each test.

Where it goes wrong anyway

• Buying the tier by price. The cheapest tier often covers one trigger and one or two tools. Compare tiers against your job, not against each other.
• Requirements written in a hurry. With 48 hours on the clock, it is tempting to send two lines. Write the brief first, then buy.
• Assuming the package includes maintenance. It usually does not. Ask, and agree the terms in the maintenance guide before the project closes.
• A job post that is just a tool name. If you go the job-post route, describe the task and the result. The cost guide shows what in your description moves the quote.

Wrap-up

The catalog is quickest when a listing already describes your job; a job post is better when your job has its own shape. Either way, put your goal, failure behaviour, handover and test in writing before you pay, and use the review window to run that test. If no listing fits, post your own job on Upwork with the brief above.