Over the past few weeks, we’ve covered:

• Common blind spots for independent software

• Home page issues & how to address them

• Baseline design for pricing pages

• Operational issues when designing as an independent developer

And now it’s time to cover our final lesson in this mini-course, which discusses what to do first.

There is the noise outside, and then there is the inner voice telling everything to shut up. We wrote about this recently, telling designers to stay in their lane, focus on the practice, and generate revenue the only way we know how.

This has turned out to be correct. 95% of recent projects fail. A new model comes out; the collective reaction is akin to a deflating balloon.

I can’t blame anyone for not believing the skeptics, though. This cycle was loud. It really did feel like the future for a minute there – maybe by sheer force of will, but it was there. There were moments when even I doubted whether my practice would continue to be relevant.

It turns out that making money is relevant.

In the past few lessons, we’ve talked about blind spots, your home page, and your pricing. But there’s a lot more, of course – like your actual product.

I care less about the final design of your product and far more about the operations that go into its maintenance. Making an amazing comp does not result in good design. High-quality operations result in good design.

And so instead of a lesson about how to teach you taste or aesthetics or even how to research, we’re starting with the bedrock of any good design process. A culture that accepts design is more likely to design well. A system that puts design at the forefront is more likely to remember design when building.

Anyone can design. You design. Every decision you make is a form of design. The goal is not to learn design. It’s to make better decisions.

One of the fun things about serving software again is that I feel like I’m working in a startup. I mean this less in terms of the economic conditions of the business and more in terms of process:

• Prototype fidelity (low, fast)
• Layers of approval (none, do what you can do)
• Process (push fast, QA/test, adapt)
• Consensus & critique (this looks good & I have notes)

Which is especially interesting as a designer. It’s always been the case that the actual design I’m doing matters less than whether & how it ships, but with such a fast turnaround cycle and so few layers of approval, you really can do quite a lot more.

If you’ve been reading these letters for over 6 years or so, you know that I once wrote a lot about how designers will code, and that learning code is how you create higher-quality design. Now the roles have flipped, and I think a lot more about how developers will learn the basic principles of design. Ultimately we’re all making design decisions, and in independent software businesses, many decisions will be made outside of a designer’s influence.

Now that we’ve chatted about some of the biggest challenges facing your business’s home page, we turn to pricing. In this paid lesson, we’ll talk about the specific elements of a pricing page, and how to get to a solid baseline with each of them.

We’re embarking on a small, private research project here at Draft – focused on independent software, of course. Here are the steps behind what we’re doing and what we hope to get from it.

1. Map the market

The short-term goal is to map our addressable market. Who will we offer to serve? In what specific ways are they in need of value-based design?

We’re figuring this out by going to a handful of watering holes & indices, and pulling down every independent business that makes more than $600k and less than $15M (more than that and they’d probably just hire us for a workshop).

Hi! We’re gathering some more topics to chat about over the next few months – and that’s where you come in.

Got any questions about practicing value-based design for independent software businesses? Hit reply and let us know. If we answer yours, we’ll give you a free membership for a month.

Thanks again for your support, and we look forward to hearing from you!

Continuing from last week’s lesson about some of the blind spots that people experience in independent software, we’re now going to move through the most load-bearing parts of your business.

In this paid lesson, we’ll talk about the four biggest parts of your home page, and what you should do instead.

One more note about staying in your lane, building off of last week’s letter.

Recent technological developments have largely occurred because of the growth imperative. We had a big success, then another big success, then a little success, and along the way a bunch of other successes that have rewritten the way that society works now. Then we ran out of ideas for a bit, and so what fills the void? Moreover, what happens when the answer to that question is forced onto customers who don’t actually want it, and are asking for something else?

There will, of course, be a quieter rebellion against that form of technology, and it will come faster than you think. People try to do stuff they like. People seek ease & convenience. And they’re smarter than you think.

In this monthlong course, we’re going to teach you about everything we’ve learned when designing for independent software businesses.

