The Software Business Library — Build It, Price It, Sell It

Why this exists

The gap nobody trains you for

Plenty of people can write excellent software. Very few were ever taught the disciplines that surround it: how to define a project properly before committing to a price, how to estimate work so the number holds up, how to write a proposal that actually closes, and how to run a sales process that doesn't leak deals at every stage.

Large, established firms have this knowledge locked in internal SOPs. Independent developers and small software companies are usually flying by the seat of their pants — and paying for it in unprofitable projects, stalled deals, and quiet pipelines. This library is an attempt to write that missing knowledge down, plainly, and give it away.

Everything here is generic and reusable — no company or product specifics — and applies whether you build for Windows, the web, or mobile; whether you're delivering a brand-new application or enhancing a system that's been in production for twenty years.

Set up shop

Form the business and build the structure, finances and habits it runs on.

Find the market

Choose what to build and for whom, and validate demand before you code.

Build it

Turn a vague idea into a spec you can define, estimate and deliver.

Price it & sell it

Price on value, write a proposal that closes, and run the deal to signed.

Protect it & get paid

Lock in payment terms and a contract that holds up when it matters.

Secure it

Build a credible security posture and pass the reviews that gate bigger deals.

Run it

Keep shipped software reliable, current and affordable in production.

Grow it & keep it

Turn a delivered project into support, retainers and recurring revenue.

Mind the money

Run the cash, tax, pay and reserves that keep the business alive.

Build a team

Grow from solo into a small team — hiring, contractors and delegation.

Scale it — or don’t

Decide whether and how to grow — or deliberately stay small.

Sell the business

Build a business worth buying, and run the sale so the value holds.

Use it

Put the working tools to work — and find what’s quietly costing you.

Prove it

Assess your knowledge — delivery, sales, or the full track.

A different path · not selling software?

Building software to run a business, not to sell it?

If your software is your company's advantage rather than its product, the usual playbook doesn't fit. There's a separate guide for you.

Start here →

Set up shop

Formation & foundations

Guide · 8 parts

Setting Up Shop

Before you can price, protect, or sell your work, there has to be a business to run it through. This is the foundation the rest of the library assumes: choosing a structure and getting the liability shield right, setting up the financial plumbing, protecting the business with insurance, assembling a lean tool stack, and building the handful of habits that quietly decide whether the business runs smoothly or fights you. Its argument: a business is a container you build before you fill it — and its shape decides how much of what you earn you actually keep.

Who it's forThe person about to go independent — or who already has, and never quite set things up properly.

Business structure — the liability shield, sole proprietor vs. company, and when to formalize
The financial plumbing — a separate account, books from day one, and the mechanics of getting paid
Insurance & liability — the cover that matters and sizing it to your real exposure
The boring essentials — registrations, records that save you, and reusable contract templates
Your operating stack — the minimal tool set, and the discipline not to over-tool
Name & presence — a clear name and a minimum viable professional presence
Habits that compound — the operating rhythm and the three disciplines that prevent most financial pain

Read online HTML

Find the market

Product & customer discovery

Guide · 8 parts

Finding Your Product & Market

The finest execution on the wrong idea produces something excellent that nobody buys. Before you build, this guide asks what to build and for whom: finding a problem worth solving, discovering what customers actually need rather than what you imagine, choosing a market you can reach and that will pay, and validating demand before you write the code, not after. Its argument: fall in love with the problem, never with your solution — and gather enough evidence to build with conviction, or the courage to walk away.

Who it's forThe developer with an itch to build their own product, and the firm choosing which work to specialize in.

Start with a problem — problem-first thinking, and what a problem worth solving looks like
Customer discovery — talking to people the right way, and fighting your own confirmation bias
Choosing a market — why narrow beats broad, and customers who are reachable and willing to pay
Validating demand — testing your riskiest assumption, real signals vs. enthusiasm, and pre-selling
Scoping the MVP — what “minimum viable” really means, and the discipline of building less
Positioning & the wedge — why you, and the narrow beachhead a small vendor can win
Deciding to build — or not — kill criteria, and whether building from scratch is even the right move

