Issue #6: Eight Gigs Where the Brief Tells You What to Build

Fast scan

1. [DEV] Senior independent AI engineer / architect

1. Write a one-page teardown of a production AI system you built: problem, architecture, evals, release path, and what broke.
2. Record a short walkthrough showing how you debug model output, retrieval quality, or workflow orchestration.
3. Pitch one narrow service first: "I will audit your RAG evaluation and failure logging" is easier to buy than "I build AI systems."

2. [DEV] [OFFICE] Developer relations / technical customer success

1. Pick one developer tool you already know and write a 700-word "first successful integration" guide.
2. Create a sample onboarding checklist that covers setup, success metrics, common blockers, and renewal risk.
3. Look for API, SDK, GIS, DevTools, and infrastructure startups; pitch a 2-week onboarding-content sprint before asking for a retainer.

3. [OFFICE] [DEV] Salesforce CRM analyst for pricing and dashboards

1. Build a sample Salesforce-style dashboard in a sandbox, spreadsheet, or BI tool: pipeline by segment, discount leakage, renewal risk, and next action.
2. Create a before/after case study from any messy CRM cleanup you have done, even if it was internal work.
3. Pitch founders and sales leaders one concrete promise: "I will find the top 10 CRM data problems blocking accurate pipeline reporting."

4. [DESIGN] [OFFICE] CRO experiment designer

1. Pick one SaaS signup flow and write three testable hypotheses, not just design opinions.
2. Mock the variants in Figma and annotate the metric each variant is meant to move.
3. Offer a "CRO backlog sprint": five experiment ideas ranked by impact, effort, and learning value.

5. [DESIGN] Webflow designer / developer for conversion sites

1. Build one niche landing page in Webflow for a real vertical: dental, home services, B2B SaaS, coaching, or local clinics.
2. Package the offer as a conversion site, not a pretty website: hero, proof, objection handling, CTA, analytics setup.
3. Add a handoff checklist: CMS instructions, style guide, mobile QA, form test, and page-speed notes.

6. [OFFICE] AI-assisted RFP / proposal manager

1. Create a sample RFP response library: company overview, security answer, implementation timeline, differentiators, and proof points.
2. Build a lightweight retrieval workflow in Notion, Google Drive, or a vector-search tool; document how reviewed answers get written back into the corpus.
3. Pitch regulated B2B software firms a fixed project: "I will turn your last five proposals into a reusable answer library."

7. [OFFICE] SaaS project / marketing manager

1. Build a portfolio artifact: a mock sprint board, user-story template, QA checklist, and campaign calendar for one SaaS feature.
2. Offer a two-week "delivery cleanup" package for tiny SaaS teams: backlog triage, bug labels, client update cadence, and KPI sheet.
3. Avoid clients who want a full-time operator at part-time pay with no scope boundaries. Ask for the product list, team size, reporting cadence, and decision owner before accepting.

8. [OFFICE] Podcast agency account manager

1. Draft a client-health dashboard: last touchpoint, next episode status, open blockers, at-risk flag, and next action.
2. Create three reusable client emails: onboarding expectations, late asset reminder, and post-launch performance recap.
3. Pitch agencies a narrow retainer: "I will manage client follow-up and production status for 5 shows per week."

Scam filter notes for this issue

• Upfront payment: never pay for training, equipment, crypto wallets, software licenses, or "verification" before work starts.
• Off-platform pressure: if the client immediately moves you to Telegram/WhatsApp and asks for sensitive documents, slow down.
• Disproportionate pay for vague work: high pay can be real, but only when the scope, skills, and review process are clear.
• No decision owner: if nobody can explain who approves work and when payment happens, you are probably joining a mess, not a gig.