This isn’t a “design for developers” course. There are plenty of those, and learning aesthetics only gets you so far. Instead, we’re going to talk about the real-world issues that independent software businesses face at various stages of growth.

You’ll come out understanding some of the biggest things that people mess up, and you’ll learn both why and what to do about it.

Our first lesson is going to focus on some of the more unintuitive principles or blind spots that we tend to encounter.

Our final office hours for paid members is today! Join us at 1p Central Time to chat about all things value-based design. Happy to answer any questions or pressing issues you may currently have. Find out what 1p Central Time is in your time zone here.

If you’re a paid member, our meeting link is at the end of this email. If you sign up between now and 1p, we’ll send the meeting link your way. Moving forward, we’re offering 30 minute 1:1 sessions for new members. Book your 1:1 here.

Returning back to design for software this week.

First, our final office hours for paid members is coming up! Join us on **Tuesday, August 5 ** to ask me anything about value-based design & getting an impact with your work. These vary in attendance from 1 to 10 people, and they’re always helpful for you and for me. August office hours link after the jump!

We’re offering free half-hour calls to new members going forward. Easier than our previous hours, and more value for you. Current members can book a half-hour call with me, too – link’s at the bottom of this letter.

Now that we’ve established that you’ll be posting price, let’s talk about what prices and how. In this paid lesson, we’ll talk about pricing tiers: why they’re important, and how you should create them.

There is much noise right now. I just spent a month discussing it. How do value-based designers stay in our lane and continue to generate outsize impact for our clients?

Your goal now is to find businesses that perceive business like normal people. The rules have not changed and will not change. Here, for those in the back, are the rules:

• A business exists to serve its customers, not the other way around.
• A business needs to make more than it spends in order to survive.
• A sustainable, durable business makes its money directly from its customers – not from investors or shareholders.

That’s it. Those are the rules.

In software businesses, we post price. We post price in almost all circumstances. We post price for B2C, we post price for B2B. We post price.

In this lesson, we’ll discuss why we post price, why you will post price, and what it means for businesses to post price.

Two brief updates to membership:

• We changed billing systems the other week. Our thanks to those who signed up after the change and called out a bunch of old cobwebs that we forgot to clean up. If you were on the old system, we sent you an email that you have a couple of weeks to switch over; we’ll be turning that one off on August 01.
• We’re offering free half-hour calls to new members going forward. Easier than our previous hours, and more value for you.

Now would be a great time to join us as a member, especially if you work in software. We’ve got a lot of great lessons planned over the coming months.

It used to be that you would build something and people would use it. But it’s not enough to just make a tool that works anymore. That’s where positioning comes in, or the process of making your product stand out in a competitive market.

In this paid lesson, we’ll be going deep on how to apply a simple positioning to independent software businesses. If you’ve never gone through this exercise before, start here.

Over the past two weeks, we talked a little about the high-level view of post-LLM design and how buyers view design now. Apparently “the nickd take on LLM” resonates, since all of my opinions are universally correct and many of you are wondering how to move going forward.

I’m going to write a little more today and a little next week, and then we’ll get back to our regular programming, because (despite what you may have heard) there’s quite a bit more to value-based design than how we respond to LLM. In the meantime, I might package some of my thoughts on post-LLM design into a smaller offering. Hit reply if you might be interested.

“Post-LLM value-based design” is a bit of a mouthful, and it’s also inaccurate, because value-based design is an evergreen principle that responds to conditions.

Presumably, your home page has a masthead, and that masthead has a button for someone to get started using your product. In this lesson, we’ll talk about how to write ones that get a little… wordy.

Our monthly office hours for paid members is today! Join us at 1p Central Time to chat about all things value-based design. Happy to answer any questions or pressing issues you may currently have. Find out what 1p Central Time is in your time zone here. If you’re a paid member, our meeting link is at the end of this email. If you sign up between now and 1p, we’ll send the meeting link your way.

