Get paid for your expertise through Pro Asks
How to assess a Pro Ask invitation, agree on the work, submit useful feedback and follow your report through evaluation, approval and payment.
Key takeaways
- A Pro Ask invites you to complete defined work, with requirements and payment per approved report stated before you begin.
- Choose work that fits your experience, access and time. A profile or invitation does not guarantee paid work.
- Provide candid feedback with evidence. Payment is for meeting the brief, rather than praising the product.
- The Verifier service evaluates your report. In the current Pro review flow, the asker gives final approval before payment.
- Account payment, cash-out and a public record of approved work are distinct; check their terms and visibility.
On this page10 sections
A Pro Ask is an invitation to contribute your expertise to a defined piece of work. You read the brief, requirements and payment terms before deciding whether to accept. In the current Pro review flow, you submit a report with evidence, the Verifier service evaluates it and the asker gives final approval, releasing payment to your account.
The video shows one pro doing a Pro Ask with Claude, from the invitation email to the payment.
Do a Pro Ask with Claude, 0:31
What's in this video
A pro gets an invitation by email and accepts. They tap Do this with your assistant. Claude tests the page and writes the report with three screenshots. The pro reads it and sends it. The checks pass, the poster approves, and $5.00 is released.
I want Asks to make it easier for people to contribute the knowledge and judgement they have developed through their work and experience. A builder may know how to make software, while you understand the circumstances in which it needs to be useful. Bringing those perspectives together can help the builder make a better product and give you a paid way to contribute.
An invitation can introduce you to a new client. You still need to assess whether the work is suitable, clarify anything uncertain and decide whether the payment is worth the commitment. What is a Pro Ask? explains the arrangement from both sides.
Where your experience adds value
The current Pro review form is structured around software reviews: a product, scenarios to attempt and a report of observations and findings. That can draw on many kinds of expertise, including experience as an intended user.
A qualified accountant reviewing an accounting agent can explain which outputs they would rely on, what needs professional judgement and which assumptions need to be made visible. A host reviewing a property-service dashboard can try scheduling a turnover and explain how the product handles the exceptions they face in practice. A guest brings another perspective on whether arrival or service information is useful and timely.
A designer, developer or QA specialist may contribute a different assessment of the same product. Choose work whose questions match what you know, and explain the perspective you bring. A professional title alone does not make every review in that field a good fit.
The wider Asks model supports other forms of expert work. Use the actual requirements and supported submission format for each ask; the structured software-review flow should not be assumed to accept every kind of professional report.
Make your profile specific
Describe the work you understand, the problems you can help assess and the experience behind that judgement. Include relevant qualifications, tools, languages and availability where they help someone choose you.
The LinkedIn tick means you logged in to the linked LinkedIn account on the date shown. It confirms that account connection. It does not mean Asks has assessed your skills, checked your employment history or verified a professional licence.
Your profile and record help requesters assess fit. They may need to establish additional qualifications for particular work. Keep your availability current so invitations reflect the work you are willing to consider.
A public profile can help requesters discover you. A private profile is hidden from the directory and can be shared through its private link. Creating a profile makes you available for suitable invitations; it does not guarantee their volume or value.
Decide whether to accept the invitation
An invitation gives you terms to consider. Read them before starting and use the private room to resolve questions about access, scope or what counts as completion.
| Check | What to establish |
|---|---|
| Scope | The product, version and scenarios you are being asked to review. |
| Fit | Whether your experience and any required qualifications match the work. |
| Access | Whether you can obtain the test accounts, sample data and tools needed. |
| Requirements | What the report must contain, including evidence and the required submission format. |
| Time | The closing date and the effort needed for both the review and write-up. |
| Payment | The amount per approved report, the evaluation and final approval arrangement, and the funded terms. |
| Visibility | What stays private and what approved work may reveal on your profile. |
Do not assume the presence of a brief means every detail has been settled. If a scenario is unclear or an evidence requirement cannot be met, ask before accepting or beginning. If the work or price is unsuitable, decline.
The reward is funded before the work begins, but funding is not a guarantee that your report will be approved. This is payment for an approved deliverable rather than an hourly engagement. Include preparation, testing, reporting and any tool costs when assessing the commitment.
Write a report that helps someone decide
Follow the published requirements and structure your report so the asker can see which scenarios you attempted and what you established. For the current software-review flow, use its required report format, including evidence, priority or severity, reproduction detail, recommendations and limitations as applicable to each finding.
A useful report distinguishes:
- What you observed. What you tried, what happened and any help you needed.
- Why it matters. The effect on the user or work, from the perspective you bring.
- What you recommend. A concrete change or a further question to investigate, with reasons.
For example, "I could not determine which invoice the agent used for this total" identifies an observation. Explain the records you supplied, the output you received and why an accountant would need a traceable calculation before relying on it. That is more useful than a general instruction to improve accuracy.
Support observations with the evidence appropriate to the brief: a screenshot, recording timestamp, sample input and output, source reference or reproducible sequence. Use test data and keep credentials and unrelated personal information out of the report.
Include what worked well, where the product helped and what you could not assess. Distinguish first-hand experience from suggestions about other users. If you used an AI assistant, check its output and make clear which conclusions come from your own work and judgement, especially where the brief requires them.
Candid feedback is the work
You are contributing an assessment, not promising praise. A critical report can complete the brief as fully as a positive one. If you find no defects in an area, describe what you examined and what that observation does and does not establish.
Do not invent findings to fill a quota. If the brief requires a number of findings you cannot honestly supply, raise that requirement with the asker rather than treating it as a reason to manufacture problems. Agree on expectations before work begins wherever possible.
Understand evaluation and final approval
The Verifier is the service that evaluates the submission against the ask's requirements. A Decision Oracle provides that service, establishing facts from the report and its evidence, with confidence levels. An Expert Decision Oracle brings specialised expertise, using AI with expert skills and qualified human judgement where needed.
The IXO Decision Engine executes the rubric, the agreed evaluation rules, deterministically against those facts. The signed result is the Universal Decision and Impact Determination (UDID). Its signature makes the determination's authorship and integrity verifiable; its conclusion remains specific to the facts and requirements evaluated.
In the current Pro review flow, Asky Pro Checker provides the Verifier service. The asker then gives final approval. A report can therefore pass evaluation and still be waiting for the approval that releases payment.
If your report is not approved, distinguish the stages. An evaluation decision can identify requirements not met; a report awaiting or declined at final approval is a separate matter. Read the decision and status, then ask the requester to explain any outstanding gap against the agreed brief. A report that is not approved is not paid. Do not assume every unpaid report has failed an automated check.
From invitation to account payment
- Receive the invitation. Read the scope, requirements, payment and closing date.
- Choose whether to accept. Clarify questions and confirm that the work fits your expertise and availability.
- Do the review. Attempt the scenarios and document observations, evidence and limitations.
- Submit the report. Use the required format and check that private material is handled appropriately.
- Follow the evaluation and approval. Inspect the result and any outstanding final approval.
- Confirm payment. In the current Pro review flow, final approval releases the agreed payment to your account in the same step. Check the payment record.
What you receive and how to cash out
The listed payment per approved report is what you receive into your account when approved. Under the current fee model, a $100 payment to you requires $125 from the asker: $100 for your work and $25 in network and hosting fees. The fee is 20% of the asker's total funding; it is not deducted again from the $100 payment.
Receiving an account payment and withdrawing it through a payout service are different steps. Check the cash-out options available to your account and country, any identity requirements, limits, fees and the quoted amount before confirming. The cash-out flow provides the applicable terms; do not assume that a route available to another Pro is available to you.
Sandbox rewards are play money. They let you practise the workflow and do not constitute real earnings. For real work, assess what remains after your own time and costs rather than treating the gross payment as profit.
Build a record while protecting client work
Approved Pro work can appear on your profile with its title, month and amount. The report and supporting files stay restricted to you, the asker and the evaluation service under the workflow's access rules.
A title can itself reveal something about a client or project. Check what will be visible and resolve confidentiality expectations before starting; do not assume that omitting the report makes every public detail suitable to share.
A private profile lets you choose whom to give its link to. Anyone with the link may be able to open it, so share it deliberately. The profile's visibility and permission to publish a client's report or quote are separate questions.
A review can also introduce you to a product you might use or a builder you would like to work with again. Follow up if that interests you. Buying the product, recommending it or writing a public customer review is a separate choice from completing the paid report. Agree on permission and wording before any private feedback is quoted publicly, with the paid review context made clear.
FAQ
How much can I earn from Pro Asks?
The asker sets the payment per approved report, and you see it before accepting. Your actual earnings depend on suitable invitations, accepted work, approval and the time and costs involved. A profile alone does not guarantee income.
Do I need to find my own clients?
Requesters can discover your profile and invite you to defined work. You can also share your profile with people who may need your expertise. Invitations can reduce the work of finding an engagement, but you still need to assess its terms and fit.
What happens if my report passes evaluation but is not yet paid?
It may still require the asker's final approval. Check the report's status and the payment record, and ask about any outstanding requirement. Passing the Verifier evaluation and receiving final approval are distinct stages.
Does the LinkedIn tick verify my expertise?
It confirms the LinkedIn account connection on the date shown. Describe your experience accurately and establish any additional credentials required for the work.
Can I give negative feedback and still be paid?
Candid criticism can meet the agreed requirements. The paid deliverable is the review work and evidence, rather than a positive endorsement. Clarify that expectation before beginning if the brief is ambiguous.
Will my report be public?
The report remains private under the Pro review workflow. Approved work can appear on your profile with its title, month and amount. Check those details and your profile visibility before accepting confidential work.
Put your expertise to work
Start at Asks for Pros and create a profile that explains the contribution you can make. Choose suitable invitations, ask clear questions before starting and deliver feedback grounded in your experience. Each completed engagement can give another builder a useful result and give you a record of that contribution.