Great software
doesn't sell itself.

Most technical people are excellent at building software and uncomfortable selling it. That discomfort is expensive: it shows up as under-priced work, proposals that never close, demos that go quiet, and a pipeline that runs dry. This playbook is the antidote — a practical, repeatable system for turning skill into revenue.

It serves three related jobs, and you can read it in any order:

• Pricing & proposals (Parts II–III) — charge what the work is worth and write proposals engineered to get a "yes."
• A working sales process (Part IV) — from first contact through the demo, the follow-up, and the close, including the exact steps to take after a demo so deals don't stall.
• Selling a product & selling yourself (Parts V–VI) — winning SaaS customers in a specific industry, and marketing your own custom-development services.

Everything here is generic and reusable. The examples are illustrative; adapt the numbers and language to your own market. Nothing works without volume and follow-through — a great script sent to too few people, or a great proposal never followed up, still fails. The discipline is the product.

Software is invisible, expensive, and easy to get wrong — and the buyer usually can't judge quality until it's too late. That combination makes buying software frightening. Sell to the fear, not around it.

The buyer's real fear

A prospect evaluating custom software or a new system is rarely asking "is this the best tool?" They are asking, quietly: "Will this work? Will it be late? Will it cost double? Will I look foolish for choosing them?" The purchase is a personal risk to the person signing, not just a business decision. Your entire job — pricing, proposals, demos, follow-up — is to systematically reduce that perceived risk until saying yes feels safer than saying no.

You sell trust; the code is the by-product

Because the buyer can't evaluate the code, they evaluate you: how clearly you understand their problem, how organized your process looks, how promptly you follow up, how confident and specific your proposal is. Every one of those is a trust signal, and trust signals close deals. Sloppy follow-up loses more work than weak technical skill ever will. The way you sell is a preview of the way you'll deliver — and the buyer knows it.

• Trust signal: fast, specific follow-up
• Trust signal: a written, structured process
• Trust signal: proof (case studies, references)
• Trust signal: speaking their industry's language
• Trust signal: a confident, itemized price

Positioning is the story a prospect tells themselves about what you are and why you fit. Get it right and pricing, proposals and outreach all become easier, because you're no longer "a developer" — you're the obvious choice for a specific problem.

Sell outcomes, not features

Features describe the software; outcomes describe the buyer's better life. Buyers pay for outcomes. Translate everything you build into the result it produces, stated in the buyer's terms.

The power of a niche

"I build custom software" is forgettable. "I build software for food distributors" (or dental practices, or freight brokers) is magnetic to that audience — because specialists are trusted more, charged more, and referred more. A niche lets you speak the buyer's language, reuse proof, and command premium pricing. You can serve outside your niche; you just shouldn't lead with generality. Depth signals expertise; breadth signals a commodity.

There are only three fundamental bases for a price. Most developers use the weakest one by default and leave money on the table every time.

Cost, market, and value

Cost and market both anchor your price to you and your rivals. Value anchors it to the buyer's world — where the numbers are almost always bigger.

How to price on value

Value-based pricing sounds abstract until you make it arithmetic. The move is simple: during discovery, quantify what the problem costs the buyer today, and what solving it is worth. Then your price is an obvious fraction of that.

The structure of a price changes how risky it feels to the buyer. Choose the model that makes the buyer's decision easiest while protecting your margin.

The models and what each signals

A powerful default for larger builds: break the first commitment into something small. A nervous buyer will say yes to a $4,000 discovery long before a $60,000 build. Land the small yes, prove yourself, and the big yes gets far easier.

Paid discovery as a closing tool

A short, paid discovery phase is the single best de-risking move in software sales. It gives the buyer a low-cost way to start, gives you a defined thing to quote, and — crucially — once someone has paid you and had a good experience, they are dramatically more likely to buy the build. It converts a cold "maybe" into a warm customer.

"The honest answer on price is that I'd be guessing until we've pinned down
exactly what you need. So here's what I suggest: a short paid discovery — a
fixed [X] — where I map the requirements and give you a firm, fixed quote for
the build, plus a written spec you own either way. If you go ahead, that work
rolls straight into the project. If you don't, you keep the plan. It means the
number you commit to is real, not a guess — which protects your budget as much
as my time."

