Good legal support should help you make better business decisions

You bring a product change, customer contract or launch plan to a lawyer. You need to know what the company can do next. You leave with a list of uncertainties, a request for more analysis and no recommendation.

That is frustrating even when every concern is technically justified. Good legal support should turn an identified risk into an informed decision: explain the consequence, show the available options and recommend a course of action.

From my experience working with technology businesses, legal advice becomes useful when it reaches the product, sales process and operational choices. A polished document can record those choices. It cannot make them on the company’s behalf.

What you will learn

A warning needs an explanation and options

Sometimes a lawyer needs to say stop. A proposed action may be unlawful, a customer claim misleading, a use of personal data unjustifiable or a contractual exposure unacceptable for the business. Speed does not remove those issues.

But “this is risky” leaves several questions unanswered. What could happen? How likely or uncertain is that consequence? Which assumption changes the answer? Can the company change the process, wording, scope or allocation of responsibility?

“It depends” can be the start of a useful answer if the lawyer identifies the missing facts and explains the decision they affect. For example: “We need to know whether customers can export their data before termination. If they can, this version of the exit process may work. If they cannot, we need to change the product flow and the terms.”

The business should understand which part of the advice is a legal requirement, which reflects an agreed obligation, and which is the lawyer’s preferred negotiation position. Treating all three as equally mandatory makes prioritisation unnecessarily difficult.

Start with the business goal and the actual product

A request to “review the terms” rarely contains enough context. Useful advice starts with what the company sells, who buys it, how payment works and what the proposed change is meant to achieve.

For a SaaS product, the relevant facts may include:

• when an account is created and when a paid subscription starts;
• what functionality is available on each plan;
• how suspension, renewal and cancellation work;
• whether customers can export their data and for how long;
• what support and availability the sales team promises;
• who controls user content and access permissions.

For an online store, the purchase flow, displayed prices, promotions, complaints and cancellation process matter. The applicable consumer rules depend on the market and transaction; a generic set of terms cannot resolve that assessment.

For a startup, legal work should follow who contributes to the project, owns the code, controls repositories and makes decisions. Founder arrangements and IP due diligence are useful examples, with local implementation addressed where it affects the answer.

A lawyer who sees only the document may miss a mismatch between the wording and what the company can actually deliver.

Some risks can be managed without delaying the whole project

There is usually more work available than time or budget. The company needs to distinguish an immediate blocker from an issue that can be addressed through a staged plan.

A lawful business choice may involve residual risk. The company might accept a negotiated liability position, narrow an initial release, change a customer promise or strengthen an operational control. The advice should explain what each option leaves unresolved.

Conscious risk acceptance is not permission to proceed with an unlawful activity. Before describing something as acceptable, establish what is mandatory and whether the proposed mitigation actually meets that requirement.

A useful recommendation identifies the decision-maker, the remaining exposure and the point at which the decision should be reviewed. “The business accepted the risk” is too vague to guide the team.

If a simpler first phase is viable, describe its boundaries. If the full review must happen before launch, explain why and identify the facts or work needed to reach a decision. A clear stop can be helpful when it comes with a route to resolution.

A practical example: a launch promise the product cannot yet meet

Consider a hypothetical SaaS team preparing its first enterprise contract. Sales proposes immediate account closure on termination. The product can suspend access immediately, but data export still requires manual support work.

A document-only review might edit the termination clause and leave the team with an impossible promise. A useful review asks engineering about the export process, support about capacity and sales about the customer’s requirement.

The team can then assess concrete options: introduce an export window supported by a defined manual process, limit the initial offering to customers whose needs that process can meet, or implement automated export before signing. Each option has a different effect on delivery time, customer experience and cost.

The chosen contract must reflect the process the company will run. Any mandatory legal requirements and commitments to existing customers still need to be checked. The example illustrates how advice supports a decision; it does not establish that one export period works for every product or market.

Warning signs in a legal review

The concern is a pattern of advice that consistently leaves decisions unresolved. Watch for these signals:

• The lawyer does not ask about the customer, product or business goal.
• Every issue receives the same urgency, regardless of consequence.
• A recommendation cites uncertainty without identifying the missing fact.
• The proposed document grows while the underlying process remains unexplained.
• No one can tell which points are mandatory and which can be negotiated.
• After the meeting, the team has no owner, deadline or next step.

A difficult answer is not itself a warning sign. Nor is a necessary request for evidence. What matters is whether the review explains the reason and helps the company reach a defensible decision.

Leave the meeting with a short action plan

Ask the lawyer to set out what must happen before launch or signature, what can follow in a second phase and what lawful residual risks require a business decision. Connect each item to an owner and a date.

The plan should also identify documents and operational changes separately. A revised customer notice, access control or support workflow may be as important as a contract clause. If a recommendation depends on an assumption, write that assumption down and assign someone to confirm it.

You can make the review more useful by providing:

• the business objective and deadline;
• a demonstration or short description of the product flow;
• the relevant customer promises and existing agreements;
• the technical constraints and available alternatives;
• the person authorised to make the commercial decision.

Ask for a recommendation as well as an analysis. If the answer remains uncertain, agree what evidence is needed, who will obtain it and when the team will return to the question.

Bring legal support into decisions earlier

Legal work is easier to use when it happens while the team can still change the process. Waiting until the final signature or release often turns a manageable choice into a costly deadline problem.

For founders, ongoing legal support can provide a regular place to discuss those decisions. The useful measure is whether the work gives the team clear priorities, workable documents and an agreed next step. The same expectations apply to a focused technology contract or product review.