In last week’s letter, I wrote about the world we exist in as designers after LLM’s broad-scale introduction. Now I’d like to talk a little bit about the labor aspects of LLM, which are, like it or not, heavily influencing those who buy design as of press time.

There’s a lot of noise out there. Almost all writing on this topic is unreadable. I sort of get why people are getting loud, though, considering western civilization is slowly collapsing and nothing feels remotely safe or permanent anymore. Kinda makes sense why people would think LLM is a cool safety blanket of future-forward manifestation, eh?

First, our monthly office hours for paid members is coming up! Join us on Tuesday, July 8 to ask me anything about value-based design & getting an impact with your work. These vary in attendance from 1 to 10 people, and they’re always helpful for you and for me. Signup link after the jump!

First, two stories about how social proof can be put in your headline. Then, a lesson about why and when you should do so.

Our prices on new consultative work will change at 5p CDT today. Now’s your last chance to buy a teardown, roadmap, or call with us at our current rate. If you’re an active client, your fees will not change for the duration of your work with us.

A couple of weeks ago, I surveyed everyone about what we should write about next, and “post-LLM design” won by a landslide. I find this to be fascinating, because we’ve positioned ourselves rather firmly as skeptical of LLM, at least with respect to some of the messaging that exists around it.

For the first half of my career, tech was changing the world, and there was a lot of optimism & promise around it. We didn’t really question much. The iPhone came out, then we all made a bunch of apps, then we ruined taxis & hotels. The internet was a place where we could all connect with one another and understand the world’s information. Twitter had infighting, but we thought it was funny.

We already established that design is not dead. In this paid lesson, we’ll discuss the specific ways that design is surviving, alongside some steps for you to take.

No.

Asking for design input from a wide range of stakeholders has its upsides and downsides. One downside is when someone sees a large company or influencer offering a specific solution, and they think “well, we should do that, too.”

On face, this is not a horrible idea. Other people did all of this work and succeeded, so why not us? It’s more efficient, helps us compete.

You know better, so let’s talk about it.

Some business announcements this week, and then a brief note on fiat plays:

• Our repositioning is more-or-less complete. If you find anything on our site that looks off or requires a rewrite, please let us know.
• We’re kicking off a major summerlong project on the topic of onboarding, and I’m doing a small literature review for it. I’m already intimately aware of Hulick’s work, but if you have any other books or resources for me to review, hit reply and point me to ‘em.
• For the first time in five years, we’re going to be changing our fees for new work in a few weeks. Since we could change it all right now, that means a lot of things are on sale as of the conclusion of this sentence. Now would be a very good time to book a roadmap, call, or retainer, if you feel so called. Thanks for your support of us, now & always.
• Lastly, one brief question: what would you like me to write about next?

In last week’s paid lesson, we defined the seam and discussed what you can do to address it. We’re building on that lesson by talking about why a style guide is important, and what makes it different from a design system.

Our monthly office hours for paid members is today! Join us at 1p Central Time to chat about all things value-based design. Happy to answer any questions or pressing issues you may currently have. Find out what 1p Central Time is in your time zone here.If you’re a paid member, our meeting link is at the end of this email. If you sign up between now and 1p, we’ll send the meeting link your way.

—

Financially, we have something here called the breakeven point, where we know we’ll be able to live comfortably, meet our expenses, and do what we want to do for the year. This typically comes around late August, when a lot of businesses lock in their strategies for the rest of the year and have chosen to get us involved. A couple of years, it didn’t happen at all. One year, it happened in early June because everybody suddenly invested in our work in response to a global pandemic.

I don’t want to jinx anything, but it’s nonzero likely that we’ll reach the breakeven point soon. Our existing client portfolio has not changed since last September, and a couple of them have chosen to hire us for more expansive work. With one more renewal, we’ll be good for the year.

Have you ever signed up for software that had a lovely-looking marketing page, and the product itself was… lacking? We call the transition between marketing & product the seam, and we think it’s of profound importance for your business.