The same number can feel expensive or cheap depending on how it's presented. These are not tricks; they're how humans actually judge value. Use them honestly.

Anchoring

The first number in a conversation sets the reference point for everything after. If the buyer names a low budget first, every price you say sounds high. So anchor first — mention the value at stake (the $60,000/year problem) before you mention your price. A $25,000 build quoted after a $60,000 problem feels like a bargain; the same build quoted cold feels like a big spend.

Good / better / best

Offering a single price invites a yes/no decision — and "no" is easy. Offering three options changes the question from "yes or no?" to "which one?" It also anchors with the top tier, makes the middle look sensible (most buyers pick it), and lets budget-conscious buyers stay in rather than walk away.

Presenting the number

• Price last. Never lead with cost. Establish the problem and the value, then reveal the investment. Price stated before value always sounds like too much.
• Call it an investment, show the return. Put your price next to the value it unlocks or the cost it removes. Numbers next to bigger numbers shrink.
• Break big numbers down. "$30,000" can be reframed honestly as "$2,500 a month over the first year, against a problem costing you $5,000 a month."
• Use confident, round numbers for premium work. Oddly precise figures ($24,750) signal a cost calculation; clean figures ($25,000) signal considered value.
• Present, don't send. Whenever possible, walk them through the price live so you can frame it — rather than emailing a number to be judged in silence.

The money conversation is where nervous sellers give away margin. A few rehearsed responses keep you calm, confident, and profitable.

When they ask "what'll it cost?" too early

Early in a conversation you can't answer accurately — and a number given blind will either scare them or trap you. Don't dodge; redirect to value and give a range tied to definition.

"Great question — and I want to give you a real number, not a random one.
Projects like this usually land somewhere between [low] and [high] depending
on [the 2–3 things that actually drive cost]. To tell you where in that range
you'd sit, I'd need to understand [X and Y]. Can I ask you a few quick
questions now, or should we set up 30 minutes to scope it properly?"

Handling price objections

"That's more than we expected" is not a rejection — it's a request for justification, or a signal you haven't established enough value yet. Never drop the price reflexively; that teaches the buyer your first number was fake. Instead, respond to the concern behind it.

Discounting discipline

Every unearned discount trains the buyer to distrust your pricing and shrinks your margin permanently. If you must move on price, get something in return — a faster decision, a deposit, a case-study agreement, a reference, a longer term, reduced scope. A discount given for nothing says the original price was padded; a discount traded for value stays professional.

Most proposals are written like invoices — a scope, a price, a signature line. That's a document that records a decision. A proposal should drive the decision: it's often the last thing the buyer reads before choosing, and frequently the thing they forward to the person who actually signs.

Reframe the proposal's job. It exists to do three things, in order: prove you understand their problem better than anyone else, make the outcome and value vivid, and make saying yes feel safe and simple. Scope and price are necessary, but they are the supporting cast, not the star.

The structure that closes

1.  Cover & title            — clean, their name/logo, a confident title
2.  Executive summary        — THEIR problem + the outcome you'll deliver,
                               in 3–4 sentences. Written for the signer.
3.  Our understanding        — restate their situation & goals in their words.
                               (This section wins the deal. It proves you listened.)
4.  The recommended solution — what you'll build, framed as outcomes
5.  Scope & deliverables      — precisely what's included…
6.  Out of scope              — …and what isn't (protects you; builds trust)
7.  Investment & options      — 3 tiers if possible; value framed before price
8.  Timeline & milestones     — when they get what; first value early
9.  Why us / proof            — brief: relevant results, references, guarantee
10. Terms & assumptions       — payment schedule, change control, what you need
11. Acceptance & next step    — ONE clear action, a start date, a validity date

Why the order matters

The sequence is deliberate psychology. By the time the buyer reaches the price (section 7), they've already read you describing their problem accurately (3), seen the outcome (4), and understood exactly what they get (5–6). Price lands as the answer to a value they now feel — not as a cold number. The "Our understanding" section does the heaviest lifting: a buyer who reads their own situation described better than they could describe it themselves has essentially already decided.