Read online HTML

Build it

Delivery & estimation

Guide · 22 chapters

The Custom Software Delivery Guide

The full lifecycle of a software project — planning, requirements, design, development, testing, beta, documentation, release and support — written so that every phase produces something you can actually quote from. Its central argument: you cannot accurately price what you have not defined.

Who it's forDevelopers and small firms who want a repeatable delivery process — and one they can show a client to prove the work will be run properly.

Requirements, high-level design and technical design — with document outlines you can copy
Estimation & quoting — work breakdown, three-point estimates, the effort everyone forgets to price, and a full worked build-up from hours to a quote
Testing, beta, release and support — including regression and impact analysis for changes to live systems
Deployment models — what stays the same and what shifts between desktop, web and cloud
Tech stacks — the main families and how to choose (or justify) one
AI across the lifecycle — where it genuinely helps, with prompts, and where it must not be trusted
Governance, risk, templates and a glossary

Read online HTML Download DOCX

Price it & sell it

Pricing · proposals · sales

Guide · 31 chapters · 7 parts

Winning the Work

A sales and marketing playbook for software professionals. How to price on value instead of hours, write proposals engineered to close, run a repeatable sales process, sell a product into a specific industry, and market yourself as a developer — with scripts, templates and worked examples throughout.

Who it's forIndependent developers, small software firms, and anyone selling a software product or custom development who is uncomfortable with the selling part.

Pricing that wins — cost vs. market vs. value pricing, the psychology of price, tiers, anchoring, and how to talk about money without flinching
Proposals & SOWs that close — the structure that persuades, why the section order matters, risk reversal, and copy-and-adapt templates
The sales engine — pipeline math, cold email & call scripts, qualifying, and demos that sell
After the demo — the 8-step follow-up and close sequence, where most deals are quietly lost
Objections, closing and referrals
Selling vertical SaaS — ROI models, de-risking the switch, and a diagnostic for "why aren't we closing?"
Marketing yourself — positioning across Windows, web and mobile; getting found; raising your rates
A 30-60-90 day plan, metrics, templates and a glossary

Read online HTML Download DOCX

Protect it & get paid

Contracts & collections

Guide · 8 parts

Getting Paid & Protecting Yourself

The library takes a project brilliantly up to the signature — this is what happens next. How to structure payment so you are never exposed, write a contract that holds up when a deal sours, and actually collect what you are owed. Its argument: getting paid is a design decision, not an afterthought.

Who it's forIndependent developers and small firms who have felt the particular dread of finished work and an unpaid invoice.

Structuring the money — deposits, milestone vs. time-and-materials, payment terms, late fees and retainers
The contract that protects you — the NDA / MSA / SOW stack and the clauses that actually matter
IP & your reusable assets — who owns the code, carving out your own tools, and source-code escrow
Acceptance, warranty & liability — defining “done,” the deemed-acceptance clause, and the liability cap
Invoicing & collections — unarguable invoices, the chase sequence, and when to stop work
Protecting the business itself — the liability shield, insurance, and back-to-back subcontractor terms
Templates — a before-you-sign checklist, ready-made chase emails and a glossary

Read online HTML

Secure it

Security & compliance

Guide · 8 parts

Security & Compliance for Small Vendors

Do a project brilliantly, price it, sell it, get paid — and then a three-hundred-line security questionnaire lands in your inbox and the deal stalls. This is how a small vendor with no security team clears that gate: a posture that’s genuinely sound and proportionate, honest answers to the reviews that block enterprise deals, responsible handling of customer data, and working out which compliance obligations actually apply to you. Its argument: you can’t credibly claim a security posture you don’t actually have — and increasingly, you’ll be asked to prove it.

Who it's forIndependent developers and small firms discovering that “we take security seriously” is no longer something you can simply assert.

Why it decides deals — security as a sales gate, the real cost of a breach, and right-sizing to your actual risk
The security questionnaire — answering honestly, building a reusable answer library, and the red flags that sink you
A sensible baseline — MFA, least privilege, encryption, tested backups, patching, and the suppliers you inherit
Handling customer data — what you hold, data minimization, access logging, and planning for the bad day
Compliance without drowning — what actually applies to you, DPAs and contract terms, and when certification is worth it
A credible posture on a budget — policies that are true, evidence over claims, and a security overview page
Security as a selling point — getting ahead of the question, what buyers want, honest limits, plus baseline & incident checklists