A prominent seam results in lower retention and higher churn, plain & simple. Competitors can take advantage of it. And it’s just not a good look.

That’s because your marketing page promises something, and so your customers expect the quality of your design to translate, in some form, to the product. When someone goes through a well-designed conversion funnel, joins, pays you, and encounters something that looks like it was built ten years ago, they feel deceived.

In this paid lesson, we’ll discuss what the seam is, where it typically occurs, why it occurs, and what you can do about it.

First, our monthly office hours for paid members is coming up! Join us on Tuesday, June 10 to ask me anything about value-based design & getting an impact with your work. These vary in attendance from 1 to 10 people, and they’re always helpful for you and for me. Signup link after the jump!

I’m currently writing this in my garden, which is the sort of place that causes people to go slack-jawed and slow down as they walk through. I garden a lot. I pull weeds on my way inside and throw them in a little basket next to the door. I harvest plants from my raised bed and make lunches from them.

I pause for lunch every day. I make lunch every other Thursday for anybody who wants to show up. I’m sitting under a 12-foot-tall serviceberry bush right now, and in a couple of weeks its fruit will start to ripen, at which point I’ll be swatting squirrels & birds away as I pick the thing clean. Then I’ll make jam with it, jar it for my close people, and hand the jars out exclusively at my biggest party of the year, which is on the second Saturday of July.

Incorrect people have recently been declaring the death of design. This is weird, because we see design everywhere. We see design in places where we don’t expect to find design. We can only conclude, in this moment, that design has won.

So what now?

One more about repositioning.

We often speak here about new positioning being easy to adopt, technically speaking. You change your home page, spin up a landing page, ask people if they’re interested. You put on new positioning like it’s a new outfit.

The real challenge is when you reposition after a decade of a previous positioning. That’s a fourth of your career! You’re kind of flushing it! Suddenly you’ve been boiling-frog’d into one of the most load-bearing decisions of your life.

There are ways to slow-pedal this and soften the impact. If you keep your existing portfolio of clients, and even your existing messaging and educational initiatives, you can test the new market without burning any bridges.

Expanding on our recent universally correct lesson about pricing, we’d like to talk about pricing tiers: namely, what goes into the strategies behind establishing each price, and what you can do to move into a correct space for pricing.

Thanks for your patience while we were out in sunny, profoundly warm Mexico. I watched a thunderstorm roll in while drinking coffee on my balcony, overlooking the Caribbean, and I felt really grateful to be alive, doing what I do for all of you.

A few small announcements:

1. I’ll be doing teardowns at MicroConf Remote tomorrow, May 21, in the morning. MicroConf is one of those extended-family things that I’ve been honored to attend over the past few years, and I’m really grateful to be on some form of stage for them. Please come through & heckle!
2. I was quoted on the App Collective’s latest episode on the topic of how we vet trusted partners. Don’t call us, we’ll call you.
3. Not a Draft-y thing, but we enjoyed this A/B test. Not a very high sample size, but you’re dividing by zero, so.

Okay, actual letter time.

Our monthly office hours for paid members is today!

Join us at 1p Central Time to chat about all things value-based design. Happy to answer any questions or pressing issues you may currently have. Find out what 1p Central Time is in your time zone here.

If you’re a paid member, our meeting link is below. If you sign up between now and 1p, we’ll send the meeting link your way.

As a humble reminder, we’re out at a conference this week. We’ll be back the week of May 19.

One of my favorite things about software is how there are so many bespoke cases that people end up with these roiling debates about how to do a thing. “Don’t charge less than $50 a month,” one says, forgetting that this is literally how dozens of thriving businesses work. “Never have a free plan,” they say, even though many businesses, including one I work for, use free plans as ways to cleanly ladder people into revenue generation.

And so there are still quite a few open questions. These are “myths,” I guess, to some, but for us they’re rules that just happen to get broken a lot. Let’s go through some of them, and outline some exceptions and contingencies.

As a humble reminder, we’re out at a conference this week. We’ll be back the week of May 19.