A few specific techniques turn a competent proposal into one that closes. Each works by lowering the buyer's perceived risk or raising the cost of waiting.

Risk reversal

The buyer's fear is the deal-killer, so take the risk onto yourself where you safely can. Options: a fixed price (you absorb overrun risk), a paid-discovery first step (they risk little to start), a satisfaction milestone (they approve stage one before committing to the rest), a workmanship guarantee (defects fixed free for a period). Each one quietly answers the question "what if this goes wrong?"

Proof & urgency

• Proof beats promises. A one-line result from a comparable client ("cut order-entry time 70% for a distributor your size"), a reference they can call, or a short case study does more than a page of adjectives. Specific numbers are more believable than superlatives.
• Honest urgency overcomes inertia — your true competitor. Use real reasons to act now: a limited onboarding slot, a price valid until a date, a busy season they'll want to be ready for, the compounding cost of the problem every month they wait. Never fabricate urgency; buyers smell it and it destroys trust.

The clear next step

End every proposal with exactly one obvious action — not three options that create decision paralysis. Make it concrete and easy: "To start, sign here and we'll book your kickoff for the week of [date]." Ambiguous endings ("let me know your thoughts") invite delay. A clear, low-friction next step invites a yes.

Ready-to-adapt language for the sections that carry the most weight.

"[Company] currently [describe their situation and the problem it causes],
which costs an estimated [time/money] and puts [growth / accuracy / margin]
at risk. This proposal outlines a solution that will [primary outcome] and
[secondary outcome], expected to [quantified benefit] within [timeframe].
We recommend the [Recommended] option below, which balances speed of results
with long-term value. We can begin as early as [date]."

"From our conversations, here's what we heard: today, [their process] means
[the pain] — [specific consequences in their words]. Your goal is [their
stated goal], and success looks like [their definition of done]. The following
is designed around exactly that."

"The problem described above is costing roughly [$X] per [month/year].
The options below are structured so you can choose how much of that value to
capture, and how quickly. Each is an investment against that ongoing cost."

"To move forward: reply to approve the [Recommended] option (or let me know
which fits best), and I'll send a short agreement and an invoice for the
[deposit]. We'll reserve your kickoff for the week of [date]. This pricing is
held until [date]."

# Prompt
Here are my discovery notes for a prospect:
"""[paste notes: their business, problem, volumes, goals, quotes they said]"""

Draft: (1) a 4-sentence executive summary written for the person who signs,
(2) an "Our understanding" section in THEIR words that proves I listened,
(3) three pricing tiers (Essential / Recommended / Complete) from this scope.
Frame everything as outcomes. Do not invent metrics I didn't provide.

Sales feels like art but runs on arithmetic. If you know your conversion rates, you can predict revenue — and, more usefully, find the exact leak that's starving you of customers.

A software sales pipeline has recognizable stages. Track how many prospects sit in each and what percentage advance:

Cold outreach fails when it's about you and generic. It works when it's short, specific, about the prospect's problem, and asks for something small.

Email that gets replies

A cold email has one job: earn a reply, not close a sale. Keep it under ~90 words, make it obviously written for them, lead with a problem they feel, offer a shred of proof, and ask one low-friction question. No brochure, no feature list, no "hop on a call to explore synergies."

Subject: [specific pain, e.g. "re-keying orders at {Company}"]

Hi [Name],

Most [type of business] I talk to lose hours every week re-keying [orders /
invoices / data] by hand — and eat the cost of the typos that creep in.

We built a system that [specific outcome] for a [comparable business]; they
cut [metric] by [number].

Worth a 15-minute look to see if the same is possible for [Company]?

[Your name]

• Subject lines should sound like an internal note, not an ad: specific, lowercase-ish, no hype. Curiosity and relevance beat cleverness.
• Personalize the first line with something real about them. A visible sign you did five minutes of homework outperforms any template.
• One call to action. A second ask can sharply cut your reply rate.

Calls that get meetings

The goal of a cold call is the next meeting, not the sale. Open with a pattern-interrupt and permission, name a specific pain fast, and propose a small next step. Expect most calls to end in "no thanks" — that's normal; volume and consistency win.

