Skip to main content
The Work Behind the Answer

Essay 03 · The Cedar acquisition

Can We Close on Friday? Start With Monday.

A transaction can be ready for signatures before it is ready for customers.

Watch the one-minute companion exercise

Watch the complete narrated film (11:31)

· 9 min read

Fictional teaching example. No measured Talden product-performance result.

It is Wednesday. The question is familiar: “Can we close on Friday?”

Cedar, our fictional buyer, is acquiring a logistics-software business. Two consents are missing.

Someone asks counsel to prepare a waiver.

Open the software license first.

It requires the licensor’s written permission for the business to keep using a component after leaving the seller’s group. Engineering confirms that the business currently depends on that component.

Cedar may be able to waive a condition to its own obligation to close. That does not supply the right to operate the software afterward.

Monday has entered the conversation.

This is a fictional transaction with stipulated documents and figures, used to examine AI-assisted preparation. The useful work is an inspectable account of how rights, operations, money, and authority fit together. Nothing in the example establishes an observed Talden result.

The waiver has a limited job

Cedar’s signed purchase agreement contains two relevant provisions: Seller promises to deliver landlord and software-licensor consents, and delivery is a condition to Buyer’s obligation to close.

Buyer may waive that condition only in writing. Neither consent has arrived; no waiver is approved.

The underlying license covers continued use after separation, including Seller supplying the licensed service to a former affiliate. Having Seller provide transition services therefore does not, on these terms, remove the permission requirement.

Counsel also needs to preserve the distinction between the closing condition and Seller’s delivery promise. The condition described here does not expressly release that promise. A proposed waiver should identify whether it affects only the condition or also the promise and related claims.

If Cedar wants to preserve remedies, check any reservation against the agreement’s survival, release, and exclusive-remedy provisions, governing law, and the parties' conduct. The words “rights reserved” are an objective to implement, not assurance of dependable recovery.

Even an enforceable damages claim leaves an operational question: what happens to customers while the service is unavailable? Recovery may help later. Its scope, cap, timing, and collectibility matter. It cannot be assumed to supply present operating capability.

The landlord issue also remains open. Read the lease, its consent requirement, and the consequences for the premises the business uses. Finding a serious software issue does not dispose of the other consent.

The useful question has changed from “Which signatures are missing?” to “What does each permission enable?”

Three clocks, one proposed closing

The transition-services agreement provides support through day 90 after closing.

Engineering estimates migration by day 120. Its separately identified delay scenario is day 150.

Sufficient license permission would solve one problem. Existing support still ends 30 days before the current migration estimate and 60 days before the delay scenario.

Preserve what those dates mean. Day 90 is a contractual term. Day 120 is an estimate. Day 150 is a scenario. Calling day 150 “the migration date” would quietly turn uncertainty into an apparent commitment.

Now read the financing commitment. It expires at 5 p.m. Friday. A banker’s email says an extension is being discussed. The packet contains no executed extension.

Waiting for consent needs a funding plan. Extending financing, if achieved, buys funding time; it does not supply software permission or lengthen transition support.

Ask what the licensor still requires, which work determines the migration timetable, and what the lender will commit to. Guessing at a counterparty’s private motive may make the story more colorful. It does not establish the next executable step.

A correct summary can leave the decision unfinished

An assistant could accurately report: “Two consents remain outstanding. Transition support runs for 90 days. Migration is estimated at 120 days. A financing extension is under discussion.”

Every sentence is consistent with the fictional record. The client must still assemble the consequence.

I would give the system a more useful assignment, using only materials the lawyer has determined may be supplied to the configured tool: “Prepare a decision brief on whether the proposed Friday closing has an established operating and funding plan. Identify consent requirements in the purchase agreement and underlying contracts. Compare transition services with the engineering evidence. Identify funding expiration and extension status. For each material proposition, give its source location, document status, qualification, and the person who can confirm its factual premise. Distinguish available choices from proposals needing another party’s agreement. Identify missing information that could change the recommendation. Prepare next steps for review.”

Then test the work. An assertion that Seller can supply the service after closing needs language permitting service to a former affiliate. A general promise of transition support cannot establish the licensor’s permission. The migration date needs the current engineering evidence. An extended funding date needs the operative commitment and its conditions.

Ask for the strongest supported reason the proposed route could fail. Permit “The supplied record identifies none,” with untested assumptions separately stated. Requiring an objection at all costs invites invented problems; requiring support makes the challenge useful.

California’s 2026 AI guidance emphasizes retained professional judgment beyond merely catching fabricated output. It also addresses confidentiality, data practices, and access. Those principles inform both the review of Cedar’s proposed route and which materials may be provided to the configured tool. They do not validate this method or a product’s performance. [1]