We’re aware that our positioning towards software is the most important technological event of the past century, and as a result, some people have questions about how we did it. We’ve undertaken a few initiatives, some done, some still in progress:

• Rework our website to reflect our new focus on software, which we wrapped up last week.

• Start from basics. Paid members have already received a couple of lessons on pricing & onboarding, with more to come.

• Outline a few years of new lessons on increasingly granular topics. Hoping to do this on the plane in a couple of days.

• Relationship building. Figure out where to speak next, who to talk to, etc.

Let’s talk about lesson planning. Content ideas are shockingly easy to brainstorm; you just need to make the writing prompts to get you going when you’re in front of a blank screen. I got this idea from Naomi Dunford at IttyBiz and have adapted it for our use.

First, come up with a few primary topics that fit your positioning. For us, that involves:

First, our monthly office hours for paid members is coming up! Join us on Tuesday, May 13 to ask me anything about value-based design & getting an impact with your work. These vary in attendance from 1 to 10 people, and they’re always helpful for you and for me. Signup link after the jump!

Onboarding is massively important, but it usually doesn’t lend itself well to specific design patterns, since the goal is to create a specific outcome that is specific to your product’s value. In this lesson, then, we’ll talk about some of the principles that onboarding should follow, and dive into some examples.

They say that a pilot earns their paycheck every tenth landing. The theory: the plane mostly flies itself when everything goes well*. When you need to do something more complex – like, say, fly into ORD mid-derecho, as I’ve had the unfortunate fate of experiencing – then that’s where your expertise kicks in.

I have had the good fortune of earning my paycheck this past month, for all of my clients, for reasons both obvious and not obvious. One client watched a vendor turn usurious with a day to go in the contract; another lost a key staff member; a third shared with me a big, intractable problem around onboarding. In each of these, we flew into the storm, stuck the landing.

The common thread is advisory, brought about through establishing the expert position ahead of time. Expertise can be publicized in the form of whitepapers, process documents, surveys, books, and reports. Most of you know we’re experts in what we do, but many others, including some who hire us(!), need a little budging.

Because what we do is value-based design, but how we create value is through advisory. It doesn’t take long for people to start asking us bigger strategic questions that, on face, have nothing to do with the actual practice. But they have everything to do with the way the business works, and there’s always something deeper to explore.

Now that we’re focused on software, it’s time to turn our attention back toward a big topic: pricing pages. In this lesson, we’ll outline the baseline anatomy of a pricing page, so you can make sure yours is doing as well as possible before you start to break rules or make improvements.

Why did we put a light bulb there? What is the point of a light bulb? Where are we attempting to put light, exactly? Are people really asking for light here in the first place? Could this be more easily solved by simply cutting a hole in the ceiling and putting a skylight in there? Do we need light when it’s dark out?

Why did the light bulb fail? Don’t we have LED lighting now? You can just buy a light that lasts for 15,000 hours and be done with it, so if the light failed and it is LED, why? Faulty wiring? A power spike? Do we need to make a warranty claim? Do we need to open up the ceiling and figure out what happened? If the light isn’t LED, why do we have incandescent or CFL bulbs in the first place?

What was the temperature of the light? Why? What is the function of the space? Are we talking a nice cozy home, or an office, or a hospital? Or maybe it’s a design consultancy where we need fully neutral 5000K daylight bulbs everywhere, so people can make sure their colors render properly?

What is our prior knowledge of this light? What value are people getting from this light? Have we talked to anyone? Why not?

Oh lawd, we’re talking about tariffs.

Our monthly office hours for paid members is today! Join us at 1p Central Time to chat about all things value-based design. Happy to answer any questions or pressing issues you may currently have. Find out what 1p Central Time is in your time zone here. If you’re a paid member, our meeting link is at the end of this email. If you sign up between now and 1p, we’ll send the meeting link your way.

—

New event alert! I’m pleased to announce that I’ll be doing live teardowns at MicroConf Remote in May. Come through! Submit your site! I promise to be firm but kind as I lovingly rip your work to shreds.