"Hi [Name], it's [You] with [Company] — I know I'm calling out of the blue,
can I take 30 seconds and you can tell me to get lost if it's not relevant?
… We help [type of business] stop [specific pain] — the [re-keying / errors /
month-end scramble] kind of thing. Is that something your team deals with, or
have you already got it handled?"

If they engage, you're not selling — you're qualifying and booking a proper conversation. "Sounds like it might be worth a closer look — I've got Thursday at 10 or Friday at 2, which is easier?" A specific two-option ask books more meetings than "when are you free?"

The outreach sequence

One touch is a lottery ticket. Most replies come from the follow-ups, yet most people send one email and give up. Run a planned multi-touch sequence across channels before you conclude someone isn't interested.

Day 1   Email — problem-led (above)
Day 3   Call — the opener; leave a short voicemail if no answer
Day 5   Email — different angle: a specific result / mini case study
Day 8   Call — reference the emails; aim for the meeting
Day 12  Email — a useful resource or insight, no ask ("thought of you")
Day 18  Email — the "break-up": permission to close the file (see Ch.15)

Time spent on a prospect who will never buy is the most expensive thing in sales. Qualify early and honestly — disqualifying a bad fit is a win, because it frees you for a real one.

Before investing in a full demo or proposal, confirm four things. If two or more are missing, slow down or step back.

A demo that lists features bores buyers. A demo that solves their problem, using their language, on their scenario, sells. The difference is discovery.

Discovery before you demo

Never demo cold. Spend the first portion — even ten minutes — asking about their process, their pain, their volumes and their goals. This does three things: it lets you tailor the demo to what they care about, it surfaces the value you'll later price against, and it makes them feel understood before they see a single screen. A demo without discovery is a product tour; a demo with discovery is a solution to a problem they just described.

Running a demo that lands

• Show their scenario first. Open with the exact thing they said hurts. "You mentioned re-keying orders — let me show you that going away." Lead with the punch, not the login screen.
• Tell, don't just show. For each feature, say the outcome: "…so your team never touches this again."
• Less is more. Demo the 20% of features that solve 80% of their pain. A firehose of capabilities creates doubt and questions, not desire.
• Make it a conversation. Ask "how would that fit how you work?" throughout. A monologue doesn't sell; a dialogue does.
• Confirm the value out loud. "So if this saved your team those ten hours a week, what would that be worth to you?" — get them to say the value; it's far more powerful than you claiming it.
• Always set the next step before you end. Never let a demo end with "we'll be in touch." Book the follow-up while you're still together (Ch. 15).

This is where most deals are won or lost — and where most sellers simply stop. A great demo followed by weak follow-up loses to a mediocre demo followed by relentless, helpful follow-up. Treat the period after the demo as its own disciplined process, not an afterthought.

The step-by-step

1. Same day — send the recapwithin hoursWhile it's warm, send a short email that recaps their stated problems, what they saw that solves each, the value discussed, and the agreed next step and date. This proves you listened and makes the follow-up about them, not your product.
2. Next day — the tailored value summary24–48hSend a brief, personalized summary of the return: their numbers, the time or money saved, and answers to any questions left open in the demo. Include a couple of relevant screenshots or a short recording. This is the artifact they'll forward internally.
3. Confirm the decision paththis weekNail down who else must see it, the budget, and the timeline if you haven't. Offer a second short demo for other stakeholders — getting the real decider in the room is often the whole game.
4. Send the proposal — fast2–4 daysMomentum decays quickly. Get a tailored proposal (Part III) over while the demo is fresh, and — whenever possible — present it live rather than emailing it into silence.
5. Follow up with value, on a cadenceongoingIf they go quiet, don't "just check in." Each touch should add something: a relevant case study, an ROI angle, an answer to an anticipated objection, a useful article. Space the touches and mix email with a call (cadence below).
6. Create an honest reason to decideas it maturesOffer a real nudge: a limited onboarding slot, pricing held to a date, readiness before a busy season, or the compounding monthly cost of waiting. Ask directly for the decision (Ch. 17).
7. Offer a lower-risk path if stuckif stalledIf they're interested but hesitant, shrink the first commitment: a paid discovery, a pilot, a phase-one milestone. A smaller yes beats a stalled maybe.
8. The break-up — then nurtureif silentAfter several unanswered touches, send a permission-to-close email (template below). It often revives dead deals. If it doesn't, move them to long-term nurture — not the bin. Timing changes; stay in view.

