3 non-AI freelance skills worth learning right now (June 8, 2026)

The skill market this week

Technical Writing (API/developer documentation)

Demand signal

Rates

Realistic learning path

• 3 days: Pick an open-source project with an existing API (GitHub has thousands). Write a "Getting Started" guide for one endpoint. Focus on structure: overview, authentication, first call, response format, error codes. This is a publishable portfolio piece.
• 4 weeks: Use a docs-as-code toolchain — either Docusaurus or MkDocs. Version-control your docs in Git alongside the code. Learn to write reference docs (auto-generated from OpenAPI specs) alongside conceptual guides (written by hand). At this milestone you can take entry-level gigs.
• 12 weeks: Build a complete developer portal for a small project: overview, getting started, API reference, changelog, tutorials. Understand the difference between docs for internal developers vs. external integrators. At this point you're a specialist, not a generalist.

Pricing template

Top 3 client red flags

1. "We'll explain the API on a call." If a client can't share API specs, a Postman collection, or existing internal docs before the call, the API isn't documented yet — and your job just became "figure out what the API does" plus "write about it." Require spec files or documented sample calls before scoping. Verbal explanations become scope disputes.
2. "We need it done in three days." Good API docs require access to engineers. If the client's engineering team isn't available for at minimum 2–3 async questions per week, the docs will be incomplete regardless of how fast you work. Agree on a communication SLA in writing before starting.
3. Vague scope plus unrealistic budget for that scope. The Indie Hackers client-vetting research validated by 50+ freelancers found "unrealistic budget for scope" as one of four top red flags visible before the project starts. 7 A client asking for a complete developer portal with tutorials and reference docs for a $200 budget has either no idea what's involved or has no budget for what's involved.

Sample Fiverr gig description

I'll write clear API documentation your developers will actually use

Bad API docs have a cost: developers build on wrong assumptions, your support queue fills up with questions the docs should have answered, and integrations take twice as long. I write API documentation that removes that friction.

What I cover:

• Getting started guides (authentication, first request, common use cases)
• Endpoint reference docs (parameters, request/response examples, error codes, edge cases)
• Conceptual guides (how the API fits into a developer's workflow)
• Changelogs and migration guides for breaking changes

What's included:

• Docs written directly from your API spec (OpenAPI/Swagger, Postman collection, or direct engineer input)
• Structured in a docs-as-code format (Docusaurus or MkDocs) that your team can maintain in Git
• Tested against your actual API — I run the example requests myself so errors don't slip through
• One revision round based on engineer feedback

What I need from you:

• Your API spec file or a Postman collection (even a partial one)
• Two to three hours of async access to an engineer for questions (Slack or email works)
• Any existing internal notes, even rough ones

I don't write docs from verbal descriptions alone. That produces docs that look right but break on edge cases.

Message me before ordering. Share your spec file and I'll give you a scoping estimate within 24 hours.

Adjacent upgrade path

Data visualization

Demand signal

Rates

Realistic learning path

• 3 days: Complete Microsoft's free Power BI learning path (available on Microsoft Learn) through the "Build your first report" module. Connect a sample dataset. Publish to Power BI Service. This is a working demo you can show clients.
• 4 weeks: Build a multi-page dashboard using a real business dataset (Kaggle has usable public datasets). Include drill-through filters, custom tooltips, and a data model with at least two joined tables. This separates you from people who can follow a tutorial.
• 12 weeks: Add a live data connection (API, SQL database, or SharePoint list). Learn DAX (Power BI's formula language) for calculated measures. Document your data model so a client's team can extend it. At this milestone, you can quote mid-tier dashboard builds without hesitation.

Pricing template

Top 3 client red flags

1. No clean data. Eighty percent of a visualization project is data prep. Clients who present unstructured spreadsheets, inconsistent field names, or data spread across 15 files have not done the prerequisite work. Before scoping, ask to see a sample of the actual data. If it takes more than an hour to understand the structure, factor cleanup time into your quote — or pass.
2. "We just want something like what we saw in that McKinsey report." Clients who show you a competitor's or consultant's dashboard and say "make this" usually have not defined what question the dashboard should answer. A beautiful dashboard that doesn't answer a specific business question is a decoration. Require a written brief that states: what decision does this dashboard inform, and who makes that decision.
3. "Can we just add one more chart?" mid-project. Each additional chart requires understanding its data source, building its model, and testing it against edge cases. Scope creep in dashboards compounds fast. Use the Indie Hackers red-flag framework: if a client showed slow communication during the proposal stage, expect scope requests mid-project. 7 Price every chart addition as a separate line item.

Sample Fiverr gig description

I'll build a Power BI or Tableau dashboard that connects to your live data

Your team has data. They're looking at it in spreadsheets. That means they're making decisions with 2-week-old numbers and no way to filter by region, product line, or time period without rebuilding the spreadsheet. A dashboard fixes that.

What I build:

• Sales dashboards: revenue by region, product, rep, or channel — filterable, real-time
• Operations dashboards: inventory levels, fulfillment rates, support ticket volume
• Financial dashboards: P&L by period, budget vs. actual, cash flow forecasting
• Executive summary views: the four numbers leadership checks every Monday morning

What's included:

• Full dashboard build in Power BI or Tableau (your choice)
• Connected to your live data source (API, database, SharePoint, or Google Sheets)
• Custom color scheme and layout matching your brand
• User documentation so your team can filter and export without calling you
• One revision round based on stakeholder feedback

What I need from you:

• Sample of your actual data (even a partial export is fine)
• The specific business question the dashboard should answer
• Who will use it and what decisions it informs

I don't build demos from fake data. Every dashboard is built and tested against your real data before delivery.

Message me first. Tell me what you're trying to see and I'll tell you in 24 hours what's realistic to build.

Adjacent upgrade path

No-code workflow automation (Zapier / Make / n8n)

Demand signal

Rates

Realistic learning path

• 3 days: Pick one tool — Zapier (easiest UI), Make (more powerful), or n8n (open-source, no per-action fees). Watch two to three YouTube tutorials. Build your first automation: form submission → email notification, or calendar event → Slack message. You now have something to show.
• 4 weeks: Build five to eight automations for different scenarios — CRM updates, report generation, meeting summaries, invoice notifications. Create short Loom videos of each one. A small portfolio of working demos is how early clients find you, not a website.
• 12 weeks: Learn conditional logic (if/then branching), error handling (what happens when a step fails), and multi-step workflows with five or more connected apps. At this level you can scope and price SMB automation contracts. The critical insight from a practitioner who earned $15,000 in five months: "Integration beats innovation every single time. Most businesses don't want an AI revolution. They want their current process to work better without having to learn anything new." 13

Pricing template

Top 3 client red flags

1. "Automate our whole business." Automation works on defined, repeatable processes. A client who can't describe the specific trigger, the specific steps, and the specific output for one workflow has not yet identified what they need automated — and that discovery work takes time you should charge for separately. Require a written process description before scoping any build.
2. "Just use what I currently use." The client's current tools may not have reliable API support or Zapier/Make integrations. Before quoting, check that every app in the workflow has a supported connector. A workflow built on a tool with a broken integration is a support ticket in waiting. Always test a connection with sample data before signing a contract.
3. "Add one more thing" pattern mid-project. The $15K-in-5-months practitioner's core lesson was that automations built to impress collapse when clients add steps their team can't actually operate: "A simple automation they use every day beats a complex one they never touch." 13 Scope every addition as a separate line item with its own delivery date. The middleman problem documented on r/freelance (May 2026) is especially active in automation: watch for clients who can't name the end user or describe who will actually run the workflow after delivery. 14

Sample Fiverr gig description

I'll automate the manual task your team does every day in Zapier, Make, or n8n

You know which task it is. Someone on your team copies data from one tool into another, sends the same email every Friday, or manually updates a spreadsheet that could update itself. I build the automation that eliminates that task — using the tools you already pay for.

What I automate:

• Lead capture: form submission → CRM entry → welcome email → sales team notification (all automatic)
• Reporting: weekly data pull from your analytics tools → formatted report → sent to your inbox every Monday at 9am
• Client onboarding: contract signed → project folder created → kickoff email sent → task list generated
• Invoice workflows: project marked complete → invoice generated → sent to client → payment tracked

What's included:

• Full workflow build in Zapier, Make, or n8n (I'll recommend the best fit for your stack)
• Testing against your actual data before delivery
• Written documentation of what each step does and what breaks it
• 30 days of support for bugs

What I need from you:

• A description of the specific task you want automated (trigger, steps, output)
• Access to the tools involved (view-level access is fine for scoping; build access needed for delivery)
• Confirmation that all tools have the integrations needed (I'll check this during scoping)

I build automations people use every day, not demos that break after one run.

Message me first with the task description. I'll tell you in 24 hours whether it's buildable and what it'll cost.

Adjacent upgrade path