A good working record should make a correction travel. If engineering changes the estimate, show which proposed conclusion depended on the old date.

The repair needs its own approval

Further investigation produces a written proposal. Seller will extend support through day 180 for another $300,000. The proposal has not been accepted. Engineering also estimates $200,000 of migration spending beyond the approved budget.

Cedar’s approved model projects $4 million of first-year operating cash contribution: cash from operations before financing and income taxes, after the operating costs included in the model.

Assume both new amounts are additional first-year operating cash outflows within that measure, without overlap or capitalization or financing treatment changing the calculation. Hold revenue and all other forecast inputs constant.

$4 million − $300,000 − $200,000 = $3.5 million.

The projection falls 12.5 percent. This measures the proposed repair’s additional operating cost. It does not price a service interruption or establish the acquisition’s value. Finance needs to confirm the inputs and wider consequences.

Cedar’s investment committee gave the deal team two limits. The team may approve no more than $250,000 of aggregate additional transition and migration spending. It must return to the committee if projected first-year operating cash contribution falls below $3.6 million.

The $500,000 additional spend crosses the first limit. The $3.5 million projection crosses the second.

These are Cedar’s fictional instructions, not general legal thresholds. But the resulting governance question is concrete: the people implementing the approved investment now have a different investment case.

The repair may be worth buying.

Updating the spreadsheet does not update the approval.

California Rule 1.13 identifies the organizational client acting through authorized constituents; the client retains its business discretion. Rule 2.1 requires independent judgment and candid advice and permits consideration of relevant economic factors, without imposing a general duty to investigate every aspect of a client’s affairs. [2]

Here, counsel should put the changed economics before the authorized decision-maker. Confirm how the organization weighs Friday, continuity, and investment return. Urgency from one participant is not a substitute for those instructions.

Make the alternatives executable

Three routes deserve work.

Friday with an approved continuity plan. Establish sufficient license rights, binding support, a validated operational plan, funding, proper treatment of closing conditions, renewed investment approval, and resolution of the landlord and remaining requirements. Support through day 180 provides 30 days beyond the day-150 scenario. Engineering must assess whether that margin is adequate and whether the contracted services cover the work actually needed.

An agreed delay that preserves the transaction. Establish the contractual route, necessary seller agreement, binding funding arrangements, additional cost, and what the time will accomplish. If both the support term and migration timetable run from closing, simply moving closing shifts both clocks. The coverage gap survives. Determine which migration work can advance before closing or what other dependency the delay changes.

A different separation plan, or reconsideration of proceeding. A revised perimeter, migration sequence, or temporary arrangement requires contractual, operational, and economic support, including relevant tax or regulatory consequences. Establish termination rights and obligations before describing an exit as available.

For each route, show what Cedar gains, spends or risks, and still needs. Estimates of uncertain outcomes should have a basis and a sensitivity. An invented probability of consent adds nothing to the immediate fact that a route requiring permission cannot proceed without it.

Preparation can happen in parallel: counsel investigates license scope, finance seeks firm extension terms, and engineering validates continuity. Asking for an extension establishes information; entering a sufficient extension secures a commitment. Migration testing may both improve the estimate and advance the work. Explain what each proposed step buys.

Authority to explore those routes does not authorize accepting their prices or committing Cedar.

Put the decision on page one

I would open the committee brief this way: “I recommend against authorizing an unconditional Friday closing on the present record. Please decide whether to authorize the Friday route on the revised case: $500,000 of additional transition and migration spending and $3.5 million of projected first-year operating cash contribution. Both delegation limits require your approval.

“That authority should depend on sufficient license rights, binding support through day 180, a validated continuity plan, funding, and resolution of the landlord and remaining closing requirements. I also recommend seeking an agreed delay and financing extension now, in parallel. Authority to seek those terms would not authorize their acceptance. If Friday’s requirements cannot be completed in time, we will need further instructions under the available contractual rights.”

That gives the committee something to approve, reject, or correct. Approval of revised economics remains distinct from permission to close with unmet prerequisites.

Supporting material should identify the sources, alternatives, and uncertainties. Name who will establish license scope, validate operations, confirm funding, and communicate the decision.

Confirm that those people have accepted the assignments.

Work backward from the funding expiration through actual draw conditions, notices, and release mechanics to set the decision time. A committee approval at 4:59 p.m. may be too late to implement even while everyone’s calendar still says Friday.