Read online HTML

Run it

Hosting, updates & operations

Guide · 8 parts

Running It in Production

Shipping isn’t the finish line — it’s the day you start operating. This is the discipline the delivery guide hands off to: keeping shipped software alive, reliable, and affordable in production. Hosting and releases, monitoring and updates, tested backups and calm incident response, and keeping the operational bill from eating your margin. Its argument: reliability isn’t a state you reach but a practice you keep — and the boring, invisible, preventive work is the work that matters most.

Who it's forThe developer or small firm running software that other people depend on, whether a product or a client’s system.

Hosting & infrastructure — managed vs. self-run, and right-sizing to what you actually run
Deployment & releases — repeatable, boring releases with real environments and a tested rollback
Reliability & monitoring — what uptime really costs, and knowing you’re down before customers do
Updates in production — a patching cadence, and changing live systems safely
Data operations — backups you’ve actually restored, and the danger of migrations
Incident operations — realistic on-call for small teams, and the calm, prepared response
Operational cost — watching the bill, and cost that scales with revenue, not ahead of it

Read online HTML

Grow it & keep it

Support & recurring revenue

Guide · 8 parts

From Project to Product

The library gets a project defined, won, delivered and paid — this is what turns that ending into an income base. How to convert finished work into support contracts, retainers and eventually recurring revenue: the on-ramp from “software consultant” to “software business” that most builders never plan deliberately. Its argument: project revenue is a series of endings; a business needs a middle.

Who it's forAnyone who has felt the anxiety of a great month followed by an empty pipeline, and wants income they can plan a year around.

The revenue ladder — project → warranty → retainer → product, and the MRR/ARR that change your valuation
Warranty vs. paid support — drawing the line cleanly and turning warranty expiry into a support sale
Support contracts & SLAs — response vs. resolution, severity levels, and ticketing discipline
Retainers & support tiers — billing in advance, packaging tiers, and pricing reserved capacity
Maintenance as a discipline — preventive vs. reactive, technical debt, and selling upkeep instead of absorbing it
From services to product — recognizing the generalizable, the productization spectrum, pricing and churn
Making the transition — protecting cash flow, keeping your base, and not out-selling your support capacity

Read online HTML

Mind the money

Financial management

Guide · 8 parts

The Money Behind the Business

Plenty of profitable-looking software businesses fail — not because they weren’t earning, but because they ran out of cash, or the tax bill arrived for money already spent. This is the financial management of the whole business, beyond any single project: cash flow, tax discipline, paying yourself sustainably, understanding which work actually makes money, and the reserves that turn feast-and-famine into something you can live on. Its argument: profit is an opinion; cash is a fact — and running out of it is the one mistake a business can’t survive.

Who it's forThe developer or owner who’s good at the work but was never taught the money — earning well, yet always one bad month from trouble.

Cash flow — cash vs. profit, the timing gap, and always knowing your runway
Seeing the money — separating and recording it, and the handful of numbers to watch
Tax discipline — setting aside as you earn, and escaping the tax trap
Paying yourself — a sustainable wage, and the take-vs-reinvest choice
Unit economics & margins — knowing what actually makes money, and shifting the mix
The money side of pricing — why raising your rates is the highest-leverage move, and pricing for the whole business
Planning & reserves — the cash buffer, and planning for the lean months every business has

Read online HTML

Build a team

Hiring, partners & contractors

Guide · 8 parts

From Solo to Small Team

The first person you bring on changes what your business is — from someone who does the work into someone responsible for others doing it. This is the leap most independent builders circle for years: when and whether to hire, what to bring on first, contractors vs. employees, the genuinely hard skill of delegation, the equity conversation with a partner, and the shift from doing the work to leading it. Its argument: growing a team is a new job, not just more of you — and it must be consciously learned.