A follow-up cadence that isn't annoying

The line between persistent and pestering is value. Persistent-with-value is welcome; "just following up" five times is not. A workable rhythm after a demo/proposal:

Day 0    Proposal sent (ideally presented live)
Day 2    Email — "anything I can clarify?" + restate the headline outcome
Day 5    Call — check reactions, surface objections, offer to re-present
Day 9    Email — value add: a relevant case study or ROI angle
Day 14   Call — ask directly where things stand & what would help
Day 21   Email — the break-up (below)
Then     Move to nurture: a useful touch every 4–6 weeks

The templates

Subject: Recap — [their goal] + next step

Hi [Name],

Thanks for the time today. Quick recap of what we covered:

• You're dealing with [problem 1] and [problem 2], costing about [value].
• You saw how [feature/flow] removes [problem 1], and [feature] handles [problem 2].
• We estimated that's worth roughly [time/$] to your team.

Next step: [agreed action] on [date]. I'll [what you'll send/do] before then.

Anything I missed or you want to dig into? Just reply.

[You]

Subject: Thought of you — [relevant result]

Hi [Name],

Not chasing — just useful: here's how a [similar business] handled the exact
[migration / concern] you raised, and what it saved them: [one-line result].

If it's helpful, I'm happy to walk through how that would look for [Company].
Where are your thoughts on moving ahead?

[You]

Subject: Should I close your file?

Hi [Name],

I haven't heard back, which usually means one of three things: the timing
isn't right, it's not a priority now, or I've dropped the ball somewhere.

Totally fine either way — should I close this out for now and check back down
the road, or is there still interest worth picking up?

No hard feelings whatever the answer.

[You]

Objections aren't rejection — they're the buyer telling you what still stands between them and yes. Welcome them; a silent prospect is far harder to close than one voicing concerns.

The universal method: acknowledge, understand, respond, confirm. Don't argue. Validate the concern, ask a question to find what's really behind it, answer that, then check you've resolved it. Common ones:

Many capable sellers do everything right and then never actually ask. Closing isn't a manipulative maneuver at the end — it's the natural, confident request that follows once value is clear.

• Assume the sale, gently. Talk in terms of "when we start" and "your kickoff," not "if you decide." Confidence is contagious; hesitation is too.
• Ask a direct closing question. "Shall we go ahead?" or "Are you ready to get started?" Then — the hardest and most important part — stop talking and let them answer.
• Offer a choice, not a yes/no. "Would you like to start with the Recommended option, or phase it?" A choice between ways to say yes is easier than a single yes/no.
• Summarize value before asking. "So this saves your team ~10 hours a week and pays for itself in [months] — ready to lock in your start date?"
• Make yes frictionless. E-signature, a small deposit, a clear first step. Every extra click between decision and action is a chance to stall.

The easiest customer to win is the friend of a happy one. A delighted client is worth far more than the deal they signed — they're a source of referrals, references, testimonials, and repeat work. Most sellers never ask.

• Deliver a great start. Referrals are earned in the first 90 days. A smooth onboarding and an early win turn a customer into an advocate.
• Ask at the peak. Right after a visible win — a successful go-live, a great result — is the moment to ask: "Who else do you know who's dealing with the same headache we just solved?"
• Make proof a habit. Turn every good outcome into a one-line result, a testimonial, or a short case study — the raw material of all your future selling.
• Stay in touch after the sale. A quarterly check-in surfaces new work and keeps you top-of-mind for the referral when it comes.

A product built for one industry will usually beat a general tool for that industry — and it sells differently. You're not selling software; you're selling a system that already understands their business.

The advantages of a vertical product compound in the sale:

