🚗🏍️ Welcome to Motoshare!

Turning Idle Vehicles into Shared Rides & New Earnings.
Why let your bike or car sit idle when it can earn for you and move someone else forward?

From Idle to Income. From Parked to Purpose.
Earn by Sharing, Ride by Renting.
Where Owners Earn, Riders Move.
Owners Earn. Riders Move. Motoshare Connects.

With Motoshare, every parked vehicle finds a purpose. Partners earn. Renters ride. Everyone wins.

Start Your Journey with Motoshare

Fast, Cheap, Good: A Freelancer’s Primer on Picking Two

New freelancers tend to learn one lesson the hard way: a client will happily ask for a job that is quick, inexpensive and flawless, and a freelancer who says yes to all three will soon be working weekends for free. This primer covers the fast-cheap-good triangle for people who sell DevOps and cloud work on their own. It explains what each corner means for a solo worker, shows how to choose which one to give up, and finishes with a handful of definitions for words clients throw around.

What the triangle means when you are one person

Inside a company the three constraints are shared across many people. As a freelancer they all land on you. Time is your hours. Money is your rate and your client’s budget. Quality is your name, because there is no brand behind you to absorb a bad delivery. That is why the choice matters more at your scale: a single bad project can cost you a referral stream.

The rule is simple. For any given job, you can usually deliver two of these:

  • Fast: done by a tight deadline.
  • Cheap: priced low, either because the client’s budget is small or because you are discounting.
  • Good: reliable, tested and documented enough that it will not break the first week.

The third will suffer. Your job is to decide which one, and to do it on purpose.

Three typical offers and how they play out

The quick, inexpensive fix

A small business owner wants a deployment script by Friday and has a small budget. You can do it: write a simple script, run it once, hand it over. What you are giving up is polish. There will be no monitoring, light documentation and limited error handling. That is acceptable if the client knows. It becomes a problem only if they assume it is production grade.

The careful, inexpensive project

A friend of a friend wants their infrastructure tidied up and has no hurry. You can take your time, fit the work between larger jobs, test properly and write a short handover note at a low rate. What you give up is speed, and the client must accept a start date weeks away.

The quick, careful project

A funded start-up needs a reliable pipeline within days. You can do it, but you will be working intensively and possibly pausing other clients. That calls for a higher rate. Charging more here is not greed; it is the price of the corner you are not allowed to give up.

A practical way to choose

  1. Ask what a failure costs the client. If an outage would lose them sales, quality is protected and you flex price or timing.
  2. Check your own calendar. If you are already full, speed is the expensive corner, so price it accordingly or decline.
  3. Look at the budget honestly. A small budget with a tight deadline means lower quality, and you should say so before starting.
  4. Decide your floor. Know in advance the lowest quality you will put your name on. Below that line, turn the work down.

The floor in the last step is the part new freelancers skip. Without it, every discount slides into work you would rather not be associated with. Newer freelancers often wonder where to start, and the site’s starter FAQ for people entering freelance DevOps pairs well to this article for the other basics.

Words you will hear on client calls

  • Scope: the exact list of things you agreed to deliver. Anything outside it counts as a separate job.
  • Deliverable: something concrete handed over, such as a script, a diagram or a working pipeline.
  • Handover note: a short document that tells the client how to run and fix what you built.
  • Rate card: your standard prices, often with a rush surcharge for tight deadlines.
  • Technical debt: shortcuts that save time now and cost more later. Choosing fast and cheap creates it, so name it.
  • Retainer: a regular monthly arrangement for ongoing small tasks, usually a better home for quality-focused work.
  • Rush fee: an extra charge that pays for the speed corner.

Where outside reading helps

Freelancers work alone, so outside reading often fills the gap a team would normally cover. For operations topics in short, easy language, the CloudOps Now website is one place to look: its home page carries brief entries on cloud operations subjects under the heading of a CloudOps blog. Treat it as a quick read for context rather than a rulebook, and always cross-check anything technical before relying on it for a client.

