Every software development firm reaches the point where referrals stop scaling and somebody suggests buying leads. What follows is usually an expensive education, because the phrase covers at least four different products: introductions from a broker, appointments booked by an outbound agency, enquiries generated by your own marketing, and directory listings sold on a pay per enquiry basis. They differ enormously in cost, quality and what happens when they stop. This page describes the realistic sources, the qualification questions that decide whether a lead is worth anything, and how to check a supplier before committing budget.
The four things sold under one name
Brokered leads are contact details for someone who filled in a form somewhere else, usually sold to several firms at once, which means you are competing on response speed rather than on fit. Booked appointments come from outbound teams who email or call at volume; they are more expensive, more variable, and heavily dependent on the list and the script. Inbound enquiries generated by your own content and search presence cost more up front and less over time, and they arrive pre-sold because the prospect chose you. Directory and marketplace enquiries sit between the two, with the platform owning the relationship and the buyer usually comparing three or four firms. Only the third of these builds an asset. The others rent access to demand, and the day you stop paying the pipeline stops, which is why firms that rely on them are permanently exposed. Most development firms that get this right end up investing in their own site and technical authority alongside whatever they buy, which is a slower and considerably cheaper way to be found.
What qualification actually means for a development lead
A contact is not a lead. For custom software, four facts determine whether a conversation is worth an hour of a senior engineer's time: is there a budget and does anyone know roughly what it is, is there a named decision maker and does the person you are speaking to have access to them, is there a deadline driven by something real, and is the problem actually a software problem. Ask any supplier which of those they verify before passing a lead, and ask to see the exact questions they ask. Vague answers here predict everything that follows. Then agree what a replacement looks like: which conditions make a lead invalid, how you report one, and how quickly the credit appears. Suppliers who will not define an invalid lead in writing are selling volume and expecting attrition to be your problem.
Outbound, and the rules it has to respect
If a supplier proposes cold email at volume, that campaign is your reputation and, to a degree, your legal exposure. The Federal Trade Commission's compliance guidance for the CAN-SPAM Act sets out the requirements for commercial email: no deceptive headers or subject lines, a clear identification of the message as an advertisement, a valid physical postal address, a working opt out mechanism, and opt out requests honoured promptly. It also states plainly that the law holds the company whose product is promoted responsible, even where another company sends the mail. Ask which domains the outbound is sent from, because sending from your primary domain and getting it burned is a far bigger cost than the campaign fee. Ask how the list was built, ask what happens to bounced and complained addresses, and ask to review the sequence before it runs. If the answers are evasive, the campaign is being run in a way you would not authorise if you could see it.
How to price it and how to judge it
Compare sources on cost per qualified opportunity, not cost per lead, and be strict about what qualified means. A development project worth a substantial fee can justify a high cost per lead, which is why this market supports prices that look absurd next to consumer lead generation. The trap is the conversion rate assumption. Ask a supplier for the rate their existing clients achieve from lead to proposal and from proposal to signature, then discount it, because their clients probably respond faster than you will. Run a paid pilot with a fixed lead count and a fixed window, track every lead to an outcome in your own system rather than the supplier's dashboard, and hold the review at the end whether it went well or badly. Also track your own response time, because on shared leads it is frequently the only variable that separates the firms that win from the ones that complain about quality.
Questions people ask about software development leads
Are purchased software development leads worth it?
They can bridge a gap while your own demand generation matures, and they are rarely a good permanent foundation because the price rises, the exclusivity falls and you never own the relationship. Treat them as rented pipeline and budget in parallel for a channel you keep.
How do I tell an exclusive lead from a shared one?
Ask directly, get it in the contract, and ask how many firms receive each enquiry. Then test it: on your first calls, ask the prospect how many other firms have contacted them. Prospects answer that honestly and the answer tells you what you actually bought.
What conversion rate should I expect?
It varies too much by lead type and deal size for any general figure to be useful, and a supplier quoting one without reference to their own client data is guessing. Run a pilot, measure your own rate, and use that number for every subsequent decision.
Is outbound email still effective for development work?
It works when the targeting is narrow and the message references something specific about the recipient's business, and it fails when it is sent at volume with a generic pitch. Whichever you run, it must comply with commercial email law, and you carry responsibility for that even when an agency presses send.