Who it's forThe solo founder stretched thin and weighing a first hire, and the small firm taking its first steps as a team.

When & whether to hire — reading when you’re the bottleneck, and whether you can truly afford it
What to hire first — the highest-leverage gap, and hiring your weakness vs. your strength
Contractors vs. employees — the spectrum, and getting classification, IP and back-to-back terms right
Learning to delegate — letting go, and handing over outcomes rather than micromanaged tasks
Partnerships — the equity conversation, and getting it in writing while you’re still friends
How a small team works — standards set by example, and protecting the closeness that makes it good
Becoming a manager — the shift from doing to leading, and what your people actually need

Read online HTML

Scale it — or don’t

Growth & staying small

Guide · 8 parts

Scaling — or Staying Small

The business world assumes growth has only one answer. This guide questions it: whether to grow, how much, and how — or whether to deliberately stay small. The real and underrated case for staying small, what actually limits a business, the levers of genuine scale, scaling on systems rather than heroics, the serious risks of growing wrong, and matching your business’s size to the life you actually want. Its argument: scale is a means, not an end — the right size is the one that gives you the life and outcomes you actually want, which is sometimes large and very often not.

Who it's forThe successful independent or small firm at a crossroads — doing well, and facing the question of whether to become more.

The question most people skip — do you even want to scale, and which game are you playing?
The case for staying small — the underrated path, and freedom over size
What actually limits you — finding the real bottleneck: demand, capacity, or systems
The levers of scale — the distinct ways to grow, and the ones that don’t cost you more hours
Scaling on systems — systems over heroics, and what to actually systematize
The risks of scaling — growing broke, and losing what made you good
Choosing your path — matching size to what you want, and revisiting the choice as you change

Read online HTML

Sell the business

Valuation & exit

Guide · 8 parts

Valuing & Selling a Software Business

Every business you build ends one of three ways — it winds down, it’s passed on, or it’s sold. This is the capstone: what actually makes a software business worth buying, how buyers put a number on it, how to build that value deliberately over years rather than scramble for it at the end, and how to run a sale so the value you created is the value you keep. Its argument: a business is worth what someone will pay to own its future without you — so the value is built, or destroyed, in how you run it long before you ever decide to sell.

Who it's forIndependent developers and small firms who’ve never thought of their work as a saleable asset — and will be surprised how much of its value is decided years before any sale.

What makes it valuable — what you’re actually selling, the value drivers, and why risk is a discount
How it’s valued — profit vs. revenue multiples, why recurring revenue changes the math, and the metrics buyers price on
The owner-dependency problem — why a business that’s really just you is worth little, and how to fix it
Preparing for sale — clean books, IP hygiene, locking in the recurring base, and the data room
The sale process — when to sell, who buys, finding buyers and advisers, and price versus terms
Structuring the deal — asset vs. share sale, earnouts and holdbacks, the handover, and the tax that decides what lands
Due diligence & closing — surviving the buyer’s inspection, plus a value-driver scorecard and readiness checklists

Read online HTML

Side track

Software that runs the business

For in-house builders

Guide · 8 parts · a separate track

Software That Runs the Business

Most software in the world is never sold to anyone — it's built inside companies that run on it. When the system you build is your employer's advantage rather than a product, the usual playbook doesn't apply: there's no customer, no invoice, no market to price it. This separate guide is for that builder — how to justify an internal build, build and run it well, keep it an asset instead of a liability, and get the credit you're owed for value that shows up as costs avoided rather than revenue booked. Its argument: software built to run a business earns its keep invisibly, so the builder's real job is to make invisible value visible and defensible.

Who it's forThe engineer or small team building software inside a company that doesn't sell software — the person who quietly becomes the reason a whole department works.

The invisible asset — why in-house value is real but shows up as no revenue line, only costs avoided and capabilities gained
Making the case — justifying a build in money and risk, and build-vs-buy from the buyer's seat
Building & running it well — the delivery, security, and operations craft, adapted for a world with no customer
The single point of failure — mission-critical software resting on a team of one, and how to defuse it
Technical debt as business risk — why in-house software rots in the dark, and how to get the fix funded
Asset or liability — when in-house software is a genuine moat, and when it's cost and lock-in in disguise
Getting the credit — capturing the value you created, and the path from builder to trusted advisor