• You speak their language. When you name their specific workflows, terms and headaches without being taught, you earn instant credibility a generalist can't.
• The ROI is concrete. A vertical system targets the exact costly problems of that industry — so the value case writes itself in their numbers.
• Proof transfers. A result for one business in the industry is directly persuasive to the next one, because they're alike.
• Referrals cluster. People in an industry know each other. A few happy customers become a reputation.

For a recurring-cost product, the buyer is comparing a monthly fee against their current way of doing things. Win by making the current way's hidden cost visible — and bigger than your price.

The value model

During discovery, gather the few numbers that drive the buyer's economics, then do the math with them (not at them). The goal is a single, believable figure: "here's what the status quo costs you a year."

The ROI one-pager

Turn that model into a single, forwardable page the buyer can show their partner or boss: their current annual cost of the problem, your annual price, and the net gain and payback period. A clear one-pager does more to close a SaaS deal than any feature list — it arms your champion to sell internally when you're not in the room.

YOUR CURRENT COST (status quo, per year)
  Manual labor:        [hours/yr] × [$rate]      = $[A]
  Errors & rework:      [errors/yr] × [$/error]    = $[B]
  Unbilled / leakage:                              = $[C]
  ─────────────────────────────────────────────────────
  Total annual cost of doing nothing:              = $[A+B+C]

THE INVESTMENT
  [Product] per year:                              = $[price]

THE RETURN
  Net first-year gain:            $[A+B+C − price]
  Pays for itself in:             [weeks/months]
  Plus: faster cash, fewer errors, room to grow.

For an established business, the biggest obstacle isn't your price — it's the fear of change. They have a way that "works," and switching feels risky, disruptive and time-consuming. Sell the transition, not just the destination.

"We already do this in spreadsheets / our old system"

The status quo is your real competitor, and it has powerful advantages: it's paid for, familiar, and blameless. You don't beat it by attacking it — you beat it by making its hidden costs impossible to unsee: the hours, the errors, the missed charges, the fact that it can't scale, the risk of it living in one person's head or one fragile file. Then contrast that ongoing, invisible bleed with a fixed, visible, ROI-positive fee.

"Spreadsheets feel free because the cost is hidden — it's spread across your
team's hours, the occasional expensive error, and the charges that slip
through. When we add those up for a business your size, it's usually [$X] a
year. The system isn't really a new cost; it's trading an invisible, growing
cost for a fixed one that pays you back."

Migration fear

"Moving all our data sounds like a nightmare" kills more SaaS deals than price. Neutralize it head-on: explain that you handle the migration, that you can run the new system in parallel with the old before fully switching, and that onboarding is phased so nothing breaks overnight. Every reassurance you give about the transition removes a reason to stall.

Pilots & trials

When a buyer is interested but can't commit, shrink the risk to almost nothing: a paid pilot, a single-department rollout, or a first phase. Let them experience a real win on a small scale. A prospect who has felt the product work on their own data is a very different buyer from one who only watched a demo — and a paid pilot filters out tire-kickers while warming up real ones.

"Not enough new customers" always traces to a specific, fixable stage. Work down this list honestly; the fix is almost never "try harder everywhere" — it's "fix the one thing that's leaking."

"Freelance developer" competes with the whole world on price. A positioned expert competes with almost no one. Your decades of experience are only an asset if your positioning makes them visible.

Your offer & niche

Buyers hire specialists. Choose a lane — an industry you know, a problem you solve repeatedly, or a type of system you build best — and lead with it. You can still take varied work; you simply market the specialty, because "the person who builds order systems for distributors" is memorable and referable in a way "a developer who can build anything" never is. Depth of experience across many industries is a strength here: it lets you say "I've solved this exact class of problem before," which is precisely what de-risks the buyer's decision.

Windows, web & mobile — positioning across platforms

Being able to deliver on any platform is valuable, but "I do everything" reads as unfocused. Position it as choosing the right tool for the outcome: you build desktop software when the work needs power and offline reliability, web when it needs reach and central control, and mobile when the work happens away from a desk. The message is judgment, not a menu.

"I'm not tied to one platform, so I recommend what actually fits the job:
a Windows application when you need speed and it has to work offline; a web
system when your team needs access anywhere and you want one central version;
a mobile app when the work happens in the field. The point isn't the
technology — it's picking the one that gets you the result with the least
risk and cost to run."

