Get paid for the questions and custom requests you already get from followers.

Create your free Brillay link

For creators

Arduino and Electronics Mentors: Get Paid to Debug Circuits and Code

Get paid for the breadboard photos and sketch code followers send you: paid debug questions, scoped ESP32 project plans and a Goal for parts, from one link.

Updated November 2026

Get paid for this — with Brillay

Who got your free breadboard trace last night, off one blurry DM photo? List that trace at your price, and the next schematic and sketch come to you only once the follower has paid.

Brillay is a link in your bio where followers pay you directly for:

Paid QuestionsCustom WorkGoalsTipsPersonalized Videos

A student whose ESP32 browns out the second Wi-Fi connects, science fair on Friday, taps the link in your TikTok bio and pays by card as a guest, so the order is sitting in your inbox when you get home from work.

No monthly fee, you only pay a small platform fee when you get paid.

Most broken projects reach you the same way: a photo of a breadboard, a sketch pasted into a DM, and "it uploads fine but the LED never turns on." Arduino and electronics mentors get paid for that message by selling the diagnosis itself: the pasted code and exact error go into a paid question, the photos and schematic go into a scoped debug. What the maker gets back is the fault, the wire to move and, when the firmware is wrong too, the corrected sketch, at a price you set.

What do makers actually send when a circuit won't work?

If you post Arduino, ESP32, Raspberry Pi or Pico builds, you already know your inbox. The requests repeat, and most of them fall into a few groups:

  • "It compiles but does nothing." The LED, relay module or buzzer stays dead. Half the time the sketch drives pin 13 while the jumper sits in pin 12, or the board is an ESP32 and the code uses Uno pin numbers.
  • Upload failures. avrdude: stk500_recv(): programmer is not responding, the wrong board or port picked in the IDE, a clone Nano that needs the old bootloader option, or an ESP32 that only flashes if the BOOT button is held at the right moment.
  • Resets and reboot loops. "Brownout detector was triggered" on an ESP32 the moment Wi-Fi starts, or an Uno that resets every time the servo moves because the servo is powered from the 5V pin.
  • Sensors that read garbage. An I2C scanner that finds no devices, a DHT22 that returns NaN, an analog value that drifts because two supplies share no common ground, a button that fires on its own because the input floats without a pull-up.
  • Mixed-voltage mistakes. A 5V sensor wired straight into a Raspberry Pi GPIO pin, which runs at 3.3V and is not 5V tolerant, or a level shifter wired with HV and LV swapped.
  • ESP32 gotchas. ADC2 pins that stop reading once Wi-Fi is on, strapping pins (GPIO 0, 2, 12 and 15) that keep the board from booting, GPIO 6 to 11 taken by the flash chip.
  • MicroPython and CircuitPython trouble. OSError: [Errno 19] ENODEV on an I2C call, a main.py that never runs on boot, a driver written for a different port.

The person asking is usually a hobbyist on their first starter kit, a student with a capstone or science-fair demo due, or a maker halfway through a home-automation build. They found your video, they are stuck, and they want one person who understands both the wiring and the code to look at it.

How is this different from a software code review?

A code reviewer reads the repository. You read the repository and the breadboard. The sketch can be perfect while the circuit is wrong: a missing ground between the motor supply and the board, a resistor one row off, an L298N with its enable jumper pulled. And sometimes the wiring is fine and the bug is a delay() that blocks the button read, or Serial.begin(9600) while the monitor listens at 115200 baud.

That is why your offer needs different inputs from a developer's. A developer asks for a repo link and a bug description. You need the board, the power source, what is connected to which pin, and what the serial monitor actually prints. Whether you call yourself an Arduino mentor, an electronics tutor, a maker educator or an IoT instructor, the job is the same: hardware-plus-firmware debugging. If you also sell pure software reviews, the developers page covers that side.

Which offers should an electronics mentor sell?

Two offers carry most of the work, and a third helps pay for your bench.

1. Paid Question: "Why won't my build do this?"

Paid Questions let a follower pay upfront to ask one private question, with up to two follow-ups, and you answer in writing on your own time. This is the right shape for problems that can be described in text: an error message, a pin conflict, which library to use for a sensor, whether an ESP32-C3 can run a project on a coin cell.