Read online HTML

Use it

Working tools

One page · print it

After the Demo — Cheat Sheet

The single highest-leverage page in this library, condensed to one sheet you can keep beside the phone. Deals rarely die in the demo — they die in the silence afterwards.

Who it's forAnyone who gives demos and then wonders why the prospect went quiet.

The 8-step follow-up sequence, with timings
A day-by-day cadence after the proposal goes out
The six objections you'll actually hear — and fast answers
Five scripts to steal: the recap, the value nudge, the break-up email, asking for the decision
Always Do / Never Do

Open & print HTML · 1pp

Spreadsheet · ready to use

Deal & Pipeline Tracker

Log every opportunity, and the dashboard tells you exactly where your deals are dying — and why. "We're not getting enough customers" is never the real problem; it's a symptom of one specific leaking stage. This finds it.

Who it's forAnyone running a pipeline who is guessing rather than measuring.

Pipeline — one row per deal, with dropdowns, weighted values, and stale deals (untouched >7 days) flagged red
Dashboard — win rate, pipeline value, and a funnel showing how many deals died at each stage
Why we lose — losses grouped by reason, each paired with its fix
Source effectiveness — which of cold calls, email or referrals actually win
Activity log — so nothing goes cold

Download XLSX

Interactive · runs in your browser

Project Profitability Tracker

The delivery-side mirror of the pipeline tracker. Log what you quoted against what each project actually cost, and the dashboard shows which kind of work quietly loses you money. A full pipeline and a busy team can still hide a loss-making category — this finds it.

Who it's forAnyone whose projects feel busy but whose margin never seems to match the effort.

Quoted vs. actual — hours estimated against hours spent, so you can tell a pricing problem from an estimation one
Margin per project — revenue, cost, profit, effective rate and overrun, with loss-making projects flagged
Profit by type — every category of work ranked worst-first, so the leak has nowhere to hide
The two-question diagnosis — did we overrun, or underprice? — pointing you straight at the fix
Yours to keep — saves locally in your browser, with one-click CSV export

Open & use HTML

How to use these together

Suggested path

If you only have a weekend

Read Winning the Work, Part IV — especially Chapter 15, "After the Demo." It is the most commonly skipped part of selling software, and the most expensive.
Print the cheat sheet. Put it where you make calls.
Open the tracker and back-fill your last 10–20 opportunities. Record the stage each one died at. The pattern will be uncomfortable and extremely useful.
Read the Delivery Guide's estimation chapter before you quote your next project. Then sell a small paid discovery instead of guessing at a fixed price.
Before you send your next contract, run the pre-signature checklist in Getting Paid & Protecting Yourself — and set the deposit and milestones so money-in never trails work-done.
Open the Project Profitability Tracker and back-fill your last 10–20 projects. It shows which kind of work quietly loses money — usually not the one you'd guess.
Finally, take the knowledge assessment for your track. Being tested fixes the material in memory far better than re-reading — and the questions you miss point you straight at the sections worth a second look.

If you’re building the whole business

The twelve guides run in a deliberate order — the life of a software business, from first idea to final sale. Read them roughly in sequence, or jump straight to wherever you are now.

First, Setting Up Shop — form the business and put its structure, finances, protection, and habits in place.
Finding Your Product & Market — decide what to build and for whom, and validate demand before you write any code.
The Custom Software Delivery Guide — plan, estimate, build, test, and ship it so every phase produces something you can quote from.
Winning the Work — price on value and run a repeatable sales process. Keep the cheat sheet by the phone and the Deal & Pipeline Tracker open.
Getting Paid & Protecting Yourself — structure payment and contracts so you’re never exposed and money-in never trails work-done.
Security & Compliance for Small Vendors — build the posture and answer the reviews that unblock bigger customers.
Running It in Production — keep what you’ve shipped reliable, current, and affordable.
From Project to Product — turn delivered projects into support, retainers, and recurring revenue. Watch the economics with the Project Profitability Tracker.
The Money Behind the Business — run the cash, tax, pay, and reserves that keep the whole thing alive.
From Solo to Small Team — when you become the bottleneck, grow capacity with hires, contractors, and real delegation.
Scaling — or Staying Small — decide, deliberately, whether and how to grow — or to stay small on purpose.
Finally, Valuing & Selling a Software Business — build something worth buying, and one day realize its value.

