1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
|
<!doctype html>
<html lang="en">
<head>
<meta charset="utf-8">
<meta name="viewport" content="width=device-width, initial-scale=1">
<link rel="icon" href="data:,">
<title>Billing for One CSS Change</title>
<link href="/atom.xml" type="application/atom+xml" rel="alternate" title="Atom feed for blog posts" />
<link href="/rss.xml" type="application/rss+xml" rel="alternate" title="RSS feed for blog posts" />
<style>*{box-sizing:border-box;}body{font-family:sans-serif;line-height:1.33;margin:0 auto;max-width:650px;padding:1rem;}img{max-width:100%;}pre{border:1px solid;overflow:auto;padding:5px;}table{text-align:left;width:100%;}.footnotes{font-size:90%;}</style>
</head>
<nav>
<a href="#menu">Menu ↓</a>
</nav>
<main>
<h1 id="billing-for-one-css-change">Billing for One CSS Change</h1>
<p>2019-11-29</p>
<p>Every second you spend working as a designer should be billed back to the client. A simple button color change? Bill them. Additional links added to an existing menu? Send that invoice over. Some basic typeface changes? Don’t do it for free.</p>
<p>You need to be charging for <em>all</em> design work, regardless of difficulty or time required.</p>
<p>This concept might seem extremely obvious to more senior level workers but I have seen a good amount of junior devs make the mistake of “working for experience” or better yet “strengthening the client relationship”. Early on in my career I was just as guilty of doing this kind of thing. It was and still is a very foolish practice.</p>
<h2 id="do-you-really-bill-for-one-css-change">Do you really bill for <em>one</em> CSS change?</h2>
<p>Absolutely. From the client’s perspective it may seem like they are being billed for one CSS change and 30 seconds of a designer’s time. In reality, they are paying for the designer’s years of experience to be able to solve that problem in <em>only</em> 30 seconds.</p>
<p>Would the client be happier with a significantly less qualified designer charging the same amount of money but taking 3 <em>hours</em> to complete the task? In the end, what’s the difference?</p>
<blockquote>
<p>If it is a simple change that they believe should cost nothing, then why aren’t they doing it themselves?</p>
</blockquote>
<p>We as developers and designers work in an odd industry. A lot of people (read clients) outside of our bubble tend to think they have a much better understanding of the work we do. Because of this, they tend to preface work requests with phrases like:</p>
<ul>
<li>“This should be a simple change”</li>
<li>“This shouldn’t take more than a couple of minutes”</li>
<li>“This seems like an easy fix”</li>
</ul>
<p>Most of the time these comments are harmless, but other times they are a subtle way of downplaying your skill and experience required to complete these work items. That skill and experience shouldn’t ever come free. It makes you wonder if these same people expect free work from trades-people (electricians, plumbers, etc) when they need what they think is a “simple” fix in their house.</p>
<p>Do you think workers in <em>most</em> other industries travel out to someone’s home and fix “small” issues for free? Hell no.</p>
<p>So why are developers and designers doing work for free? I truly don’t know - but it needs to stop.</p>
<h2 id="a-simple-but-useful-system">A simple but useful system</h2>
<p>You should live by the rule that every <em>second</em> you spend working for someone else is billable. I don’t mean that you should literally bill per second, but instead round to nearest estimated time slot (whether you are billing hourly, daily, sprint-based or per project). This ensures that your efforts are paid for and that the client will begin to truly value your time. Doing this from the get-go will save you headaches in the future.</p>
<p>I’m sorry if this comes off as preachy, but I’m just trying to inspire designers to value their work more. Don’t sell yourself short - your talent is valuable and shouldn’t be taken for granted.</p>
<footer role="contentinfo">
<h2>Menu Navigation</h2>
<ul id="menu">
<li><a href="/">Home</a></li>
<li><a href="/projects">Projects</a></li>
<li><a href="/uses">Uses</a></li>
<li><a href="/wiki">Wiki</a></li>
<li><a href="/resume">Resume</a></li>
<li><a href="/colophon">Colophon</a></li>
<li><a href="/now">Now</a></li>
<li><a href="/donate">Donate</a></li>
<li><a href="/atom.xml">RSS</a></li>
<li><a href="#top">↑ Top of the page</a></li>
</ul>
<small>
Built with <a href="https://git.sr.ht/~bt/barf">barf</a>. <br>
Maintained with ♥ for the web. <br>
Proud supporter of <a href="https://usefathom.com/ref/DKHJVX">Fathom</a> & <a href="https://nextdns.io/?from=74d3p3h8">NextDNS</a>. <br>
The content for this site is <a href="https://creativecommons.org/licenses/by-sa/2.0/">CC-BY-SA</a>.<br> The <a href="https://git.sr.ht/~bt/bt.ht">code for this site</a> is <a href="https://git.sr.ht/~bt/bt.ht/tree/master/item/LICENSE">MIT</a>.
</small>
</footer>
|