Paid Questions are text only in both directions, so your intake note should ask the follower to paste everything into the question:

  • the exact board: Uno R3, Nano clone with a CH340 chip, ESP32 DevKit V1, Pico W, Pi 4
  • the full sketch or script, or at least the part around the problem
  • the exact compiler, upload or runtime error, copied rather than paraphrased
  • a few lines of serial monitor output
  • a wiring list written pin by pin: "DHT22 data to D4, VCC to 5V, GND to GND, 10k pull-up from data to 5V"
  • the power source: laptop USB, a 9V battery, a 2S LiPo, a 12V wall adapter

The two follow-ups suit debugging well. Your first reply often ends with a test: "Put a multimeter across VIN and GND while the servo moves and send me the lowest reading." The follower reports back in a follow-up and you narrow it down. Your first reply arrives inside the window you set (1 to 24 hours, or 1 to 5 days), and each follow-up is answered within 24 hours. More on how Paid Questions work.

2. Custom Work: "Circuit and code debugged from photos"

When you need to see the board, sell it as Custom Work. You set the scope, the price and the delivery time; the follower submits a brief with up to 5 files and pays before you start. A five-item checklist that works:

  1. A sharp photo of the breadboard from directly above, in good light, so every row and column is readable
  2. A second photo at an angle, or a close-up of the module pins and solder joints
  3. The schematic: a KiCad or Fritzing export, or a clear hand-drawn diagram
  4. The sketch or script, pasted into the brief, or saved as a .txt file or shared as a link
  5. A serial log, or a short clip of what happens at power-up

You deliver one package: a written note explaining what is wrong and why, an annotated photo marking which wires to move, and, if the code needed changes, a corrected sketch in the written note, as a .txt file or as a link. Write the scope plainly in the listing: one circuit, one board, one problem. Details on Custom Work.

3. Custom Work: "ESP32 project plan"

The other common request comes before anything is wired: "I want a soil moisture sensor that reports to Home Assistant and lasts a month on batteries. What do I buy and how do I hook it up?" Sell that as a scoped plan. The follower sends the goal, the budget, the parts they already own and their skill level. You deliver a parts list with links, a pin map that avoids the strapping and ADC2 pins, a wiring diagram, a rough deep-sleep power budget, and the libraries to use. If you include a code skeleton, put it in the written note, as a .txt file or as a link.

Keep it to what fits in one order. A plan is a plan; building and debugging the whole system is a different job. When the follower hits a wall during the build, they can order a photo debug for that piece.

4. A Goal for new parts

Many mentors fund their bench out of pocket: a Raspberry Pi 5 for the next IoT series, a logic analyzer, a cheap oscilloscope, a PCB run for an open-source board, or the hours needed to clean up enclosure STL files and release them free. A Goal is one named goal with a progress bar: followers make one-time contributions, every contribution is yours whether or not the goal is reached, there is no deadline unless you set one, and there is nothing to ship. Name it concretely ("Logic analyzer so I can show I2C traffic on screen") and link it under the video that will use it.

Tips and Personalized Videos

Tips let followers send a one-time thank-you with nothing for you to deliver, which suits a free tutorial that saved someone an afternoon of guessing. Personalized Videos fit this trade less often, though a short recorded message for a robotics club or a "your first blink worked" video for a kid with a new starter kit can work if your audience asks for it.

Where should you draw the safety line?

Low-voltage hobby projects only; no mains wiring advice. Put that sentence in every listing and repeat it in replies when a project drifts toward wall power. In practice you help with 3.3V and 5V logic, USB power, battery packs, 12V LED strips and motor supplies. You decline anything that connects to mains: a relay module switching a lamp or a space heater, a modified appliance, a homemade mains power supply. If a Paid Question turns out to involve mains, decline it and tell the follower to bring in a licensed electrician.

Two more lines worth writing into your listings:

  • No guaranteed results. You are diagnosing from photos and text. A cold solder joint or a dead clone board can hide from any photo. Say what you think is wrong, how confident you are and how to test it.
  • Students. You explain the bug and the concept behind it. You never complete graded work for a student or build their assignment for them.

How long should a debug take to deliver?

You choose the delivery or reply time from 1 to 24 hours or 1 to 5 days, and five days is the maximum. There are no milestones and no built-in revision rounds, so scope each offer to fit one delivery.

A setup that works for most mentors:

  • Paid Question: 24 or 48 hours. Most debug questions take 10 to 20 minutes once you have the error and the pin list, and the window covers evenings and a day job.
  • Photo debug: 2 to 3 days.
  • ESP32 or Pi project plan: 4 to 5 days.