Also identify what returns the matter for decision: a changed migration estimate, narrower consent, altered support terms, or additional spending. An approval needs assumptions the implementation team can recognize.

The consent arrives. Read it.

One final change: the licensor grants permission, but only through day 90. Seller still offers support through day 180.

The checklist can now say “consent received.” The operating plan remains unresolved after day 90.

The longer service commitment still lacks sufficient license coverage. Committee approval of the revised economics does not cure that problem. The team must resolve the permission’s scope or establish another workable arrangement before relying on the Friday route.

This is a useful test for an AI-assisted brief: change the consent’s duration and ask exactly which conclusions change. Then check the answer against both the sources supporting its assertions and the material restrictions it must carry forward.

For your next transaction update, choose the issue most likely to change the recommendation. State what it enables, what evidence is missing, who can establish it, and who may approve the resulting choice. Put that account before the document-by-document status report.

Talden’s public fictional commercial-review inputs offer a separate place to practice this method with a business brief, vendor agreement, and data terms. Cedar is a distinct teaching example; the public materials are not a recording of this transaction or its outcome. [3]

Before you answer whether Friday is possible, establish what must be true for Monday to work.

Sources and notes

  1. State Bar of California, Practical Guidance for the Use of Generative Artificial Intelligence in the Practice of Law (2026), pp. 3–6. Guidance on competence, retained professional judgment, confidentiality and technology use; it does not validate Cedar’s method or Talden’s performance.
  2. California Rules of Professional Conduct, Rule 1.13(a), comments [1]–[2], and Rule 2.1, comments [1]–[2]. Organizational representation through authorized constituents and independent, candid advice, including relevant nonlegal considerations.
  3. Talden, public demonstration materials. Fictional vendor-review inputs for a separate practice exercise. Cedar is a distinct teaching case. Accessed October 19, 2026.

Watch the one-minute exercise

Silent · 60 seconds

Consent Arrived. Can the Deal Close?

A fictional teaching exercise. All information is presented visually; there is no spoken audio.

Read the full video transcript
[00–08 seconds]
TALDEN
Fictional acquisition
THE WORK BEHIND THE ANSWER
THE CEDAR ACQUISITION
Consent
received.
Problem solved?
The missing software consent
has arrived.

Can the buyer close?

[08–22 seconds]
TALDEN
Fictional acquisition
THE WORK BEHIND THE ANSWER
WHAT PERMISSION MUST COVER
Written permission
is required.
For an essential service after
the business leaves the seller’s
group, including service
supplied by the seller.

[22–38 seconds]
TALDEN
Fictional acquisition
THE WORK BEHIND THE ANSWER
LOOK AT THE PERIODS
Days after closing
0
90
120
180
Written permission
90 days
Proposed seller support
180 days
Estimated migration
120 days
After day 90, the proposed support
still lacks the required
license coverage.

[38–50 seconds]
TALDEN
Fictional acquisition
THE WORK BEHIND THE ANSWER
A LONGER PROMISE IS NOT PERMISSION
A longer service
commitment cannot
supply that permission.
Approving its budget
cannot either.
The recommendation needs sufficient
rights or another workable arrangement.

[50–60 seconds]
TALDEN
Fictional acquisition
THE WORK BEHIND THE ANSWER
BEFORE YOU ANSWER
Can we close
on Friday?
Establish what
must be true for
Monday to work.

Designed fictional exhibits, not recorded Talden outputs or measured product results.

Watch the complete film

Complete narrated film · 11:31

Can We Close on Friday? Start With Monday.

By Billy Dentino. Synthetic narration with prepared fictional exhibits; not Billy’s recorded voice or a Talden product run.

Chapters and full transcript
  1. 0:00 Can we close on Friday?
  2. 0:12 Who permits Monday’s use?
  3. 0:49 Give each document its job.
  4. 1:09 A claim does not keep the service running.
  5. 1:37 The seller in the middle does not solve it.
  6. 2:06 Even permission leaves a support gap.
  7. 2:29 Keep the labels attached.
  8. 2:46 Financing expires Friday, 5 p.m.
  9. 3:06 Ask for a decision, with its support.
  10. 3:40 Review the connections.
  11. 4:00 Accurate facts can still hide the gap.
  12. 4:36 Price the proposed repair.
  13. 4:55 Before the calculation: define the measure.
  14. 5:26 A $500,000 repair. A different case.
  15. 5:44 Two separate approval triggers.
  16. 6:13 The spreadsheet does not update approval.
  17. 6:26 Whose instructions count?
  18. 6:48 Route 1: Friday, subject to prerequisites.
  19. 7:18 Route 2: an agreed delay.
  20. 7:43 Route 3: a different plan or reconsideration.
  21. 8:05 Seeking terms and accepting terms differ.
  22. 8:23 Committee opening: put the decision first.
  23. 8:50 Closing remains subject to prerequisites.
  24. 9:04 Seek terms now. Reserve acceptance.
  25. 9:24 Work backward from funding expiration.
  26. 9:54 Changed fact: consent arrives.
  27. 10:12 Day 91 still has no permission.
  28. 10:29 Trace support back. Carry restrictions forward.
  29. 11:01 Before Friday, establish Monday.
