District Court makes further website payment conditional on fixing outstanding issues

The District Court ruled on October 10, 2026, that Grant Bell need not make further payment for a workshop-booking website until Nell Avery resolves its outstanding issues. Presiding judge Brock directed that Bell pay once the agreement is fulfilled, with completion to come at no additional cost. Avery had sought $11,400 in unpaid contract charges, plus allowable filing costs.

The dispute turned on whether permission to launch a site ahead of a registration deadline meant the customer had accepted it as complete. Brock found that Bell had not agreed the website was a finished product. The judgment makes payment conditional on completion rather than eliminating the payment obligation.

Brock's brief reasons rested on the outstanding issues and the absence of Bell's agreement that the site was finished. The judgment did not expressly determine whether the contract's written-acceptance condition had been satisfied or explain how each item of evidence affected the outcome.

The record nevertheless exposed the distinction between passing demonstrations and delivering reliably functioning services. Avery described an April 24 export recording six paid test bookings and six confirmation messages sent, including two mobile sessions. She acknowledged that these controlled tests did not establish inbox delivery or exclude intermittent problems.

Bell described customer reports of checkout difficulties and a missing confirmation on April 26, alongside two unsuccessful booking attempts recorded that day. Those reports preceded his April 27 payment-setting change, although he acknowledged that the available records did not diagnose the failures or establish that Avery caused every later problem.

Avery said the $24,000 development agreement left $9,600 unpaid after $14,400 in development payments. She relied on the successful demonstrations and launch authorization, while acknowledging reports of intermittent confirmation and mobile-checkout problems.

She also sought $1,800 for a multiple-workshop checkout feature. Although there was no signed change order, she argued that Bell's email instruction and use of the feature showed agreement. She maintained that genuine defects had to be distinguished from additional requests.

Bell said he authorized launch to meet the registration deadline, not to accept unfinished work. He maintained that mobile booking and confirmation emails were promised functions, and that the single-checkout request clarified the original scope rather than authorizing an extra fee. He sought a repair offset based on a replacement developer's $4,200 invoice, but conceded that some invoiced work covered redesign and reporting features rather than repairs.

Avery described the signed March 3 agreement as requiring written acceptance before the final installment, identification of material defects within five business days of delivery, and a written description and agreed price for changes. Her printed launch email did not include its attachment; Bell said that attachment listed missing confirmations and a mobile checkout error.

The judgment leaves important financial details unresolved. It does not specify the “additional amount” payable, separately dispose of the $1,800 charge, quantify any repair offset, or address filing costs. Its recorded direction is narrower: outstanding issues must be resolved without additional cost before further payment becomes due.