Then take the knowledge assessment for your track — being tested fixes the material far better than re-reading, and the questions you miss point straight at what to revisit.

Prove it — and earn your certificate

Assessment

Five tracks · 134-question bank · shared core

The Software Business Library Knowledge Assessment

Reading a guide and understanding it are different things. Selling and delivering are usually different people's jobs — so there are five separate tracks, each ending in its own printable Certificate of Achievement.

Track A · Delivery & Estimation 40 questions — requirements, design, estimation & quoting, testing, release and AI. For the person who defines, builds and prices the work.

Track B · Pricing & Sales 44 questions — value pricing, proposals & SOWs, the sales process, after-the-demo follow-up and vertical SaaS. For the person who prospects, demos and closes.

Track C · Running the Business 40 questions — setting up shop, getting paid & protecting yourself, security & compliance, operations, and financial management. For the owner keeping a healthy, protected business running.

Track D · Product, Team & Growth 40 questions — finding your product & market, recurring revenue, hiring and team, scaling, and valuing & selling. For the founder building, growing, and one day selling.

Track E · Full Assessment 134 questions — every section of all twelve guides. The comprehensive track, for owners, leads, and anyone who does it all.

Every track shares a common coreWhoever sells and whoever builds each need the basics of the other's job — that crossover is exactly where money leaks. If sales doesn't understand delivery, they promise undefined scope and quote from a conversation. If delivery doesn't understand sales, they price on cost and treat discovery as unpaid overhead. So a Shared Fundamentals section appears in all five tracks. Nobody gets to skip it.

Why take itTwo reasons. It verifies you actually absorbed the material rather than skimmed it. And — less obviously — being tested is itself one of the most effective ways to commit information to memory. Retrieving an answer under pressure fixes it far more firmly than re-reading ever will. Getting a question wrong and then reading the section that explains it is the single most valuable thing that can happen here.

Passing requires 80% overall and at least 65% in every section — so nobody passes by acing their comfort zone and skipping the crossover
A perfect score earns a Certificate "with Distinction" — gold seal, distinct wording. Your score is printed on the certificate, and retakes are unlimited: keep going until it says what you want it to say
Instant scoring, with a per-section breakdown showing exactly where you're weak
Full review of every question you missed — the correct answer, why it's correct, and a direct link to the exact section of the relevant guide
A distinct certificate for each track, personalized with your name, score and date — none issued below the pass mark
No time limit; retake as often as you like

Choose your track 5 tests

Note: this is a self-paced educational assessment based on this library. It is not an accredited degree, a professional license, or a government-recognized certification.

The eight ideas underneath all of it

If you read nothing else

On what to build

Fall in love with the problem, not your solution. The most expensive software is the kind nobody wanted. Find a real problem first; let the solution follow.

On quoting

You cannot accurately price what you have not defined. Quoting from a conversation instead of a specification is one of the most common causes of unprofitable projects.

On selling

People don't buy software. They buy a better version of their business. Stop describing what it is; describe what it does for them, in their money.

On competition

Your biggest competitor is "do nothing." Many deals are lost to inertia, not to a rival. Make the cost of waiting vivid and saying yes feel safe.

On follow-up

Deals die in the silence after the demo. A mediocre demo with relentless, helpful follow-up beats a brilliant demo with none.

On money

Profit is an opinion; cash is a fact. A business can be profitable on paper and still die of an empty account. Watch the cash, set aside the tax, keep a buffer.

On growth

Stop selling your time; start selling something that keeps earning. Being paid once for work done once is a job. Recurring revenue is a business.

On what you're building

If the business is really just you, you own a job, not a business. Build something that runs — and grows, and one day sells — without you at the center of it.