Can We Close on Friday? Start With Monday.

By Billy Dentino, retired attorney and founder of Talden Inc.
Synthetic narration with prepared fictional exhibits; not Billy’s recorded voice or a Talden product run.

[00:00:00] Can we close on Friday?

It is Wednesday. The buyer wants to close on Friday. Two consents are missing. Someone asks you to draft a waiver. Then you open the software license.

[00:00:12] Who permits Monday’s use?

Our fictional buyer, Cedar, is acquiring a logistics-software business. The business needs written permission to keep using an essential component after leaving the seller’s group. Engineering confirms the dependency. If Cedar waives a closing condition, who has given the business permission to use that software on Monday? That question changes the assignment. Cedar and every figure here are fictional. We are going to turn the packet into a decision, then change one fact to see whether the recommendation holds.

[00:00:49] Give each document its job.

The seller promised to deliver landlord and software-licensor consents. Delivery is also a condition to Cedar’s obligation to close. Cedar may waive the condition only in writing. Neither consent has arrived; no waiver is approved.

[00:01:09] A claim does not keep the service running.

The condition does not expressly release the seller’s promise. If Cedar intends to preserve a claim, express that reservation and test it against survival, releases, exclusive remedies, governing law, and the parties’ conduct. A well-worded reservation does not establish dependable recovery. And a damages claim does not keep the service running.

[00:01:37] The seller in the middle does not solve it.

Could the seller provide the software as a transition service? Our license expressly requires permission for service to a former affiliate too. Putting the seller in the middle does not solve it. The landlord issue still needs its own review: the lease requirement, the premises’ importance, and the consequences of closing without consent. One dramatic issue does not answer the other.

[00:02:06] Even permission leaves a support gap.

Now open the transition agreement. It promises ninety days of support after closing. Engineering estimates one hundred and twenty days for migration, with a separately identified one-hundred-and-fifty-day delay scenario. Even sufficient permission tomorrow would leave a support gap.

[00:02:29] Keep the labels attached.

Keep the labels attached. Ninety days is a commitment. One hundred and twenty is an estimate. One hundred and fifty is a scenario. Calling all three “deadlines” changes the evidence.

[00:02:46] Financing expires Friday, 5 p.m.

There is another clock. Financing expires at five p.m. Friday. A banker’s email says an extension is being discussed. There is no executed extension in the packet. So “let’s delay” also needs a funding answer.

[00:03:06] Ask for a decision, with its support.

This is a useful AI assignment once the lawyer has established that the materials may be supplied to the actual tool and account: “Explain whether the existing documents establish a permitted and supported operating plan from closing through migration. Identify unresolved requirements, available choices, and evidence that would change the answer. For each material proposition, supply its source, document status, qualifications, and the person who can confirm the factual premise.” Then review the connections.

[00:03:40] Review the connections.

A transition agreement’s promise of service does not supply the license permission. Engineering should confirm its current estimate and assumptions. An extended funding claim needs the operative commitment, including its conditions and expiration.

[00:04:00] Accurate facts can still hide the gap.

“Consent outstanding; support ninety days; migration one hundred and twenty” can be entirely accurate and still leave the client to discover the gap. Ask what it changes about the recommendation and for the strongest supported obstacle to the proposed route. Allow “none identified”; do not demand an invented objection. The lawyer retains professional judgment and control of strategy. California’s current AI guidance treats competence as extending beyond catching fabricated output.

[00:04:36] Price the proposed repair.

Now the seller proposes support through day one hundred and eighty for another three hundred thousand dollars. It is a written proposal, not an accepted extension. Engineering estimates two hundred thousand of migration spending beyond the approved budget.

[00:04:55] Before the calculation: define the measure.

Cedar’s approved model projects four million dollars of first-year operating cash contribution: cash from operations before financing and income taxes, after the operating costs already modeled. Assume both new costs are additional first-year operating payments, with no overlap or accounting treatment changing their inclusion. Keep revenue and every other forecast unchanged.

[00:05:26] A $500,000 repair. A different case.

