The Upwork Master Playbook: Portfolio · Catalog · Bidding · Multi-Profile Agency · Inbound Ranking — the AI-Native Execution Playbook · Companion to Sales Booklet Chapters 10 & 20 (the marketplace channel)
Volume 10 gave Upwork the engine treatment. This volume is the master edition — built around the five systems that decide marketplace outcomes: Portfolio (proof made visible), Project Catalog (productized inbound), Bidding (precision + testing), the Multi-Profile Agency (coverage, KPIs, ROI), and Inbound Ranking (the search machine).
It is also written against a real case: the FISTA assets — the personal profile (AI Agent Developer | Forward Deployed Engineer, Top Rated Plus, 100% JSS, 65 jobs, 5.6K hours, $300 consultations live) and the agency (FISTA Solutions, Top Rated Plus, $200K+ earned, 56 jobs). Throughout, Live Audit boxes apply each chapter to these actual profiles — honestly, including what's currently working against you. Where a mechanic may have changed since writing (Connects pricing, boost auctions, badge thresholds), the rule is: the system here is durable; verify current numbers in Upwork's help center before betting on them.
One strategic frame before anything: your accounts sit in the top few percent of the marketplace (Top Rated Plus + 100% JSS on both). Your problem is not credibility — it is conversion of credibility into premium positioning and inbound flow. That reframing drives every recommendation in this book.
This volume supersedes and deepens Volume 10, Part II. Prompts run P88–P95.
Upwork is a trust exchange running on an algorithm. Every system in this book manipulates the same five inputs the platform (and the client) reads:
The compounding loop this book builds:
The portfolio is where a skimming client's eyes go second (after the headline) and where hiring decisions actually form — because it's the only part of a profile that shows instead of claims. Most freelancers treat it as a screenshot dump. You will treat it as a conversion gallery: every piece is a mini case study with a designed cover, an outcome title, and a before → after narrative, curated per specialized profile.
Every piece has four layers:
Curation rules: 6–10 pieces per specialized profile, newest and biggest first, 100% wedge-relevant — the metaverse website does not belong in the AI-agents gallery, however good it was. Each Catalog project (Ch 3) and each specialized profile gets its matching subset. Refresh quarterly; a 2023-era gallery undercuts a 2026 positioning.
Step 1 — Inventory. List every shippable proof: live URLs, screenshots, Looms, repos, metrics. Mark permission status per item.
Step 2 — Generate each piece with P88. Feed it screenshots and/or a live link; get back the complete piece, including the cover-design brief.
P88 — Portfolio Piece Generator (from Screenshots / URL)
Step 3 — Batch-produce covers. Run P88's design brief through Canva (one master template, then duplicates) or an image tool; consistency across covers is itself a trust signal — it says systematized firm, not freelancer collage.
Step 4 — Deploy. Pieces → main profile (best 8), specialized profiles (wedge subsets), Catalog galleries (Ch 3), and pinned in proposals (a proposal with the matching portfolio piece attached converts measurably better — Vol 10's P78 already asks for it).
Your agency overview lists projects (OptionBlitz, Myreeldream.ai, Cisco Meraki…) as text bullets — that's portfolio material trapped in the wrong format, with zero images and zero outcomes. Chapter-2 treatment: the AI-relevant ones (Myreeldream.ai as generative-AI systems proof; the automation and agent work from your 65 personal jobs) become designed pieces; Cisco Meraki becomes an enterprise-credibility piece ("Fortune-500 delivery" is a cross-border fear-killer per Ch 20); the blockchain/metaverse items move to a legacy section or out of the AI wedge entirely.
Catalog flips the motion: instead of bidding, clients buy or inquire directly — Upwork's closest thing to productized inbound, surfaced in its own search and in Uma's AI recommendations. The Booklet's Chapter 2 logic applies exactly: Catalog is productizing a service — fixed scope, fixed price, defined deliverable — which creates leverage and a permanent search asset that sells while you sleep. Catalog listings also rank in Google, making them free landing pages.
What Catalog is for strategically: (a) capturing high-intent, low-touch demand at the small/medium ticket, (b) a low-risk entry product that converts into your real engagements (the marketplace version of Vol 7's POV logic), (c) keyword real estate in your wedge.
A service earns a Catalog listing only if it passes the Productization Test — all five:
The FISTA Catalog menu this process yields (worked example):
Structuring each listing: 3 tiers (Starter = smallest honest version / Standard = the real thing, priced where you want most buyers / Advanced = integrations + scale — classic anchoring, honest scope steps); delivery days you can beat; a requirements form that doubles as discovery (5–7 questions: current process, systems, volume, success definition, access — a good form pre-qualifies exactly like the website's "what's the problem?" field); gallery from Chapter 2's matching pieces; FAQ from real buyer questions (P4 Question Bank, Upwork edition); and for AI listings, one calm controls line in the description (Vol 7's boundary rule — it converts the nervous majority your competitors' hype scares off).
P89 — Catalog Selector & Menu Designer
P90 — Catalog Listing Writer
Operating the Catalog: treat orders' first response like A-route inbound (same-day, Vol 1 standard); over-deliver the Starter tier deliberately (it's a paid audition); at delivery, run Vol 10's P79 close (review + the ladder conversation); track per-listing funnel monthly — impressions → views → orders/inquiries → revenue → upgraded engagements — and rewrite or kill listings that view well but never convert (usually a pricing-trust or specificity problem in the first two lines).
Volume 10 set the bidding foundation (P77 qualification, P78 proposals). This chapter adds the layers that separate top-decile bidders: feed strategy, timing, boost economics, and disciplined testing. The governing math: bidding is a paid channel — every proposal costs Connects + research time — so it must be run like one, with cost-per-interview and cost-per-hire known, and every variable earning its place through evidence, not habit.
Layer 1 — Feed engineering. 3–5 saved searches per profile wedge, tuned tight (keywords + filters: payment verified, client history, budget floors). The best jobs are won in the first hours: proposals sent early sit higher in the client's default view and reach them before decision fatigue. Your operating rhythm therefore samples the feed 2–3× daily at set times (fits inside Vol 10's 20–30 min blocks) rather than binge-bidding nightly.
Layer 2 — Qualification (P77, unchanged) — with one addition for your tier: the badge-leverage check. TR+ profiles convert disproportionately on jobs where clients filtered for quality (higher budgets, longer descriptions, "expert" level, previous hires at premium rates). A $500 job doesn't just pay badly — it wastes your badge where it can't differentiate. Your floor (P80) should now reflect that.
Layer 3 — The proposal (P78, unchanged) + attachment discipline: the one matching P88 portfolio piece; for AI jobs, the calm controls line; for enterprise-smelling jobs, the consultation offer as the tiny ask alternative ("if useful, I also run 30-min architecture sessions — but happy to answer here first").
Layer 4 — Boost economics. Boosted proposals are an auction: you bid Connects for one of the top slots in the client's view. The math is simple and worth writing down: boosting pays when (uplift in win probability × expected contract value) exceeds the Connects cost by a healthy multiple — which in practice means boost selectively: high-fit + high-value + low-proposal-count + fresh jobs. Never boost to rescue a mediocre fit; a boost multiplies visibility, not quality. Availability-badge and ad features follow the same logic: paid amplification of an already-sharp signal.
Layer 5 — Invites and Uma-era matching. Answer every invite fast even to decline (response metrics feed ranking); declined invites with a gracious one-liner still bank goodwill. As Upwork's AI matching (Uma) increasingly pre-selects candidates for clients, your profile corpus (Ch 6) quietly becomes part of every "bid" — one more reason the inbound chapter is bidding strategy too.
At 10–25 proposals/week you cannot run parallel statistical A/B tests — pretending otherwise produces noise worship. The workable discipline is sequential cohort testing, the Vol 2 P32 philosophy applied to bids:
P91 — Bid Test Designer & Cohort Analyzer
With TR+ and 100% JSS, your leverage move is fewer, bigger, boosted-selectively: shift the mix toward the enterprise job classes where the badge differentiates, make the $300 consultation a standing alternative ask (it monetizes discovery AND filters tire-kickers), and run the first cohort test on exactly that — consultation-ask vs call-ask on $5K+ AI-agent jobs.
Before architecture, the hard lines — because everything in this chapter compounds on accounts that must survive for years:
This isn't compliance theater — it's Vol 9's ethics layer applied where the stakes are an account ban that erases $200K of accumulated trust overnight.
Each profile is a niche market position with its own P&L, KPIs, and quarterly OKRs. The agency's job feed is triaged centrally; a router rule assigns each qualified job to exactly one best-fit profile.
The FISTA worked example — a coverage matrix:
Rules of the matrix: wedges are mutually exclusive enough that the router is rarely ambiguous; the flagship takes anything strategic regardless of wedge; every profile links to the agency (shared trust rubs off both ways); each runs its own Chapter 2 portfolio subset and feeds the shared Catalog menu.
Weekly KPIs per profile (leading, the scorecard):
Monthly KPIs (converting): hires · new contract value · effective hourly rate realized · Catalog orders routed · JSS + review outcomes · repeat/expanded clients.
Quarterly OKR pattern per profile (example — Engineer B / Voice AI):
Agency-level OKRs sit above (total GSV, blended margin, TR+ profiles count, Expert-Vetted progress on the flagship) so profile OKRs never fight the whole.
ROI per profile — the P&L that decides scale/kill:
Decision rules: new profile gets 2 quarters to reach contribution-positive with visible KPI trend; positive and trending → add bid budget; flat after coaching + one repositioning → fold its wedge into a stronger profile. Profiles are staff (Vol 10's satellite rule, applied to people's market positions — the person stays; the position gets redesigned).
P92 — Agency Profile Matrix Designer
P93 — Profile Scorecard & Weekly Review
You already hold the rare asset: a TR+ agency with 100% JSS. The build order for you specifically: (1) fix agency positioning first (Ch 6's rewrite) so every profile inherits a sharp banner, (2) launch the matrix in waves — Voice AI profile next (highest Catalog synergy), (3) route ALL small/medium jobs away from the flagship, whose calendar should shift toward consultations, enterprise bids, and Expert-Vetted-track work.
Upwork inbound = being found and chosen without bidding: search results, client invites, Uma's AI-matched shortlists, Catalog search, and consultation bookings. It runs on the same law as Vol 1's AEO chapter: you rank for what your corpus proves, and you convert with what your proof shows. Inbound is the highest-ROI motion on the platform because its marginal cost is zero — and it compounds with every review.
Step 1 — The keyword map. Per wedge: harvest the exact phrases from (a) 30 recent job posts in the wedge, (b) Upwork's search suggestions, (c) your won-contract titles. Primary family + 4–6 secondary terms per specialized profile — buyers' words, not yours ("AI agent for customer support," "voice AI receptionist," "n8n automation expert," "RAG chatbot").
Step 2 — Rebuild the corpus with P94.
P94 — Profile SEO & Ranking Audit
Step 3 — Track and audit monthly. Freelancer Plus analytics give impressions, profile views, and invite counts; the Catalog dashboard gives listing funnels; your log gives consultation bookings. That's the inbound funnel: impressions → views → (invites + messages + orders + bookings) → interviews → hires. You can't see your literal rank position — so measure the outputs and use proxy checks (search your primary terms from a client-side view; note who outranks you and what their corpus has that yours lacks — the marketplace edition of Vol 1's P15).
P95 — Monthly Upwork Inbound Review
Four additions my review says belong in the master edition:
1. The Expert-Vetted campaign (flagship only). Invite-only, but not luck-only: concentration of high-value contracts in one category, enterprise-client reviews, rising rates, and category-consistent activity are the observable correlates. Your P92 router already engineers this — everything small routes away from the flagship precisely so its record reads "top 1% of AI engineering."
2. Enterprise & Business-Plus clients on-platform. Larger clients bring longer contracts, better rates, and compliance requirements (interviews, security questionnaires). Your Vol 1 Decision Pack and Vol 7 Trust & Controls doc work verbatim here — attach them in enterprise threads; almost no marketplace competitor has them, and they're the difference between "freelancer" and "vendor" in a procurement reviewer's eyes.
3. The review-engineering ritual (legitimate kind). Reviews are written at emotional peaks: the P79 close creates the peak (results vs criteria + friction acknowledged), and what clients write follows what you emphasized during delivery — a client who heard "milestone 2 hit the accuracy threshold" writes outcome-rich reviews that themselves become ranking keywords. Never scripted, always steered by what you make salient.
4. The graduation discipline (Vol 10's P80, restated as policy). On-platform relationships convert to direct contracts only per Upwork's conversion rules — pay the fee or serve the tenure; never invite circumvention (it risks the whole $200K asset). The healthiest end-state for FISTA: Upwork as the always-on proof-and-entry channel at 20–40% of revenue, feeding the Vols 1–2 engines that own the rest.
Days 1–15 — Reposition. P94 corpus rewrite on flagship + agency (rate move included); specialized profiles live; consultation productized. Evidence inventory → first 6 portfolio pieces via P88 with designed covers.
Days 16–40 — Productize & route. P89 Catalog menu decided; 4 listings written (P90) and live with galleries; P92 matrix designed, compliance signed, wave-1 profile (Voice AI) launched with its subset. Bid log + P91 boost policy live; first cohort test starts (consultation-ask vs call-ask on $5K+ jobs).
Days 41–90 — Operate & compound. Weekly P93 scorecard reviews; monthly P95 inbound + Catalog session ×2; corpus frozen for clean rank measurement; first Catalog orders over-delivered and laddered; review-peak closes on every completing contract. Day 90: full funnel read — inbound share, per-profile P&L, cohort test verdicts, Expert-Vetted progress — and the next wave decision.
The steady-state rhythm (fits Vol 0's calendar):
Protect if behind: response times, JSS-risky deliveries, and the weekly scorecard. Rank recovers from a slow month; a damaged JSS doesn't.
Series integration: P77/P78/P79/P80 (Vol 10) remain the bidding/closing/pricing core this volume extends. Portfolio pieces are P7 proof assets in marketplace format; Catalog is the productization logic of Vol 3/P33; the POV listing is Vol 7's P61 productized; interviews run on Vol 5's machine; contracts flow into Vol 6's CRM with source=upwork so the One Dashboard shows the channel honestly; and every Upwork review feeds the Vol 1 proof library with client permission.
A marketplace looks like a place where you compete on price against the world. Run properly, it is the opposite: the one arena where trust is scored, displayed, and compounded in public — where a decade of good behavior fits in a badge, and where the seller with the sharpest wedge, the calmest copy, and the cleanest delivery record gets found by buyers who arrived already wanting to hire. You have already done the hard decade. This book's whole argument is one sentence: stop selling like you're new there, and start pricing, positioning, and routing like the top-one-percent firm the badges say you are.
— Companion Volume 12 · FISTA Solutions · Sales Booklet 2026