1. LandOffer
  2. Blog
  3. All articles
  4. Contently Review for Technical Freelancers: Portfolio-Based Matching and Access to Paid Projects

Job search

Contently Review for Technical Freelancers: Portfolio-Based Matching and Access to Paid Projects

Current public freelancer documentation and two completed original examples separate portfolio approval, relevant clips, client pitches, commissions and received funds.

9 min readLandOffer team

Contently is worth investigating when you already have technical writing samples and want to be considered for brand assignments. A free portfolio begins the process. You still need evidence of approval, an available client route and a specific commission before counting paid work. Decide whether your existing work demonstrates a specific editorial fit and whether you have time to maintain another channel.

This review checked public Contently pages on October 21, 2026. We did not create a portfolio, submit for approval, join a client team, send a pitch, complete an assignment or receive payment. LandOffer publishes this review and offers job-search tools. If employment is also part of your search, keep a separate list of recent tech jobs rather than treating freelance possibilities as job offers.

Technical writing samples move through separate review, invitation and assignment folders.

What the free portfolio actually opens

The public registration page describes a free portfolio and an opportunity to match with brands. It asks for account information and agreement to terms; we stopped before entering anything. That visible registration surface confirms an entry route, not the quality of an authenticated editor or the supply of paid technical projects.

The current freelancer onboarding guide recommends a detailed bio, at least ten projects from three clients, and at least three clips with relevant tags. It now explicitly says review happens only after submission through the Portfolio Submission Form. Once approved and public, a contributor can mark availability; an emailed tutorial and possible client invitation are separate steps.

Those recommendations matter if most of your writing is internal documentation. Ten private runbooks do not become ten publishable clips simply because you wrote them. A reader still needs permission to see the work and an accurate account of your contribution. Do not invent client names or divide one engagement into fictitious clients to satisfy a numerical recommendation.

Contently's visibility policy says unapproved portfolios are private and past approval does not ensure continuing public visibility. Its documented review cadence is Monday mornings, not a promise of acceptance by a particular date. It also directs users with private portfolios back through the current approval process. These are published rules, not settings we tested.

For a deadline tomorrow, an unapproved portfolio is therefore an uncertain sharing route. Keep a separately permitted sample available through a channel you have actually checked. A collection visible only to its owner cannot serve a recruiter or editor merely because its URL looks complete.

Matching depends on relevant evidence

Contently's freelancer overview describes matching portfolios to client needs, including enterprise technology, followed by collaboration on a client team. It also describes crediting payment to the Contently account when work is submitted. These statements explain the intended workflow; they do not reveal today's technical assignment inventory, your selection probability, a typical rate, or how long a particular writer will wait.

Treat matching as an editorial sourcing process. An explanation of database migrations can show command of a topic, but it does not establish experience interviewing customers, reporting a case study or following a brand's sourcing requirements. Give each sample a contribution caption, a topic and a verification boundary so a prospective editor can evaluate the actual writing task.

Before investing in new samples, identify the missing evidence. Is it the ability to explain a system, assess sources, conduct a permitted interview, or organize a reader's decision? Producing another broad article about artificial intelligence may add little if your existing collection already has broad explainers and no evidence of technical verification.

The distinction also keeps your claims credible. Subject familiarity can support a proposed angle without making you a production operator, a product customer or an independent evaluator of a vendor's performance. Those roles require their own evidence.

Worked asset: choose clips for a technical editorial brief

The following is a complete fictional preparation record. Leena is an invented developer writer; Cedar Index is an invented publication, and no client has requested this work. The stipulated editorial need is an explainer for engineering managers evaluating schema changes. It asks for clear failure boundaries and neutral treatment of tools, not a product endorsement.

Candidate sample Stipulated provenance and contribution Completed selection decision
Public migration explainer Leena wrote the prose and created a toy compatibility example; publication permission exists in this fiction Lead clip: demonstrates explanations and explicit limits
Coauthored incident article Leena wrote the compatibility section; another author conducted interviews Supporting clip with that exact contribution stated, not sole authorship
Internal customer runbook Contains nonpublic configuration and no sharing permission Exclude; a renamed customer would not remove all confidential content
Public conference recap Leena attended and summarized talks; no independent system testing Keep in the broader collection, not as proof of migration validation
Unpublished benchmark draft Data provenance unresolved; no repeatable method Exclude until evidence and permission are resolved

The selected lead caption is finished: “I wrote this schema-compatibility explainer and designed the toy example. It illustrates a backward-compatibility failure; it does not report a production deployment or benchmark.” The second caption reads: “Coauthored incident article. I wrote the compatibility analysis; my coauthor conducted the interviews.” Neither caption implies sole ownership of the broader engineering work.

Leena's proposed bio sentence is equally bounded: “Developer writer explaining application and data-system behavior through sourced articles and small reproducible examples.” It avoids an invented employment title, unsupported client logos and claims of business impact. The two selected clips answer this hypothetical editorial need. The remaining collection and client breadth still need an honest inventory; these two samples alone do not satisfy Contently's stated recommendations.