Handling the awkward conversation

Most beginners dread telling a client that they cannot have everything. It helps to turn the conversation into a menu rather than a refusal. For example: “I can deliver this by Friday at your budget, with basic documentation only. Or I can deliver it in three weeks at your budget with full testing. Or Friday with full testing at a higher price. Which suits you?” The client feels in control, and you have named the trade-off without sounding negative.

A client who still demands all three has told you a lot about what working together will feel like. It is perfectly fine to walk away politely. Freelancers who accept impossible terms usually pay for them later in unpaid revisions.

A note on side work

The same triangle applies when freelancing alongside a full-time job. Your hours are limited, so speed is usually the corner you give up, and your employer’s expectations may restrict what you can take on. Writing about freelancing responsibly next to a regular job covers the practical side, such as managing time and avoiding conflicts of interest.

A worked example with round numbers

Say you normally charge a fixed day rate and a client wants a basic CI pipeline set up for a small web application. Three versions of the job might look like this.

  1. Quick and low-priced: two days, standard rate, one simple pipeline, a half-page note. The client gets something working fast, and you tell them in writing that nobody has load-tested it.
  2. Careful and low-priced: five days spread across three weeks at the same day rate, with tests, rollback steps and a proper handover. The total is higher in absolute terms, but the rate per day has not been discounted, and the long timeline is the corner you ask the client to give up.
  3. Quick and careful: three days, back to back, with a rush uplift on the rate and a clear note that other clients will be moved around.

Presenting the same job as three options takes about twenty minutes to write and often wins the client on its own, because it shows you understand their situation. It also sets a pattern for the relationship: you offer choices, they choose, and nobody is surprised.

Keep a record of what was chosen

Whatever the client picks, confirm it in an email after the call. One short paragraph is enough: which corner was relaxed, what that means in practice, and what the next step is. If a dispute ever arises, the paragraph protects you, and if the client later asks why a feature is thin, you can point to the decision calmly without any defensiveness. Keep these emails in a folder per client. A year later they make an excellent source of examples when you are explaining your approach to a new prospect.

Common beginner mistakes

  • Quoting a low price and promising a fast turnaround at the same time.
  • Letting a client define “good” as “no bugs ever”.
  • Skipping the handover note to save an hour, then spending five hours answering questions later.
  • Treating a favour for a friend as an exception to every rule.

The short version

Every freelance job is a negotiation between speed, price and quality. You will always give up one of them, so give it up deliberately and tell the client early. Keep a quality floor, price speed properly, and use plain language when you explain what you are trading. Do that consistently and you will build a reputation for being straightforward, which is worth far more than being the cheapest or the fastest.

Related Posts

Freelance DevOps Near Misses: A Six-Step Capture Routine

Freelancers have no safety net but themselves. Six practical steps for capturing close calls and converting them into small, tested guards.

Read More

Tidying a Freelance DevOps Practice as You Work: Your Questions

Answers to the questions freelance DevOps engineers ask about keeping client access, files and project debris under control during the work rather than afterwards.

Read More

What a Finished Freelance DevOps Proposal Teaches You

Take a finished four-page freelance DevOps proposal apart, page by page, and pick up the career skills hiding in how it was written and ordered.

Read More

Five Myths About Jargon in DevOps Freelance Proposals

Does technical vocabulary make a freelancer look more capable? Five common beliefs about client writing, tested with plain reasoning.

Read More

A Freelancer’s Constraint Audit: Seven Limits Worth Trying

A storytelling-style checklist for remote DevOps freelancers who want sharper proposals and calmer weeks by choosing a few creative limits on purpose.

Read More

Why Remote DevOps Freelancers Now Keep a Plan B Ready

Remote DevOps freelancing mixes short projects with long retainers. A look at how people prepare a fallback for a client, a lead source and their own energy.

Read More
0 0 votes
Article Rating
Subscribe
Notify of
guest
0 Comments
Oldest
Newest Most Voted
0
Would love your thoughts, please comment.x
()
x