In our previous lesson, we defined & discussed process design. In this week’s paid lesson, we’ll connect that lesson with our evergreen piece on sources of truth go in depth about how we can connect sources of truth to yield deeper insight.

Many wild events have happened in Draft’s history, and you could conceivably pick a few to qualify as the wildest. My consistent pick for the wildest happened in 2023, when design began the deepest winter in the industry’s whole history while we also had our second-best year ever.

Four things happened all at once:

1. We came to a global consciousness that design is a form of leveraged power, and those in power took it from us.
2. People in power wanted everything to happen faster, and since design frequently slows things down, design got cut.
3. Other tools appeared that appeared to make design more efficient to those in power. Whether or not this is true remains an open debate, but I think nobody is debating that people in power think the tools make design more efficient.
4. Global fascism, which has caused numerous tech workers to go on strike from the industry.

None of which are great! But again, we also had our second-best year ever – because prospective clients recognized the value of our work, and decided to take a chance on us.

In our previous two lessons, we set forth the idea of executional velocity and described why it’s important for teams to pursue, especially those that are beginning to scale. Usually that happens through the intentional creation of structured process.

In this lesson, we’ll talk about how to design a process, and how to apply your design skills to the creation of generous execution in any organization.

First, our monthly office hours for paid members is coming up! Join us on Tuesday, April 15 to ask me anything about value-based design & getting an impact with your work. These vary in attendance from 1 to 10 people, and they’re always helpful for you and for me. Signup link after the jump!

We are never not reworking the stupid website. The world changes; you change; you adapt. Since we’re usually busy serving our clients – and since we’ve been fully sold out since 2022 – I don’t know if we make changes often enough, but we eventually get around to it. Last week we got around to it. We got rid of some things, reworded some other things, and scrubbed a position that was no longer working for us.

The goal is correct plumage. You are signaling to a person in a way that solves their urgent, expensive problem. You do so in a way that reads the room & meets the moment. When it works well, you find kindred spirits. When it works poorly, you try to do everything for everyone, and you bungle your positioning.

In last week’s masterpiece, we coined the term executional velocity and answered a few questions about it:

• What is executional velocity?

• What’s the difference between executional velocity & productivity?

• How can we identify the main operational issues that harm executional velocity?

This week, we’re going to answer a few more questions:

• Why isn’t executional velocity discussed more broadly?

• What’s the relationship between executional velocity & key business goals?

• Under what circumstances might additional executional velocity not be desirable?

• What are some of the ways that we can address normalized deviant practices that actively harm executional velocity?

Let’s begin.

I printed a few copies of our WTF notebook, and I’m seeking beta testers. Hit reply with your mailing address if you’re able to use it for a bit and provide me with brutal, unflinching feedback in return.

Our recent paid lessons have focused on some of the dynamics that occur in teams that are over, oh, say, 7 people. By that point, roles are defined, people wear fewer hats, responsibility gets meted out, and power structures become more readily apparent.

Most businesses are this large, but what if yours isn’t? How does value-based design manifest in smaller teams, or with solo practitioners?

I’ve been lucky enough to watch several dozen growing businesses from the inside over the course of my career. Some have been successful, scaling effectively and growing into new markets. Some have been… less successful. And really, the thing that separates the two is execution. What defines the ability for a team to do things, and do them well?

The rest of this post is available to members. Upgrade now to get:

Our monthly office hours for paid members is today! Join us at 1p Central Time to chat about all things value-based design. Happy to answer any questions or pressing issues you may currently have. Find out what 1p Central Time is in your time zone here. If you’re a paid member, our meeting link is at the end of this email. If you sign up between now and 1p, we’ll send the meeting link your way.

We wrote a brief guide to why we use email when communicating with people. This joins a few other explainer bits that outline our principles & motivations.

Precisely three of you wanted a WTF notebook. I may print some as zines for my close people. We love a fun side project.