Why I Won’t Pay to Review Your Custom NDA and Service Agreement

I’m willing to sign reasonable contracts.

I’m willing to discuss confidentiality, intellectual property, ownership of work product, background technology, non-use restrictions, and the practical risks involved in a software engagement.

I’m even willing to consider a client’s custom NDA or service agreement.

But I will not personally pay an attorney to review legal documents that a prospective client requires before the engagement has even started.

That is now a firm business policy.

I Already Have a Contractual Framework

My consulting business does not operate without contracts.

I already work through a contractual framework that has been reviewed and approved for my business. On most freelance platforms I work with, there is an established set of service contract terms covering areas such as payment, confidentiality, work-product ownership, and background technology.

A client may decide those terms are not sufficient for their particular situation. That is their right.

They may have unusually sensitive technology. They may be filing patent applications. They may want additional limits on disclosure, subcontracting, competitive use, reverse engineering, or the handling of their confidential information.

I am willing to listen to those concerns.

But once a client decides that the existing framework is not enough and requires a bespoke legal agreement, the economics of forming the relationship change.

The client is no longer asking me only to perform software development.

They are asking me to participate in a custom legal process before I am allowed to begin.

I Will Not Sign an AI-Drafted Agreement Without My Attorney

AI has made contract review dramatically more accessible.

It can identify unusual clauses, compare revisions, explain legal concepts, surface contradictions, and help two parties make substantial progress before involving attorneys.

I use those capabilities.

But AI-assisted drafting is not a substitute for independent legal review.

Even if I have personally reviewed every paragraph, negotiated every sentence, and agree with the final language in principle, I will not sign a custom NDA or service agreement without having my attorney review it.

That is not because I assume the other party is acting dishonestly.

It is because custom contracts can create risks through the interaction of multiple provisions. A clause may look acceptable by itself but operate differently when combined with provisions concerning intellectual property, remedies, survival periods, governing law, evidentiary standards, or future work.

My attorney may identify problems that neither party’s AI analysis identified.

My attorney may also recommend changes to provisions that both parties thought were already resolved.

That is precisely why the review is necessary.

The First Legal Review Is Rarely the Last

A prospective client may imagine a simple process:

1. We agree on a draft.
2. I send it to my attorney.
3. My attorney approves it.
4. We sign and begin.

That is possible.

It is not the outcome I can safely assume.

A more realistic process may be:

1. The client and I negotiate a draft.
2. My attorney reviews it and proposes changes.
3. The client objects to some of those changes.
4. The client sends the revision to their attorney.
5. Their attorney proposes additional language.
6. My attorney must review the new version.
7. Another round begins.

Every round costs money.

And throughout that process, there is still no guarantee that the client will hire me, that the project will begin, or that the parties will ever reach agreement.

I could spend thousands of dollars merely determining whether a business relationship is possible.

That is not a cost I am willing to absorb.

The Economics Often Make No Sense

Businesses commonly pay their own legal fees when negotiating contracts.

But that convention only makes economic sense when the expected value and certainty of the transaction justify the expense.

Consider a software project expected to generate between $10,000 and $20,000.

A $1,500 initial legal review represents:

• 15% of a $10,000 project
• 7.5% of a $20,000 project

That is before platform fees, taxes, unpaid negotiation time, delivery costs, and any additional rounds of attorney review.

It is also before accounting for the possibility that the project never starts.

If I spend $1,500 and the client later rejects my attorney’s changes, delays the project, reduces the scope, or simply chooses not to proceed, I am left with the legal bill and no revenue.

I have worked on consulting engagements worth hundreds of thousands of dollars that began with standard commercial terms and essentially no legal expense.

It would be irrational to spend a meaningful percentage of a smaller project’s potential revenue negotiating a custom agreement before the client has made any binding commitment to purchase development work.

This Is Not About Refusing Client Protection

My policy is not:

I will never sign a custom NDA.

It is:

I will not finance the legal review of a custom agreement required by a prospective client before a paid engagement exists.

There is an important difference.

A client who wants additional protection may receive it. But the additional process must be treated as part of the cost of the client’s requirement.

The client is requesting something beyond the existing contractual framework. The client is asking me to assume new restrictions, representations, obligations, or legal risks.

I need independent counsel to evaluate those terms.

I should not have to make an unsecured legal investment merely for the chance to become the client’s developer.

My Policy for Custom Agreements

When a prospective client requires a custom NDA, service agreement, intellectual property agreement, or similar legal document, my process is now straightforward.

We may discuss the business terms and work toward a substantially final draft.

Before I authorize my attorney to review it, the estimated legal-review cost must be paid through an active contract using an approved on-platform process.

My attorney then performs the review.

If the client or the client’s attorney makes further revisions that require another review, each additional round must be separately estimated, approved, and funded before I authorize that work.

The legal-review engagement is separate from the software-development engagement.

Payment for legal review does not obligate either side to proceed with development. It simply ensures that I am not personally financing the client’s custom pre-engagement legal process.

If the agreements are finalized, the software work begins under a separate hourly contract.

Why Upfront Payment Matters

I do not treat this as a reimbursement.

Reimbursement would require me to pay my attorney first and then hope the client pays me afterward.

That leaves me exposed to the exact risk the policy is intended to eliminate.

The legal-review amount must be paid before I authorize the review.

This is not unusual in professional services. Lawyers commonly require retainers. Consultants commonly require deposits or prepaid blocks of time. Vendors frequently require payment before incurring a client-specific third-party expense.

The principle is simple:

I do not advance third-party costs on behalf of a prospective client.

This Policy Filters for the Right Clients

A good business policy does more than reduce risk. It also improves client qualification. Every consulting engagement is a business decision for both sides.

A client who is comfortable with the existing contractual framework can begin efficiently.

A client with a legitimate need for custom protection and a serious budget can fund the legal process required to create it.

A client who demands extensive custom protections, repeated revisions, independent attorney review, and no financial commitment is asking me to bear all of the downside while retaining complete freedom to walk away.

That is not a balanced transaction.

The policy allows that mismatch to become visible before I invest additional time and money.

Custom Legal Complexity Is Part of the Project Cost

Clients sometimes treat contract negotiation as if it exists outside the economics of the project.

It does not.

If an engagement requires:

• a custom NDA,
• a custom service agreement,
• multiple rounds of attorney review,
• specialized intellectual-property provisions,
• competitive-use restrictions,
• or extensive negotiation over background technology,

those requirements are part of the cost of establishing the engagement.

They may be justified.

But they are not free.

The more complex the client’s legal requirements become, the more important it is to ask whether the size and certainty of the project support that complexity.

For a large, committed, long-term relationship, substantial legal negotiation may be entirely rational.

For a speculative prototype or short-term engagement, it may cost more to form the relationship than the opportunity reasonably supports.

The Boundary Is Simple

I am willing to consider custom agreements.

I am willing to negotiate in good faith.

I am willing to have my attorney review the final documents.

I am not willing to pay legal fees merely to find out whether a prospective client might eventually hire me.

If a client requires a custom legal framework beyond the agreements I am already prepared to use, the client must fund the independent review necessary for me to evaluate and sign it safely.

That is not hostility toward contracts.

It is basic transaction discipline.