Her completed next decision is to organize existing permitted work first. She will not produce a speculative full article for an unknown brand, expose the internal runbook, or imply the collection has already been approved. A missing third client remains a gap in the preparation record. It is not repaired by counting the same client twice.

A client invitation and a pitch are different commitments

The pitching guide describes direct assignments, client pitch requests and publications that accept open pitches. Its advice is aimed at contributing to clients, not unrestricted access to every brand. A pitch can include an angle, sources, examples, proposed rate and turnaround. Acceptance leads to a story with specifications, word count and pay.

That means a plausible idea is still a proposal. Before doing a full draft, determine whether you have an actual assignment, what the editor expects, and which commercial details remain unresolved. An acknowledgment establishes that an idea reached the client. A commissioned story needs its own specifications and confirmed pay before you plan the full deliverable.

For technical writing, the brief should distinguish a sourced explainer from a hands-on tutorial. The latter may require a documented software version, a safe test environment, an executable example and maintenance expectations. If access or a source interview is unavailable, narrow the promised article rather than claiming you can verify something you cannot inspect.

An invitation can also reveal a poor fit. A writer who can explain a public protocol may not have permission to disclose a former employer's implementation. Ask whether public documentation and a synthetic example meet the requested scope. If they do not, declining that assignment preserves both the confidentiality boundary and the accuracy of your portfolio.

Separate pitch, commissioned story, account balance and received funds records remain distinct.

Worked asset: separate proposed work from received money

This second original asset uses invented writer Omar, invented publication Signal Workshop and explicitly synthetic records. It is a finished decision exercise, not a screenshot of a Contently account, a private brand brief or an observed payment.

Omar prepares this unsent proposal: “For engineering managers evaluating event retention, I propose an explainer separating retention duration from replay correctness. A small synthetic event log will show why keeping data longer does not fix a consumer's missing checkpoint. I will use public documentation and a clearly labeled local example, with no customer data or claim that a particular vendor prevents data loss. The article will close with questions an editor can use to compare assumptions. Proposed scope: 1,100 words, one diagram, two revision rounds, $600, and five working days after a complete brief.”

The price, scope and turnaround are Omar's fictional proposal, not Contently's rate card, standard revision entitlement or delivery promise. His sources are planned, not already interviewed. The first decision is to retain the proposal as unsent until the permitted client route and requirements exist.

Synthetic record What it establishes Completed decision
P1: $600 proposal saved locally An idea and proposed commercial terms No commission and no money counted
P2: client acknowledges the pitch Receipt of the idea only Do not begin the complete article
A1: fictional story specifies $650 and a revised scope Stipulated commission for this exercise Reconcile against A1; do not keep counting P1 as another project
S1: draft submitted against A1 Stipulated delivery record Check the account entry; do not assume external funds arrived
B1: $650 account credit for A1 Stipulated platform balance Record separately from received PayPal funds
C1: cash-out requested; no receipt yet A requested transfer Received funds remain $0 in this snapshot

The independent local check executed for this guide deduplicates all these records to one assignment identifier. It finds $650 of stipulated commissioned value, $650 of stipulated platform credit and $0 of evidenced received funds. Two deliberately wrong interpretations fail in the local fixture: reporting $1,250 by adding the proposed $600 to the commissioned $650, and labeling a cash-out request as $650 received. The check tests only our six synthetic records, not Contently's accounting or a payment integration.

Omar's next action is also complete: keep the missing receipt unresolved and compare the final assignment scope with his delivery record before accepting more work. He does not treat a proposal's quoted amount as income or assume cash-out immediately settles every outstanding obligation. In a real engagement, the actual agreement and transaction evidence would govern the record.

Payment speed has more than one meaning

The cash-out help page distinguishes account activity from a transfer to PayPal. It says transfers are often immediate but may take 24 hours or occasionally several business days, with support advised after more than four business days. It describes cashing out as fee-free for US freelancers; outside the US, payment-provider fees may apply. We did not test a balance, transfer, currency conversion or fee.

That is enough to qualify the registration page's instant-payment language. A credit in a platform account, a cash-out request and funds received externally are different evidence. None of the public pages inspected establishes what a particular technical assignment will pay or whether one will be offered to you.

Keep proposed and confirmed project terms separate in your own records. Include the accepted scope, delivery evidence, revisions still outstanding and payment state. Avoid budgeting a near-term expense against an unaccepted pitch or an assumed brand match.

Contently is a reasonable additional channel for a technical freelancer with permitted, relevant clips and time to maintain them. It is harder to justify as an urgent source of guaranteed assignments or as an automatically public portfolio host. Start with permitted clips and accurate contribution captions. Before adding an assignment to your workload, retain its confirmed scope and payment terms; before recording received funds, retain the separate transaction evidence. Use LandOffer alongside the freelance channel if you are also comparing employed tech roles.

Sources and Further Reading