Getting Paid

If people have started asking you to set this up for them, this page is the fork: what the work actually is, what to charge, how to find the first person, and how to deliver without it eating your life.

Being good with these tools and getting paid to use them are two different skills. Plenty of people are excellent at the first and never touch the second, and that's a completely fine place to stop. But if the requests have started coming, it helps to know what you're actually being asked to do, because it's rarely what beginners think.

1. What people actually pay for

Beginners chase flashy, complicated setups. People with a real problem pay for a boring, painful bottleneck getting cleared. The valuable work is almost always taking something repetitive that a person is doing by hand right now and making it stop hurting:

• Onboarding and intake. The manual scramble every time a new client, student, or member signs up: forms, welcome messages, adding them to systems. Handle most of it automatically and you give someone hours back every week.
• Sorting and following up on messages. Inbound emails, DMs, and form submissions that get triaged, answered, and nudged along, instead of sitting unread for two days.
• Routine communication. Reminders, status updates, review requests, rebooking nudges: the messages someone currently types out one at a time.
• A steady stream of writing. On-voice posts, newsletters, and updates produced reliably instead of being skipped or dreaded.

Your edge is the world you already know. If you've spent years around a particular kind of work, a trade, a field, a hobby with a community around it, you can name its bottlenecks before the person finishes describing them, because they were your bottlenecks too. An outside consultant has to guess at that. You don't.

2. What to charge

The beginner's instinct is to charge by the hour. Don't. Hourly pricing punishes you for getting faster and caps what you can earn. Price against the value you create instead.

Tie the price to what it saves

Work out roughly what your solution saves the person over a year, in hours, in money, in headache, then charge a small fraction of that. If a manual job is quietly costing someone a great deal of wasted time, a one-off build that removes it is an easy yes, because they come out ahead many times over. You're not expensive; you're a bargain, and the arithmetic makes the case for you. The key is that the saving is their real number, drawn from their actual costs, not one you made up.

Retainers, for ongoing work

One-off builds are how you start; recurring monthly work is how it becomes steady. A modest flat monthly fee to keep a system running, fixing what breaks, small tweaks, updates, turns a single project into a relationship. Keep the fee proportional to the original build and to how much upkeep it genuinely needs. Don't quote figures you can't stand behind; price it to the actual work.

3. Landing the first person

Do not start by blasting cold messages to strangers. It makes you look like every other template salesperson, and it doesn't work for beginners. You have something better: real relationships and real credibility in a field you know. Use them.

The warm loop (about a week)

1. Write your one-line hypothesis. "I help [kind of person] with the repetitive admin that eats their week." It'll change over time, and that's fine.
2. List about twenty people you already know in or near that world: friends, peers, people two steps removed. Warm, not cold.
3. Have low-pressure conversations with no intent to sell. "I'm learning to automate boring, repetitive work with these tools. Can I ask what feels most manual in your day?" People are glad to talk about their own headaches.
4. Offer one free pilot. Pick the most obviously-manual bottleneck you heard, and fix that one thing for free: "Let me build you a small version of this. All I ask is honest feedback." No risk to them, real proof for you.
5. Deliver, then deepen. Hand it over. If it worked, offer a small next step: a modest retainer, or a paid expansion. If they're not ready, ask for a short testimonial and who else they know. Either way you come out ahead.

4. Delivering without drowning

Landing the work is half of it. Delivering cleanly, without endless unpaid "can you also just..." requests, is the other half. A little discipline keeps you sane.

• Diagnose first: listen, repeat, poke. Listen to how they actually work, repeat the workflow back to check you understood, and poke with specific questions to put real numbers on the pain: "How long does that take? Who does it? How often?" Those numbers become your price.
• Write a tight scope before you build. One page: what you're delivering, what's not included, the timeline, what you need from them, and a clear "definition of done." This single habit prevents almost all the misery of a project that never ends.
• Test it hard before they see it. Run the thing yourself for a few days with real examples they give you. Fix the rough edges in private, so what they see just works. This is the reliability people are actually paying for.
• Hand it over so they own it. They should own their own accounts and pay their own tool costs directly. You set it up, but it's theirs. Share any passwords through a secure tool, not a text. Then give them a short screen-recorded walkthrough of how it works and what to do if something breaks.

5. Turning one job into a habit

The trap is rebuilding everything from scratch every time. Make your wins compound instead:

1. Stay in one world. Same kind of person, same repeating problems. Depth beats breadth.
2. Harden your template. Watch your first build run in the real world. Every time something breaks, add a guardrail. Your fragile first version slowly becomes a solid, reusable one.
3. Save your steps as reusable recipes. Write the process down once, so the next similar job takes a fraction of the time. (Coding tools call these "skills," see the Coding Agents page.)

Do it for yourself, do it once for someone else, then turn that into a repeatable thing for a world you already understand better than any outside consultant could. It only works if you keep being the person who delivers something that runs, which, in a market full of people selling talk, is rarer than it sounds.