First-time-user walkthrough
One linear customer workflow, one user type, and one clearly defined result.
For one customer-facing SaaS workflow
Give users a help article that shows exactly what to do.
One publish-ready, step-by-step help article with up to four annotated screenshots, prerequisites, the expected result, and basic troubleshooting. Delivered in three business days.
3 business daysafter complete inputs
One workflowone user type and outcome
Visual stepsup to four annotated screenshots
One revisionaccuracy and terminology
One workflow.
One useful article.
The pilot is for the awkward gap after launch: the feature works, but a first-time user still has to guess where to click and Support has no clear guide to send.
Annotated screenshots
Up to four screenshots that point to the controls and choices described in the steps.
CMS-ready article
Up to 800 words in Google Docs or Markdown, including prerequisites, steps, result, and basic troubleshooting.
Read the work
before you buy.
The current sample is a clearly disclosed synthetic B2B SaaS example. It shows the writing, structure, troubleshooting, and factual QA used in the smaller paid pilot.
RelayBoard guest workspaces
A synthetic release for a project-collaboration product. The linked article is the closest example of the paid pilot; the extra files show broader documentation capability.
Share a workspace with an external guest
Invite a client or partner to one workspace without adding them to your full organization.
- Open the workspace you want to share.
- Select Share, then Invite guest.
- Enter the guest's email and choose Viewer or Commenter.
- Select Send invite.
Every product fact maps to a release note, product page, screenshot, or buyer-confirmation flag.
A small scope
from start to finish.
The workflow must be reproducible from a free tier, demo invite, Loom recording, or approved screenshots. Production access and customer data are never required.
Scope
Send one workflow, the intended user, your current docs style, and a demo, Loom, or approved screenshots.
Confirm
Receive a written fit/no-fit answer, exact boundary, delivery date, and payment route.
Deliver
Get the article and annotated screenshots in Google Docs or Markdown within three business days.
Revise
Send one consolidated accuracy and terminology revision within five calendar days.
Built for a narrow,
safe first job.
Clear exclusions keep the $149 pilot useful and commercially realistic. The buyer owns factual approval and publication.
Good fit
- One linear customer-facing B2B SaaS workflow
- One user type and one intended result
- An existing help-center style to match
- Free tier, demo invite, Loom, or approved screenshots
Not included
- API, security, compliance, medical, legal, or financial docs
- Credentials, production access, or customer-ticket data
- CMS publishing, translation, strategy, or SEO promises
- Video production, branching workflows, or unlimited revisions
One visual help article.
$149 flat.
Send the workflow and the source material you already have. You will receive a written fit/no-fit answer, exact scope, delivery date, and the available payment route. Direct orders are accepted only after the payment, receipt, payout, and refund path is confirmed in writing.
Channel boundary
Clients who find Polina on Upwork contract, message, pay, and receive delivery only through Upwork. Direct payment is requested only after the buyer's payment route has been verified.
Clients who find Polina on Upwork contract, message, pay, and receive delivery only through Upwork. Direct payment is requested only after the buyer's payment route has been verified.