Salesforce admins get paid online for the flow errors, report gaps and certification questions people send them by selling the fix itself, not an hour of their time and not access to anyone's org. An ops manager pastes the exact error text and pays upfront for a written answer as a Paid Question, with up to two follow-ups, and a career changer asks which exam to sit next the same way. When a small company needs something made, such as an org health review or one record-triggered flow, they brief it as Custom Work with screenshots or a Developer sandbox, never a production login, and you deliver build notes and a package they install themselves. You set every price and every reply or delivery time.
Who actually pays a Salesforce admin for help?
Two kinds of people, and they want different things.
Small companies. A 12-person agency on Professional Edition, a nonprofit on Nonprofit Cloud or the older NPSP, a sales team whose original consultant left two years ago. The person messaging you is usually an "accidental admin": an ops manager who got the System Administrator profile because nobody else wanted it. They want one broken thing working by Monday: the flow that stopped firing, the dashboard with the wrong totals, the validation rule that blocks lead conversion. They can't justify a consulting partner's minimum engagement for that, but they can pay for one answer.
Aspiring admins. Career changers, recent grads and people moving over from support or sales ops. They're deep in Trailhead, studying for the Admin exam, and want advice from someone who has the job: which certification next, which superbadge proves anything, how to get experience without a job, and whether their resume reads like an admin's.
Both groups already find you through LinkedIn posts, Trailblazer Community answers and local user group talks. The only change is that the question now arrives paid instead of as a favor.
Which Salesforce questions sell well as Paid Questions?
A Paid Question is one private question answered in writing, with up to two follow-ups. You choose the reply time: 1β24 hours or 1β5 days. There's no call and no screen share, which suits admin work: the answer is usually a paragraph and a path through Setup, not an hour of watching someone click.
These sell because the buyer is stuck and the fix is specific:
- Flows that behave differently for different users. "My screen flow works for me but errors for the sales team." Screen flows run in user context by default, so it's usually field-level security, object permissions, or the "How to Run the Flow" setting.
- Governor limit errors. "My flow fails with Too many SOQL queries: 101." Almost always a Get Records or Update Records element sitting inside a loop.
- Entry conditions. "It fires on every edit." The fix is often switching to "Only when a record is updated to meet the condition requirements."
- Before-save vs after-save. "Fast Field Updates, or Actions and Related Records?" A short question, but the answer decides whether the build holds up.
- Migration order. "We still have six Process Builders and a pile of Workflow Rules. What do I move first, and can I trust the Migrate to Flow tool?" The Flow Trigger Explorer view for one object often answers it.
- Validation rule bypasses. "How do I let the integration user skip this rule?" The answer covers ISCHANGED, PRIORVALUE and a custom permission checked in the formula.
- Reports and visibility. "The field I need isn't in the report" (usually a custom report type or a cross filter), or "Why can this rep see every account?" (org-wide defaults, role hierarchy, sharing rules, and profile vs permission set group).
Career questions work just as well: "Admin exam first, or Platform App Builder?", "I have 140 badges and two superbadges and still no interviews. What's missing?", or "I'm a support rep at a company on Salesforce. How do I move into the admin role internally?"
Your Paid Question has one price and one reply time, so decide who it's mainly for: the company that needs a flow unblocked this week, or the career changer with one study question. If longer career asks pile up, publish a career review as Custom Work.
A Paid Question description you can paste
"Send one Salesforce question: a flow, validation rule, report or permissions problem, or one career question. Include your edition, the object, what should trigger the automation, what happens instead, and the exact error text with record IDs and names replaced by placeholders. You'll get a written answer with the steps to fix it in Setup, plus up to two follow-ups. Never share production credentials or customer data; use screenshots or a sandbox."
A Paid Question is text only in both directions, so a well-described question is the one you can answer the first time.
What Custom Work makes sense for a small company's org?
Use Custom Work when the result is a deliverable, not an answer. You publish a title, what the buyer gets, what you need, what's excluded, a price and a delivery time of up to five days. The buyer sends a brief and up to 5 files and pays before you start. You deliver a written note, up to 5 files and/or links, which can include a screen recording of up to 20 minutes.
Four offers fit admins especially well.
Org health review. Here is a full listing you can adapt:
- Title: Salesforce org health review (one org)
- What you get: A written report covering the Security Health Check score and its top risks, profiles or permission sets with Modify All Data or View All Data that shouldn't have it, record-triggered flows that overlap on the same object, Process Builders and Workflow Rules still active, unused custom fields, and report folders shared too widely, ranked by what to fix first.
- What I need from you: A Health Check screenshot, a list of active automations, a screenshot of your org-wide defaults, and recent Setup Audit Trail entries exported as a file with user names removed.
- What's excluded: Making the changes, Apex review, and any login to your production org.
- Delivery time: 5 days.
One flow built to spec. The buyer describes the business rule: "When an Opportunity hits Closed Won, create an onboarding Case and assign it by region." You build it in your own free Developer Edition org and deliver an unmanaged package link or the metadata files, with build notes and a short recording. They install it in a sandbox, test it and deploy it themselves. Exclude Apex, production deployment and changes to other automations on the same object.
Report and dashboard pack. One custom report type, up to five reports and one dashboard, delivered as a written spec with screenshots of each filter, grouping and summary formula. Sales managers ask for this constantly, and it's easy to scope.
Aspiring-admin career review. The buyer sends a resume PDF, their Trailhead profile link, the job posting they want and their questions. You return written notes on which certification to sit next, which superbadge to do, and how to describe projects in admin language ("built a screen flow that cut case intake from six fields to three"). If they mostly want resume line edits, the career coaches page covers that kind of review.
What should buyers send, and what should they never send?
Put this rule in every offer description and every Custom Work "what I need" field, word for word: Never share production credentials or customer data; use screenshots or a sandbox.
In practice:
- Error text goes into a Paid Question with record IDs and names swapped for placeholders like "Account A."
- Screenshots should show setup, not records: Flow Builder, the validation rule editor, the report builder, a permission set's object settings. If a list view or record page appears, names, emails, phone numbers and amounts get blurred first.
- A sandbox is only safe if it's the right type. Developer and Developer Pro sandboxes copy metadata only; Partial Copy and Full sandboxes copy real customer records, so they don't count. If a Custom Work order needs you inside an org, the buyer creates a Developer sandbox, adds you as a user under your own email, and deactivates that user when you're done. You never need their password.
- Your own Developer Edition org is where you build and test anything you deliver.
Write in your "what's excluded" field that you won't log into a production org, and decline any brief that contains a production login or a customer export. The IT-minded people who buy this kind of help trust you more for it.
How much should a Salesforce admin charge for questions and builds?
You set the price. Admin work sits well above template builds because it touches the system a company runs its pipeline or donations on, so price for what a wrong answer would cost the buyer, not for the minutes you spend.
Common starting points:
- Paid Question on a flow, validation rule, report or permission: $75β$150, toward the top with a 24-hour reply time.
- Aspiring-admin career review (Custom Work): $120β$250, delivered in a few days.
- One flow built to spec: $250β$500 for a single record-triggered or screen flow, more if it spans several objects.
- Org health review: $300β$600, depending on org size and how many automations you'll go through.
If most of your askers are career changers rather than companies, set your Paid Question lower, around $30β$60, and sell company fixes as Custom Work. None of this is a promise of income: your first orders will show you which questions take ten minutes and which take an evening, and you adjust from there.
What it costs you: No monthly fee, you only pay a small platform fee when you get paid. 8% platform fee when a follower pays for work, 5% platform fee on tips and goals. Card processing is separate. The details are on the pricing page.
How do you fit a bigger Salesforce project into one order?
Each order has one delivery time, five days at most, with no milestones and no built-in revision rounds. A CPQ rollout, a full migration off Process Builder or a new org from scratch won't fit, so sell a clearly scoped piece:
- the automation inventory before a migration, not the migration
- security for one object or one permission set group, not the whole sharing model
- one flow per order
- one department's dashboard, not all of them
If the buyer wants the next piece, they place another order. Also publish a short correction policy, for example: "If the delivered flow doesn't match the spec in your brief, I'll fix it once." Buyers see it before paying, and after a Custom Work delivery they can raise a correction in the order's support conversation.
Should a Salesforce admin add Tips, Goals or Personalized Videos?
Tips suit admins who post free "admin tip of the week" carousels or flow walkthroughs: someone your post saved an afternoon sends a one-time thank-you, and you owe nothing back.
Goals work for one named target with a progress bar, such as "Fund my Application Architect exams." Every contribution is yours whether or not the goal is reached, there's no deadline unless you set one, and nothing to ship.
Personalized Videos are the weakest fit, unless you run a study group and want to record a congratulations for members who pass the Admin exam.
If AppExchange vendors or consulting partners want you to post about their product, a Brand Collaboration Inquiries form collects their budget, timeline and deliverables in a separate brand inbox.
HubSpot consultants: how do clients buy a one-off portal audit?
Your buyers are small B2B companies, often a marketing lead and a sales lead who disagree about what a lifecycle stage means. They ask why a workflow enrolled the wrong contacts, how to stop duplicate deals, and why form submissions don't associate with the right company.
- HubSpot portal audit (Custom Work). Property clutter, lifecycle stage and lead status logic, deal pipelines, active workflows with their enrollment triggers, and sequences. The brief includes screenshots of the workflow list and pipeline settings, plus an export of property definitions (properties, not contacts).
- Workflow build (Custom Work). You build it in a developer test account, or in a sandbox account if the buyer is on Enterprise, and deliver a step-by-step spec with screenshots and a recording their team copies into the live portal.
Never share production credentials or customer data; use screenshots or a sandbox. Don't accept a super admin login to a live portal.
NetSuite consultants: how can people pay you for one question?
Your buyers are controllers, accounting managers and ops leads, and their questions are precise enough to sell one at a time.
- Workflow question answered (Paid Question). "Why does my SuiteFlow approval skip the second approver on vendor bills over $10,000?" The buyer describes the states, transitions and conditions in words.
- Saved search built (Custom Work). Criteria and Results tabs, summary types, formula columns such as a CASE WHEN in Formula (Text), and highlighting rules, delivered as a field-by-field spec with screenshots so the buyer rebuilds it in their account.
Never share production credentials or customer data; use screenshots or a sandbox. NetSuite sandboxes are usually copies of production with real financials, so ask for screenshots of the search definition, not its results.
Workday consultants: how can people pay you for quick questions?
Your buyers are HRIS analysts and HR operations teams at mid-size companies. A second group asks how to get into Workday at all: certification normally comes through a partner or customer sponsor, so "how do I get certified without one?" is one of the most common career questions you'll see.
- Calculated field question answered (Paid Question). "Lookup Related Value or Extract Multi-Instance for the worker's most recent promotion date?"
- Custom report built to spec (Custom Work). An Advanced, Matrix or Composite report with its data source, filters, prompts and calculated fields written out.
HR data is the most sensitive data on this page. Never share production credentials or customer data; use screenshots or a sandbox. For Workday that means no worker names, IDs, compensation or Social Security numbers, in a question or a screenshot.
SharePoint consultants: how do you sell a site plan or permissions help?
Your buyers are office managers and IT generalists at small businesses moving off a shared drive into Microsoft 365. They ask about folders vs metadata columns, team sites vs communication sites, and why a whole client folder ended up shared through an "Anyone" link.
- SharePoint site structure plan (Custom Work). The buyer sends the current folder tree (names only), teams by role, and screenshots of the site permissions and "Manage access" panels. You deliver the hub and site layout, document libraries, metadata columns and which Microsoft 365 group owns what.
- Permissions question answered (Paid Question). "We broke inheritance on twenty folders. How do we get back to group-based permissions?"
Never share production credentials or customer data; use screenshots or a sandbox. That means no global admin or site-owner login, and never the documents themselves.
Jira admins: how do engineering managers buy workflow help?
Your buyers are engineering managers and Scrum masters who inherited a messy Jira site. They ask about company-managed vs team-managed projects, statuses nobody uses, transitions that need a validator, and automation rules that loop.
- Jira workflow configuration answered (Paid Question). "How do I require a resolution only on the Done transition?" The buyer lists statuses and transitions in words.
- Board and JQL filter setup (Custom Work). The JQL for each board, swimlanes, quick filters and the column-to-status mapping, tested on a free Jira Cloud site with sample issues.
Never share production credentials or customer data; use screenshots or a sandbox. Screenshots of the workflow editor or board settings with issue titles redacted are enough.
Power Apps and Power Automate developers: what fits in one order?
Your buyers run Microsoft 365 and want a SharePoint list to stop being a manual process. They ask why an "Apply to each" loop runs a thousand times, how to format dates with formatDateTime, why their app shows a delegation warning, and whether a connector needs a premium license.
- Power Automate flow (Custom Work). For example, an approval flow triggered when a SharePoint item is created, delivered as an exported package or solution file.
- Simple Power App (Custom Work). One canvas app over one SharePoint list, built with test data in your free developer environment. Exclude Dataverse and premium connectors unless the buyer confirms their licensing.
Never share production credentials or customer data; use screenshots or a sandbox. You build in your own environment; the buyer imports the package and sets up the connections.
How do you start selling Salesforce help this week?
- Create your page and choose the public name buyers will see. It doesn't have to be your legal name.
- Add your Paid Question with a price, a reply time and the description above. The Paid Questions overview shows how it works.
- Add one Custom Work listing, such as the org health review. See the Custom Work overview, or how it works for the whole flow.
- Put the link in your LinkedIn Featured section and your Trailblazer profile. The next time someone DMs a flow error, reply with the link instead of the fix.
It works from your first follower, with nothing to apply for. Creators in 41 countries can get paid, and followers pay by card from anywhere. If Apex and trigger questions start arriving, the developers page covers code review. When you're ready, start your Brillay page.
Frequently asked questions
Can I answer a Salesforce question without logging into the org?
Usually, yes. Most flow, validation rule and permissions problems can be solved from the pasted error text and a written description of the object, trigger and entry conditions. If you really need to look around, sell it as Custom Work and ask for a Developer sandbox with a user created under your email.
Is it OK to sell admin help while I work full time as a Salesforce admin?
Check your employment agreement for outside-work and conflict-of-interest clauses. Never use your employer's org, time or data for paid answers, and build and test everything in your own Developer Edition org.
What does Brillay cost a Salesforce admin?
Nothing monthly. You pay a small platform fee only on orders that are actually paid, at the rates in the pricing section above, and card processing is separate.
Do buyers need an account to pay me?
No. A buyer pays by card as a guest on your page, so an ops manager can pay for one answer without creating yet another login.
What if a buyer sends customer data or a production login anyway?
Don't use it. Ask them to resend: in a Paid Question, the error with placeholders; in a Custom Work brief, redacted screenshots or a Developer sandbox. Decline the order if they can't. Stating the rule in every offer makes this rare.
Explore more