The revised projection is three and a half million dollars, twelve and a half percent below the approved case. We have priced the proposed repair. We have not priced a service interruption. Have we authorized the repair?

[00:05:44] Two separate approval triggers.

Cedar’s committee delegated no more than two hundred and fifty thousand dollars of aggregate additional transition and migration spending. The team must also return if projected first-year operating cash contribution falls below three point six million. Five hundred thousand crosses the spending limit. Three and a half million crosses the cash threshold.

[00:06:13] The spreadsheet does not update approval.

Those are this fictional committee’s instructions. The revised deal may still be attractive. The existing delegation does not authorize the team to substitute it. Updating the spreadsheet does not update the approval.

[00:06:26] Whose instructions count?

For organizational counsel, the client acts through authorized people. The engagement and governance arrangements establish whose instructions count. Here, the committee must decide; counsel supplies advice, not the client’s investment decision. There are three routes to examine.

[00:06:48] Route 1: Friday, subject to prerequisites.

Friday with a permitted, supported operating plan and renewed approval. That requires sufficient license rights, binding support, validated continuity, funding, and resolution of the landlord and remaining closing requirements. Support through day one hundred and eighty leaves thirty days beyond the delay scenario. Ask engineering whether that margin and the service scope are sufficient.

[00:07:18] Route 2: an agreed delay.

An agreed delay. Establish the contractual route, required seller agreement, and binding financing. Ask what migration work can advance before closing. If both timetables run from closing, delay moves both clocks and preserves the gap. Identify what the extra time actually buys.

[00:07:43] Route 3: a different plan or reconsideration.

Or a different separation plan, or reconsideration. Establish feasibility and examine affected contracts, economics, and relevant tax or regulatory consequences. Termination belongs among the choices only if the actual rights and obligations support it.

[00:08:05] Seeking terms and accepting terms differ.

Seek financing terms, resolve license questions, and validate the operating plan in parallel. Seeking terms supplies information. Accepting them creates a commitment. Keep those authorizations separate.

[00:08:23] Committee opening: put the decision first.

Here is the committee opening I would use: “I recommend against an unconditional Friday closing on this record. Please decide whether to approve the revised case: five hundred thousand dollars of additional spending and three and a half million of projected first-year operating cash contribution. Both delegation thresholds require your approval.

[00:08:50] Closing remains subject to prerequisites.

Closing would remain subject to sufficient license rights, binding support through day one hundred and eighty, validated continuity, funding, and the landlord and other closing requirements.

[00:09:04] Seek terms now. Reserve acceptance.

I also recommend seeking an agreed delay and financing extension now. Authority to seek terms would not authorize accepting them. If Friday’s requirements cannot be completed, we need further instructions under the available contractual rights.” The client can now approve, reject, or correct something concrete.

[00:09:24] Work backward from funding expiration.

Confirm who will establish each missing fact and who may authorize the resulting action. A name typed beside a task does not establish acceptance. Work backward from five p.m. using the lender’s draw conditions, notices, and release mechanics. Four fifty-nine may be too late to implement an approval. Record the scope of the decision and what changes require another review.

[00:09:54] Changed fact: consent arrives.

Now the consent arrives. Permission lasts only through day ninety. The seller still offers support through day one hundred and eighty. Does the green tick beside “consent received” solve the problem?

[00:10:12] Day 91 still has no permission.

After day ninety, the proposed support still lacks the necessary license coverage. Sufficient rights remain a condition of our proposed approval. An approved budget does not cure the missing permission.

[00:10:29] Trace support back. Carry restrictions forward.

That is the final review test. Can the brief identify the restriction, connect it to the plan, and distinguish a proposed fix from an agreed change? Trace each assertion back to its support and each material restriction forward into the recommendation. For your next transaction update, put the issue most likely to change the recommendation at the front: what it enables, what evidence is missing, who can establish it, and who may decide.

[00:11:01] Before Friday, establish Monday.

This film is by Billy Dentino, a retired attorney and founder of Talden. For a separate exercise, the fictional vendor-review inputs at Talden A I dot com slash demo include a client brief and contract materials. Begin with the decision the client needs to make. Before you answer whether Friday is possible, establish what must be true for Monday to work.

Fictional teaching examples, not measured Talden product results. See the companion essay for the complete discussion, sources and qualifications.

Put the questions to work

Bring the documents. Keep the judgment.

Explore Talden’s fictional matter materials, then see how its workflows fit your own work.

Explore the fictional examples

Start your free trial

Review current pricing and trial terms

Privacy choices

Categories

You can change these choices at any time through Privacy choices.