For Custom Work, publish a short correction policy, for example: if the fix does not solve the problem described in the brief, send what you measured and I will take one more look. After you deliver, the follower can contact you on the order with a question, a file that will not open or a correction request, and you reply in the same private conversation. For long builds, such as a whole-house sensor network or a custom PCB from schematic to layout, sell one clearly scoped piece at a time: the sensor node, the schematic review, the firmware for one board.

How much should you charge for Arduino debugging?

You set the price. A common starting point:

  • Paid Question: $10 to $25. Price it for the many hobbyists who would never book an hour-long call but would happily pay to stop being stuck tonight.
  • Photo debug: $30 to $60 for one circuit with up to five files.
  • ESP32 or Pi project plan: $60 to $150, depending on how many sensors, whether it needs Wi-Fi or MQTT, and whether you include a code skeleton.

Raise prices when your reply window fills faster than you can answer. Lower the question price if followers keep sending small one-line problems. For a wider view across fields, see how much mentors charge.

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 full breakdown is on the pricing page.

How do electronics mentors get paid today, and what changes?

Most mentors handle these requests one of three ways. They answer in comments and DMs for free, they offer hourly video calls that few hobbyists book, or they send a payment-app request after agreeing on the job in messages. Each has a cost. Free answers eat your evenings. An hourly call overprices a ten-minute pin conflict and means matching time zones with a student on another continent. Payment requests after a DM mean negotiating every job and then waiting for the money.

With a Brillay page, your price, scope and delivery time are published once. The follower taps the link in your bio, reads what you need, sends it with their request, and pays upfront by card as a guest, with no account to create. Followers see the public name you choose, not your legal name. Creators in 41 countries can get paid, and it works from your first follower, so a small channel can take its first paid debug this week. See how it works for the full flow.

I teach IoT and MicroPython. How do I accept support?

If you run a makerspace workshop, an after-school robotics club or a YouTube series on MicroPython, many of the people who learn from you want to give something back without buying anything. Add Tips for that one-time thank-you, and a Goal for what the next lesson needs: "Pico W kits for the spring workshop" or "Raspberry Pi 5 for the Home Assistant series." Then add a Paid Question for learners who get stuck between lessons, so the student who hits ENODEV at 11pm can ask you directly instead of waiting a week for the next class.

How do you start?

  1. Create your page and pick the public name followers will see.
  2. Add a Paid Question with your price, a 24- or 48-hour reply window and an intake note listing what to paste: board, code, exact error, serial output, pin-by-pin wiring, power source.
  3. Add one Custom Work listing for photo debugging, with the five-item checklist and your low-voltage line.
  4. Optionally add a Goal for the next tool on your bench, plus Tips.
  5. Put the link in your bio and pin a comment under your most-asked-about video: "Stuck on this build? Send me your wiring and code here."
  6. The next time a DM arrives with a breadboard photo, reply with the link instead of starting the trace.

Create your free Brillay page and price the next debug before it lands in your DMs.

Frequently asked questions

Can a follower attach breadboard photos to a Paid Question?

No. Paid Questions are written in both directions, so the follower pastes the code, the error, the serial output and a pin-by-pin wiring list. When you need to see the board or the schematic, point them to your photo-debug Custom Work listing, which takes up to 5 files.

What happens if my fix doesn't solve the problem?

For a Paid Question, the follower has up to two follow-ups to report what they measured, and you refine your answer. For Custom Work, your correction policy is shown before they pay, and after delivery they can contact you on the order. Either way, say clearly that there are no guaranteed results from a remote diagnosis.

Can I sell a complete project build?

Not as a single order. The longest delivery time is five days and there are no milestones, so sell scoped pieces: a project plan, one sensor node, one firmware debug. A follower who wants the next step orders it when they get there.

Do I need a big following to start?

No. There is no follower minimum and nothing to apply for. A channel with a few hundred makers who keep asking about your builds is enough to take paid questions.

What does it cost me?

There is no monthly fee or plan to buy. You pay only when a follower pays you, at the rates listed in the pricing section above, with card processing on top.

Will followers see my real name?

No. Followers see the public name you choose on your page, at checkout and on their receipt. Your legal name is used only for identity verification and payouts.

Start getting paid for the questions and requests you already get

Create your free Brillay link. 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.

Create your free Brillay link