An independent developer needs a small number of reliable ways for the right people to discover them. You don't need all of these — you need two or three, done consistently.

A buyer can't evaluate your code, so they lean on evidence that you've delivered before. Proof is the most persuasive marketing asset you own — and the easiest to neglect.

Build a habit of manufacturing proof from every engagement:

• Case studies with a simple arc: the client's problem → what you did → the measurable result. One page, numbers where possible, the outcome as the headline.
• Testimonials captured at the peak of client happiness — a couple of specific sentences beat a paragraph of vague praise. Ask right after a win.
• References — a short list of clients who'll take a call. Nothing closes a nervous buyer like hearing "yes, they delivered" from a peer.
• Before/after specifics — "reduced order entry from 4 minutes to 20 seconds" is worth more than any adjective.

[Type of business] was [problem, with a number: losing X hours / Y% errors].
We built [solution, in outcome terms]. Within [timeframe], they [result:
saved X, cut Y, grew Z]. "[One specific, enthusiastic client sentence.]"

Experienced developers routinely undercharge — anchored to an hourly wage instead of the value and low risk their experience delivers. Everything in Part II applies to you personally.

• Price the outcome, not the hours. Your speed and judgment are assets, not reasons to charge less. Move toward fixed-price and value-based work so efficiency rewards you instead of penalizing you.
• Sell risk reduction. A seasoned developer's real premium is "this won't be a disaster." Name it: fewer surprises, fewer rewrites, a plan before code. That's worth a lot to a nervous buyer.
• Raise rates deliberately. Increase your price with each new client until you start hearing "no" occasionally — if everyone says yes instantly, you're too cheap. Raise new-client pricing first; migrate existing clients gradually.
• Use tiers & discovery. Offer good/better/best and a paid discovery step, exactly as you would for any product. They work identically for a solo developer.

A consolidated library of the scripts and templates from across this guide, in one place to grab and tailor. Replace the brackets; keep the structure.

• Outreach: cold email
• Outreach: cold-call opener
• Outreach: the sequence
• Pricing: "what'll it cost?"
• Pricing: pitch discovery
• Proposal: exec summary & close
• Demo: recap & follow-ups
• Follow-up: the break-up
• SaaS: ROI one-pager
• SaaS: reframe the status quo
• You: case study

"I'm really glad [specific result] worked out. Quick favor — who else do you
know who's wrestling with the same [problem] we just solved? A quick intro
would mean a lot, and I'll take great care of them like I did with you."

Subject: [outcome], for [industry]

Hi [Name],

[Type of business] like yours are [achieving outcome] by [one-line how].
[Comparable business] recently [specific result].

If [the problem] is on your radar, I'd be glad to show you what it looks like
for [Company] in 15 minutes — no pitch, just your scenario.

Worth a quick look? [Two specific time options.]

[You]

You don't need a dashboard — you need a handful of numbers that tell you where to focus. Track these and your gut stops guessing.

Reading changes nothing; doing does. A concrete plan to turn this playbook into pipeline over the next quarter.

□ Write your positioning statement (Ch. 2) and one-line offer
□ Pick ONE niche to lead with
□ Turn 2–3 past projects into one-paragraph case studies (Ch. 25)
□ Build your good/better/best pricing & a paid-discovery offer (Part II)
□ Draft your proposal template (Part III) and cold sequence (Ch. 12)
□ List 50 well-fit prospects

□ Run the outreach sequence to your 50 — consistently, every week
□ Book & run discovery-led demos (Ch. 14)
□ Use the after-demo sequence on EVERY demo (Ch. 15) — no exceptions
□ Present proposals live; don't email-and-pray
□ Start tracking the metrics in Ch. 28
□ Ask every happy client for a referral & a testimonial

□ Review your metrics; find the one leaking stage (Ch. 22)
□ Fix that stage first — usually follow-up & closing
□ Raise your pricing on the next new deal
□ Double down on whichever lead channel is working; drop what isn't
□ Build referrals & case-study capture into your delivery process
□ Repeat — this is a system, not a sprint

Plain-language definitions of the sales and marketing terms used in this playbook.